Re: [Idr] Regd BGP-LS code points early allocation for WG adopted drafts
"Ketan Talaulikar (ketant)" <ketant@cisco.com> Thu, 28 September 2017 02:21 UTC
Return-Path: <ketant@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 7219B13526A; Wed, 27 Sep 2017 19:21:27 -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_H3=-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 W4xh19PSqrd8; Wed, 27 Sep 2017 19:21:25 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1EF4135267; Wed, 27 Sep 2017 19:21:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=31868; q=dns/txt; s=iport; t=1506565285; x=1507774885; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Awkg5Jy1/8b70qaApDYa+Hlvpn8dfkxkur2wfiWRz6k=; b=H5w0uCXWtQj7mzhZ4pkJyb4xhK/sN+f1FTXRVpp8PZPcVGXmoQeCPLAH ooHyTKkv49CQbff7CKQK5SMgOs+XY7NE2GvdNjmag75JvyIZR0Ajg2M0h ZC4I/2pFmg0SbaTfpJqdA7uz72QmSjkMgR/6dq74d4IJKZY9oDgv+EHVj o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CkAQDhW8xZ/5BdJa1cGQEBAQEBAQEBAQEBBwEBAQEBgm9tZG4nB4NxmXyBdnmHSY13ggQKJYUWAhqEQlcBAgEBAQEBAmsohRgBAQEBAyMKTBACAQgRAwEBASEHAwICAh8RFAkIAgQBDQUIiUVMAxUQp0SCJyeHFA2DOwEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgyuCAoFRgWqCczWCXoFzARIBBy8JFoJdgmAFihKOPYgYPAKHXIgIhHCCHIVuiwWMaYgzAhEZAYE4AVeBAwt4FUmFGhyBZ3aGHoEkgRABAQE
X-IronPort-AV: E=Sophos;i="5.42,447,1500940800"; d="scan'208,217";a="9160199"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Sep 2017 02:21:24 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id v8S2LL2l019742 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 28 Sep 2017 02:21:21 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 27 Sep 2017 21:21:20 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1320.000; Wed, 27 Sep 2017 21:21:20 -0500
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: 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: Stefano Previdi <stefano@previdi.net>, Susan Hares <shares@ndzh.com>, idr wg <idr@ietf.org>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "John G. Scudder" <jgs@juniper.net>, Job Snijders <job@instituut.net>
Thread-Topic: [Idr] Regd BGP-LS code points early allocation for WG adopted drafts
Thread-Index: AdL7nWosFbh13zxaTe29YgdiZl93UQB+CRWAAADnRIAAAWQjgAAAEggABAKqdHABxCZKYAjRO8mg
Date: Thu, 28 Sep 2017 02:21:20 +0000
Message-ID: <68fa61de24984dcd9b03a81ba24c1b8a@XCH-ALN-008.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>
In-Reply-To: <5ddccfb5e75f47d39676b90a3f5364c5@XCH-ALN-001.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.65.56.138]
Content-Type: multipart/alternative; boundary="_000_68fa61de24984dcd9b03a81ba24c1b8aXCHALN008ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/nuiMvl08_goT_6w13YUhzJZYNbw>
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 02:21:27 -0000
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>; Jeff Tantsura <jefftant.ietf@gmail.com>; Job Snijders <job@instituut.net>; John G. Scudder <jgs@juniper.net> Cc: Stefano Previdi <stefano@previdi.net>; Susan Hares <shares@ndzh.com>; draft-ietf-idr-bgp-ls-segment-routing-ext@ietf.org; draft-ietf-idr-te-pm-bgp@ietf.org; idr wg <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