Specification of the Qualitative Service Type
draft-moore-qualsvc-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Tim M. Moore | ||
Last updated | 1999-03-02 | ||
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 draft describes the use of RSVP [RFC2205] with applications that do not have resource requirements that may not be readily quantifiable (qualitative applications). We introduce the \146qualitative\106 service-type. This service-type can be used in conjunction with RSVP signaling to manage the allocation of network resources to traffic originating from qualitative applications. This mode of RSVP usage is particularly applicable to networks that combine differentiated service (diff-serv) QoS mechanisms with RSVP signaling [intdiff].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)