Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

Z. Ali
R. Rahman
D. Prairie
D. Papadimitriou

Stream:

IETF

Source:

ccamp (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC4558

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 4558

Abstract

Use of Node-ID based Resource Reservation Protocol (RSVP) Hellomessages is implied in a number of cases, e.g., when data and controlplanes are separated, when TE links are unnumbered. Furthermore, whenlink level failure detection is performed by some means other thanexchanging RSVP Hello messages, use of a Node-ID based Hello session isoptimal for detecting signaling adjacency failure for ResourcereSerVation Protocol-Traffic Engineering (RSVP-TE). Nonetheless, thisimplied behavior is unclear, and this document formalizes use ofthe Node-ID based RSVP Hello session in some scenarios. The proceduredescribed in this document applies to both Multi-Protocol LabelSwitching (MPLS) and Generalized MPLS (GMPLS) capable nodes. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.