1 / 6

AQM Recommendation draft-ietf- aqm-recommendation -00

AQM Recommendation draft-ietf- aqm-recommendation -00. Gorry F airhurst and Fred Baker. History. At IETF 86, TSVAREA decided to update the recommendation of RFC 2309 to not recommend the use of RED Argument: operational utility was low because of difficulty in configuration

patsy
Download Presentation

AQM Recommendation draft-ietf- aqm-recommendation -00

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AQM Recommendationdraft-ietf-aqm-recommendation-00 GorryFairhurst and Fred Baker

  2. History • At IETF 86, TSVAREA decided to update the recommendation of RFC 2309 to not recommend the use of RED • Argument: operational utility was low because of difficulty in configuration • So what algorithm do we replace RED with? • More to the point, what should be true of algorithms that the IETF would recommend?

  3. Persistent unwarranted delay disrupts competing applications

  4. draft-ietf-aqm-recommendations-00 DRAFT Recommendations

  5. Changes sincedraft-baker-aqm-recommendation-02 • S4.3, elaborated intention of auto-tuning requirement for deployment: • SHOULD NOT require tuning • MAY support further manual tuning • MAY provide logging and alarm signals • S4.6, tells about impact on transport does not specify transport CC requirements • Updated security considerations Further review appreciated (see next slide for recommendations)

  6. Conclusions/Recommendations • Network devices SHOULD implement some AQM mechanism • Deployed AQM algorithms SHOULD support Explicit Congestion Notification (ECN) as well as loss to signal congestion to endpoints. • The algorithms that the IETF recommends SHOULD NOT require operational (especially manual) configuration or tuning. • May have knobs, but in general playing with them should be unnecessary • AQM algorithms SHOULD respond to measured congestion, not application profiles. • AQM algorithms SHOULD NOT interpret specific transport protocol behaviors. • Transport protocol congestion control algorithms SHOULD maximize their use of available capacity (when there is data to send) without incurring undue loss or undue round trip delay. • Research, engineering, and measurement efforts are needed regarding … flows that are unresponsive to congestion notification or are responsive, but are more aggressive than present TCP.

More Related