IETF Logo Mail Archive

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

"Darren Dukes (ddukes)" <ddukes@cisco.com> Wed, 11 March 2020 19:03 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 B3C4C3A00E1 for <ipv6@ietfa.amsl.com>; Wed, 11 Mar 2020 12:03:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.499
X-Spam-Level:
X-Spam-Status: No, score=-9.499 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, HTTPS_HTTP_MISMATCH=0.1, 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=dFqQgbu+; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=h/t46a6f
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 iJHIB5L4viwD for <ipv6@ietfa.amsl.com>; Wed, 11 Mar 2020 12:03:07 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3279C3A0031 for <ipv6@ietf.org>; Wed, 11 Mar 2020 12:03:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14717; q=dns/txt; s=iport; t=1583953387; x=1585162987; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=MJAsvCXHBtYMtSSK15Rl9BsHDM8Pr6PEyDuiO/hjBWw=; b=dFqQgbu+JqPNgzfFMh6gNT46xrrhdHIlwFkUqaCTYEmMiazX85S24Wwx bEw5miUppJLeQjxyPbKGgUguGHRArmAaSUYllJmyJHVOCvjZz+G+YzXfJ AuVb4KZXlHmmlE3j5yxBGZUlyvqumpdrh0Z4802azdgczCQ8ggWmitZG2 k=;
IronPort-PHdr: 9a23:/XYlrx/3HYLSTP9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+/bR7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUERoMiMEYhQslVcKJFE72N9bhbjcxG4JJU1o2t3w=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CQBwANNWle/4oNJK1mHAEBAQEBBwEBEQEEBAEBgXuBJS9QBWxYIAQLKgqEC4NFA4ptgjolkzOEYoJSA1QJAQEBDAEBHg8CBAEBgw2BNgIXgXYkOBMCAwEBCwEBBQEBAQIBBQRthVYMhWMBAQEBAgESER0BATcBBAsCAQgRAQMBASgDAgICMBQDBggCBA4FIoMEAYF9TQMOIAEOoB8CgTmIYnWBMoJ/AQEFgS8Bg3UYggwDBoE4jCwagUE/gTgMFIJNPoEEgWACAoFRKRYJglsygiyQa4VzmVQKgjyHVY8WHYJKiCSQTJd6klYCBAIEBQIOAQEFgWkigVhwFWUBgkFQGA2NeSQMDAsVgzuFFIVBdAKBJ4wlAYEPAQE
X-IronPort-AV: E=Sophos;i="5.70,541,1574121600"; d="scan'208,217";a="469990169"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Mar 2020 19:03:06 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by alln-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id 02BJ36CQ009027 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 11 Mar 2020 19:03:06 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 11 Mar 2020 14:03:06 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 11 Mar 2020 14:03:05 -0500
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 11 Mar 2020 15:03:05 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=a8Wplt8T3bDelHkEwcN4gqXABZcTZts/9SpH8OpBlX1i7XOLsbLWoaivYcsglfE9GRfHpMI2SM36SIkMhp0ihL4/UTapwsQcwU7j3UAEew3vWaT5z8s92ANgh197EBQZoUGfI9dCXDfSOVA3+JoreZQqPzdKmOaocv6qSccE1iUi8JB8Cq5s0REHX5PYlM5HqKj/svBlzvhvgI8RbcZteMZeqR5cWU3a6lj1WIeC45+PePlsPokszx61QQUgqcuy7Bjbw0++j05fkxbXAhe+vvpHLicP5tzH5xzQ1DTO6fA5VChX2B77s4o7IjYmAMMmgLxb+6HTHhCR9OawEP+M2Q==
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=MJAsvCXHBtYMtSSK15Rl9BsHDM8Pr6PEyDuiO/hjBWw=; b=NIrJjJbptc4JlGuK/IwHipzito6Bj+bVTsToDh08yw55IQQsvz1GxMkd7h7zMQ3vT21qX+G3NtZCsovIHTCjpf1StdJhXG3vaQQ2vaux9EktDQRB/IiumnhpwTmhY4K0IAWzL+lZKIMsFH+kIROHMR7UNZArh4vfH46hVTmHad7oX0edtm7dgZVwbZ2gEfquQ9TxtwqU5eg4aok8VAaS4aLwJkj73EIkd0DZKEMMv1YEH4v2traNNgnaTjZE2ZPBmhWNNyFhRPmzGgHJcfUQCVgVoGGkvq7hUjH/1ZkDljpyngKgBjZuw8Z2XOhJiETJdGXukU8r1xFHFU69N1REnQ==
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=MJAsvCXHBtYMtSSK15Rl9BsHDM8Pr6PEyDuiO/hjBWw=; b=h/t46a6f0V86q7do8SiTlZit8S8WMXC2J29z6idWG9rg/ZDN3sMaxi6LwUlu9JYLJpE2dxXGvjR+6G/YckuhfvFtqQhggz9dS5NNpcsKy+AIf8ZJJqwcx251Y+aJUhfhlgVNIJSy9KQD0UIkDhy+gDVfOgDWMb3pz0AK4i/KSXU=
Received: from DM5PR11MB1818.namprd11.prod.outlook.com (2603:10b6:3:114::9) by DM5PR11MB1273.namprd11.prod.outlook.com (2603:10b6:3:f::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2793.17; Wed, 11 Mar 2020 19:03:04 +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.018; Wed, 11 Mar 2020 19:03:04 +0000
From: "Darren Dukes (ddukes)" <ddukes@cisco.com>
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
CC: "EXT-Andrew.Alston@liquidtelecom.com" <Andrew.Alston@liquidtelecom.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: AQHV9DEtyssIk3xONkKzJ07M0HVK4KhAVaOAgABQ6oCAAVzpgIABwUqAgAACQAA=
Date: Wed, 11 Mar 2020 19:03:04 +0000
Message-ID: <F0C3B5BE-EF62-49CE-8693-A578AEED4B7F@cisco.com>
References: <CAO42Z2xKWYB4F5Fd735E8xTL+KLZBVO73FjKyVqj8fy2uJkNsg@mail.gmail.com> <226A1DDB-2BF9-4F55-81A0-277E4FBB352A@cisco.com> <DBBPR03MB54157EAC694BA9C88340C686EEFE0@DBBPR03MB5415.eurprd03.prod.outlook.com> <4A42505B-7D4C-43F7-B8DA-3F3CA60C44D4@cisco.com> <DM6PR05MB63482EC9156C7E1155A1F658AEFC0@DM6PR05MB6348.namprd05.prod.outlook.com>
In-Reply-To: <DM6PR05MB63482EC9156C7E1155A1F658AEFC0@DM6PR05MB6348.namprd05.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: [173.38.117.66]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 21b2de70-de2f-44f7-bd41-08d7c5eed42c
x-ms-traffictypediagnostic: DM5PR11MB1273:
x-microsoft-antispam-prvs: <DM5PR11MB12735F61C4869C5716192721C8FC0@DM5PR11MB1273.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0339F89554
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(376002)(136003)(396003)(366004)(39860400002)(199004)(64756008)(66446008)(66556008)(66476007)(66946007)(76116006)(91956017)(86362001)(2616005)(2906002)(81166006)(54906003)(81156014)(8676002)(5660300002)(8936002)(966005)(478600001)(316002)(6512007)(6486002)(6506007)(4326008)(186003)(33656002)(53546011)(71200400001)(36756003)(26005); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1273; H:DM5PR11MB1818.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A: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: hv+TaoaNHyKy1cVu5LjFMcFUzsXbrKsTA0a+fj+q1rKtdQiYskLNeWvuVCAPTBtzYldKP8R55svIkuPx5PiAuQrEbiI7DypGARbCrXEWqgwndz5y1UgrmRwcZUWqAZz96NQdoA0MrSnv1O6ZNqolOdLNuo0NXPVhIO5aRQLP8DcOVnmZAdf7HBkWH2ASKoS6TUfHxzRe/gQBp/UqVhzwjl2FuoZRTJ29pS91AxoXxomnL0edC6MFZxtlqJ44lrtPExgIFPNLBnGcIwTuKpy4416O3LAXHf101jF8ZocO4NFyt8A17fqjLWOXXc+IxsUGXAQtz7CH3Z6jovV+eOLLuP24xiJvMX3QVLuGUs6wyN4G5/BfjC1CXMNCgkkqzBXDmKd3swyLccSjfg38vc2095FFKsQeqwVAnZQjMCSg2/F8ZKuWcfj9cWWnxNZa4nl9Eixf5cwwtI2HTlvKXmF4Fo5hUJAIm3Js5Dvd/DGB8YL11XSw4EB2z/MdTudGJ3Tk8goGWR1vDQnqPai8zGIVxQ==
x-ms-exchange-antispam-messagedata: j2NHxw3ZMzh+FRoHNtXm9dBemK7PiMS5WRXTVTOJFao2/iFj6bhjqCrSEpKnHMmyd5WrxYoi88y6gyJapCUBbnhUIYu1g2gQ6hbM81V1lN8ijwhdlwhGufxBTVip2AElxT6xOU4bftXiw6ZXRqbQLA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_F0C3B5BEEF6249CE8693A578AEED4B7Fciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 21b2de70-de2f-44f7-bd41-08d7c5eed42c
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Mar 2020 19:03:04.7295 (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: PmhSqLNvrPWO0sCImtCmGMiyp1i8OkFO3B4ngsHU5wdBFBBoP0f6VtxS9LPBty5jQRuH4SZliHJNaS7mFaj7rw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1273
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.14, xch-rcd-004.cisco.com
X-Outbound-Node: alln-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/_kWSHS_CRTxDSm3FyAX0TIjv8F0>
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: Wed, 11 Mar 2020 19:03:17 -0000

Hi Ron, I made no comment in this thread on draft-ietf-spring-network-programming.

Darren

On Mar 11, 2020, at 2:55 PM, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org<mailto:rbonica=40juniper.net@dmarc.ietf.org>> wrote:

Darren,

Didn’t we agree to close issue 66 because draft-ietf-6man-segment-routing header contains no text regarding SID/IPv6 address semantics. If that’s the case, how can you say that closing issue 66 implies WG consensus around SID/IPv6 address semantic proposed in draft-ietf-6man-network-programming?

                                                                                       Ron



Juniper Business Use Only
From: ipv6 <ipv6-bounces@ietf.org<mailto:ipv6-bounces@ietf.org>> On Behalf Of Darren Dukes (ddukes)
Sent: Tuesday, March 10, 2020 12:07 PM
To: EXT-Andrew.Alston@liquidtelecom.com<mailto:EXT-Andrew.Alston@liquidtelecom.com> <Andrew.Alston@liquidtelecom.com<mailto:Andrew.Alston@liquidtelecom.com>>
Cc: 6man WG <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Subject: Re: draft-ietf-6man-segment-routing-header-26 violating RFC4291, IPv6 Addressing Architecture?

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

https://trac.ietf.org/trac/6man/ticket/66<https://urldefense.com/v3/__https:/trac.ietf.org/trac/6man/ticket/66__;!!NEt6yMaO-gk!RN-QFuaCraX6vU74Vusek5FlDyBGgfC2Teh1Vz40nw0PBhWdPtA-SA3t_rxaFg4_$>

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