Re: [Ext] Re: [rfc-i] Evolving document sources over a long time (Re: Comments on draft-roach-bis-documents-00)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On May 23, 2019, at 13:05, Andrew G. Malis <agmalis@xxxxxxxxx> wrote:
> 
> bis RFC as close to the original as possible

In a case we are looking at right now, that would actually be true with respect to the contribution of the spec to the registry content (the registry probably should be updated to point to the bis).  But it is a bit weird to talk about the initial assignments for a registry that has since gained dozens of additional entries…

I think the IANA considerations should contain:
— all “new” registries defined by this spec
— all procedures/policies for these (might want to update)
— registry entries (in old or new registries) that should now point to the bis document as documentation (need not be wholesale — maybe the bis is dropping some cobwebs)

Usually, for RFCs the IANA considerations should already be in past tense, so that will not be a big change.  If the diff is manageable, IANA should be able to see from that what the actual actions are (new new registries, new new entries…).

Note that the documentation of the existing registered entry might very well be updated in the bis document, so updating the pointer from IANA to the bis is important.

Grüße, Carsten





[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux