Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

K. Chan
J. Babiarz
F. Baker

Stream:

IETF

Source:

tsvwg (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5127

Discuss this RFC: Send questions or comments to the mailing listtsvwg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5127

Abstract

In the core of a high-capacity network, service differentiation maystill be needed to support applications' utilization of the network.Applications with similar traffic characteristics and performancerequirements are mapped into Diffserv service classes based on end-to-end behavior requirements of the applications. However, somenetwork segments may be configured in such a way that a singleforwarding treatment may satisfy the traffic characteristics andperformance requirements of two or more service classes. In thesecases, it may be desirable to aggregate two or more Diffserv serviceclasses into a single forwarding treatment. This document providesguidelines for the aggregation of Diffserv service classes intoforwarding treatments. This memo provides information for the Internet community.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.