RFC 9705: Refresh-Interval Independent RSVP Fast Reroute Facility Protection
In plain English — editorial summary, not part of the RFC
The RSVP-TE Fast Reroute (FRR) extensions specified in RFC 4090 define two local repair techniques to reroute Label Switched Path (LSP) traffic over pre-established backup tunnels. Facility backup method allows one or more LSPs traversing a connected link or node to be protected using a bypass tunnel. The many-to-one nature of local repair technique is attractive from a scalability point of view. This document enumerates facility backup procedures in RFC 4090 that rely on refresh timeout, hence, making facility backup method refresh-interval dependent. The RSVP-TE extensions defined in this document will enhance the facility backup protection mechanism by making the corresponding procedures refresh-interval independent, and hence, compatible with the Refresh-Interval Independent RSVP (RI-RSVP) capability specified in RFC 8370. Hence, this document updates RFC 4090 in order to support the RI-RSVP capability specified in RFC 8370.
Document record
- Document ID
- RFC9705
- Published
- March 2025
- Authors
- C. Ramachandran; T. Saad; D. Pacella
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 24
- Also known as
- —
- Updates:
- RFC 4090
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9703Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data PlaneCurrent
December 2024
- RFC 9702YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSDCurrent
January 2025
- RFC 9714Encapsulation for MPLS Performance Measurement with the Alternate-Marking MethodCurrent
February 2025
- RFC 9696Routing in Fat Trees (RIFT) Applicability and Operational ConsiderationsCurrent
April 2025
- RFC 9716Mechanisms for MPLS Ping and Traceroute Procedures in Inter-Domain Segment Routing NetworksCurrent
February 2025
- RFC 9692RIFT: Routing in Fat TreesCurrent
April 2025
- RFC 9719YANG Data Model for Routing in Fat Trees (RIFT)Current
April 2025
- RFC 9689Use Cases for a PCE as a Central Controller (PCECC)Current
December 2024
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?