Path QoS Collection for RSVP-friendly Hop-by-hop QoS Routing
draft-ohta-rsvp-friendly-hop-path-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dr. Masataka Ohta , Yukinori Goto | ||
| Last updated | 1996-11-18 | ||
| 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
QoS routing needs some stabilization mechanism to prevent a delayed negative feedback on the link QoS information by the routed traffic. So far, route pinning was the only known way of the stabilization. But, as RSVP merges multiple RESV messages to create a new one, pinned route computed elsewhere for different QoS requirement is not useful after the merge. That is, we need a sticky hop-by-hop QoS routing algorithm. Path QoS Collection is such an algorithm to collect true upstream link QoS in PATH messages to correct the link QoS information distributed by QoS routing protocols.
Authors
Dr. Masataka Ohta
Yukinori Goto
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)