[L2sm] [Errata Held for Document Update] RFC8466 (6699)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 02 October 2023 14:47 UTC

To: mohamed.boucadair@orange.com, bin_wen@comcast.com, giuseppe.fioccola@tim.it, xiechf.bri@chinatelecom.cn, luay.jalil@verizon.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rwilton@cisco.com, iesg@ietf.org, l2sm@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20231002144732.14029E7292@rfcpa.amsl.com>
Date: Mon, 02 Oct 2023 07:47:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/bj_uTb8ryS5NegY_onYmXMs9mvk>
Subject: [L2sm] [Errata Held for Document Update] RFC8466 (6699)
Precedence: list

The following errata report has been held for document update 
for RFC8466, "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

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Mohamed Boucadair <mohamed.boucadair@orange.com>
Date Reported: 2021-10-01
Held by: Rob Wilton (IESG)

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.

The errata looks valid, but given this requires a new revision of the YANG module a new RFC needs to be published.

--------------------------------------
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            : PROPOSED STANDARD
Source              : L2VPN Service Model
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG

[L2sm] [Errata Held for Document Update] RFC8466 … RFC Errata System