[L2sm] [Technical Errata Reported] RFC8466 (6922)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 05 April 2022 09:20 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 679C03A1FD2 for <l2sm@ietfa.amsl.com>; Tue, 5 Apr 2022 02:20:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 3ayJ8mGEFgwU for <l2sm@ietfa.amsl.com>; Tue, 5 Apr 2022 02:20:36 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 075693A1B15 for <l2sm@ietf.org>; Tue, 5 Apr 2022 02:20:35 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 1C9C43BA9D; Tue, 5 Apr 2022 02:20:35 -0700 (PDT)
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
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: mohamed.boucadair@orange.com, l2sm@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220405092035.1C9C43BA9D@rfcpa.amsl.com>
Date: Tue, 05 Apr 2022 02:20:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/kpqUscaCSYMMExRsz60R1ukVNrY>
X-Mailman-Approved-At: Tue, 05 Apr 2022 03:24:40 -0700
Subject: [L2sm] [Technical Errata Reported] RFC8466 (6922)
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: Tue, 05 Apr 2022 09:20:41 -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/eid6922 -------------------------------------- Type: Technical Reported by: Mohamed Boucadair <mohamed.boucadair@orange.com> Section: 5.5.2.1 Original Text ------------- <svc-bandwidth> <bandwidth> <direction>input-bw</direction> <type>bw-per-cos</type> <cir>450000000</cir> <cbs>20000000</cbs> <eir>1000000000</eir> <ebs>200000000</ebs> </bandwidth> </svc-bandwidth> Corrected Text -------------- <svc-bandwidth> <bandwidth> <direction>input-bw</direction> <type>bw-per-cos</type> <cos-id>10</cos-id> <cir>450000000</cir> <cbs>20000000</cbs> <eir>1000000000</eir> <ebs>200000000</ebs> </bandwidth> </svc-bandwidth> Notes ----- * Note 1: cos-id must be included as per the following: leaf cos-id { when "derived-from-or-self(../type, " + "'l2vpn-svc:bw-per-cos')" { description "Relevant when the bandwidth type is set to 'bw-per-cos'."; } type uint8; description "Identifier of the CoS, indicated by DSCP or a CE-VLAN CoS (802.1p) value in the service frame. If the bandwidth type is set to 'bw-per-cos', the CoS ID MUST also be specified."; } * Note 2: More changes are needed because the current structure does not allow to specify multiple cos-ids. 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] [Technical Errata Reported] RFC8466 (6922) RFC Errata System