RFC 5951: Network Management Requirements for MPLS-based Transport Networks
In plain English — editorial summary, not part of the RFC
This document specifies the requirements for the management of equipment used in networks supporting an MPLS Transport Profile (MPLS-TP). The requirements are defined for specification of network management aspects of protocol mechanisms and procedures that constitute the building blocks out of which the MPLS Transport Profile is constructed. That is, these requirements indicate what management capabilities need to be available in MPLS for use in managing the MPLS-TP. This document is intended to identify essential network management capabilities, not to specify what functions any particular MPLS implementation supports. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5951
- Published
- September 2010
- Authors
- K. Lam; S. Mansfield; E. Gray
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8256Requirements for Hitless MPLS Path Segment MonitoringCurrent
October 2017
- RFC 5950Network Management Framework for MPLS-based Transport NetworksCurrent
September 2010
- RFC 5960MPLS Transport Profile Data Plane ArchitectureUpdated
August 2010
- RFC 5921A Framework for MPLS in Transport NetworksUpdated
July 2010
- RFC 5994Application of Ethernet Pseudowires to MPLS Transport NetworksCurrent
October 2010
- RFC 5860Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport NetworksCurrent
May 2010
- RFC 5718An In-Band Data Communication Network For the MPLS Transport ProfileCurrent
January 2010
- RFC 5654Requirements of an MPLS Transport ProfileCurrent
September 2009
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?