Re: [netmod] [Editorial Errata Reported] RFC8519 (7313)

[Mahesh Jethanandani <[e-mail]>]

There was a lot of discussion on the usage of what prefix should be used when importing a module, possibly after this draft was published. However, it is a BCP, and most tools will not complain if a prefix other than what is defined in the module is used. I am not sure if a BCP rises to the level of an errata.

Thanks.

> On Jan 18, 2023, at 7:02 AM, RFC Errata System <[e-mail]> wrote:
> 
> The following errata report has been submitted for RFC8519,
> "YANG Data Model for Network Access Control Lists (ACLs)".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7313
> 
> --------------------------------------
> Type: Editorial
> Reported by: Mohamed Boucadair <[e-mail]>
> 
> Section: A.1
> 
> Original Text
> -------------
>   The following figure is the tree diagram of example-newco-acl.  In
>   this example, /ietf-acl:acls/ietf-acl:acl/ietf-acl:aces/ietf-acl:ace/
>   ietf-acl:matches are augmented with two new choices: protocol-
>   payload-choice and metadata.  The protocol-payload-choice uses a
>   grouping with an enumeration of all supported protocol values.
>   Metadata matches apply to fields associated with the packet, that are
>   not in the packet header, such as overall packet length.  In another
>   example, /ietf-acl:acls/ietf-acl:acl/ietf-acl:aces/ietf-acl:ace/
>   ietf-acl:actions are augmented with a new choice of actions.
> 
> Corrected Text
> --------------
>   The following figure is the tree diagram of example-newco-acl.  In
>   this example, /acl:acls/acl:acl/acl:aces/acl:ace/acl:matches
>   are augmented with two new choices: protocol-payload-choice and
>   metadata.  The protocol-payload-choice uses a
>   grouping with an enumeration of all supported protocol values.
>   Metadata matches apply to fields associated with the packet, that are
>   not in the packet header, such as overall packet length.  In another
>   example, /acl:acls/acl:acl/acl:aces/acl:ace/acl:actions 
>   are augmented with a new choice of actions.
> 
> Notes
> -----
> The prefix is "acl" not "ietf-acl"
> 
> ==
> module ietf-access-control-list {
>  yang-version 1.1;
>  namespace "urn:ietf:params:xml:ns:yang:ietf-access-control-list";
>  prefix acl;
>  ...
> ==
> 
> 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. 
> 
> --------------------------------------
> RFC8519 (draft-ietf-netmod-acl-model-21)
> --------------------------------------
> Title               : YANG Data Model for Network Access Control Lists (ACLs)
> Publication Date    : March 2019
> Author(s)           : M. Jethanandani, S. Agarwal, L. Huang, D. Blair
> Category            : PROPOSED STANDARD
> Source              : Network Modeling
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG


Mahesh Jethanandani
[e-mail]