Attached is a colorized diff from the last revision and a new charter trying to pull in the input from the last thread on this topic.
I have completely punted on playing with the name for the moment, and have left it as matching the BoF and mailing list name for now. -- Wes Eddy MTI Systems
Active Queue Management and Packet Scheduling (AQM) (among other alternatives) Internet routers, lower-layer switches, end-host operating systems, device drivers, and many types of additional middleboxes include memory buffers in which they implement queues to hold packets that require processing or otherwise need to wait for forwarding to the next hop. The queues are intended to absorb bursts of traffic that may naturally occur, and avoid unneccessary losses. However, queues also cause latency and jitter in the eventual arrival times of packets. This can create issues and complications for interactive applications. Extremely large unmanaged buffers have been noticed in some software and equipment. When these buffers fill, interactive applications and other traffic can be severely impacted or completely broken, due to high and potentially oscillating delays. The Active Queue Management and Packet Scheduling working group (AQM) works on algorithms for managing queues in order to: (1) minimize standing queues; helping to reduce delay for interactive applications (2) help flow sources control their sending rates without unnecessary losses, e.g. through ECN (3) consider the merits of various techniques to protect flows from negative impacts of other more aggressive or misbehaving flows (4) help avoid global synchronization of flows sharing a bottleneck The AQM working group will publish Informational and Best Current Practices documents that cover the design, use, and configuration of algorithms for managing queues in Internet devices and software. The scope includes both how to best configure existing equipment and software, as well as recommendations on designing new equipment and software. The AQM working group will also publish algorithm specifications that are found to be broadly applicable and beneficial. Evaluating these algorithms shall be done in coordination with the Internet Congestion Control Research Group (ICCRG) in order to select and assess the relevant criteria, scenarios, and metrics. The working group will also explore the merits of whether to isolate flows, and mechanisms for performing this function. Note that isolation and potentially policing of flows implies some policy beyond what is required to simply minimize queues. This topic requires significant attention in the working group. AQM algorithms do not have to be implemented universally in order to be effective. Specifications will aid in producing proper implementations that avoid potential ambiguities and corner cases. "Interoperability" of algorithms and implementations of them is not the reason for creating these specifications; correctness is the primary motivation. The working group will not make changes to ECN, DiffServ, or other IETF protocols, though existing ECN, DiffServ, and other mechanisms may be used within the algorithms proposed. The proper place for changes to ECN and DiffServ is the TSVWG, but as the implementation is likely to be entwined with AQM algorithms, there is expected to be close coordination between both groups. Many AQM algorithms have been proposed in academic literature, but a smaller number are widely implemented and deployed. The goal of the working group is to produce recommendations that will actually be used, and algorithms that will actually be implemented, deployed in equipment, and enabled. Towards these ends, the group actively encourages participation from operators and implementers, and will coordinate with the IETF OPS area and other relevant parts of the IETF and Internet community. Wider research and evaluation of AQM mechanisms shall be coordinated with the IRTF/ICCRG, and significant participation in this WG from the academic and research community is highly desirable, when it is directly relevant to implementation and deployment. Goals and Milestones January 2014 Submit AQM recommendations to IESG for publication as BCP obsoleting RFC 2309 July 2014 Submit AQM evaluation guidelines to IESG for publication as Informational December 2014 Submit first algorithm specification to IESG for publication as Proposed Standard Relevant documents: Recommendations --------------- http://tools.ietf.org/html/draft-baker-aqm-recommendation Algorithms Potentially for Consideration ---------------------------------------- PIE: http://tools.ietf.org/html/draft-pan-tsvwg-pie CoDel: http://tools.ietf.org/html/draft-nichols-tsvwg-codel FavorQueue: http://arxiv.org/pdf/1103.2303v2.pdfTitle: Diff: AQM-charter-130711.txt - AQM-charter-130729.txt
| AQM-charter-130711.txt | AQM-charter-130729.txt | |||
|---|---|---|---|---|
| Active Queue Management and Packet Scheduling (AQM) | Active Queue Management and Packet Scheduling (AQM) | |||
| or | (among other alternatives) | |||
| Smarter Queue Management (SQM) (suggested by Dave Taht) | ||||
| Internet routers, lower-layer switches, other middleboxes include | Internet routers, lower-layer switches, end-host operating | |||
| buffers or queues to hold packets when they are not immediately | systems, device drivers, and many types of additional | |||
| able to be forwarded to the next hop. | middleboxes include memory buffers in which they implement | |||
| queues to hold packets that require processing or otherwise | ||||
| need to wait for forwarding to the next hop. | ||||
| The queues are intended to absorb bursts of traffic that may | The queues are intended to absorb bursts of traffic that may | |||
| naturally occur, and avoid unneccessary losses. However, queues | naturally occur, and avoid unneccessary losses. However, queues | |||
| also cause latency and jitter in the eventual arrival times of | also cause latency and jitter in the eventual arrival times of | |||
| packets. This can create issues and complications for interactive | packets. This can create issues and complications for interactive | |||
| applications. | applications. | |||
| Extremely large buffers have been noticed in some software and | Extremely large unmanaged buffers have been noticed in some | |||
| equipment. When these queues fill, interactive applications and | software and equipment. When these buffers fill, interactive | |||
| other traffic can be severely impacted or completely broken, due | applications and other traffic can be severely impacted or | |||
| to high and potentially oscillating delays. | completely broken, due to high and potentially oscillating delays. | |||
| The Active Queue Management and Packet Scheduling working group | The Active Queue Management and Packet Scheduling working group | |||
| (AQM) works on algorithms for proactively managing queues in | (AQM) works on algorithms for managing queues in order to: | |||
| order to: | ||||
| (1) help flow sources control their sending rates before the | (1) minimize standing queues; helping to reduce delay for | |||
| onset of necessary losses, e.g. through ECN | interactive applications | |||
| (2) help minimize delays for interactive applications | (2) help flow sources control their sending rates without | |||
| unnecessary losses, e.g. through ECN | ||||
| (3) help protect flows from negative impacts of other more | (3) consider the merits of various techniques to protect flows | |||
| aggressive or misbehaving flows | from negative impacts of other more aggressive or misbehaving | |||
| flows | ||||
| (4) help avoid global synchronization of flows sharing a | ||||
| bottleneck | ||||
| The AQM working group will publish Informational and Best Current | The AQM working group will publish Informational and Best Current | |||
| Practices documents that cover the design, use, and configuration | Practices documents that cover the design, use, and configuration | |||
| of algorithms for managing queues in Internet devices and software. | of algorithms for managing queues in Internet devices and software. | |||
| The scope includes both how to best configure existing equipment | ||||
| and software, as well as recommendations on designing new equipment | ||||
| and software. | ||||
| The AQM working group will also publish algorithm specifications | The AQM working group will also publish algorithm specifications | |||
| that are found to be broadly applicable and beneficial. Evaluating | that are found to be broadly applicable and beneficial. Evaluating | |||
| these algorithms shall be done in coordination with the Internet | these algorithms shall be done in coordination with the Internet | |||
| Congestion Control Research Group (ICCRG) in order to select and | Congestion Control Research Group (ICCRG) in order to select and | |||
| assess the relevant criteria, scenarios, and metrics. | assess the relevant criteria, scenarios, and metrics. | |||
| The working group will also explore the merits of whether to | ||||
| isolate flows, and mechanisms for performing this function. Note | ||||
| that isolation and potentially policing of flows implies some policy | ||||
| beyond what is required to simply minimize queues. This topic | ||||
| requires significant attention in the working group. | ||||
| AQM algorithms do not have to be implemented universally in order | AQM algorithms do not have to be implemented universally in order | |||
| to be effective. Specifications will aid in producing proper | to be effective. Specifications will aid in producing proper | |||
| implementations that avoid potential ambiguities and corner cases. | implementations that avoid potential ambiguities and corner cases. | |||
| "Interoperability" of algorithms and implementations of them is | "Interoperability" of algorithms and implementations of them is | |||
| not the reason for creating these specifications; correctness is | not the reason for creating these specifications; correctness is | |||
| the primary motivation. | the primary motivation. | |||
| The working group will not make changes to ECN, DiffServ, or other | The working group will not make changes to ECN, DiffServ, or other | |||
| IETF protocols, though existing ECN, DiffServ, and other mechanisms | IETF protocols, though existing ECN, DiffServ, and other mechanisms | |||
| may be used within the algorithms proposed. | may be used within the algorithms proposed. The proper place for | |||
| changes to ECN and DiffServ is the TSVWG, but as the implementation | ||||
| is likely to be entwined with AQM algorithms, there is expected to be | ||||
| close coordination between both groups. | ||||
| Many AQM algorithms have been proposed in academic literature, but | Many AQM algorithms have been proposed in academic literature, but | |||
| very few are widely implemented and deployed. The goal of the working | a smaller number are widely implemented and deployed. The goal of the | |||
| group is to produce recommendations that will actually be used, and | working group is to produce recommendations that will actually be used, | |||
| algorithms that will actually be implemented, deployed in equipment, | and algorithms that will actually be implemented, deployed in equipment, | |||
| and enabled. Towards these ends, the group actively encourages | and enabled. Towards these ends, the group actively encourages | |||
| participation from operators and implementers, and will coordinate | participation from operators and implementers, and will coordinate with | |||
| with the IETF OPS area and other relevant parts of the IETF and | the IETF OPS area and other relevant parts of the IETF and Internet | |||
| Internet community. Wider research and evaluation of AQM mechanisms | community. Wider research and evaluation of AQM mechanisms shall be | |||
| shall be coordinated with the IRTF/ICCRG, and significant | coordinated with the IRTF/ICCRG, and significant participation in this | |||
| participation in this WG from the academic and research community is | WG from the academic and research community is highly desirable, when it | |||
| highly desirable, when it is directly relevant to implementation and | is directly relevant to implementation and deployment. | |||
| deployment. | ||||
| Goals and Milestones | Goals and Milestones | |||
| January 2014 Submit AQM recommendations to IESG for publication as BCP obsoleting RFC 2309 | January 2014 Submit AQM recommendations to IESG for publication as BCP obsoleting RFC 2309 | |||
| July 2014 Submit AQM evaluation guidelines to IESG for publication as Informational | July 2014 Submit AQM evaluation guidelines to IESG for publication as Informational | |||
| December 2014 Submit first algorithm specification to IESG for publication as Proposed Standard | December 2014 Submit first algorithm specification to IESG for publication as Proposed Standard | |||
| Relevant documents: | Relevant documents: | |||
| Recommendations | Recommendations | |||
| End of changes. 12 change blocks. | ||||
| 27 lines changed or deleted | 43 lines changed or added | |||
This html diff was produced by rfcdiff 1.39p1. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||
_______________________________________________ aqm mailing list [email protected] https://www.ietf.org/mailman/listinfo/aqm
