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

Joe Touch <touch@isi.edu> Fri, 03 June 2016 17:21 UTC

Return-Path: <touch@isi.edu>
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 B965E12D542 for <multipathtcp@ietfa.amsl.com>; Fri, 3 Jun 2016 10:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level:
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 D23Nppic0gWu for <multipathtcp@ietfa.amsl.com>; Fri, 3 Jun 2016 10:21:54 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 412AF12B05A for <multipathtcp@ietf.org>; Fri, 3 Jun 2016 10:21:54 -0700 (PDT)
Received: from [128.9.184.224] ([128.9.184.224]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id u53HL1hM015595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 3 Jun 2016 10:21:01 -0700 (PDT)
To: Markus.Brunner3@swisscom.com
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>
From: Joe Touch <touch@isi.edu>
Message-ID: <5751BC7B.1050902@isi.edu>
Date: Fri, 03 Jun 2016 10:20:59 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <7262010A-DC38-4BDC-9965-658679D351D9@swisscom.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: u53HL1hM015595
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/Yvc-qau_gj4R-VobW1YTqZaoG7k>
Cc: multipathtcp@ietf.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 17:21:56 -0000


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)
- 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
- by recovering from loss, it increases latency and jitter
- it can use only one load monitoring mechanism (the one built-in)
- it can use only one traffic distribution mechanism (the one built-in)

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

Joe