[multipathtcp] Collection of MPTCP proxy scenarios.

"Weixinpeng (Jackie)" <weixinpeng@huawei.com> Mon, 27 April 2015 08:21 UTC

Return-Path: <weixinpeng@huawei.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 B109A1B2EEE for <multipathtcp@ietfa.amsl.com>; Mon, 27 Apr 2015 01:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 dwWfKSVgfe8P for <multipathtcp@ietfa.amsl.com>; Mon, 27 Apr 2015 01:21:00 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4027B1B2ED6 for <multipathtcp@ietf.org>; Mon, 27 Apr 2015 01:21:00 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BVJ32179; Mon, 27 Apr 2015 08:20:58 +0000 (GMT)
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 27 Apr 2015 09:20:57 +0100
Received: from NKGEML507-MBX.china.huawei.com ([169.254.5.79]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001; Mon, 27 Apr 2015 16:20:48 +0800
From: "Weixinpeng (Jackie)" <weixinpeng@huawei.com>
To: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: Collection of MPTCP proxy scenarios.
Thread-Index: AdCAwvpNnNPeumeBQfS9+TLGmrSnhw==
Date: Mon, 27 Apr 2015 08:20:48 +0000
Message-ID: <C5C3BB522B1DDF478AA09545169155B46E336D13@nkgeml507-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.76.176]
Content-Type: multipart/alternative; boundary="_000_C5C3BB522B1DDF478AA09545169155B46E336D13nkgeml507mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/vaySgPVIZ0-GgAgh1e_4rtcZ5T0>
Cc: "Weixinpeng (Jackie)" <weixinpeng@huawei.com>
Subject: [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: Mon, 27 Apr 2015 08:21:02 -0000

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