Re: [netmod] [Editorial Errata Reported] RFC8407 (7416)

[Chris Smiley <[e-mail]>]

Hi Rob,

We are unable to verify this erratum that the submitter marked as editorial. 
Please note that we have changed the “Type” of the following errata 
report to “Technical”. As Stream Approver, please review and set the 
Status and Type accordingly (see the definitions at 
https://www.rfc-editor.org/errata-definitions/).

You may review the report at: 
https://www.rfc-editor.org/errata/eid7416

Please see https://www.rfc-editor.org/how-to-verify/ for further 
information on how to verify errata reports.

Further information on errata can be found at: 
https://www.rfc-editor.org/errata.php.

Thank you.

RFC Editor/cs


> On Apr 7, 2023, at 5:50 AM, RFC Errata System <[e-mail]> wrote:
> 
> The following errata report has been submitted for RFC8407,
> "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/eid7416
> 
> --------------------------------------
> Type: Editorial
> Reported by: Mohamed Boucadair <[e-mail]>
> 
> Section: 4.8
> 
> Original Text
> -------------
>      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";
>      }
> 
> Corrected Text
> --------------
>      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";
>      }
> 
> 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. 
> 
> --------------------------------------
> RFC8407 (draft-ietf-netmod-rfc6087bis-20)
> --------------------------------------
> Title               : Guidelines for Authors and Reviewers of Documents Containing YANG Data Models
> Publication Date    : October 2018
> Author(s)           : A. Bierman
> Category            : BEST CURRENT PRACTICE
> Source              : Network Modeling
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG
>