Cisco Systems

per.ietf@ionio.se

OPS Area NETMOD Working Group This document presents YANG module file name convention. The convention extends the current YANG module file name using revision&nbhy;date, with the YANG semantic version extension. The YANG semantic version extension allows for an informative version to be associated with a particular YANG module revision. In the YANG module versioning work it was previously defined in that file names could use the revision label (YANG Semantic version extension) instead of the revision date, which is standardized in . This work was removed in an attempt to progress the module versioning work, but the YANG versioning design team was tasked to address it by the NETMOD WG. This draft extends YANG module file names conformity with the possibility to use revision label in addition to revision date.

This document defines the YANG module file convention. It extends the current convention defined in , which uses revision-date, with the YANG semantic version extension defined in .

The motivation for using YANG semantic version instead of revision date is that it carries information to the user. A revision date only tells the user that it has been updated, while, for instance, a YANG Semver version can tell the user about the module's compatibility level at a glance. Having this information available as early as possible, i.e. in the module file name, makes it possible to quickly identify the module revision; compared to searching in the file contents and checking the revisions. Having the YANG semantic version visible in the file name will make it easier to handle large sets of YANG modules. The YANG module file name schema described in this draft is already deployed in the industry. Now is the time to standardize before several proprietary solutions emerge. One possibility is to propose a standard that gains operational experience. Experiments that have updated tooling to handle YANG semantic version in the YANG module file name according to this draft have shown that it is a relatively small effort to do so. However, it is recognized that the migration of all tooling within the industry will take time.

This section updates , , and . If a revision has an associated YANG semantic version (ys:version) then it MAY use the YANG semantic version instead of the revision date in the file name of a YANG file, where it takes the form:

E.g., acme-router-module@2024-05-15.yang or acme&nbhy;router&nbhy;module#2.0.3.yang. In short, the YANG semantic version file name scheme is recommended in order to simplify for module consumers, i.e. to convey compatibility status at a glance without needing to read the module. YANG module (or submodule) files MAY be identified using either revision-date or YANG semantic version (ys:version). Typically, only one file name SHOULD exist for the same module (or submodule) revision. Two file names, one with the revision date and another with the YANG semantic version, MAY exist for the same module (or submodule) revision, e.g., when migrating from one scheme to the other.

As can be seen above, all valid identifiers for YANG semantic version are valid in the filename as well. The following example is a valid YANG module file name

One consequence of this is that there might exist two child modules of version 2.0.0 with the same X.Y.Z digits (2.0.1) but different version labels:

There are currently no known publicly available tools that support the YANG semantic version file name schema. There are known proprietary tooling that already uses the file name schema presented in this document. At the IETF 119 Hackathon, there was a project that investigated the feasibility to modify popular YANG tooling to support the proposed schema. There was a successful attempt to modify pyang to support the file name schema and also "recommended-min" previously included in . Furthermore, there were efforts in researching yanger and libyang to support the schema, but the hackathon ended before these projects could be concluded.

There are no security considerations for this draft.

The author would like to thank Joe Clarke, Reshad Rahman, for their excellent technical reviews, support, and guidance.