RSVP Extensions for ID-based Refreshes
draft-yuhara-rsvp-refresh-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Masanobu Yuhara , Mayumi Tomikawa | ||
Last updated | 1999-04-15 | ||
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
The purpose of this document is to provide a discussion on the refresh overhead reduction of RSVP. Specifically, this document proposes some extensions to deal with route change while maintaining the advantage of ID-based refreshes. For environments where PATH refreshes must be used to detect route change, ID-only refreshes are used to decrease the message size. For environments where route change is informed to RSVP process by some other means, a new message is introduced to invalidate ID.
Authors
Masanobu Yuhara
Mayumi Tomikawa
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)