1 / 7

MPTCP Architecture draft-ietf-mptcp-architectue-02

MPTCP Architecture draft-ietf-mptcp-architectue-02. Alan Ford <alan.ford@roke.co.uk> IETF79 – Beijing. Draft Overview. Providing a high-level architectural foundation for Multipath TCP, and documenting key design decisions behind the MPTCP protocol extensions Contents:

jonny
Télécharger la présentation

MPTCP Architecture draft-ietf-mptcp-architectue-02

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. MPTCP Architecturedraft-ietf-mptcp-architectue-02 Alan Ford <alan.ford@roke.co.uk> IETF79 – Beijing

  2. Draft Overview • Providing a high-level architectural foundation for Multipath TCP, and documenting key design decisions behind the MPTCP protocol extensions • Contents: • Goals (functional and compatibility) • Architectural Basis • Functional Decomposition • Design Decisions • Issues with middleboxes

  3. Design Decisions Included • Sequence numbering • Separate subflow and connection-level spaces • Reliability and Retransmissions • Connection-level acknowledgements; need to retransmit on original paths; etc • Buffer size calculations • Option-based signalling • Path management based on multiple addresses • External draft references: • Connection ID – see API and protocol design • Congestion control – see dedicated draft • Security – see threats and protocol design

  4. Responded to Reviews • Many thanks to Olivier Bonaventure, GorryFairhurst, Iljitsch van Beijnum and Phillip Eardley • Review comments responded to in current version of the draft • Many terminology consistencies fixed • Clear distinction between overall Multipath TCP architecture and design decisions for MPTCP protocol

  5. Major Clarifications • On reliability and retransmissions • Many recommendations will have to wait until we can conduct large-scale experiments • Buffer sizing • Recommendation for 2*sum(BWi)*RTT_max • Security • Bridging the threat analysis to the protocol design • Decision on Options from Maastricht • Better linkage to Congestion Control and API

  6. Moving elsewhere… • The implementation architecture (Appendix A) has gone and will re-appear as a separate, focused draft, based on real-world implementation experience

  7. Next steps • The draft is in Last Call • Deadline is 19 November • Please send comments ASAP • Any issues to be raised now?

More Related