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

"UTTARO, JAMES" <> Thu, 20 September 2018 13:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5A240130EA3; Thu, 20 Sep 2018 06:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id gK81CxdRXs00; Thu, 20 Sep 2018 06:06:53 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D7081130EA2; Thu, 20 Sep 2018 06:06:51 -0700 (PDT)
Received: from pps.filterd ( []) by ( with SMTP id w8KD5ZHY015401; Thu, 20 Sep 2018 09:06:51 -0400
Received: from ( []) by with ESMTP id 2mm9x43rhm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 20 Sep 2018 09:06:50 -0400
Received: from (localhost []) by (8.14.5/8.14.5) with ESMTP id w8KD6ldK021625; Thu, 20 Sep 2018 09:06:47 -0400
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id w8KD6eFw021511; Thu, 20 Sep 2018 09:06:41 -0400
Received: from ( []) by (Service) with ESMTP id E3D9D4048B50; Thu, 20 Sep 2018 13:06:40 +0000 (GMT)
Received: from (unknown []) by (Service) with ESMTPS id D03794048B53; Thu, 20 Sep 2018 13:06:40 +0000 (GMT)
Received: from ([]) by ([]) with mapi id 14.03.0415.000; Thu, 20 Sep 2018 09:06:40 -0400
From: "UTTARO, JAMES" <>
To: "Acee Lindem (acee)" <>, John Scudder <>, "" <>
CC: "" <>
Thread-Topic: [Idr] Requesting WG adoption for draft-scudder-idr-capabilities-registry-change-02.txt
Thread-Index: AQHUUMV+sqEn2M98Pke/8kwMHYP+c6T5I+5Q
Date: Thu, 20 Sep 2018 13:06:39 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-20_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809200134
Archived-At: <>
Subject: Re: [Idr] Requesting WG adoption for draft-scudder-idr-capabilities-registry-change-02.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 20 Sep 2018 13:06:54 -0000


	Jim Uttaro

-----Original Message-----
From: Idr [] On Behalf Of Acee Lindem (acee)
Sent: Thursday, September 20, 2018 5:37 AM
To: John Scudder <>et>;
Subject: Re: [Idr] Requesting WG adoption for draft-scudder-idr-capabilities-registry-change-02.txt

Hi John, 

I support WG adoption. 



On 9/20/18, 2:11 AM, "Idr on behalf of John Scudder" < on behalf of> 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.




    --John (an individual contributor to the WG, and recusing myself as co-chair from the adoption and subsequent process)




    Idr mailing list


Idr mailing list