<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!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.3.8) -->
<?rfc strict="yes"?>
<?rfc comments="yes"?>
<?rfc docmapping="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-netmod-rfc6020-iana-update-00" category="std" consensus="true" submissionType="IETF" updates="6020" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.28.1 -->
  <front>
    <title abbrev="YANG Module Names">Update to YANG Module Names Registration</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-netmod-rfc6020-iana-update-00"/>
    <author fullname="Andy Bierman">
      <organization>YumaWorks</organization>
      <address>
        <postal>
          <country>USA</country>
        </postal>
        <email>andy@yumaworks.com</email>
      </address>
    </author>
    <author fullname="Mohamed Boucadair" role="editor">
      <organization>Orange</organization>
      <address>
        <postal>
          <country>France</country>
        </postal>
        <email>mohamed.boucadair@orange.com</email>
      </address>
    </author>
    <author fullname="Qin Wu">
      <organization>Huawei</organization>
      <address>
        <postal>
          <country>China</country>
        </postal>
        <email>bill.wu@huawei.com</email>
      </address>
    </author>
    <date year="2025" month="May" day="13"/>
    <area>Operations and Management</area>
    <workgroup>Network Modeling</workgroup>
    <keyword>NETCONF</keyword>
    <keyword>RESTCONF</keyword>
    <keyword>Automation</keyword>
    <abstract>
      <?line 54?>

<t>This document amends the IANA guidance on the uniqueness of YANG module and submodule names.</t>
      <t>The document updates RFC 6020 to clarify how modules and their revisions are handled by IANA.</t>
    </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>
  <middle>
    <?line 60?>

<section anchor="introduction">
      <name>Introduction</name>
      <t><xref target="RFC6020"/> defines a registry for YANG module and submodule 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"/>.
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>
      <t>This document amends the guidance on the uniqueness of names (<xref section="14" sectionFormat="of" target="RFC6020"/>)
to comply with the IANA practices for registering modules and their revisions.</t>
    </section>
    <section anchor="requirements-notation">
      <name>Requirements Notation</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

</section>
    <section anchor="sec-iana">
      <name>IANA Considerations</name>
      <section anchor="update-yang-parameters-registry">
        <name>Update YANG Parameters Registry</name>
        <t>This document requests IANA to update the reference for
the "YANG Module Names" registry under the "YANG Parameters" registry group <xref target="IANA-MOD-NAMES"/>
to point to the RFC number that will be assigned to this document.</t>
      </section>
      <section anchor="revisions-of-published-modules">
        <name>Revisions of Published Modules</name>
        <t>This document amends the guidance on the uniqueness of names, initially defined in <xref section="14" sectionFormat="of" target="RFC6020"/>, as follows:</t>
        <dl newline="true">
          <dt>OLD:</dt>
          <dd>
            <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>
          </dd>
          <dt>NEW:</dt>
          <dd>
            <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 <bcp14>MUST</bcp14> be unique.</t>
          </dd>
          <dt/>
          <dd>
            <t>All XML namespaces of initial version modules in the registry <bcp14>MUST</bcp14> be unique.</t>
          </dd>
          <dt/>
          <dd>
            <t>All modules and submodules revisions <bcp14>MUST</bcp14> have the same 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 namespace as the initial version of the module.</t>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>This document defines an update to an IANA registration procedure defined in <xref target="RFC6020"/>.
It does not introduce any new or increased security risks that need to be discussed.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC6020">
          <front>
            <title>YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)</title>
            <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/>
            <date month="October" year="2010"/>
            <abstract>
              <t>YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF 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</title>
            <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 signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, 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</title>
            <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 protocol 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 anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="IANA-MOD-NAMES" target="https://www.iana.org/assignments/yang-parameters/">
          <front>
            <title>YANG Module Names</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="I-D.ietf-netmod-rfc8407bis">
          <front>
            <title>Guidelines for Authors and Reviewers of Documents Containing YANG Data Models</title>
            <author fullname="Andy Bierman" initials="A." surname="Bierman">
              <organization>YumaWorks</organization>
            </author>
            <author fullname="Mohamed Boucadair" initials="M." surname="Boucadair">
              <organization>Orange</organization>
            </author>
            <author fullname="Qin Wu" initials="Q." surname="Wu">
              <organization>Huawei</organization>
            </author>
            <date day="5" month="May" year="2025"/>
            <abstract>
              <t>   This memo provides guidelines for authors and reviewers of
   specifications containing YANG modules, 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>
          <seriesInfo name="Internet-Draft" value="draft-ietf-netmod-rfc8407bis-25"/>
        </reference>
      </references>
    </references>
    <?line 124?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The content of this document was part of <xref target="I-D.ietf-netmod-rfc8407bis"/>.</t>
      <t>Mahesh Jethanandani suggested to offload this part from <xref target="I-D.ietf-netmod-rfc8407bis"/>.
