Quality of Service Extensions to OSPF or Quality Of Service Path First Routing (QOSPF)
draft-zhang-qos-ospf-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | William Salkewicz , Eric S. Crawley , Zhaohui (Jeffrey) Zhang , Cheryl Sanchez 0 | ||
| Last updated | 1997-09-10 | ||
| 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 series of extensions for OSPF[1] and MOSPF[2] that can be used to provide Quality of Service (QoS) routing in conjunction with a resource reservation protocol such as RSVP[4] or other mechanisms that can notify routing of the QoS needs of a data flow. Advertisements indicating the resources available and the resources used are advertised to the OSPF routing domain and paths are computed based on topology information, link resource information, and the resource requirements of a particular data flow.
Authors
William Salkewicz
Eric S. Crawley
Zhaohui (Jeffrey) Zhang
Cheryl Sanchez 0
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)