Re: [multipathtcp] potential new work item on MPTCP API

"Scharf, Michael (Nokia - DE)" <> Thu, 21 July 2016 15:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5BFA112D759 for <>; Thu, 21 Jul 2016 08:53:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id WirjEp6dyRTq for <>; Thu, 21 Jul 2016 08:53:06 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 48D0612D5C5 for <>; Thu, 21 Jul 2016 08:52:54 -0700 (PDT)
Received: from (unknown []) by Websense Email Security Gateway with ESMTPS id 94D5DA2823DA5; Thu, 21 Jul 2016 15:52:49 +0000 (GMT)
Received: from ( []) by (GMO-o) with ESMTP id u6LFqqLg024482 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 21 Jul 2016 15:52:52 GMT
Received: from ( []) by (GMO) with ESMTP id u6LFqpSt028499 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 Jul 2016 17:52:51 +0200
Received: from ([]) by ([]) with mapi id 14.03.0195.001; Thu, 21 Jul 2016 17:52:51 +0200
From: "Scharf, Michael (Nokia - DE)" <>
To: "" <>, "" <>
Thread-Topic: potential new work item on MPTCP API
Thread-Index: AdHjY9uMuLhvUNPnTqK0jHsvvSjLBQAA8xGA
Date: Thu, 21 Jul 2016 15:52:51 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: de-DE, en-US
Content-Language: de-DE
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_655C07320163294895BBADA28372AF5D4892D4F2FR712WXCHMBA15z_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [multipathtcp] potential new work item on MPTCP API
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-path extensions for TCP <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 21 Jul 2016 15:53:09 -0000

As author of RFC 6897 I'd be fine with revisiting that document as some aspects may be a bit outdated. I have not closely followed MPTCP recently but I'd assume that parts of RFC 6897 are still valid.


From: multipathtcp [] On Behalf Of
Sent: Thursday, July 21, 2016 5:43 PM
Subject: [multipathtcp] potential new work item on MPTCP API

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