Quality of Service Support in an OBAST Architecture
draft-needham-obast-qos-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Matthew Needham , Steven W. Gilbert , Phillip D. Neumiller | ||
| Last updated | 2000-07-24 | ||
| 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 outlines some of the fundamental requirements and issues related to the control and maintenance of quality of service (QoS) in an Open Base Station Transport (OBAST) architecture. It begins with a review of a baseline OBAST architecture, highlighting those elements that are particularly relevant to QoS provisioning, then discusses the requirements for QoS within this framework. In particular, the requirements for control and maintenance of QoS during mobility handoffs, and for support of adaptive applications, is addressed.
Authors
Matthew Needham
Steven W. Gilbert
Phillip D. Neumiller
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)