[multipathtcp] Multipath TCP Implementors workshop, Saturday 24th July

<philip.eardley@bt.com> Tue, 18 May 2010 09:55 UTC

Return-Path: <philip.eardley@bt.com>
X-Original-To: multipathtcp@core3.amsl.com
Delivered-To: multipathtcp@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 75EBC3A68BA for <multipathtcp@core3.amsl.com>; Tue, 18 May 2010 02:55:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.718
X-Spam-Status: No, score=-1.718 tagged_above=-999 required=5 tests=[AWL=-0.720, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id pQT5fk+dMeBT for <multipathtcp@core3.amsl.com>; Tue, 18 May 2010 02:55:08 -0700 (PDT)
Received: from smtp3.smtp.bt.com (smtp3.smtp.bt.com []) by core3.amsl.com (Postfix) with ESMTP id ADB0F3A6843 for <multipathtcp@ietf.org>; Tue, 18 May 2010 02:55:06 -0700 (PDT)
Received: from E03MVB1-UKBR.domain1.systemhost.net ([]) by smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 18 May 2010 10:54:58 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAF670.1C804B6A"
Date: Tue, 18 May 2010 10:54:30 +0100
Message-ID: <4A916DBC72536E419A0BD955EDECEDEC06364028@E03MVB1-UKBR.domain1.systemhost.net>
Thread-Topic: Multipath TCP Implementors workshop, Saturday 24th July
Thread-Index: Acr2cBy38BjdnALPRnGU5z5P+iouBw==
From: philip.eardley@bt.com
To: multipathtcp@ietf.org
X-OriginalArrivalTime: 18 May 2010 09:54:58.0385 (UTC) FILETIME=[2CEB0410:01CAF670]
Subject: [multipathtcp] Multipath TCP Implementors workshop, Saturday 24th July
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multipathtcp>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2010 09:55:09 -0000

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)

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:
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

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

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