Re: [Idr] Requesting WG adoption for draft-scudder-idr-capabilities-registry-change-02.txt

"Acee Lindem (acee)" <acee@cisco.com> Thu, 20 September 2018 09:37 UTC

Return-Path: <acee@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 62E89130E50; Thu, 20 Sep 2018 02:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 IJqhyVFMgDCM; Thu, 20 Sep 2018 02:37:07 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4141E130DE4; Thu, 20 Sep 2018 02:37:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2566; q=dns/txt; s=iport; t=1537436227; x=1538645827; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=JWAa/mM272ZjNQqdbfLV7FPnYLvXyx+kK9vyx0Xpy7w=; b=ZZ064FZFhbYtJzVbdVYepfAkAB3HxycmQZ4ggbLnaymau7ue4U9Uzsuv 9mXO8RFBfnREpyhyk5jt1fbhyl1JBw7lYJ35JU9YD+Jj2yJKDJHwMPL+2 msqqYbHDalBIIR9LwC2bJOK8fj2gfVMq/xsvAzJO9sLFc5CgfJ4gtV3mS k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BUAABJaaNb/5JdJa1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYFQgghlfygKg2mIFYwyhUqTEYF6CxgNhEcZgykhNBgBAwE?= =?us-ascii?q?BAgEBAm0cDIU5AgEDAQEhEToLEgEIDgwCJgIEJQsVEgQBDQWDIQGCAQ+jYYE?= =?us-ascii?q?uhHeFIwWBC4lkF4IAgRInH4JMgUEBgVkBAYEtNIMBMYImAoYfgh2GcY1BCQK?= =?us-ascii?q?MVINOF4FEhFCJDpROAhEUgSUdOIFVcBU7KgGCQYIxHIhJhT5vAYxOgR4BAQ?=
X-IronPort-AV: E=Sophos;i="5.53,397,1531785600"; d="scan'208";a="174192075"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Sep 2018 09:37:06 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id w8K9b6Xm002375 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 20 Sep 2018 09:37:06 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-011.cisco.com (64.101.220.151) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 20 Sep 2018 05:37:05 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1395.000; Thu, 20 Sep 2018 05:37:05 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: John Scudder <jgs@juniper.net>, "idr@ietf.org" <idr@ietf.org>
CC: "idr-chairs@ietf.org" <idr-chairs@ietf.org>
Thread-Topic: [Idr] Requesting WG adoption for draft-scudder-idr-capabilities-registry-change-02.txt
Thread-Index: AQHUUMV+sqEn2M98Pke/8kwMHYP+cw==
Date: Thu, 20 Sep 2018 09:37:05 +0000
Message-ID: <CE32697D-F459-446D-95CE-535B717D1D2A@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.199]
Content-Type: text/plain; charset="utf-8"
Content-ID: <3F15667CF78D2E488370EE8351BAC7E5@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.151, xch-rtp-011.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/pTM4ExTvjl5HqkZ1XvBY4gxrIYQ>
Subject: Re: [Idr] Requesting WG adoption for draft-scudder-idr-capabilities-registry-change-02.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Sep 2018 09:37:09 -0000

Hi John, 

I support WG adoption. 

Thanks,
Acee

On 9/20/18, 2:11 AM, "Idr on behalf of John Scudder" <idr-bounces@ietf.org on behalf of jgs@juniper.net> wrote:

    Hi All,
    
    People with sharp memories may recall that in 2015 I proposed we revise the BGP Capabilities registry to provide a good-sized FCFS space. I think our experience shows this works fine in practice and makes it easier for implementors to get code points in a timely fashion, helping prevent conflicts. I wrote a draft at that time but failed to follow it up. I've revised the draft and would like to propose it as a WG item. Here's the abstract:
    
       This document updates RFC 5492 by making a change to the registration
       procedures for BGP Capability Codes.  Specifically, the range
       formerly designated "Reserved for Private Use" is divided into three
       new ranges, respectively designated as "First Come First Served",
       "Experimental" and "Reserved".
    
    One thing to draw your attention to in the revised draft:
    
       Finally, we invite implementors who have used values in the range
       128-255 to contribute to this draft, so that the values can be
       included in the registry.
    
    That is, if you have a shipped implementation that's using one of the Private Use values, please contribute that information to the draft and (assuming the draft progresses) you'll automatically get a registered code point.
    
    https://www.ietf.org/id/draft-scudder-idr-capabilities-registry-change-02.txt
    
    Thanks,
    
    --John (an individual contributor to the WG, and recusing myself as co-chair from the adoption and subsequent process)
    
    
    _______________________________________________
    Idr mailing list
    Idr@ietf.org
    https://www.ietf.org/mailman/listinfo/idr