Re: [multipathtcp] Collection of MPTCP proxy scenarios.

Jordan Melzer <Jordan.Melzer@telus.com> Thu, 30 April 2015 17:13 UTC

Return-Path: <Jordan.Melzer@telus.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17EA61A9044 for <multipathtcp@ietfa.amsl.com>; Thu, 30 Apr 2015 10:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level:
X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 qJXGEqi3XzlO for <multipathtcp@ietfa.amsl.com>; Thu, 30 Apr 2015 10:13:01 -0700 (PDT)
Received: from donder.nssi.telus.com (donder.nssi.telus.com [208.38.59.82]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9691A8A8D for <multipathtcp@ietf.org>; Thu, 30 Apr 2015 10:13:00 -0700 (PDT)
DomainKey-Signature: s=donder.nssi; d=telus.com; c=nofws; q=dns; h=X-IronPort-Anti-Spam-Filtered: X-IronPort-Anti-Spam-Result:X-IronPort-AV:Received: Received:From:To:Date:Subject:Thread-Topic:Thread-Index: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: acceptlanguage:Content-Type:MIME-Version; b=OvwOSa08kPQ0CDiHbK7V1fS94Krt3oaPZJq7J5nBVx+8oVIRphO5/cww fQrz8SSM4Dp9KXyw731AXcPe9wHEp5eeeQBOCQGvYeAnEVN3qHurcEE/H WnwPFjGCZEGJB+kCiQnigVLQ/3lEBRP47ZDf0zbgMIqFR8Mti+vd2CEbE s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2B+BAA9YkJV/5Jjso5cgkUhJlNcgxutKpUKCYFJAQmFNk4CHIE5OBQBAQEBAQEBgQqEIAEBAQQBAQEgCiYbGwIBCA0EBAEBKAMCAgIlCxQJCAEBBBMIE4gQAQy0c5NPAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSKNoEChDoaFhcKAYItOxIdgRYFhkiFI4Nbhi2HYoYxC4pOg1AjHkKBBYIuUIJFAQEB
X-IronPort-AV: E=Sophos;i="5.11,677,1422921600"; d="scan'208,217";a="407184957"
Received: from unknown (HELO WP40081.corp.ads) ([142.178.99.146]) by donder-o.nssi.telus.com with ESMTP/TLS/AES128-SHA; 30 Apr 2015 17:12:59 +0000
Received: from WP40046.corp.ads ([::1]) by WP40081.corp.ads ([::1]) with mapi; Thu, 30 Apr 2015 11:12:59 -0600
From: Jordan Melzer <Jordan.Melzer@telus.com>
To: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Date: Thu, 30 Apr 2015 11:12:54 -0600
Thread-Topic: [multipathtcp] Collection of MPTCP proxy scenarios.
Thread-Index: AdCAwvpNnNPeumeBQfS9+TLGmrSnh///e4sA//49DdD/+HUGkA==
Message-ID: <80C0017654A043479F53C41112BE847687D93BC532@WP40046.corp.ads>
References: <C5C3BB522B1DDF478AA09545169155B46E336D13@nkgeml507-mbx.china.huawei.com> <553DF29E.7000502@tu-berlin.de> <C5C3BB522B1DDF478AA09545169155B46E337225@nkgeml507-mbx.china.huawei.com>
In-Reply-To: <C5C3BB522B1DDF478AA09545169155B46E337225@nkgeml507-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_80C0017654A043479F53C41112BE847687D93BC532WP40046corpad_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/Ynjrm21dgrvof7G6SRT5_ktKTGU>
Subject: Re: [multipathtcp] Collection of MPTCP proxy scenarios.
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
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: <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: Thu, 30 Apr 2015 17:13:04 -0000

Hi Xinpeng,

I have used a back-to-back MPTCP proxy setup to allow TCP to multipath over a segment of network.  My use case is allowing a home router to use more than one Internet connection.  The home router would have one MPTCP proxy and the ISP would have another.  The home devices would not need to run MPTCP, nor would any Internet servers.  The advantage of MPTCP proxies here is that the different network connections coming into the home need not have deterministic capacities, and the system supports smooth failover as well as aggregation.  DSL, LTE, cable, and WiFi (eg, from a neighbouring home) are all candidate technologies to be aggregated.

The challenge in this configuration is for the proxy to not prevent a native MPTCP device from running an end-to-end MPTCP connection.  The default proxy one gets by running a TCP proxy, eg HAPROXY, on a machine running an MPTCP kernel doesn’t avoid proxying MP_JOINs from sessions it doesn’t know about and doesn’t keep the keys the same on both sides of the connection, preventing an MPTCP capable home client from successfully doing an MP_JOIN using a path that doesn’t go through the home proxy.

One could probably modify HAPROXY to do this behaviour or make nftables rules that make MPTCP traffic bypass the proxies altogether.

I am not entirely satisfied that this kind of setup is a great idea, but the use case of bonding different connections together without changing anything at the ends of the network could be compelling.

Jordan

From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of Weixinpeng (Jackie)
Sent: April 28, 2015 11:14 PM
To: lukasz.budzisz@tu-berlin.de; multipathtcp@ietf.org
Subject: Re: [multipathtcp] Collection of MPTCP proxy scenarios.

Hi Lukasz,
         Thanks for your information.
         I have read through the document, and find it an interesting solution, but I think the solution in the document is
about how to transmit traditional TCP traffic through multipath, and it is a bit of different from MPTCP protocol.
         Thanks.
Regards,
Xinpeng

From: Lukasz Budzisz [mailto:lukasz.budzisz@tu-berlin.de]
Sent: Monday, April 27, 2015 4:26 PM
To: Weixinpeng (Jackie)
Subject: Re: [multipathtcp] Collection of MPTCP proxy scenarios.

Dear Xinpeng,
you may have a look at the draft we presented in the IETF Paris meeting:
https://tools.ietf.org/html/draft-ayar-transparent-sca-proxy-00
Best regards,
Lukasz

------------------------------------------

Łukasz Budzisz, Ph.D.

Research Fellow

Technische Universität Berlin (TU Berlin)

Telecommunication Networks Group

Tel: +49 30 314 23836

------------------------------------------
On 27/04/15 10:20, Weixinpeng (Jackie) wrote:
Hi all,
MPTCP proxy aims to provide additional deployment support for MPTCP protocol, and the functions provided
by MPTCP proxy could involve several different aspects such as supporting establishment of MPTCP connection between
MPTCP host and traditional TCP host, aggregating of subflows to one point for security reasons,…

I am trying to figure out as many MPTCP proxy deployment scenarios as possible to have a more deep understanding
of how MPTCP proxy should work. As an example, here are some potential scenarios:
(1) MPTCP proxy in operator’s network. The operator could deploy MPTCP proxy to assist MPTCP-capable UE to communicate
with TCP server on Internet using MPTCP.
(2) MPTCP proxy in enterprise network. Enterprise network could ask all the traffic pass through security check point for security reasons,
in this case, all the subflows belong to a MPTCP connection should be aggregated at the same point.
Besides, some existing documents such as draft-deng-mptcp-proxy-01 and draft-lopez-mptcp-middlebox-00 also provide some related discussion.

So if you know some additional MPTCP proxy deployment scenarios especially the ones that have some special requirements, It will be appreciated if you could
share it here. Or if you have any other considerations on the MPTCP proxy topic, we can also discuss it here.

Thanks!

Regards,
-Xinpeng







_______________________________________________

multipathtcp mailing list

multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>

https://www.ietf.org/mailman/listinfo/multipathtcp