[multipathtcp] potential new work item on MPTCP API

<philip.eardley@bt.com> Thu, 21 July 2016 15:43 UTC

Return-Path: <philip.eardley@bt.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 458B512B031 for <multipathtcp@ietfa.amsl.com>; Thu, 21 Jul 2016 08:43:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.888
X-Spam-Status: No, score=-3.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Gwf5wpf4o2SH for <multipathtcp@ietfa.amsl.com>; Thu, 21 Jul 2016 08:43:15 -0700 (PDT)
Received: from smtpb1.bt.com (smtpb1.bt.com []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DF2C12D77E for <multipathtcp@ietf.org>; Thu, 21 Jul 2016 08:43:15 -0700 (PDT)
Received: from EVMHT04-UKBR.domain1.systemhost.net ( by EVMED01-UKBR.bt.com ( with Microsoft SMTP Server (TLS) id; Thu, 21 Jul 2016 16:43:09 +0100
Received: from rew09926dag03b.domain1.systemhost.net ( by EVMHT04-UKBR.domain1.systemhost.net ( with Microsoft SMTP Server (TLS) id 8.3.342.0; Thu, 21 Jul 2016 16:43:13 +0100
Received: from rew09926dag03b.domain1.systemhost.net ( by rew09926dag03b.domain1.systemhost.net ( with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 21 Jul 2016 16:43:12 +0100
Received: from rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e]) by rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e%12]) with mapi id 15.00.1178.000; Thu, 21 Jul 2016 16:43:12 +0100
From: <philip.eardley@bt.com>
To: <multipathtcp@ietf.org>
Thread-Topic: potential new work item on MPTCP API
Thread-Index: AdHjY9uMuLhvUNPnTqK0jHsvvSjLBQ==
Date: Thu, 21 Jul 2016 15:43:12 +0000
Message-ID: <3b62f69a53554789966e8a281a4000d7@rew09926dag03b.domain1.systemhost.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_3b62f69a53554789966e8a281a4000d7rew09926dag03bdomain1sy_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/ZOxH-lgscfxwzjPOQy6f1edarEA>
Subject: [multipathtcp] potential new work item on MPTCP API
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 21 Jul 2016 15:43:18 -0000

Yesterday Olivier presented about his & Benjamin's recent work on MPTCP socket api. We didn't have much discussion whether to add this to the charter. One comment was that any work should build on /reference RFC6897.
Please can you comment whether you see this as a useful work item, or you think it shouldn't be worked on, or how it should be adapted to something you think the WG should work on.

To help prompt the discussion, here's a very first version of some possible charter text
RFC6897 defined an optional, basic application interface for MPTCP-aware applications, including a set of socket operations. Now there is more experience of how MPTCP is being used, the WG will re-visit this work, and consider adding more advanced socket operations.

RFC6897 was Informational - would this new Milestone be Informational or Experimental?


Philip Eardley
Research and Innovation
This email contains BT information, which may be privileged or confidential. It's meant only for the individual(s) or entity named above. If you're not the intended recipient, note that disclosing, copying, distributing or using this information is prohibited. If you've received this email in error, please let me know immediately on the email address above. Thank you.
We monitor our email system, and may record your emails.
British Telecommunications plc
Registered office: 81 Newgate Street London EC1A 7AJ
Registered in England no: 1800000