Re: [multipathtcp] draft-boucadair-mptcp-plain-mode-07

Mingui Zhang <> Fri, 01 July 2016 02:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 98B8A12D08D for <>; Thu, 30 Jun 2016 19:47:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id saoa_Bw1fOh6 for <>; Thu, 30 Jun 2016 19:47:56 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 06B0512B077 for <>; Thu, 30 Jun 2016 19:47:54 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id CMY91183; Fri, 01 Jul 2016 02:47:52 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Fri, 1 Jul 2016 03:47:50 +0100
Received: from ([fe80::a54a:89d2:c471:ff]) by ([]) with mapi id 14.03.0235.001; Fri, 1 Jul 2016 10:47:47 +0800
From: Mingui Zhang <>
To: "" <>, "" <>, "" <>
Thread-Topic: [multipathtcp] draft-boucadair-mptcp-plain-mode-07
Thread-Index: AQHRvDS7HI9JfmbW4UOj9XGa1EY3EJ/e2NIAgCQl5AA=
Date: Fri, 1 Jul 2016 02:47:47 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.5775D9D9.002F, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: b7356afac8419864b0fedb55675a86b0
Archived-At: <>
Subject: Re: [multipathtcp] draft-boucadair-mptcp-plain-mode-07
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: Fri, 01 Jul 2016 02:47:58 -0000


In the paired MPTCP proxies mechanism, there is user's TCP session and there is also multipath TCP session. It is a TCP over TCP idea, correct? 
As for TCP over TCP, the following page explains why an internal meltdown effect would take place due to the interaction between two leveled retransmission mechanisms.
Do we have solid solutions for this issue nowadays?


> -----Original Message-----
> From: multipathtcp [] On Behalf Of
> Sent: Wednesday, June 08, 2016 5:54 PM
> To:;
> Subject: Re: [multipathtcp] draft-boucadair-mptcp-plain-mode-07
> I believe you're right that such work would be outside the charter.
> We're hoping (if we get 2 sessions) in Berlin to have some discussion about
> potential re-chartering. In practice we haven't managed to get much work
> focussed specifically on meeting the current charter item on proxy (there was
> some individual drafts a while back) - but there seems to be quite a bit of
> industry work on proxies (beyond charter's single-ended proxy). So potential
> discussion topic
> >From my perspective there seems to be some operator interest in hybrid. See
> for instance the discussions in banana bar-bofs we've had at last couple of ietfs -
> including description of the DT deployment. (note, not all hybrid solutions use
> mptcp)
> Best wishes
> phil
> -----Original Message-----
> From: multipathtcp [] On Behalf Of Behcet
> Sarikaya
> Sent: 01 June 2016 19:38
> To:
> Subject: [multipathtcp] draft-boucadair-mptcp-plain-mode-07
>  Hi all,
> Recent mails in this thread came to my attention because I work on the hybrid
> access network issues and wish to convey my views on some of the issues
> discussed.
> First of all, the claims that there is strong operator interest on this is over blown.
> Hybrid access is based on offloading some CPE traffic to 3G/LTE network, I don't
> think mobile operators are fond of such a thing.
> Also I strongly concur with Yoshi's point of CPE to convert UDP or TCP into MPTCP
> and requires Concentrators to convert back MPTCP into UDP or TCP is a complex
> process. The crux of this is the problems arising from the use of MPTCP for
> tunneling, which is what this draft is advocating.
> Here I recommend Joe Touch's Intarea draft
> on IP Tunnels in the Internet Architecture. IETF developed many tunneling
> protocols which are surveyed in this draft but none of them are TCP/MPTCP
> based.
> I also question suitability of this work to the charter. There is this charter text:
> Finally, the working group will explore whether an MPTCP-aware
>   middlebox would be useful, where at least one end host is MPTCP-enabled.
>   For example, potentially helping MPTCP's incremental deployment by
>   allowing only one end host to be MPTCP-enabled and the middlebox acts as
>   an MPTCP proxy for the other end host, which runs TCP; and potentially
>   helping some mobility scenarios, where the middlebox acts as an anchor
>   between two MPTCP-enabled hosts. The working group will detail what real
>   problems an MPTCP-enabled middlebox might solve, how it would impact the
>   Multipath TCP architecture (RFC6182), what proxy approach might be
>   justified as compared against alternative solutions to the problems, and
>   the likely feasibility of solving the technical and security issues.
> This draft has a middlebox called Concentrator but it is not trying to enable
> MPTCP hosts to communicate with TCP hosts, it is just tunneling the traffic. So
> there is no charter item that fits to this draft.
> I strongly suggest staying away from making MPTCP a tunneling protocol.
> Regards,
> Behcet
> _______________________________________________
> multipathtcp mailing list
> _______________________________________________
> multipathtcp mailing list