[L2sm] [Errata Rejected] RFC8466 (6384)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 12 January 2024 17:40 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: l2sm@ietfa.amsl.com
Delivered-To: l2sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB60EC14F68C; Fri, 12 Jan 2024 09:40:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MbTBK_mUC6gC; Fri, 12 Jan 2024 09:40:35 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C91D5C14F602; Fri, 12 Jan 2024 09:40:35 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 9E2951B65DCC; Fri, 12 Jan 2024 09:40:35 -0800 (PST)
To: jlucek@juniper.net, 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: <20240112174035.9E2951B65DCC@rfcpa.amsl.com>
Date: Fri, 12 Jan 2024 09:40:35 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/37fwKwha0lmS1fl8MpbXUrD1InA>
Subject: [L2sm] [Errata Rejected] RFC8466 (6384)
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" <l2sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2sm>, <mailto:l2sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2sm/>
List-Post: <mailto:l2sm@ietf.org>
List-Help: <mailto:l2sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2sm>, <mailto:l2sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jan 2024 17:40:39 -0000
The following errata report has been rejected 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/eid6384 -------------------------------------- Status: Rejected Type: Editorial Reported by: Julian Lucek <jlucek@juniper.net> Date Reported: 2021-01-08 Rejected by: Robert Wilton (IESG) Section: 8 Original Text ------------- identity pbb-evpn { base service-type; description "Provider Backbone Bridge (PBB) service type using EVPNs as specified in RFC 7432."; } Corrected Text -------------- identity evpn { base service-type; description "EVPN service type as specified in RFC 7432."; } Notes ----- The mention of PBB is a mistake, it should be normal (non-PBB) EVPN, given that Section 3.1 lists EVPN and not PBB-EVPN among the supported L2VPN types. However, the reference to RFC 7432 in the original text box above is correct, as that RFC deals with EVPN, not PBB-EVPN. (n.b. see erratum 5921 that has the "opposite" interpretation, i.e. that pbb-evpn is correct but that the RFC number is wrong) --VERIFIER NOTES-- I think that this errata report can be regarded as a duplicate of 5922, that I have resolved as "held for document update". Certainly, I don't think that it is possible to infer consensus that the YANG module is wrong by defining pbb-evpn but the accompanying text is correct. -------------------------------------- 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 Rejected] RFC8466 (6384) RFC Errata System