RFC 7412: Requirements for MPLS Transport Profile (MPLS-TP) Shared Mesh Protection
In plain English — editorial summary, not part of the RFC
This document presents the basic network objectives for the behavior of Shared Mesh Protection (SMP) that are not based on control-plane support. This document provides an expansion of the basic requirements presented in RFC 5654 ("Requirements of an MPLS Transport Profile") and RFC 6372 ("MPLS Transport Profile (MPLS-TP) Survivability Framework"). This document provides requirements for any mechanism that would be used to implement SMP for MPLS-TP data paths, in networks that delegate protection switch coordination to the data plane.
Document record
- Document ID
- RFC7412
- Published
- December 2014
- Authors
- Y. Weingarten; S. Aldrin; P. Pan; J. Ryoo; G. Mirsky
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 16
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7409Forwarding and Control Element Separation (ForCES) Packet ParallelizationCurrent
November 2014
- RFC 7416A Security Threat Analysis for the Routing Protocol for Low-Power and Lossy Networks (RPLs)Current
January 2015
- RFC 7408Forwarding and Control Element Separation (ForCES) Model ExtensionCurrent
November 2014
- RFC 7419Common Interval Support in Bidirectional Forwarding DetectionCurrent
December 2014
- RFC 7420Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) ModuleCurrent
December 2014
- RFC 7399Unanswered Questions in the Path Computation Element ArchitectureCurrent
October 2014
- RFC 7394Definition of Time to Live TLV for LSP-Ping MechanismsCurrent
November 2014
- RFC 7431Multicast-Only Fast RerouteCurrent
August 2015
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?