RFC 7950, "The YANG 1.1 Data Modeling Language", August 2016

Note: This RFC has been updated by RFC 8342, RFC 8526

Errata ID: 7021
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Balazs Lengyel
Date Reported: 2022-07-12

Section 11 says:

A definition in a published module may be revised in any of the
   following ways:

   o  An "enumeration" type may have new enums added, provided the old
      enums's values do not change.  Note that inserting a new enum
      before an existing enum or reordering existing enums will result
      in new values for the existing enums, unless they have explicit
      values assigned to them.

It should say:

A definition in a published module may be revised in any of the
   following ways:

   o  The "revision-date" substatement of an existing "import" statement 
      may get a changed argument.


   o  An "enumeration" type may have new enums added, provided the old
      enums's values do not change.  Note that inserting a new enum
      before an existing enum or reordering existing enums will result
      in new values for the existing enums, unless they have explicit
      values assigned to them.

Notes:

In section 5.1.1 it is stated that a module may be republished with an updated "import"
statement. This is needed, otherwise a user of the revision-date statement (inside an import) would never be able to migrate to a newer version of the imported module.

However in section 11. Updating a Module this change is not listed in the list of allowed updates, thus it is forbidden.

Report New Errata