RFC 8679: MPLS Egress Protection Framework
In plain English — editorial summary, not part of the RFC
This document specifies a fast reroute framework for protecting IP/MPLS services and MPLS transport tunnels against egress node and egress link failures. For each type of egress failure, it defines the roles of Point of Local Repair (PLR), protector, and backup egress router and the procedures of establishing a bypass tunnel from a PLR to a protector. It describes the behaviors of these routers in handling an egress failure, including local repair on the PLR and context-based forwarding on the protector. The framework can be used to develop egress protection mechanisms to reduce traffic loss before global repair reacts to an egress failure and control-plane protocols converge on the topology changes due to the egress failure.
Document record
- Document ID
- RFC8679
- Published
- December 2019
- Authors
- Y. Shen; M. Jeganathan; B. Decraene; H. Gredler; C. Michel; H. Chen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8104Pseudowire (PW) Endpoint Fast Failure ProtectionCurrent
March 2017
- RFC 8400Extensions to RSVP-TE for Label Switched Path (LSP) Egress ProtectionCurrent
June 2018
- RFC 7916Operational Management of Loop-Free AlternatesCurrent
July 2016
- RFC 9488Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP)Current
October 2023
- RFC 9855Topology Independent Fast Reroute Using Segment RoutingCurrent
October 2025
- RFC 8678Enterprise Multihoming using Provider-Assigned IPv6 Addresses without Network Prefix Translation: Requirements and SolutionsCurrent
December 2019
- RFC 8685Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) ArchitectureUpdated
December 2019
- RFC 8687OSPF Routing with Cross-Address Family Traffic Engineering TunnelsCurrent
November 2019
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?