RFC 8424: Extensions to RSVP-TE for Label Switched Path (LSP) Ingress Fast Reroute (FRR) Protection
In plain English — editorial summary, not part of the RFC
This document describes extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for locally protecting the ingress node of a Point-to-Point (P2P) or Point-to-Multipoint (P2MP) Traffic Engineered (TE) Label Switched Path (LSP). It extends the Fast Reroute (FRR) protection for transit nodes of an LSP to the ingress node of the LSP. The procedures described in this document are experimental.
Document record
- Document ID
- RFC8424
- Published
- August 2018
- Authors
- H. Chen; R. Torvi
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 28
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8426Recommendations for RSVP-TE and Segment Routing (SR) Label Switched Path (LSP) CoexistenceCurrent
July 2018
- RFC 8430RIB Information ModelCurrent
September 2018
- RFC 8431A YANG Data Model for the Routing Information Base (RIB)Current
September 2018
- RFC 8416Simplified Local Internet Number Resource Management with the RPKI (SLURM)Current
August 2018
- RFC 8432A Framework for Management and Control of Microwave and Millimeter Wave Interface ParametersCurrent
October 2018
- RFC 8413Framework for Scheduled Use of ResourcesCurrent
July 2018
- RFC 8408Conveying Path Setup Type in PCE Communication Protocol (PCEP) MessagesUpdated
July 2018
- RFC 8405Shortest Path First (SPF) Back-Off Delay Algorithm for Link-State IGPsCurrent
June 2018
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?