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

Jordan Melzer <Jordan.Melzer@telus.com> Tue, 05 July 2016 15:48 UTC

Return-Path: <Jordan.Melzer@telus.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 EDD5612D0AA for <multipathtcp@ietfa.amsl.com>; Tue, 5 Jul 2016 08:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.727
X-Spam-Level:
X-Spam-Status: No, score=-5.727 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=Jordan.Melzer@telus.com header.d=telus.com
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 4lRlRV6J4AJ8 for <multipathtcp@ietfa.amsl.com>; Tue, 5 Jul 2016 08:48:00 -0700 (PDT)
Received: from donder.nssi.telus.com (donder.nssi.telus.com [208.38.59.82]) by ietfa.amsl.com (Postfix) with ESMTP id 6D5D712B004 for <multipathtcp@ietf.org>; Tue, 5 Jul 2016 08:48:00 -0700 (PDT)
DomainKey-Signature: s=donder.nssi; d=telus.com; c=nofws; q=dns; h=X-IronPort-Anti-Spam-Filtered: X-IronPort-Anti-Spam-Result:X-IronPort-AV:Received: Received:From:To:CC:Date:Subject:Thread-Topic: Thread-Index:Message-ID:References:In-Reply-To: Accept-Language:Content-Language:X-MS-Has-Attach: X-MS-TNEF-Correlator:acceptlanguage:Content-Type: Content-Transfer-Encoding:MIME-Version; b=HsX+JgMp9wqMuYBP8j1abov9tMwkaSHjZDSDzbSgZ8l5/eRvrNs92Jmk 9Rm5Rl8h6wImlkY8O7muKymFG/Hq4xg6JTWJOmNFODAUJdq1FamzfJMbe eHWXZwl+doysKfxOjRhacytKj6N2j+UZRVydtqwqZ2iHlWHKB9kuAnhyR 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2ClBABW1XtX/5Jjso5cDoMDLUkNfKEtmBmBdyKFLEoCgTQ4FAEBAQEBAQFlJ4RMAQEFAQE4GRsLDAQCAQgNBAQBAQEeCQcnCxQJCAEBBA4FCBOIFQEECbskAQEBAQEBAQEBAQEBAQEBAQEBAQEBHIYnhE2EKhiDKoIvBY54ihuGCYp2hyqFSJAKHjaDNVpPiHkBAQE
X-IronPort-AV: E=Sophos;i="5.26,580,1459814400"; d="scan'208";a="534899993"
Received: from unknown (HELO WP40081.corp.ads) ([142.178.99.146]) by donder-o.nssi.telus.com with ESMTP/TLS/AES128-SHA; 05 Jul 2016 15:47:57 +0000
Received: from WP40046.corp.ads ([::1]) by WP40081.corp.ads ([::1]) with mapi; Tue, 5 Jul 2016 09:47:57 -0600
From: Jordan Melzer <Jordan.Melzer@telus.com>
To: Joe Touch <touch@isi.edu>
Date: Tue, 5 Jul 2016 09:47:55 -0600
Thread-Topic: [multipathtcp] draft-boucadair-mptcp-plain-mode-07
Thread-Index: AdHTvfdIGR2fbGVHRB6rTxFRFD3TsQCPkb4w
Message-ID: <80C0017654A043479F53C41112BE8476897A4F31B1@WP40046.corp.ads>
References: <CAC8QAccht1nMP95HVdP6YcqJfxNryvDbhaK=LY0LcW5-JKM82A@mail.gmail.com> <e597f6bc66d24c679edee2121ae7fc38@rew09926dag03b.domain1.systemhost.net> <4552F0907735844E9204A62BBDD325E787CE22C1@NKGEML515-MBX.china.huawei.com> <68c2382a-74c9-1999-e8d4-e5aceccbf4db@uclouvain.be> <5776A7F3.1000906@isi.edu>
In-Reply-To: <5776A7F3.1000906@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/SUdzIeyeRUPiDndOK_9gOsM4Y-A>
Cc: "multipathtcp@ietf.org Mailing List \(multipathtcp@ietf.org\)" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] draft-boucadair-mptcp-plain-mode-07
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: Tue, 05 Jul 2016 15:48:03 -0000

Hi Joe,

The main RFC reference for performance enhancing proxies is here:
https://tools.ietf.org/html/rfc3135

It gives consideration to the end-to-end principle and describes deployments (current as of 2001).

Do you have an informational RFC (or other BCP) reference for routing-based approaches to multipathing individual-user traffic?

Re TCP over TCP approaches, if they could work, would you like them better than a proxy approach?  Eg, (untested) MP-DCTCP lower layer?

Jordan

-----Original Message-----
From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of Joe Touch
Sent: July 1, 2016 01:27 PM
To: Olivier.Bonaventure@uclouvain.be; Mingui Zhang; philip.eardley@bt.com; sarikaya@ieee.org; multipathtcp@ietf.org
Subject: Re: [multipathtcp] draft-boucadair-mptcp-plain-mode-07



On 7/1/2016 12:01 AM, Olivier Bonaventure wrote:
> Hello,
>>
>> 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?
>
> No, there are three TCP connections in this scenario :
>
> - one (regular) TCP connection between client and CPE
> - one Multipath TCP connection between the CPE and the Concentrator
> - one (regular) TCP connection between the Concentrator and the remote 
> server
>
>> 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.
>> http://sites.inka.de/bigred/devel/tcp-tcp.html
>
> This is a well known issue.
>
>> Do we have solid solutions for this issue nowadays?
>
> The solution is to terminate the TCP connections transparently. This 
> is what most TCP optimisers used in mobile networks do already.

Is there a current standard or BCP endorsing this practice?

AFAICT, it's in direct opposition of RFC1122. I hope we don't want to create a new RFC that flies in the face of what few standards we have unless we're prepared to revise those standards first.

"deployed in the wild" is not a sufficient justification, IMO.

Joe

_______________________________________________
multipathtcp mailing list
multipathtcp@ietf.org
https://www.ietf.org/mailman/listinfo/multipathtcp