Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC4736
Discuss this RFC: Send questions or comments to the mailing listccamp@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 4736
This document defines a mechanism for the reoptimization of looselyrouted MPLS and GMPLS (Generalized Multiprotocol Label Switching)Traffic Engineering (TE) Label Switched Paths (LSPs) signaled withResource Reservation Protocol Traffic Engineering (RSVP-TE). This documentproposes a mechanism that allows a TE LSP head-end Label SwitchingRouter (LSR) to trigger a new path re-evaluation on every hop that hasa next hop defined as a loose or abstract hop and a mid-point LSR tosignal to the head-end LSR that a better path exists (compared to thecurrent path) or that the TE LSP must be reoptimized (because ofmaintenance required on the TE LSP path). The proposed mechanismapplies to the cases of intra- and inter-domain (Interior GatewayProtocol area (IGP area) or Autonomous System) packet and non-packetTE LSPs following a loosely routed path. This memo provides information for the Internet community.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.