QoS Path Management with RSVP
draft-guerin-qospath-mgmt-rsvp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dr. Roch Guerin , Shai Herzog , Sanjay Kamat | ||
| Last updated | 1997-03-21 | ||
| 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
This document describes a proposal aimed at allowing management through the RSVP [RZB+96] protocol of paths selected by a QoS routing algorithm such as those of [GOW96, ZSSC96]. The goals of the proposal are to allow efficient management of such QoS paths with the minimum possible impact to the RSVP protocol and the existing routing infrastructure. Basic features of the approach include leveraging of RSVP soft state mechanisms, and simple extensions to enable soft pinning (sticking) of paths selected by the QoS routing algorithm. In addition, the proposal addresses the issue of preventing the formation of data path loops, and of avoiding potential race conditions.
Authors
Dr. Roch Guerin
Shai Herzog
Sanjay Kamat
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)