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

"Henderickx, Wim (Nokia - BE)" <> Wed, 03 August 2016 18:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CE3D312D0B0 for <>; Wed, 3 Aug 2016 11:58:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id E6BK7jCkOf2z for <>; Wed, 3 Aug 2016 11:58:17 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AEFFA12D51A for <>; Wed, 3 Aug 2016 11:58:16 -0700 (PDT)
Received: from (unknown []) by Websense Email Security Gateway with ESMTPS id 0AA24A52AEE72; Wed, 3 Aug 2016 18:58:09 +0000 (GMT)
Received: from ( []) by (GMO-o) with ESMTP id u73IwCPX015472 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 3 Aug 2016 18:58:12 GMT
Received: from ( []) by (GMO) with ESMTP id u73IwBgt004204 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 3 Aug 2016 20:58:12 +0200
Received: from ([]) by ([]) with mapi id 14.03.0195.001; Wed, 3 Aug 2016 20:58:11 +0200
From: "Henderickx, Wim (Nokia - BE)" <>
To: Alan Ford <>
Thread-Topic: [multipathtcp] towards a potential work item on two-ended proxy
Thread-Index: AQHR6/78+H5KVobs2E61DPJLQEiUPaA0T3oAgAAn1gCAARlmAIAAeo6AgACqOQCAAOR5AA==
Date: Wed, 3 Aug 2016 18:58:10 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: nl-BE, en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_FCC775C9EA484E7DA48D3059C255569Anokiacom_"
MIME-Version: 1.0
Archived-At: <>
Cc: "" <>
Subject: Re: [multipathtcp] towards a potential work item on two-ended proxy
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: Wed, 03 Aug 2016 18:58:19 -0000

Alan, in-line

From: Alan Ford <<>>
Date: Wednesday 3 August 2016 at 09:20
To: Wim Henderickx <<>>
Cc: Rao Shoaib <<>>, "<>" <<>>
Subject: Re: [multipathtcp] towards a potential work item on two-ended proxy

Hi Wim, all,

Comment inline...

On 2 Aug 2016, at 20:11, Henderickx, Wim (Nokia - BE) <<>> wrote:
On 02/08/16 15:52, "Alan Ford" <<>> wrote:

I’m trying to distinguish the various use cases; can we confirm this is correct?

Transparent Mode
- Source address = real source address
WH> not always since NAT can be in the path
- Destination address = real destination address
- Transparent proxies create MPTCP functionality in the stream, adding and removing the MPTCP headers, mapping seq numa, etc
- Latest proposal is to add an indicator to say “this is proxied” so that a proxy can intercept it
WH> indeed or not intercept it based on the indication

Plain Mode
- Source address = real source
WH> could also be NATed in some use cases
- Destination address = proxy destination address
- Signalling protocol inside indicates real destination address
WH> or SRC address

So - please correct me if this is wrong - but the main difference is that Plain Mode is targeted towards a proxy server whereas the transparent mode does not change src/dst addresses?
WH> the main difference is mainly DST IP is changed to get explicit routing to the proxy versus being implicit in the transparent case

OK, so my understanding appears correct here.
WH> yes

The issue I see with a generic proxy bit is that it does not contain any context about what kind of proxy is being intercepted. You could be sending in good faith expecting it to be picked up by Proxy from Operator A, but in fact is picked up by Operator B.
WH> the network assisted proxy is mainly targeting single operator/controlled operator use cases to avoid these issues.

As I’ve said before, the plain mode option is not MPTCP-specific and is simple a signal that says “everything that follows is actually targeted for IP address a.b.c.d” - this is entirely transport-agnostic. If the HAG could know where to find a proxy (e.g. a well-known anycast address) then addresses could be rewritten and packets forwarded, with no need for any MPTCP protocol changes.
WH> you would still need to know the original destination IP@ that the application wanted to go to.

Which is the point of the signalling protocol - the proposed “plain mode option” which is actually carried in the payload. My issue with this is that this is _not MPTCP-specific_. This is simply a signal above the transport layer to inform a proxy what the real destination is.

WH> I hear, you and I understand but we have an explicit use case for this with MPTCP and so far not in any other protocol. Hence I think it is good to extend MPTCP with this capability and liase with other WG(s) about this.