Specification of the Qualitative Service Type
draft-moore-qualservice-00

Document Type Expired Internet-Draft (individual)
Last updated 1999-08-03 (latest revision 1999-06-29)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-moore-qualservice-00.txt

Abstract

This draft describes the use of RSVP [RFC2205] with applications that do not have resource requirements that are readily quantifiable per the standard Intserv token-bucket model (qualitative applications). We introduce the 'qualitative' 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

Bruce Davie (bsd@cisco.com)
Andrew Smith (ah_smith@pacbell.net)
Yoram Bernet (yoramb@microsoft.com)
Tim Moore (timmoore@microsoft.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)