Re: [multipathtcp] towards a potential work item on two-ended proxy

"Henderickx, Wim (Nokia - BE)" <wim.henderickx@nokia.com> Mon, 08 August 2016 16:49 UTC

Return-Path: <wim.henderickx@nokia.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 1529D12D675 for <multipathtcp@ietfa.amsl.com>; Mon, 8 Aug 2016 09:49:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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 FXzk3rhxLFH9 for <multipathtcp@ietfa.amsl.com>; Mon, 8 Aug 2016 09:49:05 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 CD73412D0FD for <multipathtcp@ietf.org>; Mon, 8 Aug 2016 09:49:04 -0700 (PDT)
Received: from fr712umx3.dmz.alcatel-lucent.com (unknown [135.245.210.42]) by Websense Email Security Gateway with ESMTPS id 2BBEDE198E885; Mon, 8 Aug 2016 16:48:59 +0000 (GMT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1.zeu.alcatel-lucent.com [135.239.2.122]) by fr712umx3.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u78Gn2RH001407 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 8 Aug 2016 16:49:02 GMT
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id u78Gn1lQ003206 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 8 Aug 2016 18:49:02 +0200
Received: from FR711WXCHMBA07.zeu.alcatel-lucent.com ([169.254.3.82]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Mon, 8 Aug 2016 18:49:01 +0200
From: "Henderickx, Wim (Nokia - BE)" <wim.henderickx@nokia.com>
To: "philip.eardley@bt.com" <philip.eardley@bt.com>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: [multipathtcp] towards a potential work item on two-ended proxy
Thread-Index: AQHR7DWI+H5KVobs2E61DPJLQEiUPaA1odiAgABSA4CACL40gIAAnxMA
Date: Mon, 8 Aug 2016 16:49:01 +0000
Message-ID: <05931B1F-5F73-472A-A544-5498899D0096@nokia.com>
References: <b779dd12f1bb412c96c800eddaaf0247@rew09926dag03b.domain1.systemhost.net> <e2aa6ac517194af4b8c25c07f8e469fb@rew09926dag03b.domain1.systemhost.net> <9cafc779-502e-cc7f-676c-f6659e207c81@uclouvain.be> <5fadd9cfcc01401b84db03052e165c69@rew09926dag03b.domain1.systemhost.net> <D3994CAB-846A-4418-A399-C48D196717A3@nokia.com> <1612497ced7e4f288781dfd89ff1e6cf@rew09926dag03b.domain1.systemhost.net> <07C3A957-7706-4A26-9D7B-864C6B93D157@nokia.com> <8b32db1c85584a7f879ae47e05374ca4@rew09926dag03b.domain1.systemhost.net>
In-Reply-To: <8b32db1c85584a7f879ae47e05374ca4@rew09926dag03b.domain1.systemhost.net>
Accept-Language: nl-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/0.0.0.151008
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="utf-8"
Content-ID: <15DD2033F070E243BB81D3282C3167AE@exchange.lucent.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/Yv_f1oBtW5GD3bMYREF6who9OE0>
Subject: Re: [multipathtcp] towards a potential work item on two-ended proxy
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: Mon, 08 Aug 2016 16:49:06 -0000

Phil, in-line




On 08/08/16 11:19, "philip.eardley@bt.com" <philip.eardley@bt.com> wrote:

>>
>>Phil:
>>What are the interactions with endhost-to-endhost MPTCP?  I imagined there wouldn’t be any, but it sounds like there are some.
>
>WH> there should be none, but the proxy should ensure he doesn’t touch it. Hence we are looking to understand if a dual ended proxy should  perform a proxy function or not. So the end-host is not impacted but the network-assisted proxies would be made aware what to do. Make sense?
>> 
>Afraid not. 
>(personal view) if I get it right, a (?router, ?proxy) has to distinguish whether the (?mptcp signalling message ?every packet) is part of end-to-end mptcp connection, or part of mptcp proxied connection. That seems to add overhead, an may mean you have to be careful about the deployment.

> 
>A dual ended proxy so far was meant in a controlled environment, so indeed if you have this requirement you need to control deployment.