RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP Tunnels

This document defines RSVP-TE extensions to establish backup label-switched path (LSP) tunnels for local repair of LSP tunnels. These mechanisms enable the…

Read RFC 4090 on the RFC Editor

Incoming relationships (49 related RFCs)

Updated by — RFC 8271: Updates to the Resource Reservation Protocol for Fast Reroute of Traffic Engineering GMPLS Label Switched Paths (LSPs)
Updated by — RFC 8537: Updates to the Fast Reroute Procedures for Co-routed Associated Bidirectional Label Switched Paths (LSPs)
Updated by, Normatively referenced by — RFC 8796: RSVP-TE Summary Fast Reroute Extensions for Label Switched Path (LSP) Tunnels
Updated by — RFC 9705: Refresh-Interval Independent RSVP Fast Reroute Facility Protection
Normatively referenced by — RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP)
Normatively referenced by — RFC 4875: Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)
Normatively referenced by — RFC 5921: A Framework for MPLS in Transport Networks
Normatively referenced by — RFC 5481: Packet Delay Variation Applicability Statement
Normatively referenced by — RFC 7325: MPLS Forwarding Compliance and Performance Requirements
Normatively referenced by — RFC 5146: Interworking Requirements to Support Operation of MPLS-TE over GMPLS Networks
Normatively referenced by — RFC 9130: YANG Data Model for the IS-IS Protocol
Normatively referenced by — RFC 5824: Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN
Normatively referenced by — RFC 6413: Benchmarking Methodology for Link-State IGP Data-Plane Route Convergence
Normatively referenced by — RFC 8104: Pseudowire (PW) Endpoint Fast Failure Protection
Normatively referenced by — RFC 6894: Methodology for Benchmarking MPLS Traffic Engineered (MPLS-TE) Fast Reroute Protection
Normatively referenced by — RFC 9488: Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP)
Informatively referenced by — RFC 4872: RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery
Informatively referenced by — RFC 5884: Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)
Informatively referenced by — RFC 4873: GMPLS Segment Recovery
Informatively referenced by — RFC 5714: IP Fast Reroute Framework
Informatively referenced by — RFC 4461: Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs)
Informatively referenced by — RFC 5420: Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE)
Informatively referenced by — RFC 4216: MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements
Informatively referenced by — RFC 5715: A Framework for Loop-Free Convergence
Informatively referenced by — RFC 4124: Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering
Informatively referenced by — RFC 5151: Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions
Informatively referenced by — RFC 4920: Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE
Informatively referenced by — RFC 7297: IP Connectivity Provisioning Profile (CPP)
Informatively referenced by — RFC 8283: An Architecture for Use of PCE and the PCE Communication Protocol (PCEP) in a Network with Central Control
Informatively referenced by — RFC 4420: Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
Informatively referenced by — RFC 6976: Framework for Loop-Free Convergence Using the Ordered Forwarding Information Base (oFIB) Approach
Informatively referenced by — RFC 9522: Overview and Principles of Internet Traffic Engineering
Informatively referenced by — RFC 5029: Definition of an IS-IS Link Attribute Sub-TLV
Informatively referenced by — RFC 5695: MPLS Forwarding Benchmarking Methodology for IP Flows
Informatively referenced by — RFC 6601: Generic Connection Admission Control (GCAC) Algorithm Specification for IP/MPLS Networks
Informatively referenced by — RFC 7267: Dynamic Placement of Multi-Segment Pseudowires
Informatively referenced by — RFC 7439: Gap Analysis for Operating IPv6-Only MPLS Networks
Informatively referenced by — RFC 9912: Reliable and Available Wireless (RAW) Architecture
Informatively referenced by — RFC 5330: A Link-Type sub-TLV to Convey the Number of Traffic Engineering Label Switched Paths Signalled with Zero Reserved Bandwidth across a Link
Informatively referenced by — RFC 5439: An Analysis of Scaling Issues in MPLS-TE Core Networks
Informatively referenced by — RFC 9026: Multicast VPN Fast Upstream Failover
Informatively referenced by — RFC 9791: Use Cases for MPLS Network Action Indicators and Ancillary Data
Informatively referenced by — RFC 4859: Codepoint Registry for the Flags Field in the Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Session Attribute Object
Informatively referenced by — RFC 5468: Performance Analysis of Inter-Domain Path Computation Methodologies
Informatively referenced by — RFC 6411: Applicability of Keying Methods for RSVP Security
Informatively referenced by — RFC 6974: Applicability of MPLS Transport Profile for Ring Topologies
Informatively referenced by — RFC 7965: LDP Extensions for Pseudowire Binding to Label Switched Path (LSP) Tunnels
Informatively referenced by — RFC 8679: MPLS Egress Protection Framework
Informatively referenced by — RFC 8694: Applicability of the Path Computation Element to Inter-area and Inter-AS MPLS and GMPLS Traffic Engineering