Subject: [L2sm] [Technical Errata Reported] RFC8466 (6699)

From: Alice Russo <[email-masked]>
Date: Fri, 1 Oct 2021 09:09:41 -0700

FYI, in this report, the RFC number has been corrected from RFC 8644 to RFC 8466.
Please see below for details.

RFC Editor/ar

> On Oct 1, 2021, at 1:17 AM, RFC Errata System <[email-masked]> wrote:
> 
> The following errata report has been submitted for
RFC 8466, "A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6699
> 
> --------------------------------------
> Type: Technical
> Reported by: Mohamed Boucadair <[email-masked]>
> 
> Section: 8
> 
> Original Text
> -------------
>                  container lacp {
>                    if-feature "lacp";
>                    leaf enabled {
>                      type boolean;
>                      default "false";
>                      description
>                        "LACP on/off.  By default, LACP is disabled.";
>                    }
>                    leaf mode {
>                      type neg-mode;
>                      description
>                        "LACP mode.  LACP modes have active mode and
>                         passive mode ('false').  'Active mode' means
>                         initiating the auto-speed negotiation and
>                         trying to form an Ethernet channel with the
>                         other end.  'Passive mode' means not initiating
>                         the negotiation but responding to LACP packets
>                         initiated by the other end (e.g., full duplex
>                         or half duplex).";
>                    }
> 
> 
> 
> Corrected Text
> --------------
> 
>                  container lacp {
>                    if-feature "lacp";
>                    leaf enabled {
>                      type boolean;
>                      default "false";
>                      description
>                        "LACP on/off.  By default, LACP is disabled.";
>                    }
>                    leaf mode {
>                      type identityref {
>                        base lacp-mode;
>                      }
>                      description
>                        "LACP mode. LACP modes have active mode and
>                         passive mode ('false').  'Active mode' means
>                         initiating the auto-speed negotiation and
>                         trying to form an Ethernet channel with the
>                         other end.  'Passive mode' means not initiating
>                         the negotiation but responding to LACP packets
>                         initiated by the other end (e.g., full duplex
>                         or half duplex).";
>                    }
> 
> 
> Also, make this change: 
> 
> OLD:
> 
>           |  +--rw lag-interfaces {lag-interface}?
>           |  |  +--rw lag-interface* [index]
>           |  |     +--rw index    string
>           |  |     +--rw lacp {lacp}?
>           |  |        +--rw enabled?           boolean
>           |  |        +--rw mode?              neg-mode
> 
> NEW:
> 
>           |  +--rw lag-interfaces {lag-interface}?
>           |  |  +--rw lag-interface* [index]
>           |  |     +--rw index    string
>           |  |     +--rw lacp {lacp}?
>           |  |        +--rw enabled?           boolean
>           |  |        +--rw mode?              identityref
> 
> 
> Notes
> -----
> The LACP mode can be set to active or passive, which is not what neg-mode is supposed to cover. lacp-mode identity should be used, instead.
> 
> 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. 
> 
> --------------------------------------
RFC8466 (draft-ietf-l2sm-l2vpn-service-model-10)
> --------------------------------------
Title               : A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery
Publication Date    : October 2018
Author(s)           : B. Wen, G. Fioccola, Ed., C. Xie, L. Jalil
Category            : Standards Track 
Source              : L2VPN Service Model
Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG