[Ntp] Antw: [EXT] Re: Quick review of WGLC for status change for draft‑ietf‑ntp‑update‑registries

[Ulrich Windl <[e-mail]>]

>>> "Salz, Rich" <rsalz=[e-mail]> schrieb am 09.08.2022 um
17:28
in Nachricht <[e-mail]>:
>>     It makes more sense to me to use the existing model.  If somebody wants

>     to experiment, assign them the next unused number in the registry, say,

>     0x**0A,  That give them plenty of (sub)code bits (up to 6, and to date 
>     no proposal has used more than 4 bits) for whatever purpose they want.
> 
> This is what's known as a first‑come first‑served (FCFS) registry.  Instead,

> we are allocating a range and telling people "use something in this range
for 
> your private tests"  It might conflict with other people's private tests; 
> that's on you. If you want an official number, you can't just ask for one, 
> you have to document it. See next section for why many people think this 
> model makes more sense than what used to be done.
> 
>>    That's still the case.  But as I said before, once something has been 
>     used it will live on.  The mess remains.
> 
> Yes, with your proposal that happens. But with an experimental section set 
> aside, there is less chance of that happening for two reasons:
> 
> 	‑ Some other experiment may end up conflicting; and
> 	‑ You won't get an official number until things are documented
> 
> We have seen problems before with autokey implementation compared to 
> documentation. Making the public section of the registry "Specification 
> Required" prevents that. But the Internet does not require permission before

> standing up clients and servers, so making a portion of the number space 
> "Experimental" also allows that.
> 
> RFC 5226, particularly page 10 (only available as a printer‑style output)
has 
> the summary. In particular, look for the definition of Specification 
> Required.

For completeness, that RFC is also BCP-26 (best current practice).

> 
> 
> _______________________________________________
> ntp mailing list
> [e-mail] 
> https://www.ietf.org/mailman/listinfo/ntp