RFC Errata
RFC 8407, "Guidelines for Authors and Reviewers of Documents Containing YANG Data Models", October 2018
Note: This RFC has been updated by RFC 8819
Source of RFC: netmod (ops)
Errata ID: 7416
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Mohamed Boucadair
Date Reported: 2023-04-07
Section 4.8 says:
revision "2017-12-11" { description "Added support for YANG 1.1 actions and notifications tied to data nodes. Clarify how NACM extensions can be used by other data models."; reference "RFC 8407: Network Configuration Protocol (NETCONF) Access Control Model"; }
It should say:
revision "2017-12-11" { description "Added support for YANG 1.1 actions and notifications tied to data nodes. Clarify how NACM extensions can be used by other data models."; reference "RFC UUUU: Network Configuration Access Control Model"; }
Notes:
This example is supposed to illustrate the use of revisions in unpublished updates. Having an RFC under the reference clause is inconsistent:
o published: A stable release of a module or submodule. For
example, the "Request for Comments" described in Section 2.1 of
[RFC2026] is considered a stable publication.
o unpublished: An unstable release of a module or submodule. For
example the "Internet-Draft" described in Section 2.2 of [RFC2026]
is considered an unstable publication that is a work in progress,
subject to change at any time.
I suspect that RFC XXXX in draft-ietf-netmod-rfc6087bis was erroneously replaced by RFC 8407:
revision "2017-12-11" {
description
"Added support for YANG 1.1 actions and notifications tied to
data nodes. Clarify how NACM extensions can be used by other
data models.";
reference
"RFC XXXX: Network Configuration Protocol (NETCONF)
Access Control Model";
}