IETF Logo Mail Archive

Re: draft-ietf-6man-segment-routing-header-26 violating RFC4291, IPv6 Addressing Architecture?

"Darren Dukes (ddukes)" <ddukes@cisco.com> Tue, 10 March 2020 16:07 UTC

Return-Path: <ddukes@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3DF83A158D for <ipv6@ietfa.amsl.com>; Tue, 10 Mar 2020 09:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.599
X-Spam-Level:
X-Spam-Status: No, score=-9.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=mh74eWa7; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=eRNYpcDm
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MhR2ipfY1VVQ for <ipv6@ietfa.amsl.com>; Tue, 10 Mar 2020 09:07:01 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 173173A14DE for <ipv6@ietf.org>; Tue, 10 Mar 2020 09:07:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3815; q=dns/txt; s=iport; t=1583856421; x=1585066021; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=jaMlc7lp+b532d9+ZlTEElKnTwwjGvWF3KTPIZgNQ/Q=; b=mh74eWa7iYzcUtVDfpK24JnWcXFrofkQFZFYlYWOtI7zc+ApEBaYN6bw E5OiC0DGQwKVQ2aOxYEAPLW8lN+AhzZZMkQTE72bqpcwWRisYY0YBGpY9 Mz20uLX9mP/IQrjEE/R49X5nEfcDXI8sRVdi5vJzxqVzyJ8QuWLnJzztN M=;
IronPort-PHdr: 9a23:Us/K6hJRYX95zKfbmNmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeCtKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUgMdz8AfngguGsmAXEH3Mf3ndAQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0APCABGumde/5pdJa1mHQEBAQkBEQUFAYF7gVRQBWxYIAQLKgqEC4NFA4pxgl+TM4RiglIDVAkBAQEMAQEjCgIEAQGEQwIXgW8kOBMCAwEBCwEBBQEBAQIBBQRthVYMhWQBAQECARIRHQEBNwEECwIBCAQOLQMCAgIwFAMOAgQOBSKDBAGBfU0DDiABDp5jAoE5iGJ1gTKCfwEBBYEvAYNaGIIMAwaBOIwsGoFBP4E4IIJNPoEEgWACgVM/gmQygiyQbIVymVAKgjyHVI8WHYJKiCSQTJd2klUCBAIEBQIOAQEFgWkigVhwFWUBgkFQGA2OHRgggzuFFIVBdIEpjEcBgQ8BAQ
X-IronPort-AV: E=Sophos;i="5.70,537,1574121600"; d="scan'208,217";a="457224264"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 Mar 2020 16:07:00 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 02AG70Y8006906 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 10 Mar 2020 16:07:00 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 10 Mar 2020 11:06:59 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 10 Mar 2020 12:06:59 -0400
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 10 Mar 2020 11:06:58 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ffhXtzkQ5FuJbG7Lvq4qccdri/L4i8zo+OEWpzO42OZlSvOfjjQTTbxD0OMlx9GA13HQdBTjp+K9xU913TyhiXOLDr8+Wp2wILCaleZQ4NxHR5oAe7Jhei6KsCvmZZuVpitWtJdbo/mjxEyoBPipVouXMMFA2HXJKb8Q4ZUgMjjrKGqhCxvVXZTvjjwbsi1bYJjkO1qTyqG3Um2Oy+GkASNHzDvE3FUfKji0wnolbUzpKzJmvmnPXTMQHWkAgVa0whgQ4HfDV3ORgyoIL2XeYF0lSsVVVfo6WJFReySWYwrDuePpdY6DjfLbp8rkItjsQhO7mE9Ob0Cnw2vbWarDbg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;bh=jaMlc7lp+b532d9+ZlTEElKnTwwjGvWF3KTPIZgNQ/Q=; b=Vw13xpjOmNHfv+NpRGnK4UuD9PxZEJtfdOd0Ad17CJJ/HnRl6qnLf5nRLrA2aSpwFcqXrNthhMf2fi2pVrXbxbfM54MALmsLFBk+83D3yRrt7LTb+E7LXRrIh0qU8mPCPBezG3bZ9JPXsj5tcyib9O2eLFHa/jnLTJItI9g2HMeAtwVn8/Jrag2pWPg26ilHTqDKu04Bw2E0PlKcvkHfgQ+eGG7YjaN8MKzNPq7/aN5BaLJmPh/hBibibSCXYwQkTMJDzljNVlfYFfvQLf81icshK10cXme+SGm5AXl8pj6f2mhLO05sDGSJhg8/neDPlf7gJjdbj5V5Hb4X3V2DNQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jaMlc7lp+b532d9+ZlTEElKnTwwjGvWF3KTPIZgNQ/Q=; b=eRNYpcDmfSjhxvzR5LgZRfsomR1/Xhg9HiubkJ9Zv9Rr5er2pAFFuTtu2cpNw4pujvOXp2O42rbzJkj3QIjE9nZbIIgTmqwQUvIOseYPz+Lfsm9UzV/Iy4UbMlSkGM98T5nv2WSpmikAlt3PakoaaPaj6Tc+TbtVhviFCWMhr/U=
Received: from DM5PR11MB1818.namprd11.prod.outlook.com (2603:10b6:3:114::9) by DM5PR11MB1370.namprd11.prod.outlook.com (2603:10b6:3:9::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2793.17; Tue, 10 Mar 2020 16:06:58 +0000
Received: from DM5PR11MB1818.namprd11.prod.outlook.com ([fe80::4d47:30fc:1b10:3db8]) by DM5PR11MB1818.namprd11.prod.outlook.com ([fe80::4d47:30fc:1b10:3db8%12]) with mapi id 15.20.2793.013; Tue, 10 Mar 2020 16:06:58 +0000
From: "Darren Dukes (ddukes)" <ddukes@cisco.com>
To: Andrew Alston <Andrew.Alston@liquidtelecom.com>
CC: Mark Smith <markzzzsmith@gmail.com>, 6man WG <ipv6@ietf.org>
Subject: Re: draft-ietf-6man-segment-routing-header-26 violating RFC4291, IPv6 Addressing Architecture?
Thread-Topic: draft-ietf-6man-segment-routing-header-26 violating RFC4291, IPv6 Addressing Architecture?
Thread-Index: AQHV9DEtyssIk3xONkKzJ07M0HVK4KhAVaOAgABQ6oCAAVzpgA==
Date: Tue, 10 Mar 2020 16:06:58 +0000
Message-ID: <4A42505B-7D4C-43F7-B8DA-3F3CA60C44D4@cisco.com>
References: <CAO42Z2xKWYB4F5Fd735E8xTL+KLZBVO73FjKyVqj8fy2uJkNsg@mail.gmail.com> <226A1DDB-2BF9-4F55-81A0-277E4FBB352A@cisco.com> <DBBPR03MB54157EAC694BA9C88340C686EEFE0@DBBPR03MB5415.eurprd03.prod.outlook.com>
In-Reply-To: <DBBPR03MB54157EAC694BA9C88340C686EEFE0@DBBPR03MB5415.eurprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ddukes@cisco.com;
x-originating-ip: [161.44.212.149]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: bf00385d-4dfe-4be7-d2c4-08d7c50d0f8b
x-ms-traffictypediagnostic: DM5PR11MB1370:
x-microsoft-antispam-prvs: <DM5PR11MB1370D5ECB0C383A9E29CA5AEC8FF0@DM5PR11MB1370.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 033857D0BD
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(366004)(396003)(136003)(376002)(39860400002)(199004)(189003)(5660300002)(26005)(186003)(66446008)(66476007)(64756008)(66946007)(66556008)(91956017)(6486002)(6506007)(6512007)(53546011)(6916009)(478600001)(966005)(76116006)(4326008)(81156014)(54906003)(33656002)(86362001)(316002)(36756003)(4744005)(81166006)(71200400001)(2906002)(2616005)(8676002)(8936002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1370; H:DM5PR11MB1818.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 2UySEJX0NlnX3BNfkb8Knap0zB1pC8N/XKxAyDHbtIoPG0GXplKW7bOsTpAagfE2hISH1OxF2mjMXWyTRIp2qEkRS8d4eePntWIswgck3Z2QoyIOeE+QGhGd0RvqIneTf6uEQYaL6vdwaapXUIP5mXqt5bsRFOfSPYrpS1u8s/sE08ypXYJu/s9o3cskdvWxnV1HrG3i4X1CAsa0pLv3vjDHvv3AnBbxB6LPVF/70Se/7bY2LniA30KYIcx0zQsqICLjW7cvPD5lGcg1WYNatUSUB87Rmys2GcDfke9+wlvckev6Dzmd8boqHLMSWWmn+swM7MUhUiBCWA5rle/ekFgMB+qT6O9ddB5KuTfrcq9CHdtimRI/revtR5sIjreQ4BUDLOZoG6nirJ32RmobzJU3LviQ8JJG8mMdXND2dE2+YYErfKItCVqAJDLy/5fc15VrY/ltBDhy2fRzBFzdlSENq40L+2piZs3wpLUQAexsvWOIzhDFnRYBiBVG/UIXVLj296Hs2bxFM6w1SIujwA==
x-ms-exchange-antispam-messagedata: 0JaxZ56SSy1NWSuNtXf5dyHov/j1ZVjMBA5zut1eIeZr7jX2yr01HumVSiM4YwgY0NDIk3JVd9MbiZb6H4r8lii/Z4N+V5FlPrZGfiX4nKTEWY4LzYaKErnKO6uSNtP9F0+lyW6iZ3kqc/F2zKG2sQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_4A42505B7D4C43F7B8DA3F3CA60C44D4ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: bf00385d-4dfe-4be7-d2c4-08d7c50d0f8b
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Mar 2020 16:06:58.0433 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: SLNLz8+mPkTeTrOJdefVoB6iDiIz/ZoFFS7fQGMicba4aciR1Ml+uzeFffD+rYOwBqomCi8+eLckEqPp8BoFTQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1370
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/OnhcjZyEsGEqQ_te28raX80wPiE>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Mar 2020 16:07:10 -0000

Hi Andrew please see issue #66 for the closure record.

https://trac.ietf.org/trac/6man/ticket/66

Darren

On Mar 9, 2020, at 3:18 PM, Andrew Alston <Andrew.Alston@liquidtelecom.com<mailto:Andrew.Alston@liquidtelecom.com>> wrote:

Hi Darren

>  Hi Mark, the working group discussed the
 > association with RFC4291 and closed it with
 > the text in the document.

Can we get a reference to these discussions please - would just be useful to back and refresh memories and wasn’t able to find them

Thanks

Andrew

v2.23.0 | Report a Bug | By Email