Hi Jürgen, We added in -13 text to cover a related point. Please see the diff (See 5.3):
https://author-tools.ietf.org/iddiff?url1=draft-ietf-netmod-rfc8407bis-12&url2=draft-ietf-netmod-rfc8407bis-13&difftype=--html Both NEW/Updated use the same template to register the module on the "YANG Module Names" registry. We don't have explicit text to say that a rev has to ask to update the ref in "ns", though. Please check this diff and let me know if this is OK: https://author-tools.ietf.org/api/iddiff?url_1=https://netmod-wg.github.io/rfc8407bis/draft-ietf-netmod-rfc8407bis.txt&url_2=https://netmod-wg.github.io/rfc8407bis/iana-template-update/draft-ietf-netmod-rfc8407bis.txt Thank you. Cheers, Med > -----Message d'origine----- > De : Jürgen Schönwälder <[email protected]> > Envoyé : lundi 21 octobre 2024 15:23 > À : [email protected] > Objet : [netmod] IANA considerations for revised RFCs in > rfc8407bis > > > Hi, > > we sometimes revise RFCs with YANG modules and I now learned that > IANA wants to have IANA consideration sections that are patterned > like the one in RFC 8341. In short, the first sentence clarifies > that the existing registration in the XML registry is reused and > the second specifies that IANA creates a new entry in their module > registry (they have an entry for each revision of the module > there). Perhaps this is something RFC 8407 could clarify what to > write for a new module and what to write for an udpated module. > > /js > > -- > Jürgen Schönwälder Constructor University Bremen > gGmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | > Germany > > _______________________________________________ > netmod mailing list -- [email protected] > To unsubscribe send an email to [email protected] ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
