| Internet-Draft | YANG Module Names | April 2025 |
| Bierman, et al. | Expires 27 October 2025 | [Page] |
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.¶
This note is to be removed before publishing as an RFC.¶
Discussion of this document takes place on the Network Modeling Working Group mailing list (netmod@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/netmod/.¶
Source for this draft and an issue tracker can be found at https://github.com/boucadair/rfc8407bis.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 27 October 2025.¶
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 (https://trustee.ietf.org/license-info) 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.¶
[RFC6020] defines a registry for YANG module and submodule names, called "YANG Module Names" [IANA-MOD-NAMES].¶
Specifically, IANA considerations to register YANG module and submodule names are specified in Section 14 of [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.¶
This document amends the guidance on the uniqueness of names (Section 14 of [RFC6020]) to comply with the IANA practices for registering modules and their revisions.¶
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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
This document requests IANA to update the reference for the "YANG Module Names" registry under the "YANG Parameters" registry group [IANA-MOD-NAMES] to point to the RFC number that will be assigned to this document.¶
This document amends the guidance on the uniqueness of names, initially defined in Section 14 of [RFC6020], as follows:¶
All module and submodule names in the registry MUST be unique.¶
All XML namespaces in the registry MUST be unique.¶
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.¶
This document defines an update to an IANA registration procedure defined in [RFC6020]. It does not introduce any new or increased security risks that need to be discussed.¶
The content of this document was part of [I-D.ietf-netmod-rfc8407bis].¶
Mahesh Jethanandani suggested to offload this part from [I-D.ietf-netmod-rfc8407bis]. Thanks to Mahesh for the discussion and comments.¶