@misc{rfc4558,
    series =    {Request for Comments},
    number =    4558,
    howpublished =  {RFC 4558},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC4558},
    url =       {https://www.rfc-editor.org/info/rfc4558},
    author =    {Zafar Ali and Reshad Rahman and Danny Prairie and Dimitri Papadimitriou},
    title =     {{Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification Statement}},
    pagetotal = 7,
    year =      2006,
    month =     jun,
    abstract =  {Use of Node-ID based Resource Reservation Protocol (RSVP) Hello messages is implied in a number of cases, e.g., when data and control planes are separated, when TE links are unnumbered. Furthermore, when link level failure detection is performed by some means other than exchanging RSVP Hello messages, use of a Node-ID based Hello session is optimal for detecting signaling adjacency failure for Resource reSerVation Protocol-Traffic Engineering (RSVP-TE). Nonetheless, this implied behavior is unclear, and this document formalizes use of the Node-ID based RSVP Hello session in some scenarios. The procedure described in this document applies to both Multi-Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) capable nodes. {[}STANDARDS-TRACK{]}},
}