[L2sm] [Editorial Errata Reported] RFC8466 (6384)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 08 January 2021 16:11 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 EBEF53A10B7 for <l2sm@ietfa.amsl.com>; Fri, 8 Jan 2021 08:11:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YsvZoq2imdIa for <l2sm@ietfa.amsl.com>; Fri, 8 Jan 2021 08:11:20 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B43A83A10B1 for <l2sm@ietf.org>; Fri, 8 Jan 2021 08:11:20 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 62A65F40720; Fri, 8 Jan 2021 08:11:15 -0800 (PST)
To: bin_wen@comcast.com, giuseppe.fioccola@tim.it, xiechf.bri@chinatelecom.cn, luay.jalil@verizon.com, warren@kumari.net, rwilton@cisco.com, adrian@olddog.co.uk, bill.wu@huawei.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: jlucek@juniper.net, l2sm@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20210108161115.62A65F40720@rfc-editor.org>
Date: Fri, 08 Jan 2021 08:11:15 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/Zv54CSpRmModaUIyBK44JwDpHNs>
X-Mailman-Approved-At: Fri, 08 Jan 2021 08:15:23 -0800
Subject: [L2sm] [Editorial Errata Reported] RFC8466 (6384)
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Jan 2021 16:11:22 -0000
The following errata report has been submitted 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 -------------------------------------- Type: Editorial Reported by: Julian Lucek <jlucek@juniper.net> 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) 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 : PROPOSED STANDARD Source : L2VPN Service Model Area : Operations and Management Stream : IETF Verifying Party : IESG
- [L2sm] [Editorial Errata Reported] RFC8466 (6384) RFC Errata System