Re: [Idr] Regd BGP-LS code points early allocation for WG adopted drafts
"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Thu, 28 September 2017 17:17 UTC
Return-Path: <ginsberg@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18309126BF3; Thu, 28 Sep 2017 10:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Level:
X-Spam-Status: No, score=-14.519 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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
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 xDfxDdvu_KrD; Thu, 28 Sep 2017 10:17:10 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52271134293; Thu, 28 Sep 2017 10:17:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=62030; q=dns/txt; s=iport; t=1506619030; x=1507828630; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=o6bB2EX0yuvvRgwfcptoE5OjrTK7BraQatsNwIXDGgo=; b=T865GItVMtowmp15EUlfTwEQueF7e058xnl0u61rTgu+RxquVqTTn7/9 7I9sKnAoWtie0O2W/RMoD+HXErFHACHjAwhwMpxheCoGoCDsX6kRmTxDN eqh4eaMbrIq6i4RCCQTWyisPWwSxfDbqSQejD3Ig2MsCjHqRN57CKsZED 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C2AQBfLc1Z/5BdJa1TChkBAQEBAQEBAQEBAQcBAQEBAYJvQC1kbicHg3GZfYF2eYdJjXeCBAolhRYCGoQLVwECAQEBAQECayiFGAEBAQEDIwo+DhACAQgRAwEBASEBBgMCAgIfERQJCAIEAQ0FCIlFTAMVEKcYgicnhxMNg0sBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYMrggKBUYFpAYJzNYJegXMBBwsBBy8JBhCCXYJgBYoShyuHFIgbPAKHXIgJhHCCHIVuiwWMbIg0AhEZAYE4AVeBAwt4FUmFGhyBZ3aGUIEkgRABAQE
X-IronPort-AV: E=Sophos; i="5.42,450,1500940800"; d="scan'208,217"; a="10037961"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Sep 2017 17:17:09 +0000
Received: from XCH-ALN-009.cisco.com (xch-aln-009.cisco.com [173.36.7.19]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id v8SHH9Qa017124 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 28 Sep 2017 17:17:09 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-009.cisco.com (173.36.7.19) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 28 Sep 2017 12:17:08 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1320.000; Thu, 28 Sep 2017 12:17:08 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>, Susan Hares <shares@ndzh.com>, 'Jeff Tantsura' <jefftant.ietf@gmail.com>, "draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org" <draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org>
CC: 'idr wg' <idr@ietf.org>, 'Stefano Previdi' <stefano@previdi.net>, "Acee Lindem (acee)" <acee@cisco.com>
Thread-Topic: [Idr] Regd BGP-LS code points early allocation for WG adopted drafts
Thread-Index: AdL7nWosFbh13zxaTe29YgdiZl93UQB+CRWAAADnRIAAAWQjgAAAEggABAKqdHABxCZKYAjRO8mgAA6WzIAAFl+2gAAKZmcQAA/1x7A=
Date: Thu, 28 Sep 2017 17:17:08 +0000
Message-ID: <584f916c4ceb48deb011ec5d53ea379a@XCH-ALN-001.cisco.com>
References: <999f002984de432bb168f60309d66b63@XCH-ALN-008.cisco.com> <EAC48055-71DF-4DC2-841C-D4C6C0102276@juniper.net> <7DCAAFA1-1E14-4374-834B-4E6FB174ACFE@gmail.com> <CACWOCC8f=h5Zu_Cf2WE0KGz5RnHXSZuuB-6K-4UL0c7_XCbeuQ@mail.gmail.com> <37805F15-E265-4C37-B491-2BCBABD29D2D@gmail.com> <f4289b163f99483b8777d0071116cc85@XCH-ALN-008.cisco.com> <5ddccfb5e75f47d39676b90a3f5364c5@XCH-ALN-001.cisco.com> <68fa61de24984dcd9b03a81ba24c1b8a@XCH-ALN-008.cisco.com> <01d101d3380f$a97be3d0$fc73ab70$@ndzh.com> <018501d33869$28312fb0$78938f10$@ndzh.com> <1877ebbe206648dabdff5bf07d94e9c6@XCH-ALN-008.cisco.com>
In-Reply-To: <1877ebbe206648dabdff5bf07d94e9c6@XCH-ALN-008.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.199.16]
Content-Type: multipart/alternative; boundary="_000_584f916c4ceb48deb011ec5d53ea379aXCHALN001ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/NYgJZylh2YZYctr1MlfxDNVuDcQ>
Subject: Re: [Idr] Regd BGP-LS code points early allocation for WG adopted drafts
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Sep 2017 17:17:14 -0000
Sue – I also am confused. The thread you included below is – as Ketan states – about a common registry for defining MSD types. What Ketan is asking for is early allocation of BGP-LS code points for advertising the MSD types in BGP-LS. These are not the same thing and I see no reason why early allocation of the BGP-LS codepoints should be blocked by the final disposition of the MSD registry. Given that the MSD registry will be a NEW registry (in whatever location), there will be no early allocation for those codepoints because there is no existing usage to create potential conflicts. So we should be able to go full speed ahead with BGP-LS early allocation. ??? Les From: Ketan Talaulikar (ketant) Sent: Thursday, September 28, 2017 8:00 AM To: Susan Hares; 'Jeff Tantsura'; draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org Cc: 'idr wg'; 'Stefano Previdi'; Acee Lindem (acee); Les Ginsberg (ginsberg) Subject: RE: [Idr] Regd BGP-LS code points early allocation for WG adopted drafts Hi Susan, Thanks for sharing this and I do remember this discussion. But I thought this proposed registry was about MSD sub-types which we wanted to share across the protocols. The early allocation in question on this thread is the BGP-LS code points for the Node and Link MSD attributes. These come from within BGP-LS registry. The corresponding code-points in OSPF and ISIS have already got through the early allocation process after those drafts became WG items. While we do want to close on the common registry for the MSD sub-types at the earliest, does the WG want to gate the BGP-LS code points early allocation for this? Thanks, Ketan From: Susan Hares [mailto:shares@ndzh.com] Sent: 28 September 2017 20:21 To: Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>; 'Jeff Tantsura' <jefftant.ietf@gmail.com<mailto:jefftant.ietf@gmail.com>>; draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org<mailto:draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org> Cc: 'idr wg' <idr@ietf.org<mailto:idr@ietf.org>>; 'Stefano Previdi' <stefano@previdi.net<mailto:stefano@previdi.net>> Subject: RE: [Idr] Regd BGP-LS code points early allocation for WG adopted drafts Ketan and Jeff: After looking at my email and notes on this, I found that I had put this on pause because of Acee’s note with the following information on September 3rd (I’ve reformatted Acce’s 9/3 note for consumption). The following email chain left me awaiting a draft describing the registry. Is there a document I should review or put before the IDR WG in addition to draft-ietf-idr-bgp-ls-segment-routing-msd? Susan Hares PS - Normally, I do not do WG calls on Early adoptions during August because for 8 years the response has been terrible and then the AD (Alvaro) or the IESG asks me if there is support. Getting this response on the 3rd of September slowed down the progress. I apologize for the delay. I should have actively pushed to get a resolution of the msd registry. ============= (This has been informally discussed in the past with some of the folks on this thread – but wanted to present this more formally as the set of drafts matures.) IS-IS/OSPF/IDR WG Chairs – The authors of: draft-ietf-isis-segment-routing-msd draft-ietf-ospf-segment-routing-msd draft-ietf-idr-bgp-ls-segment-routing-msd would like to highlight the point that we wish to create a shared protocol independent registry for defining the MSD types which will be advertised as described in the three drafts mentioned above. We think having a single common registry will make it easier to maintain the consistency of additional MSD types when/if they are added in the future. The description of the new registry is most accurately described in the IANA section of draft-ietf-isis-segment-routing-msd: <snip> This document requests the creation of a new IANA managed registry to identify MSD types as proposed in Section 3, Section 4. The registration procedure is "Expert Review" as defined in [RFC5226]. Suggested registry name is "MSD Sub-types". Types are an unsigned 8 bit number. The following values are defined by this document Value Name Reference 0 Reserved This document 1 Base MSD This document 2-250 Unassigned This document 251-254 Experimental This document 255 Reserved This document Figure 4: MSD Sub-type Codepoints Registry <end snip> If any of you have concerns or suggestions regarding this plan we (the set of authors) welcome your input. Les (on behalf of all the authors) From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares Sent: Thursday, September 28, 2017 12:10 AM To: 'Ketan Talaulikar (ketant)'; 'Jeff Tantsura'; draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org<mailto:draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org> Cc: 'idr wg'; 'Stefano Previdi' Subject: Re: [Idr] Regd BGP-LS code points early allocation for WG adopted drafts Ketan: I will work on expediting this in the morning (ET (eastern US)). Sue Hares IDR WG Chair From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Ketan Talaulikar (ketant) Sent: Wednesday, September 27, 2017 10:21 PM To: Jeff Tantsura; draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org<mailto:draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org> Cc: idr wg; Stefano Previdi; Susan Hares Subject: Re: [Idr] Regd BGP-LS code points early allocation for WG adopted drafts Hi Jeff/Authors, Can we know the status of the IANA allocation process for early allocation of the code points for draft-ietf-idr-bgp-ls-segment-routing-msd? Can we please expedite this? The other two drafts mentioned in this email thread have got the code points allocated already. Also, the latest versions have removed the code point “suggestions” based on the discussions on this matter on the WG email list here AND at the past IETF. It would be great though if we could get the same code points as below from IANA, if they are still available. https://tools.ietf.org/html/draft-tantsura-idr-bgp-ls-segment-routing-msd-02 Node MSD : 1050 Link MSD : 1110 Thanks, Ketan From: Les Ginsberg (ginsberg) Sent: 14 August 2017 10:34 To: Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>; Jeff Tantsura <jefftant.ietf@gmail.com<mailto:jefftant.ietf@gmail.com>>; Job Snijders <job@instituut.net<mailto:job@instituut.net>>; John G. Scudder <jgs@juniper.net<mailto:jgs@juniper.net>> Cc: Stefano Previdi <stefano@previdi.net<mailto:stefano@previdi.net>>; Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>; draft-ietf-idr-bgp-ls-segment-routing-ext@ietf.org<mailto:draft-ietf-idr-bgp-ls-segment-routing-ext@ietf.org>; draft-ietf-idr-te-pm-bgp@ietf.org<mailto:draft-ietf-idr-te-pm-bgp@ietf.org>; idr wg <idr@ietf.org<mailto:idr@ietf.org>> Subject: RE: [Idr] Regd BGP-LS code points early allocation for WG adopted drafts WG Chairs – If you have not already done so please initiate early allocation of code points for https://datatracker.ietf.org/doc/draft-ietf-idr-te-pm-bgp/ Thanx. Les From: Ketan Talaulikar (ketant) Sent: Friday, August 04, 2017 10:24 PM To: Jeff Tantsura; Job Snijders; John G. Scudder; Les Ginsberg (ginsberg) Cc: Stefano Previdi; Susan Hares; draft-ietf-idr-bgp-ls-segment-routing-ext@ietf.org<mailto:draft-ietf-idr-bgp-ls-segment-routing-ext@ietf.org>; draft-ietf-idr-te-pm-bgp@ietf.org<mailto:draft-ietf-idr-te-pm-bgp@ietf.org>; idr wg Subject: RE: [Idr] Regd BGP-LS code points early allocation for WG adopted drafts Hi All, The IANA early allocation has been done for the BGP-LS SR extension drafts now, but the other two drafts related to MSD and draft-idr-te-pm are still pending early allocations. May I request the authors to please request for the same at the earliest? We have a collision right now between these drafts with their previously “suggested” code point values so would appreciate if this was resolved ASAP to aid implementations. For the record, the previously suggested values were: TLV Type Value -------------------------------------------------------- 1104 (Suggested) Unidirectional Link Delay 1105 (Suggested) Min/Max Unidirectional Link Delay 1106 (Suggested) Unidirectional Delay Variation 1107 (Suggested) Unidirectional Packet Loss 1108 (Suggested) Unidirectional Residual Bandwidth 1109 (Suggested) Unidirectional Available Bandwidth 1110 (Suggested) Unidirectional Bandwidth Utilization Then from the MSD draft, we have collision Code-point: 1110 (Suggested value - to be assigned by IANA) from BGP- LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs registry Thanks, Ketan From: Jeff Tantsura [mailto:jefftant.ietf@gmail.com] Sent: 15 July 2017 19:48 To: Job Snijders <job@instituut.net<mailto:job@instituut.net>>; John G. Scudder <jgs@juniper.net<mailto:jgs@juniper.net>>; Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>> Cc: Stefano Previdi <stefano@previdi.net<mailto:stefano@previdi.net>>; Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>; draft-ietf-idr-bgp-ls-segment-routing-ext@ietf.org<mailto:draft-ietf-idr-bgp-ls-segment-routing-ext@ietf.org>; draft-ietf-idr-te-pm-bgp@ietf.org<mailto:draft-ietf-idr-te-pm-bgp@ietf.org>; idr wg <idr@ietf.org<mailto:idr@ietf.org>> Subject: Re: [Idr] Regd BGP-LS code points early allocation for WG adopted drafts That’s the plan! Cheers, Jeff From: Job Snijders <job@instituut.net<mailto:job@instituut.net>> Date: Saturday, July 15, 2017 at 16:15 To: Jeff Tantsura <jefftant.ietf@gmail.com<mailto:jefftant.ietf@gmail.com>>, "John G. Scudder" <jgs@juniper.net<mailto:jgs@juniper.net>>, "Ketan Talaulikar (ketant)" <ketant@cisco.com<mailto:ketant@cisco.com>> Cc: Stefano Previdi <stefano@previdi.net<mailto:stefano@previdi.net>>, Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>, "draft-ietf-idr-bgp-ls-segment-routing-ext@ietf.org<mailto:draft-ietf-idr-bgp-ls-segment-routing-ext@ietf.org>" <draft-ietf-idr-bgp-ls-segment-routing-ext@ietf.org<mailto:draft-ietf-idr-bgp-ls-segment-routing-ext@ietf.org>>, "draft-ietf-idr-te-pm-bgp@ietf.org<mailto:draft-ietf-idr-te-pm-bgp@ietf.org>" <draft-ietf-idr-te-pm-bgp@ietf.org<mailto:draft-ietf-idr-te-pm-bgp@ietf.org>>, idr wg <idr@ietf.org<mailto:idr@ietf.org>> Subject: Re: [Idr] Regd BGP-LS code points early allocation for WG adopted drafts On Sat, 15 Jul 2017 at 15:35, Jeff Tantsura <jefftant.ietf@gmail.com<mailto:jefftant.ietf@gmail.com>> wrote: Would you want the authors of draft-tantsura-idr-bgp-ls-segment-routing-msd to remove suggested values or wait for early allocation and replace? The outcome of the IANA Early Allocation process is not directly connected to self-assigning (squatting) in the current document. I would suggest the squatted codepoint should be removed at the earliest opportunity (Monday morning). Uploading new drafts is cheap and easy after all. Kind regards, Job
- [Idr] Regd BGP-LS code points early allocation fo… Ketan Talaulikar (ketant)
- Re: [Idr] Regd BGP-LS code points early allocatio… John G. Scudder
- Re: [Idr] Regd BGP-LS code points early allocatio… Jeff Tantsura
- Re: [Idr] Regd BGP-LS code points early allocatio… Job Snijders
- Re: [Idr] Regd BGP-LS code points early allocatio… Jeff Tantsura
- Re: [Idr] Regd BGP-LS code points early allocatio… Ketan Talaulikar (ketant)
- Re: [Idr] Regd BGP-LS code points early allocatio… Acee Lindem (acee)
- Re: [Idr] Regd BGP-LS code points early allocatio… Jeff Tantsura
- Re: [Idr] Regd BGP-LS code points early allocatio… Ketan Talaulikar (ketant)
- Re: [Idr] Regd BGP-LS code points early allocatio… Acee Lindem (acee)
- Re: [Idr] Regd BGP-LS code points early allocatio… Les Ginsberg (ginsberg)
- Re: [Idr] Regd BGP-LS code points early allocatio… Ketan Talaulikar (ketant)
- Re: [Idr] Regd BGP-LS code points early allocatio… Susan Hares
- Re: [Idr] Regd BGP-LS code points early allocatio… Susan Hares
- Re: [Idr] Regd BGP-LS code points early allocatio… Ketan Talaulikar (ketant)
- Re: [Idr] Regd BGP-LS code points early allocatio… Les Ginsberg (ginsberg)
- Re: [Idr] Regd BGP-LS code points early allocatio… Susan Hares
- Re: [Idr] Regd BGP-LS code points early allocatio… Les Ginsberg (ginsberg)
- Re: [Idr] Regd BGP-LS code points early allocatio… Jeff Tantsura
- Re: [Idr] Regd BGP-LS code points early allocatio… Susan Hares