RFC 8227: MPLS-TP Shared-Ring Protection (MSRP) Mechanism for Ring Topology
In plain English — editorial summary, not part of the RFC
This document describes requirements, architecture, and solutions for MPLS-TP Shared-Ring Protection (MSRP) in a ring topology for point- to-point (P2P) services. The MSRP mechanism is described to meet the ring protection requirements as described in RFC 5654. This document defines the Ring Protection Switching (RPS) protocol that is used to coordinate the protection behavior of the nodes on an MPLS ring.
Document record
- Document ID
- RFC8227
- Published
- August 2017
- Authors
- W. Cheng; L. Wang; H. Li; H. van Helvoort; J. Dong
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 56
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8231Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCEUpdated
September 2017
- RFC 8223Application-Aware Targeted LDPCurrent
August 2017
- RFC 8232Optimizations of Label Switched Path State Synchronization Procedures for a Stateful PCECurrent
September 2017
- RFC 8233Extensions to the Path Computation Element Communication Protocol (PCEP) to Compute Service-Aware Label Switched Paths (LSPs)Updated
September 2017
- RFC 8234Updates to MPLS Transport Profile (MPLS-TP) Linear Protection in Automatic Protection Switching (APS) ModeCurrent
August 2017
- RFC 8220Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)Current
September 2017
- RFC 8218Multipath Extension for the Optimized Link State Routing Protocol Version 2 (OLSRv2)Current
August 2017
- RFC 8237MPLS Label Switched Path (LSP) Pseudowire (PW) Status Refresh Reduction for Static PWsCurrent
October 2017
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?