Aggregation of Diffserv Service Classes
RFC 5127, “Aggregation of Diffserv Service Classes”, is an Informational document published in February 2008 by K. Chan, J. Babiarz, F. Baker. The canonical text is published by the RFC Editor.
Abstract
In the core of a high-capacity network, service differentiation may still be needed to support applications' utilization of the network. Applications with similar traffic characteristics and performance requirements are mapped into 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 may satisfy the traffic characteristics and performance requirements of two or more service classes. In these cases, it may be desirable to aggregate two or more Diffserv service classes into a single forwarding treatment. This document provides guidelines for the aggregation of Diffserv service classes into forwarding treatments. This memo provides information for the Internet community.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 5127 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5126 CMS Advanced Electronic Signatures
- RFC 5128 State of Peer-to-Peer Communication across Network Address Translators
- RFC 5125 Reclassification of RFC 3525 to Historic
- RFC 5129 Explicit Congestion Marking in MPLS
- RFC 5124 Extended Secure RTP Profile for Real-time Transport Control Protocol -Based Feedback
- RFC 5130 A Policy Control Mechanism in IS-IS Using Administrative Tags
- RFC 5123 Considerations in Validating the Path in BGP
- RFC 5122 Internationalized Resource Identifiers and Uniform Resource Identifiers for the Extensible Messaging and Presence Protocol