IETF Recommendations Regarding Active Queue Management
RFC 7567
| Document | Type |
RFC - Best Current Practice
(July 2015; Errata)
Obsoletes RFC 2309
Also known as BCP 197
|
|
|---|---|---|---|
| Last updated | 2019-02-20 | ||
| Replaces | draft-baker-aqm-recommendation | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Richard Scheffenegger | ||
| Shepherd write-up | Show (last changed 2014-12-09) | ||
| IESG | IESG state | RFC 7567 (Best Current Practice) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Martin Stiemerling | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | No IANA Actions | ||
Internet Engineering Task Force (IETF) F. Baker, Ed.
Request for Comments: 7567 Cisco Systems
BCP: 197 G. Fairhurst, Ed.
Obsoletes: 2309 University of Aberdeen
Category: Best Current Practice July 2015
ISSN: 2070-1721
IETF Recommendations Regarding Active Queue Management
Abstract
This memo presents recommendations to the Internet community
concerning measures to improve and preserve Internet performance. It
presents a strong recommendation for testing, standardization, and
widespread deployment of active queue management (AQM) in network
devices to improve the performance of today's Internet. It also
urges a concerted effort of research, measurement, and ultimate
deployment of AQM mechanisms to protect the Internet from flows that
are not sufficiently responsive to congestion notification.
Based on 15 years of experience and new research, this document
replaces the recommendations of RFC 2309.
Status of This Memo
This memo documents an Internet Best Current Practice.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7567.
Baker & Fairhurst Best Current Practice [Page 1]
RFC 7567 Active Queue Management Recommendations July 2015
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Baker & Fairhurst Best Current Practice [Page 2]
RFC 7567 Active Queue Management Recommendations July 2015
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Congestion Collapse . . . . . . . . . . . . . . . . . . . 4
1.2. Active Queue Management to Manage Latency . . . . . . . . 5
1.3. Document Overview . . . . . . . . . . . . . . . . . . . . 6
1.4. Changes to the Recommendations of RFC 2309 . . . . . . . 7
1.5. Requirements Language . . . . . . . . . . . . . . . . . . 7
2. The Need for Active Queue Management . . . . . . . . . . . . 7
2.1. AQM and Multiple Queues . . . . . . . . . . . . . . . . . 11
2.2. AQM and Explicit Congestion Marking (ECN) . . . . . . . . 12
2.3. AQM and Buffer Size . . . . . . . . . . . . . . . . . . . 12
3. Managing Aggressive Flows . . . . . . . . . . . . . . . . . . 13
4. Conclusions and Recommendations . . . . . . . . . . . . . . . 16
4.1. Operational Deployments SHOULD Use AQM Procedures . . . . 17
4.2. Signaling to the Transport Endpoints . . . . . . . . . . 17
4.2.1. AQM and ECN . . . . . . . . . . . . . . . . . . . . . 18
4.3. AQM Algorithm Deployment SHOULD NOT Require Operational
Tuning . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.4. AQM Algorithms SHOULD Respond to Measured Congestion, Not
Application Profiles . . . . . . . . . . . . . . . . . . 21
4.5. AQM Algorithms SHOULD NOT Be Dependent on Specific
Transport Protocol Behaviors . . . . . . . . . . . . . . 22
4.6. Interactions with Congestion Control Algorithms . . . . . 22
Show full document text