Integrated Services in the Presence of Compressible Flows
draft-davie-intserv-compress-01

Document Type Expired Internet-Draft (intserv WG)
Last updated 1999-02-19
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
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-davie-intserv-compress-01.txt

Abstract

An Integrated Services router performs admission control and resource allocation based on the information contained in a TSpec (among other things). As currently defined, TSpecs convey information about the data rate (using a token bucket) and range of packet sizes of the flow in question. However, the TSpec may not be an accurate representation of the resources needed to support the reservation if the router is able to compress the data at the link level. This draft describes an extension to the TSpec which enables a sender of potentially compressible data to provide hints to int-serv routers about the compressibility they may obtain. Routers which support appropriate compression take advantage of the hint in their admission control decisions and resource allocation procedures; other routers ignore the hint. An initial application of this approach is to notify routers performing RTP header compression that they may allocate fewer resources to RTP flows.

Authors

David Oran (oran@cisco.com)
Stephen Casner (casner@acm.org)
Bruce Davie (bsd@cisco.com)
John Wroclawski (jtw@lcs.mit.edu)
Carol Iturralde (cei@cisco.com)

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