Re: [multipathtcp] explicit mode for smartphone scenario

<mohamed.boucadair@orange.com> Mon, 27 March 2017 12:33 UTC

Return-Path: <mohamed.boucadair@orange.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 57870129534 for <multipathtcp@ietfa.amsl.com>; Mon, 27 Mar 2017 05:33:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level:
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 XAcXaTX7N4YZ for <multipathtcp@ietfa.amsl.com>; Mon, 27 Mar 2017 05:33:49 -0700 (PDT)
Received: from relais-inet.orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA512129537 for <multipathtcp@ietf.org>; Mon, 27 Mar 2017 05:33:48 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id 32E5116017B for <multipathtcp@ietf.org>; Mon, 27 Mar 2017 14:33:47 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.32]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 068D8180071; Mon, 27 Mar 2017 14:33:47 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM32.corporate.adroot.infra.ftgroup ([fe80::8924:188:2124:a046%19]) with mapi id 14.03.0319.002; Mon, 27 Mar 2017 14:33:46 +0200
From: <mohamed.boucadair@orange.com>
To: "philip.eardley@bt.com" <philip.eardley@bt.com>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: explicit mode for smartphone scenario
Thread-Index: AdKk89pFNH1mP7GcQzmQXaZZ59UVOQCAPZeQ
Date: Mon, 27 Mar 2017 12:33:46 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009E40EF8@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <11215e1e3fdf4500958a24524d123bf0@rew09926dag03b.domain1.systemhost.net>
In-Reply-To: <11215e1e3fdf4500958a24524d123bf0@rew09926dag03b.domain1.systemhost.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.3]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933009E40EF8OPEXCLILMA3corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/ztapLxxc5GvGTNAE-qrxMNKd1tE>
Subject: Re: [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: Mon, 27 Mar 2017 12:33:51 -0000

Hi Phil,

The main issues with SOCKS are:

·         Too chatty: Up to 6 messages to establish a subflow

·         Introduce extra delay to establish MPTCP connections: several tens of ms were reported.

·         Some issues with incoming connections (compatibility with UPnP IGD).


You can refer to slides 14 and 18: https://www.ietf.org/proceedings/95/slides/slides-95-mptcp-1.pdf

Cheers,
Med

De : multipathtcp [mailto:multipathtcp-bounces@ietf.org] De la part de philip.eardley@bt.com
Envoyé : vendredi 24 mars 2017 18:37
À : multipathtcp@ietf.org
Objet : [multipathtcp] explicit mode for smartphone scenario

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