Hi, I'm trying to decide how to process this errata.
Regarding the issue raised in the errata, I think that RFC 7950 is probably inconsistent because section 5.1.1 allows an import by revision-date to be updated to a newer revision-date, but section 11 seems to implicitly exclude it. It is worth noting that section 11 doesn't seem to make any mention of adding or changing import statements at all, so perhaps this errata should be broadened to also cover that, or is that already intended to be covered by the catch all paragraph. The YANG module revision handling document could also be updated to clarify these two points. Any thoughts for the authors or WG on how to process this errata? Regards, Rob > -----Original Message----- > From: RFC Errata System <[email protected]> > Sent: Tuesday, July 12, 2022 4:42 PM > To: [email protected]; [email protected]; Rob Wilton (rwilton) > <[email protected]>; [email protected]; [email protected]; > [email protected] > Cc: [email protected]; [email protected]; [email protected] > Subject: [Technical Errata Reported] RFC7950 (7021) > > The following errata report has been submitted for RFC7950, > "The YANG 1.1 Data Modeling Language". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid7021 > > -------------------------------------- > Type: Technical > Reported by: Balazs Lengyel <[email protected]> > > Section: 11 > > Original Text > ------------- > 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. > > Corrected Text > -------------- > 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. > > Instructions: > ------------- > This erratum is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC7950 (draft-ietf-netmod-rfc6020bis-14) > -------------------------------------- > Title : The YANG 1.1 Data Modeling Language > Publication Date : August 2016 > Author(s) : M. Bjorklund, Ed. > Category : PROPOSED STANDARD > Source : Network Modeling > Area : Operations and Management > Stream : IETF > Verifying Party : IESG _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
