RFC 6923: MPLS Transport Profile (MPLS-TP) Identifiers Following ITU-T Conventions
In plain English — editorial summary, not part of the RFC
This document specifies an extension to the identifiers to be used in the Transport Profile of Multiprotocol Label Switching (MPLS-TP). Identifiers that follow IP/MPLS conventions have already been defined. This memo augments that set of identifiers for MPLS-TP management and Operations, Administration, and Maintenance (OAM) functions to include identifier information in a format typically used by the International Telecommunication Union Telecommunication Standardization Sector (ITU-T).
Document record
- Document ID
- RFC6923
- Published
- May 2013
- Authors
- R. Winter; E. Gray; H. van Helvoort; M. Betts
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6916Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI)Current
April 2013
- RFC 6938Deprecation of BGP Path Attributes: DPA, ADVERTISER, and RCID_PATH / CLUSTER_IDCurrent
May 2013
- RFC 6907Use Cases and Interpretations of Resource Public Key Infrastructure (RPKI) Objects for Issuers and Relying PartiesCurrent
March 2013
- RFC 6941MPLS Transport Profile (MPLS-TP) Security FrameworkCurrent
April 2013
- RFC 6905Requirements for Operations, Administration, and Maintenance (OAM) in Transparent Interconnection of Lots of Links (TRILL)Current
March 2013
- RFC 6945Definitions of Managed Objects for the Resource Public Key Infrastructure (RPKI) to Router ProtocolCurrent
May 2013
- RFC 6898Link Management Protocol Behavior Negotiation and Configuration ModificationsCurrent
March 2013
- RFC 6952Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design GuideCurrent
May 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?