Draft agenda (as at 14 JUly) Tuesday 1710-1810 Auditorium 2 Options vs payload discussion Objective: To come to WG consensus on which approach MPTCP will use (options or payload). Useful reading: http://tools.ietf.org/html/draft-ietf-mptcp-architecture (especially Sections 5.4 & 9) http://tools.ietf.org/html/draft-ietf-mptcp-multiaddressed http://tools.ietf.org/html/draft-scharf-mptcp-mctcp-00.txt ------------------------------------------------------------- Thursday 1510-1610 Auditorium 1 Objectives: * Progress to fulfil our Milestone (Aug 2010) - Submit to IESG architectural guidelines and security threat analysis as informational RFC(s) * Progress on other WG drafts * Consensus to create WG draft(s) for Milestones on extended API and applications considerations. 1. Report back from Implementors workshop (10mins, Chairs) 2. Placeholder to confirm options vs payload decision (if further discussion time is needed, subsequent items may get pushed to an Audio meeting) (5mins) 3. Progress on draft-ietf-mptcp-threat (10mins, Marcelo Bagnulo) 4. Progress on draft-ietf-mptcp-architecture (5mins, Alan Ford) 5. Progress on draft-ietf-mptcp-multiaddressed (13mins, Alan Ford) 6. Progress on draft-ietf-mptcp-congestion (5mins, Costin Raicu) 7. Progress on API and application considerations (10mins, Michael Scharf) 8. Alert about work on interface between multipathing and address selection (2mins, Aleksi Suhonen) Useful reading: http://tools.ietf.org/html/draft-ietf-mptcp-architecture http://tools.ietf.org/html/draft-ietf-mptcp-multiaddressed http://tools.ietf.org/html/draft-ietf-mptcp-threat http://tools.ietf.org/html/draft-raiciu-mptcp-congestion-01.txt (note, already agreed that next version is a WG draft) http://tools.ietf.org/html/draft-scharf-mptcp-api-02.txt ------------------------------------------------------------- REMINDER Multipath TCP Implementors Workshop Saturday 24th July, 2pm start (ends about 6pm), Room 2.8 Rhine. The room is at “MECC”, the IETF venue, on Level 2 Note, limited room size, registration required to mptcp-chairs@tools.ietf.org Agenda: 1. Intro, background, assumptions - Philip Eardley 2. Demo of Linux implementation - Sebastien Barre 3. Use cases discussion – * AIM: how to improve MPTCP's design to increase its usefulness? what are the most likely apps? what ones are easiest to deploy first? * Mobility - discussion led by Lars Eggert * Data centres - discussion led by Costin Raicu 4. OS implementation – discussion led by Sebastien Barre and Costin Raicu * AIM: how to improve the chances that MPTCP makes its way into OSes? what are the requirements, constraints and potential stumbling blocks on the various platforms? what adjustments to the protocol design could lower the deployment barriers? * Changes to linux kernel – new /modified functions, implementation difficulty, status, priorities * how to get into mainline Linux kernel * how to get into other OS Below is the email about the workshop -----Original Message----- From: multipathtcp-bounces@ietf.org [mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.com Sent: 18 May 2010 10:55 To: multipathtcp@ietf.org Subject: [multipathtcp] Multipath TCP Implementors workshop,Saturday 24th July The IETF's Multipath TCP (MPTCP) working group is organising a workshop with the OS and applications communities on the Saturday afternoon immediately before the IETF meeting in Maastricht (i.e. on 24th July) (http://www.ietf.org/meeting/78/index.html) If you would like to come, please register to mptcp-chairs@tools.ietf.org. Due to room size, numbers are limited and registration is required. Multipath TCP enables a single TCP connection to use multiple network interfaces and paths simultaneously for one TCP connection. From an applications perspective, this increases resilience and enables a basic form of connection mobility, whilst from an OS perspective it requires a change to the host TCP stack. IETF working group:       http://www.ietf.org/dyn/wg/charter/mptcp-charter Supplemental information: http://nrg.cs.ucl.ac.uk/mptcp/ The objective of the workshop is to help make MPTCP real, i.e., to get it implemented in many operating systems and to get it used by key applications. This will be an interactive workshop with application designers (who would use MPTCP), OS implementors (who would implement and ship MPTCP) and MPTCP working group people (who are designing and standardising MPTCP). Note that this is not a passive "dissemination" workshop! The aim is to have an active discussion with the OS and applications communities about their requirements and needs, in order to influence and improve the MPTCP protocol design. The workshop will be highly interactive and focus on two topics: * On the one hand, it is to understand the process through which   Multipath TCP could make its way into OSes. The OS implementers   and active community members can explain their real world   requirements and constraints on the various platforms. What are   the potential stumbling blocks for MPTCP's implementation and how   could the protocol designers lower the deployment barriers? * On the other hand, the WG would like to discuss the use cases for   Multipath TCP with the applications community. What are the gotchas   and how can the protocol designers increase the usefulness of   MPTCP? Where & when? The workshop will be held on July 24, 2010 in Maastricht at the IETF meeting venue, "MECC", starting at 2pm (room to be confirmed). This is the Saturday afternoon before the start of the IETF week. We hope that remote participation will also be possible, via Webex. We would be pleased to hear feedback on the scope and purpose of the workshop. The workshop is organised under the auspices of the MPTCP working group, but is not a formal WG meeting - for instance, WG consensus calls will not be made. Best wishes, Philip Eardley Yoshifumi Nishida mptcp-chairs@tools.ietf.org