Hi Per, I agree it is neat to have a script rather than every one writing this manually.
The guidance is in 8407bis: Designers of IANA-maintained modules MAY supply the full initial version of the module in a specification document that registers the module or only a script to be used (including by IANA) for generating the module (e.g., an XSLT stylesheet as in Appendix A of [RFC9108]). For both cases, the document that defines an IANA-maintained module MUST include a note indicating that the document is only documenting the initial version of the module and that the authoritative version is to be retrieved from the IANA registry. ... It is RECOMMENDED to include the URL from where to retrieve the recent version of the module. When a script is used, the Internet- Draft that defines an IANA-maintained module SHOULD include an appendix with the initial full version of the module. Including such an appendix in pre-RFC versions is meant to assess the correctness of the outcome of the supplied script. The authors MUST include a note to the RFC Editor requesting that the appendix be removed before publication as RFC and that RFC IIII is replaced with the RFC number that is assigned to the document. Initial versions of IANA- maintained modules that are published in RFCs may be misused despite the appropriate language to refer to the IANA registry to retrieve the up-to-date module. Given the concern raised by IANA and confusion about the intent of the script, the new version of the acl model follows "MAY supply the full initial" of the guidance part. I think that we need better integrated tooling to exclusively rely on the script approach. IANA would BTW develop this to transform any registry to an IANA-maintained module. That would safe many cycles. Hope this is better. Cheers, Med > -----Message d'origine----- > De : Per Andersson <[email protected]> > Envoyé : vendredi 4 avril 2025 13:58 > À : BOUCADAIR Mohamed INNOV/NET <[email protected]> > Cc : Roman Danyliw <[email protected]>; The IESG <[email protected]>; > [email protected]; [email protected]; > [email protected] > Objet : Re: [netmod] Roman Danyliw's Discuss on draft-ietf-netmod- > acl-extensions-15: (with DISCUSS and COMMENT) > > > Hi! > > I thought it was pretty neat to have stumbled upon a ready made > method for generating IANA YANG modules from the IANA registry. > > However, I understand that it might not be suitable to have in the > draft. It was possible though for me as a YANG Doctor reviewer to > suggest changes in the generation though with a patch. > > Is there some guidance documented anywhere on how to generate the > initial IANA YANG modules? I couldn't find anything on the IETF > Wiki. > > > -- > Per ____________________________________________________________________________________________________________ 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]
