RFC 4594: Configuration Guidelines for DiffServ Service Classes
In plain English — editorial summary, not part of the RFC
This document describes service classes configured with Diffserv and recommends how they can be used and how to construct them using Differentiated Services Code Points (DSCPs), traffic conditioners, Per-Hop Behaviors (PHBs), and Active Queue Management (AQM) mechanisms. There is no intrinsic requirement that particular DSCPs, traffic conditioners, PHBs, and AQM be used for a certain service class, but as a policy and for interoperability it is useful to apply them consistently. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4594
- Published
- August 2006
- Authors
- J. Babiarz; K. Chan; F. Baker
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 57
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7141Byte and Packet Congestion NotificationCurrent
February 2014
- RFC 9330Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: ArchitectureCurrent
January 2023
- RFC 9331The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
- RFC 9332Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
- RFC 3140Per Hop Behavior Identification CodesCurrent
June 2001
- RFC 2836Per Hop Behavior Identification CodesObsoleted
May 2000
- RFC 8033Proportional Integral Controller Enhanced (PIE): A Lightweight Control Scheme to Address the Bufferbloat ProblemCurrent
February 2017
- RFC 8289Controlled Delay Active Queue ManagementCurrent
January 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?