Re: [multipathtcp] Offload MPTCP Proxy (was RE: potential MPTCP proxy charter item)

<> Tue, 08 November 2016 07:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 02986129515 for <>; Mon, 7 Nov 2016 23:08:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.116
X-Spam-Status: No, score=-4.116 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id S7S8iAtNjmOO for <>; Mon, 7 Nov 2016 23:08:16 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 30EB0129497 for <>; Mon, 7 Nov 2016 23:08:16 -0800 (PST)
Received: from (unknown [xx.xx.xx.65]) by (ESMTP service) with ESMTP id AA3FB180379; Tue, 8 Nov 2016 08:08:14 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.10]) by (ESMTP service) with ESMTP id 7CBDE1A0083; Tue, 8 Nov 2016 08:08:14 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM5C.corporate.adroot.infra.ftgroup ([fe80::4bd:9b2b:3651:6fba%19]) with mapi id 14.03.0319.002; Tue, 8 Nov 2016 08:08:14 +0100
To: "" <>
Thread-Topic: [multipathtcp] Offload MPTCP Proxy (was RE: potential MPTCP proxy charter item)
Thread-Index: AQHSORDnIoSKbSpHIUyVnwAFO1k5B6DOoymg
Date: Tue, 08 Nov 2016 07:08:14 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009DADED1@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B933009DAD705@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20161107160628.GG3546@Chimay.local>
In-Reply-To: <20161107160628.GG3546@Chimay.local>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Cc: "" <>
Subject: Re: [multipathtcp] Offload MPTCP Proxy (was RE: potential MPTCP proxy charter item)
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-path extensions for TCP <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 08 Nov 2016 07:08:18 -0000

Hi Christoph, 

Please see inline.


> -----Message d'origine-----
> De : []
> Envoyé : lundi 7 novembre 2016 17:06
> Cc :; Mirja Kühlewind; Alan Ford;
> Objet : Re: [multipathtcp] Offload MPTCP Proxy (was RE: potential MPTCP
> proxy charter item)
> Hello,
> On 07/11/16 - 15:03:49, wrote:
> > I'm not sure it is that clear we need to systematically include
> MP_CAPABLE option in the SYN to the ultimate server. I see some value
> there...but also some side effects. I'm reiterating what I already said in
> this thread:
> >
> > (+) I see "a big benefit" for some operators to offload the MTPCP
> proxies if the server is MPTCP-capable.
> I think it is not only for "offloading" but also just to allow for native
> MPTCP. When there is a choice between native MPTCP and proxied MPTCP, the
> former should always be preferred. I guess we all agree on that.

[Med] I hear you Christoph, but I think we need to elaborate a little bit further to understand what are the incentives for an MCP to be removed from the path. Optimizing the use of MCP resources has a clear benefit for an operator because this is about OPEX/CAPEX.

> > (-) I don’t see "a big benefit" for the client from a QoE perspective,
> because they already have the MPTCP experience with the network assistance
> (network aggregation, path resiliency).
> When MPTCP goes end-to-end, the routing is optimal because the TCP-
> subflows
> don't have to go through a detour to reach the proxy. 

[Med] You are making an invalid assumption here about forwarding. This is deployment-specific. An MCP proxy can also be on-path. BTW, path stretch is a requirement for deciding the location of an MCP. This is clearly mentioned the deployment I-D.

The path through the
> proxy is always less or equally as good as the direct path.

[Med] You are right. My comment was not about the basic delay transfer, but about the "MPTCP experience": network aggregation, path resiliency.  Of course a proxy may fail, but means to protect carrier grade functions are widely in use in operators networks.

> From a QoE perspective I see a benefit in that the native server has more
> info on the traffic-characteristics it is sending to the client. So it can
> optimize based on this. This info (coming from the server-side) is not
> available to the proxy.

[Med] I see your point, but there are cases (mainly in the cellular world) that may require some knowledge of the radio cells to react quickly to congestions. FWIW, some experiments were conducted to define an API that can be exposed to a content provider to help for direct delivery without involving a proxy. The server has not to be aggressive to the network. Having information from the network to the server, and vice versa would be ideal.  

> > (-) I don’t see "a big benefit" for the client if the MPTCP-capable
> server decides to use a given path to place data, while that path is
> subject to a data volume quota. This means that the client will be mono-
> path quickly if an MPTCP-capable server adopts some traffic distribution
> schemes.
> This shows that we need signalling on an MPTCP-connection so that the
> client
> can tell the server "don't send on this subflow now". We actually already
> have
> this with the MP_PRIO-option, but something more sophisticated might be
> needed.

[Med] Agree. Having an option would help but it still this is tricky because an MPTCP client may not have access to "subscription" information. It may use the interface technology as a hint, but still this a hint. Other complications may arise to acquire such information.

> While a proxy might have access to the data-quota and can schedule traffic
> based on this, data-quota is not the only variable that makes one want to
> avoid cellular. If the device is a mobile device, battery-constraints come
> into play as well.

[Med] Agree, too. 

> Christoph
> >
> > That said, I have no problem to leave this as a configurable parameter.
> A configuration knob can be supported to instruct the MCP about the
> behavior to follow. Also, a white list of servers can be provided to the
> MCP.
> >
> > This is exactly the kind of technical considerations for which we need a
> formal WG document so that we can record the WG decision.
> >
> > Cheers,
> > Med
> >
> > > -----Message d'origine-----
> > > De : Olivier Bonaventure []
> > > Envoyé : dimanche 6 novembre 2016 22:12
> > > À : Mirja Kühlewind; BOUCADAIR Mohamed IMT/OLN; Alan Ford
> > > Cc :
> > > Objet : Re: [multipathtcp] potential MPTCP proxy charter item
> > >
> > >
> > > It's clear that the MCP should send the MP_CAPABLE option in the SYN
> > > towards the destination server and fallback to TCP is this fails.
> Since
> > > there are some middleboxes that continue to silently drop the
> > > option, the MCP should be able to maintain a list of destination
> servers
> > > where it had to fallback to regular TCP (e.g. after n retransmissions
> of
> > > the SYN with MP_CAPABLE as suggested in RFC6824) and no attempt to use
> > > MPTCP for these destinations. This cache should be reset on a regular
> > > basis to probe again the destination servers.
> > _______________________________________________
> > multipathtcp mailing list
> >
> >