Re: [multipathtcp] potential new work item on MPTCP API
Christoph Paasch <cpaasch@apple.com> Fri, 22 July 2016 08:48 UTC
Return-Path: <cpaasch@apple.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id F0EFB12D9F9
for <multipathtcp@ietfa.amsl.com>; Fri, 22 Jul 2016 01:48:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.378
X-Spam-Level:
X-Spam-Status: No, score=-5.378 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001,
RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001,
RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, T_DKIM_INVALID=0.01]
autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key)
reason="fail (message has been altered)"
header.d=apple.com
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id BuEUpMhsPyXi for <multipathtcp@ietfa.amsl.com>;
Fri, 22 Jul 2016 01:48:27 -0700 (PDT)
Received: from mail-in6.apple.com (mail-out6.apple.com [17.151.62.28])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id ECB2412B05D
for <multipathtcp@ietf.org>; Fri, 22 Jul 2016 01:48:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s;
c=relaxed/simple;
q=dns/txt; i=@apple.com; t=1469177306; x=2333090906;
h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type:
Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From:
Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id:
List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
bh=LRXSeHpq5qS6pmxAyuS3fvA7Va/dH29L6bnMVHrLQZs=;
b=pIQvOaANc3WaKn/shScxl3KW3icG3B77cqRVAviNFNRd4vqGQ2Z3NkoLjRN6HA//
LKpKL0FTa5fY1cJtL1gijtco2dG8Dih0kbW1MNS1ztDBYEbv60LHOUZ/yOTKPfBt
mOMnBbpDS5ri5EPO9DuHqjC6Ab5zXaRWyR3vsGx+xJCFr5L2V8skSutN4U5rnKLS
IMgARI8wzWHqhK9cFwjyXrBtJD++AXxfbqk7De9QbHprcDwBShP2hjX8eMW2b6UI
NmdwdKqJXpca9AThaA5wGC7X0mVZaL87RXp93hqmG06KmzXeLElQrer+B16NcK2H
eSMG5u79J88BrmqKfhNs4Q==;
Received: from relay5.apple.com (relay5.apple.com [17.128.113.88])
by mail-in6.apple.com (Apple Secure Mail Relay) with SMTP id
CE.A0.07752.ADDD1975; Fri, 22 Jul 2016 01:48:26 -0700 (PDT)
X-AuditID: 11973e15-f798f6d000001e48-fe-5791ddda076f
Received: from foxglove.apple.com (foxglove.apple.com [17.171.128.130])
by relay5.apple.com (Apple SCV relay) with SMTP id 2B.60.30701.ADDD1975;
Fri, 22 Jul 2016 01:48:26 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative;
boundary="Boundary_(ID_8/xTf/ZR4ghMNuZ3j/CLSA)"
Received: from [17.168.89.14] (unknown [17.168.89.14])
by foxglove.apple.com (Oracle Communications Messaging Server 8.0.1.1.0 64bit
(built May 17 2016)) with ESMTPSA id <0OAP00JO3KGNOW00@foxglove.apple.com>;
Fri, 22 Jul 2016 01:48:26 -0700 (PDT)
Sender: cpaasch@apple.com
From: Christoph Paasch <cpaasch@apple.com>
In-reply-to: <3b62f69a53554789966e8a281a4000d7@rew09926dag03b.domain1.systemhost.net>
Date: Fri, 22 Jul 2016 10:48:25 +0200
Message-id: <82899074-7E27-4792-BBC3-222A4E869B25@apple.com>
References: <3b62f69a53554789966e8a281a4000d7@rew09926dag03b.domain1.systemhost.net>
To: Philip Eardley <philip.eardley@bt.com>
X-Mailer: Apple Mail (2.3124)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrHLMWRmVeSWpSXmKPExsUi2FAYoXvr7sRwgx3L9C0+r77OZrFs7QpG
ByaPti+TmTyWLPnJFMAUxWWTkpqTWZZapG+XwJXxbfMSxoJdSRU/H01na2A8E9rFyMkhIWAi
MWHFLBYIW0ziwr31bF2MXBxCAnsZJWY3HGGCKXp+6zojRGIHo0Tvo8VgCV4BQYkfk++BdTML
hEnMXtDBAlH0h1Hiz45DbCAJYQFJie47d5ghbAeJOxu2sYPYbAJaEm9vt7OC2JwC4RId03qB
mjk4WARUJX72i4CYzALGElNmGkGsspH4cvgJ2BQhoFXrvq8As0WApvQsuQh1p6zEk5OLwE6Q
EDjBJnH63meWCYzCs5CcOgvJqbPAVqhLTJmSCxHWlnjy7gIrhK0msfD3IiZk8QWMbKsYhXIT
M3N0M/PM9BILCnJS9ZLzczcxgiJkup3oDsYzq6wOMQpwMCrx8J54OiFciDWxrLgy9xCjNAeL
kjjvB5GJ4UIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoYj6+qz2lfFhRiyR5zoW5niYay4+bs
b0yXKpKkbk6x+jZrn96jkGyHH+f8JH5clPKZ+vaFRMwDSf4jVxKl3+nzZS3WsOD4z/aHm322
da2eUPmN2uqGzwlXFtUWXExon+MpuNZKKPnOXu+nhuI96uvL85yrbRpme3keuPsj0C07c/te
3Q+hupeUWIozEg21mIuKEwGBNWV3cQIAAA==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrBIsWRmVeSWpSXmKPExsUiuLqhSffW3YnhBju6tC0+r77OZrFs7QpG
ByaPti+TmTyWLPnJFMAUxWWTkpqTWZZapG+XwJXxbfMSxoJdSRU/H01na2A8E9rFyMkhIWAi
8fzWdUYIW0ziwr31bF2MXBxCAjsYJXofLWYCSfAKCEr8mHyPBcRmFgiTmL2ggwWi6A+jxJ8d
h9hAEsICkhLdd+4wQ9gOEnc2bGMHsdkEtCTe3m5nBbE5BcIlOqb1AjVzcLAIqEr87BcBMZkF
jCWmzDSCWGUj8eXwE7ApQkCr1n1fAWaLAE3pWXKRCeJOWYknJxexTGAUmIXkullIrpsFNlVd
YsqUXIiwtsSTdxdYIWw1iYW/FzEhiy9gZFvFKFCUmpNYaaqXWFCQk6qXnJ+7iREU0A2FETsY
/y+zOsQowMGoxMN74umEcCHWxLLiytxDjBIczEoivD13JoYL8aYkVlalFuXHF5XmpBYfYpzI
CPTiRGYp0eR8YLzllcQbmpgYmBgbmxkbm5uY01JYSZx3xrK+cCGB9MSS1OzU1ILUIpijmDg4
pRoYIxVEzrqv5En12/pm44K1Uf4PPnHdsV919PVpe8c130W75nsduXdQOb5kwqYzrK/01q7X
mxuYfivWeuZapS0XWXedZPV9EWIUY/i+Pv1e87dUpv/MWs/Ku8PXn9Cd1vv2+eP3CmtDr64s
vPg+/mZ/a3nVse3/Ej9k7br3N7My8cenTAuvI11ubUosxRmJhlrMRcWJANBdpuHbAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/wCDZw854rA6RtPpwM3xQhHOTwMg>
Cc: MultiPath TCP - IETF WG <multipathtcp@ietf.org>
Subject: Re: [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: Fri, 22 Jul 2016 08:48:29 -0000
Hello, > On Jul 21, 2016, at 5:43 PM, philip.eardley@bt.com wrote: > 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. > https://www.ietf.org/proceedings/96/slides/slides-96-mptcp-4.pdf <https://www.ietf.org/proceedings/96/slides/slides-96-mptcp-4.pdf> > 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. yes, I think it is a very useful work item and am willing to contribute to this work. I'm not sure whether this can be seen as an update to 6897. I'm under the impression that 6897 takes a different approach, giving users a high-level overview of how using MPTCP might look like to an application that is talking to a TCP-socket (which happens to end up using MPTCP). Olivier's work seems to rather make MPTCP entirely explicit to the application. So, I think both works take a different approach. > 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? I think it should be Informational. Christoph > > Thanks > phil > > 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 > > _______________________________________________ > multipathtcp mailing list > multipathtcp@ietf.org <mailto:multipathtcp@ietf.org> > https://www.ietf.org/mailman/listinfo/multipathtcp <https://www.ietf.org/mailman/listinfo/multipathtcp>
- Re: [multipathtcp] potential new work item on MPT… Olivier Bonaventure
- Re: [multipathtcp] potential new work item on MPT… Christoph Paasch
- Re: [multipathtcp] potential new work item on MPT… Scharf, Michael (Nokia - DE)
- Re: [multipathtcp] potential new work item on MPT… Christoph Paasch
- Re: [multipathtcp] potential new work item on MPT… philip.eardley
- [multipathtcp] potential new work item on MPTCP A… philip.eardley