rfc9890.original.xml   rfc9890.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version='1.0' encoding='UTF-8'?>
<!-- [rfced] Because this document updates RFC 6020, please
review the errata reported for RFC 6020
(https://www.rfc-editor.org/errata/rfc6020)
and let us know if you confirm our opinion that none of them
are relevant to the content of this document.
-->
<!DOCTYPE rfc [ <!DOCTYPE rfc [
<!ENTITY nbsp "&#160;"> <!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;"> <!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;"> <!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;"> <!ENTITY wj "&#8288;">
]> ]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.29 (Ruby 3.4. <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
4) --> -ietf-netmod-rfc6020-iana-update-02" number="9890" category="std" consensus="tru
<?rfc strict="yes"?> e" submissionType="IETF" updates="6020" obsoletes="" tocInclude="true" sortRefs=
<?rfc comments="yes"?> "true" symRefs="true" version="3" xml:lang="en">
<?rfc docmapping="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
-ietf-netmod-rfc6020-iana-update-02" category="std" consensus="true" submissionT
ype="IETF" updates="6020" tocInclude="true" sortRefs="true" symRefs="true" versi
on="3">
<!-- xml2rfc v2v3 conversion 3.30.0 -->
<front> <front>
<title abbrev="YANG Module Names">An Update to YANG Module Names Registratio n</title> <title abbrev="YANG Module Names">An Update to YANG Module Names Registratio n</title>
<seriesInfo name="Internet-Draft" value="draft-ietf-netmod-rfc6020-iana-upda te-02"/> <seriesInfo name="RFC" value="9890"/>
<author fullname="Andy Bierman"> <author fullname="Andy Bierman">
<organization>YumaWorks</organization> <organization>YumaWorks</organization>
<address> <address>
<postal> <postal>
<country>USA</country> <country>United States of America</country>
</postal> </postal>
<email>andy@yumaworks.com</email> <email>andy@yumaworks.com</email>
</address> </address>
</author> </author>
<author fullname="Mohamed Boucadair" role="editor"> <author fullname="Mohamed Boucadair" role="editor">
<organization>Orange</organization> <organization>Orange</organization>
<address> <address>
<postal> <postal>
<country>France</country> <country>France</country>
</postal> </postal>
skipping to change at line 45 skipping to change at line 49
</author> </author>
<author fullname="Qin Wu"> <author fullname="Qin Wu">
<organization>Huawei</organization> <organization>Huawei</organization>
<address> <address>
<postal> <postal>
<country>China</country> <country>China</country>
</postal> </postal>
<email>bill.wu@huawei.com</email> <email>bill.wu@huawei.com</email>
</address> </address>
</author> </author>
<date year="2025" month="August" day="07"/> <date year="2025" month="October"/>
<area>Operations and Management</area> <area>OPS</area>
<workgroup>Network Modeling</workgroup> <workgroup>netmod</workgroup>
<keyword>NETCONF</keyword> <keyword>NETCONF</keyword>
<keyword>RESTCONF</keyword> <keyword>RESTCONF</keyword>
<keyword>Automation</keyword> <keyword>Automation</keyword>
<abstract> <abstract>
<?line 54?> <t>This document amends the IANA guidance on the uniqueness of YANG module
and submodule names.</t>
<t>This document amends the IANA guidance on the uniqueness of YANG module and s
ubmodule names.</t>
<t>The document updates RFC 6020 to clarify how modules and their revision s are handled by IANA.</t> <t>The document updates RFC 6020 to clarify how modules and their revision s are handled by IANA.</t>
</abstract> </abstract>
<note removeInRFC="true">
<name>Discussion Venues</name>
<t>Discussion of this document takes place on the
Network Modeling Working Group mailing list (netmod@ietf.org),
which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/
netmod/"/>.</t>
<t>Source for this draft and an issue tracker can be found at
<eref target="https://github.com/boucadair/rfc8407bis"/>.</t>
</note>
</front> </front>
<middle> <middle>
<?line 60?>
<section anchor="introduction"> <section anchor="introduction">
<name>Introduction</name> <name>Introduction</name>
<t><xref target="RFC6020"/> defines a registry for YANG module and submodu le names, called "YANG Module Names" <xref target="IANA-MOD-NAMES"/>.</t> <t><xref target="RFC6020"/> defines a registry for YANG module and submodu le names, called "YANG Module Names" <xref target="IANA-MOD-NAMES"/>.</t>
<t>Specifically, IANA considerations to register YANG module and submodule names are specified in <xref section="14" sectionFormat="of" target="RFC6020"/> . <t>Specifically, IANA considerations to register YANG module and submodule names are specified in <xref section="14" sectionFormat="of" target="RFC6020"/> .
These considerations require that all module and submodule names in the registry must be unique. However, These considerations require that all module and submodule names in the registry must be unique. However,
the practice followed by IANA is not consistent with that guidance.</t> the practice followed by IANA is not consistent with that guidance.</t>
<t>This document amends the guidance on the uniqueness of names (<xref sec tion="14" sectionFormat="of" target="RFC6020"/>) <t>This document amends the guidance on the uniqueness of names (<xref sec tion="14" sectionFormat="of" target="RFC6020"/>)
to comply with the IANA practices for registering modules and their revisions.</ t> to comply with the IANA practices for registering modules and their revisions.</ t>
</section> </section>
<section anchor="requirements-notation"> <section anchor="requirements-notation">
<name>Requirements Notation</name> <name>Requirements Notation</name>
<t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14 <t>
>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECO "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
MMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be i "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
nterpreted as "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and to be interpreted as described in BCP&nbsp;14 <xref target="RFC2119"/>
only when, they <xref target="RFC8174"/> when, and only when, they appear in all capitals,
appear in all capitals, as shown here.</t> as shown here.
<?line -18?> </t>
</section>
</section>
<section anchor="sec-iana"> <section anchor="sec-iana">
<name>IANA Considerations</name> <name>IANA Considerations</name>
<section anchor="sec-update"> <section anchor="sec-update">
<name>Update YANG Parameters Registry</name> <name>Update YANG Parameters Registry</name>
<t>This document requests IANA to update the reference for <t>IANA has updated
the "YANG Module Names" registry under the "YANG Parameters" registry group <xre f target="IANA-MOD-NAMES"/> the "YANG Module Names" registry under the "YANG Parameters" registry group <xre f target="IANA-MOD-NAMES"/>
to also list to the RFC number that will be assigned to this document. This upda te is needed to list this document as an additional reference. This update is needed
because the procedure in this document is authoritative for assigning names in t hat registry.</t> because the procedure in this document is authoritative for assigning names in t hat registry.</t>
</section> </section>
<section anchor="sec-amend"> <section anchor="sec-amend">
<name>Revisions of Published Modules</name> <name>Revisions of Published Modules</name>
<t>This document amends the guidance on the uniqueness of names, initial ly defined in <xref section="14" sectionFormat="of" target="RFC6020"/>, as follo ws:</t> <t>This document amends the guidance on the uniqueness of names, initial ly defined in <xref section="14" sectionFormat="of" target="RFC6020"/>, as follo ws:</t>
<dl newline="true">
<dt>OLD:</dt> <t>OLD:</t>
<dd>
<blockquote>
<t>All module and submodule names in the registry <bcp14>MUST</bcp14 > be unique.</t> <t>All module and submodule names in the registry <bcp14>MUST</bcp14 > be unique.</t>
</dd>
<dt/>
<dd>
<t>All XML namespaces in the registry <bcp14>MUST</bcp14> be unique. </t> <t>All XML namespaces in the registry <bcp14>MUST</bcp14> be unique. </t>
</dd> </blockquote>
<dt>NEW:</dt>
<dd> <t>NEW:</t>
<blockquote>
<t>Modules and their revisions are maintained in the registry.</t> <t>Modules and their revisions are maintained in the registry.</t>
</dd>
<dt/>
<dd>
<t>All initial version module and submodule names in the registry <b cp14>MUST</bcp14> be unique.</t> <t>All initial version module and submodule names in the registry <b cp14>MUST</bcp14> be unique.</t>
</dd>
<dt/>
<dd>
<t>All XML namespaces of initial version modules in the registry <bc p14>MUST</bcp14> be unique.</t> <t>All XML namespaces of initial version modules in the registry <bc p14>MUST</bcp14> be unique.</t>
</dd>
<dt/>
<dd>
<t>All module and submodule revisions <bcp14>MUST</bcp14> have the s ame name as the one in the initial version of the module and submodule.</t> <t>All module and submodule revisions <bcp14>MUST</bcp14> have the s ame name as the one in the initial version of the module and submodule.</t>
</dd>
<dt/>
<dd>
<t>All module revisions <bcp14>MUST</bcp14> have the same XML namesp ace as the initial version of the module.</t> <t>All module revisions <bcp14>MUST</bcp14> have the same XML namesp ace as the initial version of the module.</t>
</dd> </blockquote>
</dl>
</section> </section>
</section> </section>
<section anchor="operational-considerations"> <section anchor="operational-considerations">
<name>Operational Considerations</name> <name>Operational Considerations</name>
<t>This document aligns an IANA policy with the practice for handling YANG module names (<xref target="sec-amend"/>). As such, there are no new operations or manageability requirements introduced by this document.</t> <t>This document aligns an IANA policy with the practice for handling YANG module names (<xref target="sec-amend"/>). As such, there are no new operations or manageability requirements introduced by this document.</t>
</section> </section>
<section anchor="security-considerations"> <section anchor="security-considerations">
<name>Security Considerations</name> <name>Security Considerations</name>
<t>This document defines a new IANA action (<xref target="sec-update"/>) a nd defines an update (<xref target="sec-amend"/>) to an IANA registration proced ure defined in <xref target="RFC6020"/>. <t>This document defines a new IANA action (<xref target="sec-update"/>) a nd an update (<xref target="sec-amend"/>) to an IANA registration procedure defi ned in <xref target="RFC6020"/>.
It does not introduce any new or increased security risks that need to be discus sed.</t> It does not introduce any new or increased security risks that need to be discus sed.</t>
</section> </section>
</middle> </middle>
<back> <back>
<displayreference target="I-D.ietf-netmod-rfc8407bis" to="YANG-GUIDE"/>
<references anchor="sec-combined-references"> <references anchor="sec-combined-references">
<name>References</name> <name>References</name>
<references anchor="sec-normative-references"> <references anchor="sec-normative-references">
<name>Normative References</name> <name>Normative References</name>
<reference anchor="RFC6020"> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6
<front> 020.xml"/>
<title>YANG - A Data Modeling Language for the Network Configuration <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2
Protocol (NETCONF)</title> 119.xml"/>
<author fullname="M. Bjorklund" initials="M." role="editor" surname= <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
"Bjorklund"/> 174.xml"/>
<date month="October" year="2010"/>
<abstract>
<t>YANG is a data modeling language used to model configuration an
d state data manipulated by the Network Configuration Protocol (NETCONF), NETCON
F remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6020"/>
<seriesInfo name="DOI" value="10.17487/RFC6020"/>
</reference>
<reference anchor="RFC2119">
<front>
<title>Key words for use in RFCs to Indicate Requirement Levels</tit
le>
<author fullname="S. Bradner" initials="S." surname="Bradner"/>
<date month="March" year="1997"/>
<abstract>
<t>In many standards track documents several words are used to sig
nify the requirements in the specification. These words are often capitalized. T
his document defines these words as they should be interpreted in IETF documents
. This document specifies an Internet Best Current Practices for the Internet Co
mmunity, and requests discussion and suggestions for improvements.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="14"/>
<seriesInfo name="RFC" value="2119"/>
<seriesInfo name="DOI" value="10.17487/RFC2119"/>
</reference>
<reference anchor="RFC8174">
<front>
<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</ti
tle>
<author fullname="B. Leiba" initials="B." surname="Leiba"/>
<date month="May" year="2017"/>
<abstract>
<t>RFC 2119 specifies common key words that may be used in protoco
l specifications. This document aims to reduce the ambiguity by clarifying that
only UPPERCASE usage of the key words have the defined special meanings.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="14"/>
<seriesInfo name="RFC" value="8174"/>
<seriesInfo name="DOI" value="10.17487/RFC8174"/>
</reference>
</references> </references>
<references anchor="sec-informative-references"> <references anchor="sec-informative-references">
<name>Informative References</name> <name>Informative References</name>
<reference anchor="IANA-MOD-NAMES" target="https://www.iana.org/assignme nts/yang-parameters/"> <reference anchor="IANA-MOD-NAMES" target="https://www.iana.org/assignme nts/yang-parameters/">
<front> <front>
<title>YANG Module Names</title> <title>YANG Module Names</title>
<author> <author>
<organization>IANA</organization> <organization>IANA</organization>
</author> </author>
<date/> <date/>
</front> </front>
</reference> </reference>
<reference anchor="I-D.ietf-netmod-rfc8407bis">
<!-- [I-D.ietf-netmod-rfc8407bis]
draft-ietf-netmod-rfc8407bis-28
IESG State: RFC Ed Queue (EDIT) as of 09/30/25
-->
<reference anchor="I-D.ietf-netmod-rfc8407bis" target="https://datatrack
er.ietf.org/doc/html/draft-ietf-netmod-rfc8407bis-28">
<front> <front>
<title>Guidelines for Authors and Reviewers of Documents Containing YANG Data Models</title> <title>Guidelines for Authors and Reviewers of Documents Containing YANG Data Models</title>
<author fullname="Andy Bierman" initials="A." surname="Bierman"> <author initials="A." surname="Bierman" fullname="Andy Bierman">
<organization>YumaWorks</organization> <organization>YumaWorks</organization>
</author> </author>
<author fullname="Mohamed Boucadair" initials="M." surname="Boucadai r"> <author initials="M." surname="Boucadair" fullname="Mohamed Boucadai r" role="editor">
<organization>Orange</organization> <organization>Orange</organization>
</author> </author>
<author fullname="Qin Wu" initials="Q." surname="Wu"> <author initials="Q." surname="Wu" fullname="Qin Wu">
<organization>Huawei</organization> <organization>Huawei</organization>
</author> </author>
<date day="5" month="June" year="2025"/> <date month="June" day="5" year="2025" />
<abstract>
<t> This document provides guidelines for authors and reviewers
of
specifications containing YANG data models, including IANA-maintained
modules. Recommendations and procedures are defined, which are
intended to increase interoperability and usability of Network
Configuration Protocol (NETCONF) and RESTCONF Protocol
implementations that utilize YANG modules. This document obsoletes
RFC 8407.
Also, this document updates RFC 8126 by providing additional
guidelines for writing the IANA considerations for RFCs that specify
IANA-maintained modules.
</t>
</abstract>
</front> </front>
<seriesInfo name="Internet-Draft" value="draft-ietf-netmod-rfc8407bis- 28"/> <seriesInfo name="Internet-Draft" value="draft-ietf-netmod-rfc8407bis- 28" />
</reference> </reference>
</references> </references>
</references> </references>
<?line 129?>
<section numbered="false" anchor="acknowledgments"> <section numbered="false" anchor="acknowledgments">
<name>Acknowledgments</name> <name>Acknowledgments</name>
<t>The content of this document was part of <xref target="I-D.ietf-netmod- <t>The content of this document was part of <xref
rfc8407bis"/>.</t> target="I-D.ietf-netmod-rfc8407bis"/>.</t>
<t>Mahesh Jethanandani suggested to offload this part from <xref target="I <t><contact fullname="Mahesh Jethanandani"/> suggested to offload this
-D.ietf-netmod-rfc8407bis"/>. part from <xref target="I-D.ietf-netmod-rfc8407bis"/>. Thanks to Mahesh
Thanks to Mahesh and Kent Watsen for the discussion and comments.</t> and <contact fullname="Kent Watsen"/> for the discussion and comments.</t>
<t>Thanks to Mallory Knodel for the genart review and Barry Leiba artart r <t>Thanks to <contact fullname="Mallory Knodel"/> for the GENART review
eview.</t> and <contact fullname="Barry Leiba"/> for the ARTART review.</t>
<t>Thanks Mike Bishop for the IESG review.</t> <t>Thanks <contact fullname="Mike Bishop"/> for the IESG review.</t>
</section> </section>
</back> </back>
<!-- ##markdown-source: <!-- [rfced] Please review the "Inclusive Language" portion of the online
H4sIAAAAAAAAA61X727bNhD/zqfg3C/rEDlJF6yd0H9u4rZZYzuNE2RBMQy0 Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language>
RFlEJFIlqRia4XfZs+zJdkdKsuW4yQrMX0yRx/t/vzsGQUCssBkPaW8g6VUR and let us know if any changes are needed. Updates of this nature typically
M8upVfRmMP5ARyouM07HLOeGXvC5MFYzK5TsETabaX4Ht+4R9kgEPOZKVyE1 result in more precise language, which is helpful for readers.
Nial42lC+svBswNCYhVJIAtprFliA8FtEkhucxUHOomQJhBMssBfCw6eEVPO
cmEMiLVVARdPh5fviSzzGdchQaKQREoaLk0JUqwuOQHFfiZMcwYKTgrulTaU
yZiOgPmc51zaHlkofTvXqiyAbMwtfqIpPBNy3iO3vIKdOCQ0oOPh5fFk/B6X
F8Npux6UVuWOOSHGAvs/WaYk6FhxQwoR0i9WRXvUKG01TwysqrxeWC0iu0cj
laMusAOOyVlRgOg/CGGlTZVG0YTCLymzzHttIOOKvhNc50y6I6XnTIq/nBIh
vSlzdg1mGHcWqVJajMPVdOA2eM5EFqIfqrcVkKLFpg86kPuSRiqF/5i+U2XE
Yib0DnETzeScuwOtMIl4LKzSXeHvgSjim/Jzz7o/a1i/VY7RNzT5LCS9LneI
/1iyBRddacepkGxT2ExkWX9Rvk0dsRchlcaw3UHqECGTjS+4dzoYD4LR5CQY
D0bDaeh4rX9NtezI+y5hG8KtH5gQOhlbJy6TacIyw7dFMj3nNqSptYUJ9/cX
i0Ufa6QPrPYZVMZcuhzar8CJQcE0qGO5NvuEBEFA2QzLNrLOuMtUGEy1Em9Q
IJSxoTblTiM6L0WMwaJKus1Siq8ll9wYqhKPCbk3GUsJC9N/YZxMvxbA1/zr
2qcX749d+SOyRBnTIqloqhY1M1+YIE9oCqAijC9WzWkKBxnk4Kxy+vW9QbmI
YZeQJxArCDrwiHwJLpc/gCQUtFrRmCdCIm/g6ZCrohDox4yAimQZitwRYLpc
dnNjtQKNpgWPRCLwWrXn3YhwJOIWdsBorwJ/VLyz2niOoAQk/nI55c48eniE
QVhb2Cfga8O3pWn+tRTAxaYMApxlD0kTPsytg/LSWDpr4t6nH9WC33G9R5Cq
wCQSkByJyjI4aMNCIaWksl4RsBICvxA29Ro0KQWe+mbuPZx2XtUfv+2IpwTT
SuVFVjWC63xuVDYu9E0QAGIfyrw+ZtaF96KrKzpWtgZ5zG7oCxQbg6G90dX0
srfn/+l44tYXw89XpxfDE1xPPw7OztoFqSmmHydXZyfr1frm8WQ0Go5P/GXY
pZ0t0hsNbuAEde5Nzi9PJ+PBWc8HseNZ7Vo4xFFIMLfQgAYxZYbE3ERazHxi
vTs+/+dvcKUvmmeHh79C0fiPF4fPj+BjkXLppSmJrnWf4KyKQJ/iTCMXTLCI
FcICbgGtoQbqWtKUa4z4T1/QM3+E9OUsKg6PXtcbaHBns/FZZ9P57P7Ovcve
iTu2dohpvdnZ3/J0V9/BTee78fvG5ss3MDBwGhy+ePOaeFjC5Dvu1uXyieGR
m21WQPOkmbUcIJy3mN2MWVVN7xF0tV08WOTcQGo6SRDssp7cXDUn4H3pClW7
yt2FZW3NlxJ0pGuytS4bRG5K2oF/WHkQeUUzoEM9kA+ivZ/PPAQsoANjNvpW
Bdnn6DbM6fu2VNuAaMJ5zGMy4xErjbeq0Crican5/XyHtW+2wro27ordC8NS
34A6ZluT+i4IF227AUQ5L2dgRgoKjmp08DFwSHUvBN+HX3uggLACm0TdmR5B
d1dMHmkNzCXLkN6ZgkX8Ve+gtyKTs5OQwDT4ffDuam8N7zWD30dnnh7ZP36J
jIfXKHv0SO+G6Uta1hi6ybIRXHuEQofBa/+7JeDP3SL+K7+dCq2tdJdSducT
1IBgJx0DhxvwEGjkbKsBmuH2Lv5bsh+U1rG3EfugLNfb2hcRUHVB6l6OZ1BD
GOK6napMRBs9dmMi0H5Ww3rbHHHa3r2uo9XTPh1Anyij1HUTSBVMF6mg6hdU
rV9rwDN3jzUGI7ywVTPZ+J4s6snPjyFdOHEYDIVVarz2sInrMRHFOzOZr8ha
6xqBV09dnFpy2cDVlnEIbo2/9MaTeQPAOvW/Oc+dgjqK+2GqtQ+4Vd412HAj
eNQauGsa67Qwt8ZDG6Jm3fhjYaLSAGE9Ms9YdIteGUS3Ui1gvp07LwKseKDm
8auee3r0Vn7IgVnODXIuezb9tYA0gyeGO1ku35wGJ/2tN/yLo4PnM2HccDxi
MKKm9DcOCkrwHzzeIPLzOfQur6tKkkyx2AtxfBOt8sc5XwK/Wzda1yIwOJ9Q
wWtmDZcuJTFHa09gBJCkeW+7cXTNAmAWUOCTxMd/e3XOJSqEJQjux9vvmAay
My5mDJLWrk/X7EbilsMDHcagomV0Opx+aAn/BRtRJA1zEQAA
Note that our script did not flag any words in particular, but this should
still be reviewed as a best practice.
--> -->
</rfc> </rfc>
 End of changes. 35 change blocks. 
194 lines changed or deleted 85 lines changed or added

This html diff was produced by rfcdiff 1.48.