[mpls] [Editorial Errata Reported] RFC6215 (7521)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 23 May 2023 06:48 UTC

To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: mohamed.boucadair@orange.com, matthew.bocci@alcatel-lucent.com, lieven.levrau@alcatel-lucent.com, danfrost@cisco.com, mpls@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230523064846.B5ED97FDDA@rfcpa.amsl.com>
Date: Mon, 22 May 2023 23:48:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/ILLYsrhCctF6tfFUvo5GVQq1ihs>
Subject: [mpls] [Editorial Errata Reported] RFC6215 (7521)
Precedence: list

The following errata report has been submitted 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

--------------------------------------
Type: Editorial
Reported by: Mohamed Boucadair <mohamed.boucadair@orange.com>

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".

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.

--------------------------------------
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
Verifying Party : IESG

[mpls] [Editorial Errata Reported] RFC6215 (7521) RFC Errata System
Re: [mpls] [Editorial Errata Reported] RFC6215 (7… Andrew G. Malis
Re: [mpls] [Editorial Errata Reported] RFC6215 (7… Stewart Bryant