I'm okay with this Errata. Kent // contributor
> On Apr 15, 2026, at 4:08 AM, RFC Errata System <[email protected]> > wrote: > > The following errata report has been submitted for RFC9907, > "Guidelines for Authors and Reviewers of Documents Containing YANG Data > Models". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid8880 > > -------------------------------------- > Type: Editorial > Reported by: Mohamed BOUCADAIR <[email protected]> > > Section: 4.30.3.2 > > Original Text > ------------- > IANA is requested to add this note to the registry: > > New values must not be directly added to the "iana-foo" YANG > module. They must instead be added to the "foo" registry. > > Corrected Text > -------------- > IANA is requested to add this note to the registry: > > New values must not be directly added to the "iana-foo" YANG > module. They must instead be added to the "foo" registry. > > IANA is requested to add this note to [reference-to-the-iana-foo- > registry]: > > When this registry is modified, the YANG module "iana-foo" > [IANA_FOO_URL] must be updated as defined in RFC IIII. > > Notes > ----- > * The note was present in the approved draft, but was lost during editing of > that section. The note was at the button of the template but, as can be seen > in Section 4.30.3.1, it was moved upper to group both notes. > > * Section 5.3.1 (Requirements for All Modules) says: > > CURRENT: > > In addition, when the module is published, IANA must add the > following notes to: > > The YANG Module Names registry: > New values must not be directly added to the "iana-foo" YANG > module. They must instead be added to the "foo" registry. > > The underlying registry: > When this registry is modified, the YANG module "iana-foo" > [IANA_FOO_URL] must be updated as defined in RFC IIII. > > * IANA will always implement these two actions per 5.3.1, but better to have > the templates in 4.30.3.1/4.30.3.2 consistent. > > Instructions: > ------------- > This erratum is currently posted as "Reported". (If it is spam, it > will be removed shortly by the RFC Production Center.) Please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party > will log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC9907 (draft-ietf-netmod-rfc8407bis-28) > -------------------------------------- > Title : Guidelines for Authors and Reviewers of Documents > Containing YANG Data Models > Publication Date : March 2026 > Author(s) : A. Bierman, M. Boucadair, Ed., Q. Wu > Category : BEST CURRENT PRACTICE > Source : Network Modeling > Stream : IETF > Verifying Party : IESG > > _______________________________________________ > netmod mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
