Dear Authors (cc: intarea WG), Before the IETF meeting, we check working group agendas for documents with IANA-related issues. We have a minor note about this document's IANA Considerations section:
https://datatracker.ietf.org/doc/html/draft-ietf-intarea-arp-yang-model-00 About Section 6, Figure 5: we missed this a few times in the past, but RFC 3688 requires that the IESG be listed as the Registrant Contact for XML ns registrations. (This may contradict other advice you’ve seen from us. In general, the IESG has preferred that the IETF be listed as the registrant/assignee/change controller for registrations made by IETF stream RFCs, but a few older RFCs require that the IESG be named instead.) If you have any questions, just let us know. If you'd like to talk in person, you can find us next to the RFC Editor's table from Monday through Thursday. You can also request another review at any time by contacting us at [email protected]. For more information about IANA Considerations section requirements, please see https://www.iana.org/help/protocol-registration Best regards, Amanda Baber IANA _______________________________________________ Int-area mailing list -- [email protected] To unsubscribe send an email to [email protected]
