datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification Statement
draft-ietf-ccamp-rsvp-node-id-based-hello-03

RFC
Document Stream: IETF
Last updated: 2006-03-07
Replaces: draft-ali-ccamp-rsvp-node-id-based-hello
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 4558
Responsible AD: Alex Zinin
Send notices to: kireeti@juniper.net, adrian@olddog.co.uk, dbrungard@att.com

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-ccamp-rsvp-node-id-based-hello.

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]

Authors:
Zafar Ali <zali@cisco.com>
Reshad Rahman <rrahman@cisco.com>
Danny Prairie <dprairie@cisco.com>
Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)