An Update to YANG Module Names Registration YumaWorks
United States of America andy@yumaworks.com
Orange
France mohamed.boucadair@orange.com
Huawei
China bill.wu@huawei.com
OPS netmod NETCONF RESTCONF Automation This document amends the IANA guidance on the uniqueness of YANG module and submodule names. The document updates RFC 6020 to clarify how modules and their revisions are handled by IANA.
Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at .
Copyright Notice Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents () in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.
Table of Contents
  • .  Introduction
  • .  Requirements Notation
  • .  IANA Considerations
    • .  Update YANG Parameters Registry
    • .  Revisions of Published Modules
  • .  Operational Considerations
  • .  Security Considerations
  • .  References
    • .  Normative References
    • .  Informative References
  • Acknowledgments
  • Authors' Addresses
Introduction defines a registry for YANG module and submodule names, called "YANG Module Names" . Specifically, IANA considerations to register YANG module and submodule names are specified in . 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. This document amends the guidance on the uniqueness of names () to comply with the IANA practices for registering modules and their revisions.
Requirements Notation The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.
IANA Considerations
Update YANG Parameters Registry IANA has updated the "YANG Module Names" registry under the "YANG Parameters" registry group to list this document as an additional reference. This update is needed because the procedure in this document is authoritative for assigning names in that registry.
Revisions of Published Modules This document amends the guidance on the uniqueness of names, initially defined in , as follows: OLD:
All module and submodule names in the registry MUST be unique. All XML namespaces in the registry MUST be unique.
NEW:
Modules and their revisions are maintained in the registry. All initial version module and submodule names in the registry MUST be unique. All XML namespaces of initial version modules in the registry MUST be unique. All module and submodule revisions MUST have the same name as the one in the initial version of the module and submodule. All module revisions MUST have the same XML namespace as the initial version of the module.
Operational Considerations This document aligns an IANA policy with the practice for handling YANG module names (). As such, there are no new operations or manageability requirements introduced by this document.
Security Considerations This document defines a new IANA action () and an update () to an IANA registration procedure defined in . It does not introduce any new or increased security risks that need to be discussed.
References Normative References Key words for use in RFCs to Indicate Requirement Levels 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. YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF) 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] Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words 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. Informative References YANG Module Names IANA Guidelines for Authors and Reviewers of Documents Containing YANG Data Models YumaWorks Orange Huawei Work in Progress
Acknowledgments The content of this document was part of . suggested to offload this part from . Thanks to Mahesh and for the discussion and comments. Thanks to for the GENART review and for the ARTART review. Thanks for the IESG review.
Authors' Addresses YumaWorks
United States of America andy@yumaworks.com
Orange
France mohamed.boucadair@orange.com
Huawei
China bill.wu@huawei.com