QoSjava: An Open and Scalable Architecture Decoupling QoS Requirements from QoS Techniques
draft-bupt-qosjava-arch-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Xiaohui Huang | ||
| Last updated | 2005-10-20 | ||
| 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
QoSJava, an architecture decoupling QoS reuirements from QoS techniques is proposed in this draft. Referring to the idea of Java, QoSJava can conceal the heterogeneity of different QoS mechanisms as well as different vendors' devices. Users' requirements are translated into a "middle language", i.e. deployment task specification. And QoS mechanisms adapter plus Device Driver constitute the "Virtual Machine" of QoSJava. Thus network devices can be configured and QoS requirements can be fulfilled automatically. Moreover, QoSJava is not only compatible with current QoS mechanisms and devices, but open to new QoS solutions and advanced facilities in the future.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)