[multipathtcp] explicit mode for smartphone scenario

<philip.eardley@bt.com> Fri, 24 March 2017 23:36 UTC

Return-Path: <philip.eardley@bt.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 7A2CF1293DB for <multipathtcp@ietfa.amsl.com>; Fri, 24 Mar 2017 16:36:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.397
X-Spam-Level:
X-Spam-Status: No, score=-5.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] 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 WJSI3xOYNR5y for <multipathtcp@ietfa.amsl.com>; Fri, 24 Mar 2017 16:36:54 -0700 (PDT)
Received: from smtpb1.bt.com (smtpb1.bt.com [62.7.242.137]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1351127342 for <multipathtcp@ietf.org>; Fri, 24 Mar 2017 16:36:53 -0700 (PDT)
Received: from EVMHT05-UKBR.domain1.systemhost.net (193.113.108.58) by EVMED03-UKBR.bt.com (10.216.161.33) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 24 Mar 2017 23:36:46 +0000
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by EVMHT05-UKBR.domain1.systemhost.net (193.113.108.58) with Microsoft SMTP Server (TLS) id 8.3.342.0; Fri, 24 Mar 2017 23:36:51 +0000
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by rew09926dag03b.domain1.systemhost.net (10.55.202.22) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 24 Mar 2017 23:36:50 +0000
Received: from rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e]) by rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e%12]) with mapi id 15.00.1210.000; Fri, 24 Mar 2017 23:36:50 +0000
From: <philip.eardley@bt.com>
To: <multipathtcp@ietf.org>
Thread-Topic: explicit mode for smartphone scenario
Thread-Index: AdKk89pFNH1mP7GcQzmQXaZZ59UVOQ==
Date: Fri, 24 Mar 2017 23:36:50 +0000
Message-ID: <11215e1e3fdf4500958a24524d123bf0@rew09926dag03b.domain1.systemhost.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.216.161.24]
Content-Type: multipart/alternative; boundary="_000_11215e1e3fdf4500958a24524d123bf0rew09926dag03bdomain1sy_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/917Bnn16LkFBVHVwcXS2kax2VEA>
Subject: [multipathtcp] explicit mode for smartphone scenario
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
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, 24 Mar 2017 23:36:56 -0000

Hi,
So continuing to concentrate first **specifically** on the solution for this use case:

<<. The other scenario involves an MPTCP-enabled smartphone, with LTE and WiFi, plus a proxy in the operator's network.>>
And now looking at "explicit" solutions - meaning the smartphone is configured to know about the proxy.

I'd like to understand better the pros and cons of the solution proposed in the plain-mode draft and the solution that uses SOCKS protocol between smartphone and the proxy.  (I'm not sure where /if the latter is fully defined, described in https://www.ietf.org/proceedings/93/slides/slides-93-mptcp-3.pdf  and   https://dial.uclouvain.be/downloader/downloader.php?pid=thesis%3A366&datastream=PDF_01

Thanks
phil