[mpls] [Errata Verified] RFC6215 (7521)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 23 May 2023 21:02 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2961EC151083; Tue, 23 May 2023 14:02:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.947
X-Spam-Level:
X-Spam-Status: No, score=-3.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 iW383SPlh82E; Tue, 23 May 2023 14:02:17 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [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 43D1CC151086; Tue, 23 May 2023 14:02:17 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 005AA5668D; Tue, 23 May 2023 14:02:16 -0700 (PDT)
To: mohamed.boucadair@orange.com, matthew.bocci@alcatel-lucent.com, lieven.levrau@alcatel-lucent.com, danfrost@cisco.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rfc-ed@rfc-editor.org, iesg@ietf.org, mpls@ietf.org, iana@iana.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230523210217.005AA5668D@rfcpa.amsl.com>
Date: Tue, 23 May 2023 14:02:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/MH03PtMsJQ7xP0OhYHdkfXKZPP0>
Subject: [mpls] [Errata Verified] RFC6215 (7521)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 May 2023 21:02:21 -0000
The following errata report has been verified for RFC6215, "MPLS Transport Profile User-to-Network and Network-to-Network Interfaces". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7521 -------------------------------------- Status: Verified Type: Editorial Reported by: Mohamed Boucadair <mohamed.boucadair@orange.com> Date Reported: 2023-05-23 Verified by: RFC Editor Section: 1.1 Original Text ------------- The Transport Service Interfaces for MPLS-TP are defined in Section 3.4.3 of [RFC5921]. These definitions are illustrated by showing MPLS-TP Provider Edges (PEs) containing a UNI and an NNI. The figures illustrate the UNI and the NNI as a span. However, it is convention to illustrate these interfaces as reference points. Furthermore, in the case of a UNI, it is useful to illustrate the distribution of UNI functions between the Customer Edge (CE) side and the PE side of the UNI, i.e., the UNI-C (User-to-User Interface, Client side) and UNI-N (User-to-Network Interface, Network side), in order to show their relationship to one another. Corrected Text -------------- The Transport Service Interfaces for MPLS-TP are defined in Section 3.4.3 of [RFC5921]. These definitions are illustrated by showing MPLS-TP Provider Edges (PEs) containing a UNI and an NNI. The figures illustrate the UNI and the NNI as a span. However, it is convention to illustrate these interfaces as reference points. Furthermore, in the case of a UNI, it is useful to illustrate the distribution of UNI functions between the Customer Edge (CE) side and the PE side of the UNI, i.e., the UNI-C (User-to-Network Interface, Client side) and UNI-N (User-to-Network Interface, Network side), in order to show their relationship to one another. Notes ----- This is a very minor nit. As listed in Section 1.2., UNI stands for "User-to-Network Interface", not "User-to-User Interface". -------------------------------------- RFC6215 (draft-ietf-mpls-tp-uni-nni-03) -------------------------------------- Title : MPLS Transport Profile User-to-Network and Network-to-Network Interfaces Publication Date : April 2011 Author(s) : M. Bocci, L. Levrau, D. Frost Category : INFORMATIONAL Source : Multiprotocol Label Switching Area : Routing Stream : IETF
- [mpls] [Errata Verified] RFC6215 (7521) RFC Errata System