Support of Shortcuts for RSVP Flows Over ATM
draft-guerin-issll-rsvp-shortcut-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Lou Berger , Dr. Vijay Srinivasan | ||
| Last updated | 1997-08-01 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Support for RSVP flows across an ATM network has been defined in [BB97, GB97, Ber97a]. Although the use of shortcuts was mentioned in [BB97, Sec. 3.7], and [Ber97a, Sec. 3.6] the current specifications do not address this case in sufficient details so as to allow interoperable implementations. The purpose of this document is to identify issues in using ATM shortcuts for RSVP flows. For purposes of illustrations, the NHRP protocol [LKPC97] will be assumed as the mechanism used to discover shortcuts, and a possible interface between RSVP and NHRP will be outlined. However, it should be noted that other shortcut mechanisms are possible, e.g., PAR [J96], and the general conclusions of this document should also hold in such cases. Since the issue of shortcut discovery is significantly more complex in the multicast case, for which in most instances has not been defined, e.g., NHRP, this document is limited to the case of unicast flows.
Authors
Lou Berger
Dr. Vijay Srinivasan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)