Node-ID Based Resource Reservation Protocol Hello: A Clarification Statement
RFC 4558, “Node-ID Based Resource Reservation Protocol Hello: A Clarification Statement”, is a Proposed Standard document published in June 2006 by Z. Ali, R. Rahman, D. Prairie, D. Papadimitriou. The canonical text is published by the RFC Editor.
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4558 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4557 Online Certificate Status Protocol Support for Public Key Cryptography for Initial Authentication in Kerberos
- RFC 4559 SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows
- RFC 4556 Public Key Cryptography for Initial Authentication in Kerberos
- RFC 4560 Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
- RFC 4555 IKEv2 Mobility and Multihoming Protocol
- RFC 4561 Definition of a Record Route Object Node-Id Sub-Object
- RFC 4554 Use of VLANs for IPv4-IPv6 Coexistence in Enterprise Networks
- RFC 4562 MAC-Forced Forwarding: A Method for Subscriber Separation on an Ethernet Access Network