[IANA #171390] FW: Revision of IANA Enumservice registry
"Michelle Cotton via RT" <[email protected]> Fri, 3 Oct 2008 20:47:35 +0000
| Newsgroups | gmane.ietf.enum |
|---|---|
| Message-ID | <[email protected]> |
Hi Bernie, I've chatted with our XML folks helping us with the conversions. (They are copied on this message) They will begin converting the current registry next week. See more responses inline below. On Fri Oct 03 08:15:52 2008, [email protected] wrote: > Hi Michelle > > Thanks for your answer. > > To summarize, in Ticket [IANA #171390] there are basically two open > issues: > > 1) How should the specification look, if an IANA Registry is in XML? If someone writes a document to add a new registration to the enum-services registry, it would be great if they included in their document an XML chunk that IANA would simply cut and paste in the registry itself after the registration is approved. The spec itself does not have to be in XML. > > 2) Is the process as currently described in draft-ietf-enum- > enumservices-guide-12 suitable for IANA? (We made some major > changes since our talk in Dublin.) I've reviewed version 12 of the document. All seems pretty good. I do have the following comments: In section 11.1.2., I understand that it is requested that IANA archive the specification in the cases of it not being an RFC. Will IANA need to make that document public or just archive it for purposes of inquires and registration? I see the use "Authors" frequently. We mainly use the term "Requester". The expert review process in this document is slightly different than the one that IANA currently uses. For most registries, requests are sent to IANA, we forward the request to the expert for review, after the approval IANA registers the parameter and then notifies the requester of the completed registration. In this case, the expert is approving the template and it appears they also have to approve the specification after it is published? It seems a bit fuzzy to me. Or is this the case where the expert my assist in making the template better before it gets finalization in a document? If that is the case, then IANA will have to go to the expert twice in this case? Once for the enumservice template, and then second to verify the specification has been published. Tell me if I'm mistaken in my understanding of the instructions. :) Also, for the document, having the xml chunk for the registration itself would be very useful. We can help with providing what that should look like as we convert the registry in the next few weeks. > > We would appreciate your answer to these two questions by the end of > this week. > > cheers, > Bernie > I hope this helps. Please let us know if you have any further questions. Best regards, Michelle IANA