RFC 5710: PathErr Message Triggered MPLS and GMPLS LSP Reroutes

This document describes how Resource ReserVation Protocol (RSVP) PathErr messages may be used to trigger rerouting of Multi-Protocol Label Switching (MPLS)…

Read RFC 5710 on the RFC Editor

Outgoing relationships (12 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
Normative reference — RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Normative reference — RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
Normative reference — RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description
Normative reference — RFC 4201: Link Bundling in MPLS Traffic Engineering (TE)
Normative reference — RFC 3477: Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)
Normative reference — RFC 4920: Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE
Informative reference — RFC 4736: Reoptimization of Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Loosely Routed Label Switched Path (LSP)
Informative reference — RFC 5711: Node Behavior upon Originating and Receiving Resource Reservation Protocol (RSVP) Path Error Messages
Informative reference — RFC 5712: MPLS Traffic Engineering Soft Preemption

Incoming relationships (2 related RFCs)

Normatively referenced by — RFC 5817: Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks
Informatively referenced by — RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)