[Idr] Regd BGP-LS code points early allocation for WG adopted drafts
"Ketan Talaulikar (ketant)" <ketant@cisco.com> Thu, 13 July 2017 06:01 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 9C13713181C; Wed, 12 Jul 2017 23:01:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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
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 UD4FHF8uTzei; Wed, 12 Jul 2017 23:01:19 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBF7E12EC06; Wed, 12 Jul 2017 23:01:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20282; q=dns/txt; s=iport; t=1499925678; x=1501135278; h=from:to:cc:subject:date:message-id:mime-version; bh=hxYy5JGcNU6Twu0pC1cJP1cYNE8WUXGQff108S/hLMs=; b=lNusz20X3X7Tsdn6Mw5cihLTTqBoo1/gsMy/vrepxdXFJ1EFVH836Sza 2mJLGrmwe8eIeAjLh70L5pZIsvw+8fEVDF1ccabzF5mqWRtf7GUg/Yr2E eJLQ/QIvE2CpltnDrKhByVSdDtOXU0elrflIAoiV8enej7zfPHcVJXHHy 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CoAACWC2dZ/4wNJK1dGQEBAQEBAQEBAQEBBwEBAQEBgm8+LWSBFAeOApFydI9jhSyCESEBCoVKAhqDPj8YAQIBAQEBAQEBayiFGAEBAQEEASEKQQsMBgEZBAEBKAMCBCULFAkJAQQBDQUIiUNkEK1pgiaLIQEBAQEBAQEBAQEBAQEBAQEBAQEBAR2DKINNgWABgnA0gyaBWw8QCIJVgmEFiWONWodvAodGg0iId4IVV4EPg2WKUJVSAQ8QOIEKdRUfKoUTHIFndodMgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.40,352,1496102400"; d="scan'208,217";a="269412946"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Jul 2017 06:01:17 +0000
Received: from XCH-RCD-008.cisco.com (xch-rcd-008.cisco.com [173.37.102.18]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v6D61HrI027465 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 13 Jul 2017 06:01:17 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-008.cisco.com (173.37.102.18) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 13 Jul 2017 01:01:16 -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.1210.000; Thu, 13 Jul 2017 01:01:16 -0500
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Stefano Previdi <stefano@previdi.net>, Susan Hares <shares@ndzh.com>, 'idr wg' <idr@ietf.org>, Jeff Tantsura <jefftant.ietf@gmail.com>
CC: "draft-ietf-idr-bgp-ls-segment-routing-ext@ietf.org" <draft-ietf-idr-bgp-ls-segment-routing-ext@ietf.org>, "draft-ietf-idr-te-pm-bgp@ietf.org" <draft-ietf-idr-te-pm-bgp@ietf.org>
Thread-Topic: Regd BGP-LS code points early allocation for WG adopted drafts
Thread-Index: AdL7nWosFbh13zxaTe29YgdiZl93UQ==
Date: Thu, 13 Jul 2017 06:01:16 +0000
Message-ID: <999f002984de432bb168f60309d66b63@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.65.80.235]
Content-Type: multipart/alternative; boundary="_000_999f002984de432bb168f60309d66b63XCHALN008ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/4DK8K5wrBzvwSFsCgQPPyQzUHug>
Subject: [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, 13 Jul 2017 06:01:22 -0000
Hello, May I request the authors of the draft-ietf-idr-bgp-ls-segment-routing-ext and draft-ietf-idr-te-pm-bgp and WG chairs to please request for early allocation of their IANA code points? Also, the link MSD codepoint in draft-tantsura-idr-bgp-ls-segment-routing-msd collides with the suggested codepoints in draft-ietf-idr-te-pm-bgp. Early allocations for WG adopted drafts would help avoid collisions. Jeff, may I suggest to request the code point 1111 for the Link MSD since the TE PM draft is already a WG item and there may be implementations out there already? Thanks, Ketan From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Stefano Previdi Sent: 28 June 2017 21:51 To: Susan Hares <shares@ndzh.com>; 'idr wg' <idr@ietf.org> Subject: Re: [Idr] I-D Action: draft-ietf-idr-bgp-ls-segment-routing-ext-02.txt Hi Sue, Yes, that definitely would help. Thanks. s. On June 28, 2017 5:36:46 PM GMT+02:00, Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>> wrote: Stefano: Did you want early allocation for the code points while we work through the documentation process? If so, I will include this in the WG LC. Sue -----Original Message----- From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of stefano previdi Sent: Monday, June 26, 2017 3:08 AM To: idr wg Subject: Re: [Idr] I-D Action: draft-ietf-idr-bgp-ls-segment-routing-ext-02.txt FYI, this version has been cleaned up from all unused TLVs according to the changes being done in draft-ietf-[ospf|isis]-segment-routing-extensions. Due to the number of codepoints this drafts proposes, I’d like to ask the chairs to consider the document for publication. Thanks. s. On Jun 26, 2017, at 8:56 AM, internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> wrote: A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing of the IETF. Title : BGP Link-State extensions for Segment Routing Authors : Stefano Previdi Peter Psenak Clarence Filsfils Hannes Gredler Mach(Guoyi) Chen Filename : draft-ietf-idr-bgp-ls-segment-routing-ext-02.txt Pages : 27 Date : 2017-06-25 Abstract: Segment Routing (SR) allows for a flexible definition of end-to-end paths within IGP topologies by encoding paths as sequences of topological sub-paths, called "segments". These segments are advertised by the link-state routing protocols (IS-IS, OSPF and OSPFv3). This draft defines extensions to the BGP Link-state address-family in order to carry segment information via BGP. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-segment-routing -ext/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-idr-bgp-ls-segment-routing-ext- 02 https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-ls-segment-ro uting-ext-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgp-ls-segment-routin g-ext-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts<http://ftp.ietf.org/internet-drafts>/ ________________________________ Idr mailing list Idr@ietf.org<mailto:Idr@ietf.org> https://www.ietf.org/mailman/listinfo/idr ________________________________ Idr mailing list Idr@ietf.org<mailto:Idr@ietf.org> https://www.ietf.org/mailman/listinfo/idr
- [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