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

David Allan I <david.i.allan@ericsson.com> Fri, 03 June 2016 19:29 UTC

Return-Path: <david.i.allan@ericsson.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 A4C2E12D941 for <multipathtcp@ietfa.amsl.com>; Fri, 3 Jun 2016 12:29:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 t1I4iZYqdXGN for <multipathtcp@ietfa.amsl.com>; Fri, 3 Jun 2016 12:29:14 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7ABB012D940 for <multipathtcp@ietf.org>; Fri, 3 Jun 2016 12:29:14 -0700 (PDT)
X-AuditID: c6180641-f796f6d000000e1e-8a-5751da51dd37
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id D0.01.03614.15AD1575; Fri, 3 Jun 2016 21:28:18 +0200 (CEST)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0294.000; Fri, 3 Jun 2016 15:29:13 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: Joe Touch <touch@isi.edu>, "Markus.Brunner3@swisscom.com" <Markus.Brunner3@swisscom.com>
Thread-Topic: [multipathtcp] draft-boucadair-mptcp-plain-mode-07
Thread-Index: AQHRvDS2BAjEk24HX0GvN2aAbwiqtZ/WbT4QgAEt+QCAAKgEgP//3hog
Date: Fri, 03 Jun 2016 19:29:12 +0000
Message-ID: <E6C17D2345AC7A45B7D054D407AA205C4BCF59ED@eusaamb105.ericsson.se>
References: <CAC8QAccht1nMP95HVdP6YcqJfxNryvDbhaK=LY0LcW5-JKM82A@mail.gmail.com> <836B90ED-2110-4F0F-86CB-7B12C0C4D1E8@swisscom.com> <57506A37.60502@isi.edu> <7262010A-DC38-4BDC-9965-658679D351D9@swisscom.com> <5751BC7B.1050902@isi.edu>
In-Reply-To: <5751BC7B.1050902@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprIIsWRmVeSWpSXmKPExsUyuXRPrG7QrcBwg31ruC3eNtxjsvi8+jqb xeze0ywW6/7MZXFg8Xg64SCTx5IlP5k8dr/fyuJxt2smcwBLFJdNSmpOZllqkb5dAldG94pn rAWTRSsOtr5gamCcItjFyMkhIWAi8WvudhYIW0ziwr31bF2MXBxCAkcZJd5d+gjlLGOU2LXq GytIFZuAgcSe/18YQWwRgTiJ+Wt+gNnMQPbBtbfYQWxhAXuJH7tmsEHUOEj8WXeGFcJ2k1jU uAasnkVAReLpmm5mEJtXwFfi98unzBDLPjFKHPn9DCzBKaAu8WrtHjCbEei876fWMEEsE5e4 9WQ+E8TZAhJL9pxnhrBFJV4+/scKYStJzHl9jRmiXkdiwe5PbBC2tsSyha+hFgtKnJz5hGUC o9gsJGNnIWmZhaRlFpKWBYwsqxg5SosLcnLTjQw3MQIj6pgEm+MOxr29nocYBTgYlXh4E9YE hAuxJpYVV+YeYpTgYFYS4VU/HxguxJuSWFmVWpQfX1Sak1p8iFGag0VJnFf/pWK4kEB6Yklq dmpqQWoRTJaJg1OqgXGpjJoG7wexm45NH6sm6Uy3qkhrl2/a2iQ7403Bnqq8oCXH/1Q/WZiT MnW1TNWCaclO9bebDEq5Licx2VpartC3z74v/8lC6FncaYHtKb23/a6FGNS7rEk6y2B/saTx aPqh3RVaC31fR66YszP0lmKSwZK9D7VUqkMDm83suQs/sm5d6jcjRImlOCPRUIu5qDgRAP7X YfGkAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/N9TtVnJFzOiPFTmVhSKG7DNrqjU>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "sarikaya@ieee.org" <sarikaya@ieee.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: Fri, 03 Jun 2016 19:29:16 -0000

Hi Joe:

Comments below prefaced by DA>

-----Original Message-----
From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of Joe Touch
Sent: Friday, June 03, 2016 10:21 AM
To: Markus.Brunner3@swisscom.com
Cc: multipathtcp@ietf.org; sarikaya@ieee.org
Subject: Re: [multipathtcp] draft-boucadair-mptcp-plain-mode-07



On 6/3/2016 12:19 AM, Markus.Brunner3@swisscom.com wrote:
> Hi Joe,
>
> If you mean with dynamic routing a packet by packet routing decision, that could work however, how do you incorporate the path characteristic feedback into that decision. 
That's what multipath routing has been doing for years.

AFAIK, the mechanisms in MPTCP are an instance inspired by existing multipath routing.

> Here the MPTCP mechanisms just come in handy and do the job quite well, but as you say we pay with some complexity. That complexity we feel,will have anyway with whatever solution we are going.

Perhaps, but MPTCP is the wrong solution for an IP tunnel for many reasons:

- it will layer congestion control on top of congestion control for all transports in the payload IP that already support it (which they should)
DA> Would that not be true of any tunnel mechanism that used feedback of the tunnel leg as well as the e2e application?

- it fails to preserve payload IP messages inside a single TCP segment, which increases loss due to a lack of fate-sharing and increases latency and jitter
DA> I apologize for not getting your point here.

- by recovering from loss, it increases latency and jitter
DA> AFAIK, any loss does that irrespective of the delivery mechanism. In the hybrid access case you are correcting loss with a smaller RTT are you not?

- it can use only one load monitoring mechanism (the one built-in)
DA> How many did you want?

- it can use only one traffic distribution mechanism (the one built-in)
DA> If you are saying it is "implementation constrained", well go figure :-)  

That's a lot of baggage vs. just using tunnels and existing dynamic multipath routing -- and the latter doesn't require a new spec.

DA> Can you point me to the feedback mechanisms embodied in making dynamic multipath work?  And if you are striping flows across multiple paths (absolute requirement in my application), any indication of how successful this is in minimizing the residence time of packets in the reordering function?

DA> If all we are talking about is a slightly smarter ECMP , IMO it does not cut it.

Dave

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