Future Enumservice Registration Process
Bernie Hoeneisen <[email protected]>
| Newsgroups | gmane.ietf.enum |
|---|---|
| Message-ID | <Pine.LNX.4.64.0711021122180.14252@machb> |
Hi all *** Please comment until Wednesday, Nov 05 *** One major issue in draft-ietf-enum-enumservices-guide-05.txt seems to be, which process to apply for future Enum service registrations. I went through existing similar IANA processes and found at least four variants, how a registration document can be processed: A) Author -> IESG -> Expert Review -> IESG -> IANA -> Publication B) Author -> Expert Review -> IESG -> IANA -> Publication C) Author -> IANA -> Expert Review -> IANA -> Publication D) Author -> IESG -> IANA -> Expert Review -> IANA -> Publication In the current revision of draft-ietf-enum-enumservices-guide-05.txt process B) is documented, however I am tending to replace it by process A), as this way the responsibilities are much more clear. In case registrations should be made without IESG looking at it, C) could be the choice. Maybe for experimental Enumservice registrations this makes sense. If we want to apply such a simple process for normal Enumservice registrations, a major change in RFC 3761 is needed, as RFC 3761 states: "Enumservice registrations needs to be Standards Track, Experimental or BCP" What do you think about? In case there it no major opposition within the next 5 days, I'll rewrite draft-ietf-enum-enumservices-guide-06.txt in favour of process A) and submit it for the Vancouver meeting. cheers, Bernie