IETF Logo Mail Archive

Re: [Idr] Early allocation WG call (1-2 weeks) (Sept

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Fri, 06 October 2017 05:26 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 602CD129A89 for <idr@ietfa.amsl.com>; Thu, 5 Oct 2017 22:26:05 -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 ePjLCrOLKyIC for <idr@ietfa.amsl.com>; Thu, 5 Oct 2017 22:26:03 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29DE3124B18 for <idr@ietf.org>; Thu, 5 Oct 2017 22:26:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14080; q=dns/txt; s=iport; t=1507267563; x=1508477163; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=Eg0gPIavqcZSFkMWIVrZTFEzMWyzykRFLWlYJJRdix8=; b=lIvbXnsbV29h29jMkGAflwyyW09VuDV8q420gt9hR6xovJTq4DiAT1Wp VoBMd5glziQdvS4mhIHiHjEs+jb3yd60v7Cei15at31c+cifs9MNDWLi9 aE3VupufRiqmw5xXRNZ+CG8ujLXWqDLjXELz0bndUCfTdMhDDY7tf+nFk Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CnAAAUE9dZ/4YNJK1bGQEBAQEBAQEBAQEBBwEBAQEBgm9uZG4nB44Sj2aBdpBwhT+CEgolhRYChBs/GAECAQEBAQEBAWsohRgBAQEBAy1cAgEIDgMEAQEoBzIUCQgBAQQBEgiJRGQQqFaLLQEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgy2CAoFRgWqDKYMyggiFPgWhMwKHXIx+gh2Fb4sHlSwCERkBgTgBHziBDngVh2Z2h3OBEAEBAQ
X-IronPort-AV: E=Sophos; i="5.42,482,1500940800"; d="scan'208,217"; a="13345121"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 06 Oct 2017 05:26:02 +0000
Received: from XCH-RCD-007.cisco.com (xch-rcd-007.cisco.com [173.37.102.17]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v965Q1C8012215 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 6 Oct 2017 05:26:02 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-007.cisco.com (173.37.102.17) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 6 Oct 2017 00:26:01 -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; Fri, 6 Oct 2017 00:26:01 -0500
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Susan Hares <shares@ndzh.com>, 'idr wg' <idr@ietf.org>
Thread-Topic: [Idr] Early allocation WG call (1-2 weeks) (Sept
Thread-Index: AdM4jaYL6TSRCD10TXu5hNxjKcHuwwF1KDUQ
Date: Fri, 06 Oct 2017 05:26:01 +0000
Message-ID: <a0efeb4a9c5a42adb6944655985a8741@XCH-ALN-008.cisco.com>
References: <005d01d3388e$4c3ffdd0$e4bff970$@ndzh.com>
In-Reply-To: <005d01d3388e$4c3ffdd0$e4bff970$@ndzh.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.94.219]
Content-Type: multipart/alternative; boundary="_000_a0efeb4a9c5a42adb6944655985a8741XCHALN008ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/LcMGuKmH5n7QNzIygv9f2wZUVYI>
Subject: Re: [Idr] Early allocation WG call (1-2 weeks) (Sept
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: Fri, 06 Oct 2017 05:26:05 -0000

Thanks Sue for starting this call and please see inline for response.

Support early allocation of code points since we have implementations awaiting the same.

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: 29 September 2017 00:47
To: 'idr wg' <idr@ietf.org>
Subject: [Idr] Early allocation WG call (1-2 weeks) (Sept

This is a WG call to approve the early allocation of code points requested in draft-ietf-idr-bgp-ls-segment-routing-msd-00.   These points are:


   This document requests IANA to assign 2 new code-points from the BGP-

   LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute

   TLVs registry as specified in sections 3<https://tools.ietf.org/html/draft-ietf-idr-bgp-ls-segment-routing-msd-00#section-3> and 4<https://tools.ietf.org/html/draft-ietf-idr-bgp-ls-segment-routing-msd-00#section-4>. (section 5)




While considering this early allocation, please consider


1)      Are there multiple vendors wishing to implement?
[KT] Yes

2)      Is the specification stable and accurate?
[KT] Yes

3)      How quickly do the implementers wish to progress the specification?
[KT] Would like the spec to proceed rather quickly since we have implementations. The Base MSD sub-type is defined in both IGP specs so would like these drafts to at least proceed with that. The other sub-types could be done via separate drafts. We would need the base IGP specs to progress through before this BGP-LS one. The early allocations have been already done for the OSPF & ISIS MSD specs and the shared registry for the sub-types need to be requested by the authors of those documents.

4)      Do you have any concerns on granting this early allocation?
[KT] No

5)      Are you concerned about the IPR on this draft?
[KT] No

There is one IPR Statement on this draft:
https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-idr-bgp-ls-segment-routing-msd

The authors should indicate if they know of an IPR in addition to this draft.

For easy access
https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-idr-bgp-ls-segment-routing-msd

Susan Hares

PS - Thank to Les, Ketan, and Jeff for helping to clear up my confusion

v2.23.0 | Report a Bug | By Email