MPTCP – MULTIPATH TCP WG meeting #1 Nov 9 th, 2009 Hiroshima, ietf-76

Admin Chairs –Philip Eardley –Yoshifumi Nishida Scribes Jabber Please include “-mptcp-” in your draft names Please SIGN blue sheets (flashing optional) Please flash/say your name at mike

Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: * The IETF plenary session * The IESG, or any member thereof on behalf of the IESG * Any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices * Any IETF working group or portion thereof * The IAB or any member thereof on behalf of the IAB * The RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879). Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 5378 and RFC 3979 for details. A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.

Agenda 1. Intro [10mins] – Chairs ( note takers, blue sheets, Note well, charter summary ) 2. Architecture [30mins] –Jana Iyengar 3. Protocol [20mins] – Alan Ford 4. Congestion control [20mins] – Costin Raiciu 5. Threats [15mins] - Marcelo Bagnulo 6. Application considerations [10mins] - Michael Scharf 7. Extended API [5mins] - Michael Scharf 8. Host routing [10mins] – Mark Handley We will concentrate especially on architectural issues and high-level design goals & decisions – towards our first Milestone for March 2010, “Established WG consensus on the Architecture”

Advert “corridor” meeting, so that people who are already implementing MPTCP plus those who may implement it can get together to coordinate 3pm Wed, nearby café Costin Raiciu

What is MPTCP? Add the capability of simultaneously using multiple paths to a regular TCP session

What is the MPTCP WG doing? Two main things: –protocol extensions needed to deploy MPTCP Both ends are modified Paths may disappear –adaptations to congestion control to safely support multipath resource sharing. The paths may be fully or partially joint multipath equivalent of SACK/NewReno The output is experimental or informational.

Assumptions set by the charter Existing applications can use MPTCP without modification –an extended API may bring extra benefit Works over the current internet –stable and congestion-safe over the wide range of existing Internet paths –NATs –MTU Different paths achieved through different addresses –The design should allow for future extensions where path diversity is achieved through other means

6 work items Architectural framework Security threats analysis coupled multipath-aware congestion control algorithm. Extensions to current TCP to support multi-addressed multipath TCP. An extended API Application considerations

Schedule Mar 2010: –Established WG consensus on the architecture, high-level design decisions Proposal: WG last call Feb (to allow revision for ietf-77 i-d deadline) Aug 2010: –security threats Proposal: create WG I-D asap –Architectural guidelines Proposal: create WG I-D asap (to capture overview, motivations…) Mar 2011: –congestion control; Proposal: ietf-77, what are the alternative proposals –protocol specification for MPTCP extensions Proposal: ietf-77, what are the alternative proposals –extended API –application considerations

Agenda 1. Intro [10mins] – Chairs ( note takers, blue sheets, Note well, charter summary ) 2. Architecture [30mins] –Jana Iyengar 3. Protocol [20mins] – Alan Ford 4. Congestion control [20mins] – Costin Raiciu 5. Threats [15mins] - Marcelo Bagnulo 6. Application considerations [10mins] - Michael Scharf 7. Extended API [5mins] - Michael Scharf 8. Host routing [10mins] – Mark Handley We will concentrate especially on architectural issues and high-level design goals & decisions – towards our first Milestone for March 2010, “Established WG consensus on the Architecture”