RSVP Mobility Proxy
draft-paskalis-rsvpmp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Sarantis Paskalis | ||
| Last updated | 2001-12-17 | ||
| 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
Mobility management and QoS provision have been research topics in the past years. Mobile IP is the dominant protocol for mobility management, whereas RSVP is a well established protocol for QoS provision. These protocols when deployed separately can work quite efficiently. However, their interworking has been widely recognized to be problematic. We propose a new approach that limits mobility and QoS related network modifications inside the domain in which a user moves.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)