Node ID based RSVP Hello: A Clarification Statement
draft-ali-ccamp-rsvp-node-id-based-hello-01

Document Type Replaced Internet-Draft (individual)
Last updated 2010-01-11 (latest revision 2004-04-16)
Replaced by draft-ietf-ccamp-rsvp-node-id-based-hello
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-ccamp-rsvp-node-id-based-hello
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ali-ccamp-rsvp-node-id-based-hello-01.txt

Abstract

Use of node-id based RSVP Hello messages is implied in a number of cases, e.g., when data and control plan are separated, when TE links are unnumbered. Furthermore, when link level failure detection is performed by some means other than RSVP Hellos, use of node-id based Hellos is optimal for detecting signaling adjacency failure for RSVP- TE. Nonetheless, this implied behavior is unclear and this document formalizes use of node-id based RSVP Hello sessions as a best current practice (BCP) in some scenarios.

Authors

Reshad Rahman (rrahman@cisco.com)
Danny Prairie (dprairie@cisco.com)
Dimitri Papadimitriou (dimitri.papadimitriou@alcatel.be)
Zafar Ali (zali@cisco.com)

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