Re: [multipathtcp] potential MPTCP proxy charter item

Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch> Tue, 18 October 2016 15:46 UTC

Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
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 572591296AB for <multipathtcp@ietfa.amsl.com>; Tue, 18 Oct 2016 08:46:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.631
X-Spam-Level:
X-Spam-Status: No, score=-4.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.431] 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 1-9ZxIfCWM6U for <multipathtcp@ietfa.amsl.com>; Tue, 18 Oct 2016 08:46:25 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC6F51296B6 for <multipathtcp@ietf.org>; Tue, 18 Oct 2016 08:46:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 2055FD930E; Tue, 18 Oct 2016 17:46:19 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id wGFe3NVKMC2A; Tue, 18 Oct 2016 17:46:18 +0200 (MEST)
Received: from [192.168.178.33] (p5DEC2052.dip0.t-ipconnect.de [93.236.32.82]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id B2611D930C; Tue, 18 Oct 2016 17:46:18 +0200 (MEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009D945B7@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Date: Tue, 18 Oct 2016 17:46:16 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <428609FE-DE79-45CD-B668-EF95F409B593@tik.ee.ethz.ch>
References: <CCD1A987-0F3C-4775-8B0E-5232965E7E22@nokia.com> <787AE7BB302AE849A7480A190F8B933009D945B7@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
To: mohamed.boucadair@orange.com
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/4u3EbkpWq2C3ox95rkwk3P8CNfE>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] potential MPTCP proxy charter item
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, 18 Oct 2016 15:46:27 -0000

Hi Med, hi all,

there are two cases to distinguish here:

1) you have one or two MPTCP proxies that terminate the TCP connection and open a new MPTCP connection

2) you tunnel other traffic over MPTCP

Case two is using TCP as a tunneling mechanism. This is discussed in several working groups for different purposes and is not very straight-forward in a lot of cases. Such an approach definitely needs coordination and transport as well as tunnel expertise.

Which case are you talking about? While Phil’s proposal sounded rather like case 1, your proposal sounds very much like case 2.

Mirja


> Am 18.10.2016 um 07:52 schrieb mohamed.boucadair@orange.com:
> 
> Hi Wim,
>  
> Yes, this can be main stream.
>  
> Cheers,
> Med
>  
> De : Henderickx, Wim (Nokia - BE) [mailto:wim.henderickx@nokia.com] 
> Envoyé : lundi 17 octobre 2016 23:22
> À : BOUCADAIR Mohamed IMT/OLN; philip.eardley@bt.com; multipathtcp@ietf.org
> Objet : Re: [multipathtcp] potential MPTCP proxy charter item
>  
> Sorry for the late reply, but more in-line
>  
> From: multipathtcp <multipathtcp-bounces@ietf.org> on behalf of "mohamed. boucadair" <mohamed.boucadair@orange.com>
> Date: Friday, 7 October 2016 at 09:08
> To: "philip.eardley@bt.com" <philip.eardley@bt.com>om>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
> Subject: Re: [multipathtcp] potential MPTCP proxy charter item
>  
> Hi Phil,
>  
> Please see inline.
>  
> Cheers,
> Med
>  
> De : multipathtcp [mailto:multipathtcp-bounces@ietf.org] De la part de philip.eardley@bt.com
> Envoyé : lundi 8 août 2016 11:50
> À : multipathtcp@ietf.org
> Objet : [multipathtcp] potential MPTCP proxy charter item
>  
> I had thought a potential charter item could be something on the lines of:
> <Experimental Extensions to the MPTCP protocol to enable an MPTCP-aware middlebox to act as an MPTCP proxy for an end host, which runs TCP. One or both end hosts may be MPTCP-unaware, and the MPTCP proxy(s) is (are) not necessarily on the default routing path(s). The working group will also detail, in an Informational document, the use cases /deployment scenarios and the operational considerations.>
>  
> [Med] I would like to see the charter includes the following; “The working group will also edit Network-Assisted Multipath provisioning documents. In particular, the WG will specify DHCP options and RADIUS attributes for MPTCP.” 
>  
>  
> WH> I am fine with this, but why do we state experimental extensions? Why is this not main stream?
> However, if I get the discussion right, this is not quite right.
> * assume a controlled environment (to avoid a problem where the message reaches the ‘wrong’ proxy) (IETF usually prefers generally applicable protocols)
> * assume some (?additional) ‘header swapping’ protocol and a new signalling protocol (not an mptcp extension – so probably in INTAREA WG’s remit)
> [Med] IMHO, it is not odd to document in the mptcp wg how a Network-Assisted MPTCP solution can also be applicable to other protocols (UDP in particular). This work can be done jointly/closely with other WGs. The important point is whether there is enough interest from the mptpcp WG members to work on this.
> WH> indeed is to specify the means in MPTCP WG and other WG can be consulted to review the work. If you split it out it becomes less efficient from a protocol perspective.
> If the above is roughly right, then I think some extra work is needed before we can get a clear charter item. Can some of the work that isn’t mptcp extensions be cleanly separated out? Can you be clear what deployment assumptions are being made (and preferably reduce them, so there is wider applicability). Personally I’d also find it very helpful if the plain/transparent ‘merged’ draft could try and follow the guidance about protocol models in RFC4101 (personally I found the plain mode doc difficult to understand).
>  
> Thanks
> phil
>  
>  
>  
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp