Node ID based RSVP Hello: A Clarification Statement
draft-ali-ccamp-rsvp-node-id-based-hello-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Reshad Rahman , Danny Prairie , Dimitri Papadimitriou , Zafar Ali | ||
| Last updated | 2010-01-11 (Latest revision 2004-04-16) | ||
| Replaced by | draft-ietf-ccamp-rsvp-node-id-based-hello | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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 | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Danny Prairie
Dimitri Papadimitriou
Zafar Ali
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)