Re: [multipathtcp] Towards a Multipath TCP Proxy work item
<Markus.Brunner3@swisscom.com> Tue, 15 November 2016 07:57 UTC
Return-Path: <Markus.Brunner3@swisscom.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 53E3E1294E3 for <multipathtcp@ietfa.amsl.com>; Mon, 14 Nov 2016 23:57:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.706
X-Spam-Level:
X-Spam-Status: No, score=-5.706 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
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 GbKZeIu50dY8 for <multipathtcp@ietfa.amsl.com>; Mon, 14 Nov 2016 23:57:55 -0800 (PST)
Received: from mail.swisscom.com (outmail110.swisscom.com [193.222.81.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77ED8129459 for <multipathtcp@ietf.org>; Mon, 14 Nov 2016 23:57:54 -0800 (PST)
Received: by mail.swisscom.com; Tue, 15 Nov 2016 08:57:50 +0100
From: Markus.Brunner3@swisscom.com
To: philip.eardley@bt.com, alan.ford@gmail.com
Thread-Topic: [multipathtcp] Towards a Multipath TCP Proxy work item
Thread-Index: AdI7N1nf0aKADf/wTiuUhe6Yz4SJ8QATzjrQAKu92wAAALmrAAA3YR2A
Date: Tue, 15 Nov 2016 07:57:48 +0000
Message-ID: <0B758A41-338E-4E3B-B4D2-53DB8DF71610@swisscom.com>
References: <0898853c01b245aa8b3c45c9da478d6a@rew09926dag03b.domain1.systemhost.net> <286B053B-7E5E-4FD8-A767-DAC55E8D42C9@gmail.com> <1479105129326.45083@bt.com>
In-Reply-To: <1479105129326.45083@bt.com>
Accept-Language: de-CH, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [138.190.134.7]
Content-Type: multipart/alternative; boundary="_000_0B758A41338E4E3BB4D253DB8DF71610swisscomcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/kQ6Q97GNaE6D9EnRNowleIy2SoI>
Cc: multipathtcp@ietf.org
Subject: Re: [multipathtcp] Towards a Multipath TCP Proxy work item
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: Tue, 15 Nov 2016 07:57:57 -0000
Phil, If you feel it would take too long and to be too complex to achieve in a reasonable timeframe, we are ok with excluding non-tcp traffic, however, for our total solution we do requires also non-tcp traffic to be sent over multiple paths. We could argue that we can use a different mechanisms specifically for UDP and other protocols, but it would be nice to have as single MPTCP-based solution. (my gut feeling is that we would need to replicate a lot of MPTCP scheduling features into a new mechanism). Marcus Von: multipathtcp <multipathtcp-bounces@ietf.org> im Auftrag von "philip.eardley@bt.com" <philip.eardley@bt.com> Datum: Montag, 14. November 2016 um 07:32 An: "alan.ford@gmail.com" <alan.ford@gmail.com> Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org> Betreff: Re: [multipathtcp] Towards a Multipath TCP Proxy work item i think we should move beyond "exploring whether it would be useful". i'd like us to assess proposed solutions. i think we should say this is what we're doing - at the moment we've had quite a lot of discussion about one proposal. we should give the chance for other proposals, and make the discussion more structured (what are the assessment criteria). i also think we should explicitly exclude non-tcp traffic (i think non-tcp traffic is too big a topic for our WG) phil ________________________________ From: Alan Ford <alan.ford@gmail.com> Sent: 14 November 2016 06:11 To: Eardley,PL,Philip,TUB8 R Cc: multipathtcp@ietf.org Subject: Re: [multipathtcp] Towards a Multipath TCP Proxy work item I think this work item is achievable by simply removing references to “at least one end” from the existing charter item on the proxy. So the item would now read: Finally, the working group will explore whether an MPTCP-aware middlebox would be useful. For example, potentially helping MPTCP’s incremental deployment by allowing only one end host to be MPTCP-enabled and the middlebox acts as an MPTCP proxy for the other end host, which runs TCP; and potentially helping some mobility scenarios, where the middle box acts as an anchor between two MPTCP-enabled hosts. Alternatively, neither end host could be MPTCP-enabled but a pair of proxies could work together to bring MPTCP benefits to such connections. The working group will detail what real problems an MPTCP-enabled middlebox might solve, how it would impact the Multipath TCP architecture (RFC6182), what proxy approach might be justified as compared against alternative solutions to the problems, and the likely feasibility of solving the technical and security issues. In some ways, the two ended proxy work could even be seen as an extension of the previous operational experience work within this WG. Regards, Alan On 10 Nov 2016, at 19:17, philip.eardley@bt.com<mailto:philip.eardley@bt.com> wrote: Hi, Perhaps this is speaking too soon, but it looks like the very active discussion is reaching some common understanding? We’re trying to work out what a work item might look like, so would like to understand what assumptions we would make, eg about the scenario, & what common agreements we’d assume & restrictions on how the solution works. This seems important to frame work by WG. If possible we’d like discussion on these points to avoid getting into the fine details of one particular existing proposal. What we’d appreciate is a summary of what the assumptions /understandings are about: • The scenario (for instance: the MPTCP-enabled host knows the address of the proxy (eg through configuration); and it knows the address of the ‘legacy’ host it wants to communicate with) • If any impact is already envisaged on the current MPTCP protocol’s fallback behaviour and coping with middleboxes • If we can agree that the solution is based on a new MPTCP option • If any impact is already envisaged on the current MPTCP protocol’s semantics (other than the new option) eg in terms of https://tools.ietf.org/html/rfc6824#section-4 • If any impact is already envisaged on TCP’s semantics, or any mods are needed, or assumptions about its behaviour, etc • If any impact is already envisaged on other existing transport protocol’s semantics (presuming people still would like non-TCP in scope?) • Anything else that you think is needed in order to frame the work item It may be clearer to do this for the two use cases (single-ended proxy, ie where only one host is MPTCP-enabled; and double-ended proxy, ie where neither host is MPTCP-enabled). This may seem like a long list, but most of the answers can be “none” – we’ll end up with just a short paragraph or a few bullets in the charter. We’d also have to work out interactions with non-MPTCP WGs, but Mirja and IESG will probably want the main input on this. Thanks Phil & Yoshi _______________________________________________ multipathtcp mailing list multipathtcp@ietf.org<mailto:multipathtcp@ietf.org> https://www.ietf.org/mailman/listinfo/multipathtcp
- [multipathtcp] Towards a Multipath TCP Proxy work… philip.eardley
- [multipathtcp] Single-ended Multipath TCP Proxy w… Olivier Bonaventure
- [multipathtcp] Dual-ended Multipath TCP Proxy wor… Olivier Bonaventure
- Re: [multipathtcp] Single-ended Multipath TCP Pro… Joe Touch
- Re: [multipathtcp] Single-ended Multipath TCP Pro… Olivier Bonaventure
- Re: [multipathtcp] Single-ended Multipath TCP Pro… Joe Touch
- Re: [multipathtcp] Towards a Multipath TCP Proxy … Alan Ford
- Re: [multipathtcp] Towards a Multipath TCP Proxy … philip.eardley
- Re: [multipathtcp] Towards a Multipath TCP Proxy … mohamed.boucadair
- Re: [multipathtcp] Towards a Multipath TCP Proxy … philip.eardley
- Re: [multipathtcp] Towards a Multipath TCP Proxy … Henderickx, Wim (Nokia - BE)
- Re: [multipathtcp] Towards a Multipath TCP Proxy … Olivier Bonaventure
- Re: [multipathtcp] Towards a Multipath TCP Proxy … Olivier Bonaventure
- Re: [multipathtcp] Towards a Multipath TCP Proxy … Henderickx, Wim (Nokia - BE)
- Re: [multipathtcp] Towards a Multipath TCP Proxy … N.Leymann
- Re: [multipathtcp] Towards a Multipath TCP Proxy … David Allan I
- Re: [multipathtcp] Towards a Multipath TCP Proxy … mohamed.boucadair
- Re: [multipathtcp] Towards a Multipath TCP Proxy … Markus.Brunner3
- Re: [multipathtcp] Towards a Multipath TCP Proxy … mohamed.boucadair
- Re: [multipathtcp] Towards a Multipath TCP Proxy … Robert Skog