Found 1 record.

Status: Verified (1)

RFC 6215, "MPLS Transport Profile User-to-Network and Network-to-Network Interfaces", April 2011

Errata ID: 7521
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Mohamed Boucadair
Date Reported: 2023-05-23
Verifier Name: RFC Editor
Date Verified: 2023-05-23

Section 1.1 says:

   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.

It should say:

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

Report New Errata