Re-, Please see inline.
Cheers, Med > -----Message d'origine----- > De : Jürgen Schönwälder <[email protected]> > Envoyé : lundi 21 octobre 2024 16:32 > À : BOUCADAIR Mohamed INNOV/NET <[email protected]> > Cc : [email protected] > Objet : Re: [netmod] IANA considerations for revised RFCs in > rfc8407bis > > On Mon, Oct 21, 2024 at 01:48:57PM +0000, > [email protected] wrote: > > > > We don't have explicit text to say that a rev has to ask to > update the ref in "ns", though. > > > > I think IANA does not touch the XML namespace registration at all, [Med] Actually, it does. Please, for example, yang:ietf-interfaces, yang:ietf-template, etc. > hence RFC 8341 says something like: > > This document reuses the URI for "$module" in the "IETF XML > Registry". [Med] Still, that entry was updated to point to 8341: yang:ietf-netconf-acm urn:ietf:params:xml:ns:yang:ietf-netconf-acm ns/yang/ietf-netconf-acm.txt [RFC8341] > > Ideally, there is a cut and paste friendly template for the common > cases: > > a) A document defining new YANG modules not maintained by IANA > b) A document defining new YANG modules maintained by IANA > c) A document revising YANG modules not maintained by IANA > d) A document revising YANG modules maintained by IANA > > Well, d) should exist since the module is maintained by IANA, so > we have cases a)-c). Mixing things together in some what may make > it harder than necessary for document authors to engineer the text > they need to use. > [Med] a/b are the same. What differs is the answer to "Maintained by IANA?". Created sub-sections to easily reference the templates, but only kept two cases. > /js > > -- > Jürgen Schönwälder Constructor University Bremen > gGmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | > Germany ____________________________________________________________________________________________________________ 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]
