Re: [GROW] Making BMP registries FCFS


Sent from my iPhone

> On Sep 20, 2018, at 22:33, Christopher Morrow <christopher.morrow@gmail.com> wrote:
> 
> Hello Grow Folks,
> This seems like a sane plan ... I or Job can either unilaterally accept this, or ask for adoption...
> 
> If there's enough immediate call to avoid the 2wk call for adoption I'd be happy to just put it on the docket...

I think you can adopt it and move on.  Support making registries low effort as a general principle.
> 
>> On Thu, Sep 20, 2018 at 1:12 AM John Scudder <jgs@juniper.net> wrote:
>> Hi All,
>> 
>> A while ago we talked about this. I finally wrote a draft for it, https://www.ietf.org/id/draft-scudder-grow-bmp-registries-change-00.txt:
>> 
>> Abstract
>> 
>>    This document updates RFC 7854, BGP Monitoring Protocol (BMP) by
>>    making a change to the registration procedures for several
>>    registries.  Specifically, any BMP registry with a range of
>>    32768-65530 designated "Specification Required" has that range re-
>>    designated as "First Come First Served".
>> 
>> It's super short, 3 pages including all the boilerplate. I'd like to propose it as a WG item (and ideally, move it quickly to WGLC).
>> 
>> Thanks,
>> 
>> --John
>> 
>> P.S.: I'm one of the designated experts for those registries ("Specification Required" requires designated experts who review all requests). So I have the ulterior motive of trying to get rid of work. :-)
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow