[L2sm] [Errata Verified] RFC8466 (6683)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 12 January 2024 14:33 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 6D024C14CE5D; Fri, 12 Jan 2024 06:33:07 -0800 (PST)
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.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 CGaNX92aeAbw; Fri, 12 Jan 2024 06:33:02 -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 DE13DC14F6B7; Fri, 12 Jan 2024 06:33:02 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id B46791B315BD; Fri, 12 Jan 2024 06:33:02 -0800 (PST)
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, iana@iana.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240112143302.B46791B315BD@rfcpa.amsl.com>
Date: Fri, 12 Jan 2024 06:33:02 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/PQ2_Mv8XcFftytXacE9kPHoqhok>
X-Mailman-Approved-At: Fri, 12 Jan 2024 09:04:11 -0800
Subject: [L2sm] [Errata Verified] RFC8466 (6683)
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 14:33:07 -0000
The following errata report has been verified 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/eid6683 -------------------------------------- Status: Verified Type: Editorial Reported by: Mohamed Boucadair <mohamed.boucadair@orange.com> Date Reported: 2021-09-14 Verified by: Robert Wilton (IESG) Section: 5.10.2.1 Original Text ------------- QoS classification rules are handled by "qos-classification-policy". qos-classification-policy is an ordered list of rules that match a flow or application and set the appropriate target CoS (target-class-id). The user can define the match using a more specific flow definition (based on Layer 2 source and destination MAC addresses, cos, dscp, cos-id, color-id, etc.). A "color-id" will be assigned to a service frame to identify its QoS profile conformance. A service frame is "green" if it is conformant with the "committed" rate of the bandwidth profile. A service frame is "yellow" if it exceeds the "committed" rate but is conformant with the "excess" rate of the bandwidth profile. Finally, a service frame is "red" if it is conformant with neither the "committed" rate nor the "excess" rate of the bandwidth profile. Corrected Text -------------- QoS classification rules are handled by "qos-classification-policy". qos-classification-policy is an ordered list of rules that match a flow or application and set the appropriate target CoS (target-class-id). The user can define the match using a more specific flow definition (based on Layer 2 source and destination MAC addresses, dscp, color-type, etc.). A "color-type" will be assigned to a service frame to identify its QoS profile conformance. A service frame is "green" if it is conformant with the "committed" rate of the bandwidth profile. A service frame is "yellow" if it exceeds the "committed" rate but is conformant with the "excess" rate of the bandwidth profile. Finally, a service frame is "red" if it is conformant with neither the "committed" rate nor the "excess" rate of the bandwidth profile. Notes ----- There is no "color-id" under "qos-classification-policy". The text should refer to "color-type" given that the "qos-classification-policy" substree is as follows: +--rw service | +--rw qos {qos}? | | +--rw qos-classification-policy | | | +--rw rule* [id] | | | +--rw id string | | | +--rw (match-type)? | | | | +--:(match-flow) | | | | | +--rw match-flow | | | | | +--rw dscp? inet:dscp | | | | | +--rw dot1q? uint16 | | | | | +--rw pcp? uint8 | | | | | +--rw src-mac? yang:mac-address | | | | | +--rw dst-mac? yang:mac-address | | | | | +--rw color-type? identityref | | | | | +--rw target-sites* | | | | | | svc-id {target-sites}? | | | | | +--rw any? empty | | | | | +--rw vpn-id? svc-id | | | | +--:(match-application) | | | | +--rw match-application? identityref | | | +--rw target-class-id? string The same applies for "cos" and "cos-id". The corrected text uses "color-type" instead of "color-id" and removes "cos" and "cos-id" from the flow definition examples. -------------------------------------- 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 Verified] RFC8466 (6683) RFC Errata System