1 / 9

ConEx Abstract Mechanism: Designing Algorithms & Protocol for Enhanced Transport Efficiency

Explore the ConEx Working Group draft on abstract design of algorithms and protocol encodings for improved transport efficiency. Discover improvements such as sender congestion control and TCP enhancements for wider use. Delve into the concepts and mechanisms for congestion policing and policy monitoring to optimize network performance.

mattocks
Download Presentation

ConEx Abstract Mechanism: Designing Algorithms & Protocol for Enhanced Transport Efficiency

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. ConEx Concepts and Abstract Mechanismdraft-ietf-conex-abstract-mech-01.txt Matt Mathis, Google Bob Briscoe, BT IETF-80 ConEx Mar 2011 This work is partly funded by Trilogy, a research project supported by the European Community www.trilogy-project.org

  2. ConEx Concepts and Abstract Mechanism • working group draft: draft-ietf-conex-abstract-mech-01.txt • intended status: informational • immediate intent: attract review comments, then WGLC • milestone target: Jul 2011 recall • defer encoding to avoid obscuring underlying design • abstract design of algorithms & protocol • encoding in different protocol headers can follow (IPv6, v4) • scope • loss-based (for incremental deployment), not just ECN • any transport, ConEx just using TCP as first concrete step 2

  3. basic signals and functional units transportsender transportreceiver ACKS SACK ECE congestednetworkelement policy audit DATA ECN loss Re-Echo-ECN Re-Echo-Loss 3

  4. improvements to draft • what ConEx is not (requested on & off list) • sender does NOT expose congestion to network so that routers can do detailed congestion control • rational for Credit signal (presented in Beijing) • simplify audit by making e2e transport responsible for RTT delay • change to TCP ECN feedback could have wider use than ConEx • feeding back all congestion events, not just one per RTT • data centre (DCTCP) needs this, and others...? • chartered ConEx-TCP draft should make this feedback a separate module • behaviour constraints for audit function (see next slide) • normative text in an informative draft • monitoring against policy as most generic function (insight from concepts-uses) • combined with other actions • capacity upgrade, penalty clause, charge, warning • congestion policing → policy monitoring + congestion policing

  5. added whole subsectionbehaviour constraints for audit function • Minimal false hits • Minimal false misses • responsive – pref at first packet that sends balance negative • Transport oblivious • Sufficient sanction • even against tradeoff attack between policer & audit • Non-vulnerability to memory exhaustion • Non-vulnerability to identifier white-washing

  6. minor mods • updated filename etc (wg item) • general clarifications and tarted up ASCII art • acks: Toby M, Nandita D, Mirja K, Caitlin B • oops – missed off acking Marcelo’s review

  7. main item left on To Do list: partial deployment • propose new section collecting pointers to all aspects of partial deployment • ConEx and/or non-ConEx packets • encoding [abstract-mech] • ConEx and/or non-ConEx receivers • ConEx Components [abstract-mech] • Interwork with loss and/or ECN queues • encoding & reqs [abstract-mech] • Some networks use ConEx signals, others don't • partial deployment [concepts-uses] • other non-e2e arrangements • eg. ConEx proxy [draft-kutscher-conex-mobile]

  8. status & plans • more “What ConEx is NOT” • more & better ASCII art • e.g. the architecture I just showed • new section to collect partial deployment pointers • consider interaction between ECN & drop • get wider review • otherwise, looking in fairly good shape • could go to WGLC then queue for concepts-uses? 8

  9. ConEx Concepts and Abstract Mechanismdraft-ietf-conex-abstract-mech-01.txt Q&A

More Related