Thanks to Mahesh for the discussion and comments.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA61XbW/bNhD+zl/BuV+2IXKSNlg7oW9u4iwZYju1E3RBUQy0
RFlEJFIlqQiakf+y37JftjtSsi3HTTZs/mKROt5zL88dT0EQECtsxkPauy5i
Zjm1it4Mxr/QkYrLjNMxy7mhU74QxmpmhZI9wuZzze/gyAPBHolAx0LpOqTG
xqR0Ok1Ifzp4fkBIrCIJYiGNNUtsILhNAsltruJAJxHKBIJJFvhjwcEBMeU8
F8YArK0LOHg+vDolssznXIcEhUISKWm4NCWgWF1yAoa9IExzBgZOCu6NNpTJ
mI5A+YLnXNoeqZS+XWhVFiA25haX6ArPhFz0yC2vYScOCQ3oeHh1PBmf4uN0
OFs9D0qrcqecEGNB/e8sUxJsrLkhhQjpZ6uiPWqUtponBp7qvHmwWkR2j0Yq
R1tgBwKTs6IA6C+EsNKmSiM0ofBLyizzURvIuKYfBNc5k+6V0gsmxR/OiJDe
lDn7BG4Y9y5SpbSYh+vZwG3wnIksxDjU72sQRY9NH2wgD5FGKoX/mH5QZcRi
JvQOuIlmcsHdC62QQTwWVuku+CkIRXwTP/eq+/NW9XvlFH3Dko9C0k/lDviz
klVcdNGOUyHZJthcZFm/Kt+nTthDSKUxbXdAHSJksrGCc+eD8SAYTU6C8WA0
nIVO1/rXlsoO3ncFVync+oELocPYeuOYTBOWGb4NyfSC25Cm1hYm3N+vqqqP
NdIHVfsMKmMhHYf2awhiUDAN5liuzT4hQRBQNseyjaxz7ioVBqlW4gkKgjI2
1KbcWUQXpYgxWVRJt1lK8bXkkhtDVeJ7Qu5dxlLCwvQrzJPpNwB8rb+pfTo9
PXblj50lypgWSU1TVTXKfGECntAUmoowvlg1pym8yICD89rZ1/cO5SKGXUKe
Qa4g6aAj8iW4XH4HSAh0f09jngiJukGn61w1hUQ/5QRUJMsQckeC6XLZ5cb9
PVg0K3gkEoHH6j0fRmxHIl61HXDam8CfhHdeG68RjADiL5cz7tyjh0eYhLWH
fQKxNnwbTfOvpQAtNmWQ4Cx7DE34NK8ClJfG0nmb9z49UxW/43qPoFSBJBJA
jkRlGbxYpYUCpaSy3hDwEhJfCZt6C1pKQaS+yb3HaedN/f7bgfiBIK1UXmR1
C9zwuTXZuNS3SYAW+xjz+sisqY+iqys6VrZp8shuuBcoXgyG9kbXs6venv+n
44l7ng4/Xp9Phyf4PDsbXFysHkgjMTubXF+crJ/WJ48no9FwfOIPwy7tbJHe
aHADb9Dm3uTy6nwyHlz0fBI7kdXuCoc8CgnuFhq6QUyZITE3kRZzT6wPx5d/
/Qmh9EXz/PDwZygav3h1+PIIFlXKpUdTEkPrlhCsmsA9xZlGLUiwiBXCQt8C
WUMN1LWkKdeY8R8/Y2S+hPT1PCoOj942G+hwZ7ONWWfTxezhzoPDPog7tnbA
rKLZ2d+KdNfewU1n3cZ9Y/P1OxgYOA0OX717S3xbQvIdd+ty+czwyM029yDz
jDazlmsIl6ue3Y5Z9Xa5YFlzA2R0uiG9ZTOrufpNIN7SlaZ2tbqre62qvJRg
FV2LrdE3hNxctKPjYa0VCoiFNqAO7O1+GvMFX8F9i9zzFxNwzcltuNJ37k9X
jR5q+bKcZ8KkIOxNNv+tWewBM4UV2JGba+CJVuqY69uagSFgGdI7U7CIv+kd
9O7J5OIkJDB6/bte6oi+7qWNgt9GF14e1T99iIyHnxB79MRFCaOOtKx1dFNl
C9xEhEI7x2P/uycQz90Q/1TfZkdeWWQ2/HTHUnbnOW8A2uFj6nAD5u4WadsQ
sA23d7ncRX8creNxC/solrtKKLCu1MLWWx1hm+OrgUWualvhwhW83vj6gmtN
RTwuIe8ddm+OBuegT3F/L4tmSELXayp5BTMobEbwfWTgrGnN08LcGl/EkvvC
hSzFwkSlAcFm+pqz6BbdGkS3UlUwKi3cJQlF47sAj9/03BQLlePuSxgL3Ezg
IrPpcAUhhGnVvVku350HJ/2tz8FXRwcv58K4OWvEYNpJ6a8cDJSQQ/gOgDQu
FtAUva0qSTLFYg/i9CZa5U9rvgJ9t25KayBwVsAcNp5jxJEz7adan/wNCe7M
7TMPAAA=

-->

</rfc>
