1 / 5

Understanding the Benefits and Pitfalls of Explicit Congestion Notification (ECN)

This draft highlights the advantages of using Explicit Congestion Notification (ECN) in network traffic management, including less obvious benefits and deployment scenarios. It identifies potential pitfalls such as policies affecting deployment, middlebox requirements, and issues with ECN codepoint handling. The conclusion emphasizes the importance of configuring host stacks and network devices properly to support ECN without disruption. The draft aims for Working Group Last Call (WGLC) at the next IETF meeting, inviting further contributions and comments on deployment use cases.

zeph-hogan
Télécharger la présentation

Understanding the Benefits and Pitfalls of Explicit Congestion Notification (ECN)

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. The Benefits and Pitfalls of using Explicit Congestion Notification (ECN)draft-ietf-aqm-ecn-benefits-00 Michael WelzlUniversity of Oslo Gorry FairhurstUniversity of Aberdeen 91st IETF Meeting Honolulu, Hawaii10 November 2014

  2. Draft goals • Point of draft: • document gains of ECN • includes less obvious gains • Could include deployment scenarios to illustrate benefit • NEW: now also “pitfalls” (next slide) • Out of scope: • To recommend a specific behavior

  3. Pitfalls • Policies that bleach and middlebox requirements to deploy • Also points to RFC6040 for correct use of tunnelling • Cheating by hosts • Possible need for mechanisms to verify if a path really supports ECN

  4. New conclusion(not “turn it on”, but “don’t break it”) • People configuring host stacks and network devices should ensure that their equipment correctly reacts to packets carrying ECN codepoints. • This includes: • routers not resetting the ECN codepoint to zero • middleboxes not resetting the ECN codepoint to zero • correctly updating the codepoint when congested • routers correctly supporting alternate ECN semantics ([RFC4774]) • hosts receiving ECN marks correctly reflecting them

  5. Next Steps • Aim to WGLC after next (Dallas) IETF! • Deployment scenarios / use cases still pretty empty • This section could be small • Text donations welcome • Other comments?

More Related