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

["Dongjie (Jimmy)" <[e-mail]>]

Yes, support. This would be helpful to avoid conflicts in future. 

Best regards,
Jie

> -----Original Message-----
> From: John Scudder [mailto:[e-mail]]
> Sent: Thursday, September 20, 2018 2:11 PM
> To: [e-mail]
> Cc: [e-mail]
> Subject: Requesting WG adoption for
> draft-scudder-idr-capabilities-registry-change-02.txt
> 
> 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)
>