]> YumaWorks

USA andy@yumaworks.com

Orange

France mohamed.boucadair@orange.com

Huawei

China bill.wu@huawei.com

Operations and Management Network Modeling 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.

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 This document requests IANA to update the reference for the "YANG Module Names" registry under the "YANG Parameters" registry group to also list to the RFC number that will be assigned to this document. 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 modules and submodules 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.

Operations and Manageability 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 defines 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 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] 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. 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 IANA YumaWorks Orange Huawei 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.

Acknowledgments The content of this document was part of . Mahesh Jethanandani suggested to offload this part from . Thanks to Mahesh and Kent Watsen for the discussion and comments.