Re: [Int-area] Middleboxes to aid the deployment of MPTCP

Tom Herbert <tom@herbertland.com> Wed, 19 July 2017 16:02 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25696131B54 for <int-area@ietfa.amsl.com>; Wed, 19 Jul 2017 09:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.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 Z-9OFAz72k7x for <int-area@ietfa.amsl.com>; Wed, 19 Jul 2017 09:02:51 -0700 (PDT)
Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::233]) (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 B4F84127B60 for <int-area@ietf.org>; Wed, 19 Jul 2017 09:02:50 -0700 (PDT)
Received: by mail-wr0-x233.google.com with SMTP id k71so7019405wrc.2 for <int-area@ietf.org>; Wed, 19 Jul 2017 09:02:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=JyZUUwhZ0FxLQ/3kOfnewTNjAFXbiveoVhSGFtFTswM=; b=WZJhXUUXsISQqtT+IFwX7ZW97aaJpRgvy8tdjeKh0YHo/tzjC0Te7HxUnaiiaw0Mhc eFaM2EvmZnpxm8owlW2zzbCgdMoa2g1jxAbBFQGi3NVtXRAkPYrRhl2TF9dNdz9XsM+g ZgTOGwF6YjMyH+vGtf6iQi9Zh2U8RScH2DAhjZQYkVsR+C2m33620uvzCby/hGPR1/Lm p5dsyQyCcV6PEo429G/Lg2oQE4zenoSGObFl4cEm6NSTt3XTFowzzJu0j1JqcfEsurTS qcnzANBCF47YIoyrVt7m8XMsPfv+VWxaz2sX8CkY1vxnQwvcoUillY47JyLFzJ7k9asG YQ3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=JyZUUwhZ0FxLQ/3kOfnewTNjAFXbiveoVhSGFtFTswM=; b=K+L15HP7d5R0Dmh7Ek5hbLrsCZsSmTzMN9QmzUXpzUTKVGGLyaHlzMTcKJqPaGiDjH 2Oki6W+tTjlONXZHD2/OhAW4VWhhzGIh2Bz0yVw2iUTwLHSb/Reo897t6xAUckSZQ1dX 5yS+mQJ03iRZ5Bgk23MzeCjb3rC4K1MXBulDZ0db1Oevxe4xS0rqbk8pyKD+1vUPmEhI K2dZf6n7Lxc3+MlUj/42JYYCEkx5S3CR+OquD4dKqMlo7dFLxJt6pNK+Lq5AVtiVCsYB DD93a4NC9v7jMduGW7eh0XyfjOPcamfU8uS+bGXTr9+QkDuI9CrNk/LFn7wp6ImJxCBv Mxqw==
X-Gm-Message-State: AIVw110UAShJYpeXIC22th1musrpBF7qtTPYOjZAtpHsZ69CpU3imuHL 19nKjFgI/vQEq+BjZa+98opLIp8T+PGL
X-Received: by 10.223.169.2 with SMTP id u2mr751918wrc.288.1500480169275; Wed, 19 Jul 2017 09:02:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.128.66 with HTTP; Wed, 19 Jul 2017 09:02:48 -0700 (PDT)
In-Reply-To: <787AE7BB302AE849A7480A190F8B93300A00ECBE@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <fe384d2b-a0ba-9444-2ee9-cd0de6d24b7c@tessares.net> <61608b70-6861-e7f8-96de-5679718a9680@isi.edu> <CALx6S35LpE=Z8DhanPuVcN9sVR2rkxtFPUZMd6Z4v1PHsnzF0w@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93300A00EA6D@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CAAedzxqqNM-oc85HLXTQtkQ4Sh+VE=Jsd7wQMjab99ib37_8YQ@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93300A00ECBE@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
From: Tom Herbert <tom@herbertland.com>
Date: Wed, 19 Jul 2017 09:02:48 -0700
Message-ID: <CALx6S34NJG5z_CsfbfnB2-n+LaNNuxmGX0+sBa2+rvfiKLzWMQ@mail.gmail.com>
To: mohamed.boucadair@orange.com
Cc: Erik Kline <ek@google.com>, Joe Touch <touch@isi.edu>, Internet Area <int-area@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/Mw23xP62Izz1wxFWgLKczGZKHjA>
Subject: Re: [Int-area] Middleboxes to aid the deployment of MPTCP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 16:02:52 -0000

On Wed, Jul 19, 2017 at 1:46 AM,  <mohamed.boucadair@orange.com> wrote:
> Hi Erik,
>
> That's the intuitive approach to follow but unfortunately the situation is not that obvious to get into.
>
I can give a little background on the Linux situation. There have been
several attempts to get MPTCP into the stack over the past few years.
Each time the patches were rejected primary because of complexity and
invasiveness. I believe in the initial attempt there were something
like 7,000 LOC change to tcp and that was whittled down to 5K on the
next attempt IIRC. It is not impossible to get the code in the stack,
but it's going to take more work to minimize code change and convince
the maintainer the complexity is justified.

> Network providers do not have a control on the servers and the terminals that are enabled by customers behind the CPE. So making use of MPTCP to grab more resources (when available) or to provide better resiliency (when a network attachment is lost) will require both endpoints to be MPTCP-capable.
>
Network providers don't control CPE is either. I know iOS has support
for MPTCP, AFAIK Android does not (Erik is that correct?). If Android
were shipping it that would be a strong datapoint towards getting
support in Linux.

Tom