Re: [multipathtcp] towards a potential work item on two-ended proxy

Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be> Tue, 26 July 2016 16:08 UTC

Return-Path: <olivier.bonaventure@uclouvain.be>
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 B954012D8A5 for <multipathtcp@ietfa.amsl.com>; Tue, 26 Jul 2016 09:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=uclouvain.be
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 gFiIKy7M6bLq for <multipathtcp@ietfa.amsl.com>; Tue, 26 Jul 2016 09:07:51 -0700 (PDT)
Received: from smtp4.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8CA212DC09 for <multipathtcp@ietf.org>; Tue, 26 Jul 2016 08:56:42 -0700 (PDT)
Received: from mbpobo.dhcp.info.ucl.ac.be (mbpobo.dhcp.info.ucl.ac.be [130.104.228.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: obonaventure@smtp4.sgsi.ucl.ac.be) by smtp4.sgsi.ucl.ac.be (Postfix) with ESMTPSA id 054AD67E0A4; Tue, 26 Jul 2016 17:56:36 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.9.2 smtp4.sgsi.ucl.ac.be 054AD67E0A4
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1469548596; bh=KK3Mi4q8U4bMPSvo9lM3/CvTgIgFv5dTAU2wWixaHU0=; h=Reply-To:Subject:References:To:From:Date:In-Reply-To; b=AFTRs5Z2aoXAyOMF4CwAUSBTvs9Apybjer6OZjbe2Tom18o7TvZzaKP//AKb5Ncdg PV2SoxF5JupSzfuuBVO8LccIAqYGvD3GQ1sRPoRV6Xq/Ep+6SOvtL6hpCz89ghTqKQ Zr/WkUgQfjx9TY4s8/kwsfqFKzm6AWgl03N7X7HA=
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.99 at smtp-4
References: <b779dd12f1bb412c96c800eddaaf0247@rew09926dag03b.domain1.systemhost.net>
To: philip.eardley@bt.com, multipathtcp@ietf.org
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Message-ID: <9ec53eb3-f648-c0a8-0c8d-dd01a0bc78ec@uclouvain.be>
Date: Tue, 26 Jul 2016 17:56:53 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <b779dd12f1bb412c96c800eddaaf0247@rew09926dag03b.domain1.systemhost.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Sgsi-Spamcheck: SASL authenticated,
X-SGSI-Information:
X-SGSI-MailScanner-ID: 054AD67E0A4.A8249
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: olivier.bonaventure@uclouvain.be
X-SGSI-Spam-Status: No
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/YENmEhrRgE4VZ7txo4wwctMU8lg>
Subject: Re: [multipathtcp] towards a potential work item on two-ended proxy
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Olivier.Bonaventure@uclouvain.be
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, 26 Jul 2016 16:08:11 -0000

Phil,

> We started the discussion yesterday on a potential new work item on
> “two-ended proxy scenario” – where there’s an MPTCP proxy in both the
> CPE and an aggregation point (for instance). The current charter is that
> one end host is MPTCP.
>
>
>
> If I can try and summarise the brief discussion yesterday (plus some
> side discussions) (please correct my inaccuracies):
>
> -          there are now deployments & products with an MPTCP proxy at
> each end, plus planned Broadband Forum work (WT-348 is about to be made
> public, with subsequent work to follow). So IETF work is timely (eg help
> allow an operator to buy CPE from one vendor and aggregation gateway
> from another vendor).

I fully agree
>
> -          However, some people object to going beyond the current
> charter’s “one-ended proxy scenario” (since the “two-ended proxy”
> discourages deployment of MPTCP to all the end hosts, which is the
> ultimate goal)

I don't think that deploying MPTCP proxies would discourage the 
deployment of MPTCP end-to-end. This deployment shows that MPTCP is a 
valid solution to some problems where bandwidth can be aggregated and 
would convince users that MPTCP would be a good way to solve their problems.

The scenario is the following :

client ----  CPE --------- HAG -------- server
               +-------------+


The network operators want to use MPTCP between the CPE and the HAG 
because MPTCP is from a technical viewpoint the best solution to react 
to congestion and varying traffic conditions (delay, losses, ...) on the 
two access networks that are bonded. Since today's clients and servers 
only support regular TCP, operators want to have :
  - a TCP<->MPTCP proxy on the CPE
  - a MPTCP<->TCP proxy on the HAG

Note that since the CPE and the HAG support MPTCP by design, they could 
be MPTCP<->MPTCP proxies and support MPTCP end-to-end as a series of 
proxied connections. Proxied connections have two advantages in wireless 
networks compared to regular end-to-end MPTCP connections :
  - feedback loops are much shorter, which improves performance as shown 
by the deployment of various TCP optimisers in mobile networks
  - network operators can apply policies to prefer one network over the 
other

If the IETF works on this problem, we can ensure that the solution will 
support by design a scenario where MPTCP is used on the client and MPTCP 
is used as well on the server side.

>
> -          There are two proposals (transparent & plain mode:
> draft-boucadair-mptcp-plain-mode-08 &
> draft-peirens-mptcp-transparent-00). Are these addressing different use
> cases, or do we need to choose between them? would a (potential) charter
> item be to standardise existing draft(s), or to solve a problem /scenario?


The use case is the same : hybrid access networks. They both rely on 
MPTCP-MPTCP proxies. The deployment mode is different.

The plain-mode draft allows the HAG to be placed anywhere in the network 
and the destination address of the SYN is used to reach the HAG. The 
plain-mode option, included in the SYN, contains the final destination 
of the end-to-end connection.

The transparent-mode draft assumes that the HAG is placed on the path 
to/from the CPE. This implies that there is no need to change the 
destination address of the SYN to reach the HAG.

>
> -          I think there was mention (by Wim??) that there’s a third
> proposal – how does this fit in, or did I get it wrong?
>
> -          One aspect of the plain mode draft is to allow transport of
> UDP traffic as well as TCP traffic. I think this is a proposal that
> should be discussed separately  - for instance it needs INT-area expertise.

Agreed, we should focus on the TCP discussion in this WG

> I think it would be good to have more discussion before attempting to
> write some potential charter text (and then seeing if there’s consensus
> for it).
>

Olivier