RFC 8234: Updates to MPLS Transport Profile (MPLS-TP) Linear Protection in Automatic Protection Switching (APS) Mode
In plain English — editorial summary, not part of the RFC
This document contains updates to MPLS Transport Profile (MPLS-TP) linear protection in Automatic Protection Switching (APS) mode defined in RFC 7271. The updates provide rules related to the initialization of the Protection State Coordination (PSC) Control Logic (in which the state machine resides) when operating in APS mode and clarify the operation related to state transition table lookup.
Document record
- Document ID
- RFC8234
- Published
- August 2017
- Authors
- J. Ryoo; T. Cheung; H. van Helvoort; I. Busi; G. Wen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
- Updates:
- RFC 7271
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8233Extensions to the Path Computation Element Communication Protocol (PCEP) to Compute Service-Aware Label Switched Paths (LSPs)Updated
September 2017
- RFC 8232Optimizations of Label Switched Path State Synchronization Procedures for a Stateful PCECurrent
September 2017
- RFC 8231Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCEUpdated
September 2017
- RFC 8237MPLS Label Switched Path (LSP) Pseudowire (PW) Status Refresh Reduction for Static PWsCurrent
October 2017
- RFC 8241Interface to the Routing System (I2RS) Security-Related RequirementsCurrent
September 2017
- RFC 8227MPLS-TP Shared-Ring Protection (MSRP) Mechanism for Ring TopologyCurrent
August 2017
- RFC 8242Interface to the Routing System (I2RS) Ephemeral State RequirementsCurrent
September 2017
- RFC 8243Alternatives for Multilevel Transparent Interconnection of Lots of Links (TRILL)Current
September 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?