Skip to main content

Aggregation of DiffServ Service Classes

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Fred Baker , Jozef Babiarz , Kwok Ho Chan
Last updated 2006-01-19
Replaced by RFC 5127
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-tsvwg-diffserv-class-aggr
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:


In the core of a high capacity network, service differentiation is still needed to support applications' utilization of the network. Applications with similar traffic characteristics and performance requirements are mapped into different diffserv service classes based on end-to-end behavior requirements of the applications. However, some network segments may be configured in such a way that a single forwarding treatment satisfy the traffic characteristics and performance requirements of two or more service classes. For such cases, it may be desirable to aggregate two or more service classes into a forwarding treatment. This document provides guidelines for aggregation of service classes into forwarding treatments.


Fred Baker
Jozef Babiarz
Kwok Ho Chan

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