Re: [multipathtcp] Consensus call on potential MPTCP proxy work

Costin Raiciu <costin.raiciu@cs.pub.ro> Wed, 19 April 2017 08:04 UTC

Return-Path: <costin.raiciu@cs.pub.ro>
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 0F202131554 for <multipathtcp@ietfa.amsl.com>; Wed, 19 Apr 2017 01:04:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 izuswp1CPPq9 for <multipathtcp@ietfa.amsl.com>; Wed, 19 Apr 2017 01:04:51 -0700 (PDT)
Received: from vesa.cs.pub.ro (vesa.cs.pub.ro [141.85.227.187]) by ietfa.amsl.com (Postfix) with ESMTP id 5A2E8131552 for <multipathtcp@ietf.org>; Wed, 19 Apr 2017 01:04:50 -0700 (PDT)
IronPort-PHdr: 9a23:NmibxhVMth+OtzQYqTrb9D6W9w3V8LGtZVwlr6E/grcLSJyIuqrYbRKEt8tkgFKBZ4jH8fUM07OQ6PG8HzRYqb+681k6OKRWUBEEjchE1ycBO+WiTXPBEfjxciYhF95DXlI2t1uyMExSBdqsLwaK+i764jEdAAjwOhRoLerpBIHSk9631+ev8JHPfglEnjSwbLd9IRmssQndqtQdjJd/JKo21hbHuGZDdf5MxWNvK1KTnhL86dm18ZV+7SleuO8v+tBZX6nicKs2UbJXDDI9M2Ao/8LrrgXMTRGO5nQHTGoblAdDDhXf4xH7WpfxtTb6tvZ41SKHM8D6Uaw4VDK/5KpwVhTmlDkIOCI48GHPi8x/kqRboA66pxdix4LYeZyZOOZicq/Ye94RWGhPUdtLVyFZHoyzYJYBAeoDMuhWoIfzpFUOowW5CwS3GOPv0zpIimP23aEmzegsFxzN0gw6H9IJtXTZtMv4NKAJUeCpzanIyyjIYe9M1jf89IfIcw0hquyLUL1sdsrR0lUvFwLDjlmKs4zqJTKV2fgMs2iG9OdvSfmvh3Q/qwFsuTej3N0sio7Qi48T11vK9j15zZ4oKdC3VUJ3e92pHZtKuy2EKYd7QNkuTm9wtConxbAKpIS3cSsKxZg92RLSZfKKf5KV7h/sSuqcJypzimh/d7KlnRmy9FCtyuj7VsapzllHtjFFktzQtnAV0BzT99SHRuN9/ki/3TaP0Bje6v9BIU8ulKrbL4QtzaIrlpYJqUTDAzT5lF/sjK+Rbkkk++6o5Pr7Yrj+u5OROJJ4hhv9P6kugMCzH/o0PwoUU2WV4ei80afs/Uz9QLVElP02lazZvYjGKsQcva65Hw5V0oA55xalFTim0cgXnXgaLF9eZB2HlJLlO0nTIP/jF/u/mVOsnC9xx//aJr3hHonNLn/bnbf5fbZ96kpcyAsrzdxF+Z1bEKsBL+/3WkDvtN3VFQQ2MxCuz+n7D9V905sUWXiTDa+BLKPSrViI6/oqI+mRYI8VpDf9K+A/6P7yjX85hUMSfbGy0JsWdn+4AvpmL1+eYXr2jdcLCX0KsRYmTOz2lF2CViZeaW+2X6I9+DE7CZypDZ3ZSo2wh7yB2j20HoNIaWBAFlCMDG3oeJufVvcRdC2SJshhkiEaVbe7So8h0wuiuxTkxOkvEu2B3SkZq5PuzpBf4Ovaixw06SFuAozJ9GWMUWB5hCUiQDk/wq15vVFnx3+e2qx/nuJRFNoV7f4fASkgMpuJ5OthF9H0EjjIf9yIVR7ySdK9HTA3CMg4wtQPfm52AJO6kxqFxS38UOxdrKCCGJFhqvGU5HP2Pcsoji+ejKQ=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2CCCgDrGPdY/wPjVY1cHAEBBAEBCgEBFwEBBAEBCgEBhA2Pd5Bwl3GGJAKEUgEBAQEBAQEBAgFqKIIzIgGCQAEEATo/BQsLRlcGLol2DK1mizABAQEHAQEBAQEjhlOCCIJuhEEWgzSCMQWQfowvggibVIZdj1SEOgJXgQUmHYEKAYJDhBOKBwEBAQ
X-IPAS-Result: A2CCCgDrGPdY/wPjVY1cHAEBBAEBCgEBFwEBBAEBCgEBhA2Pd5Bwl3GGJAKEUgEBAQEBAQEBAgFqKIIzIgGCQAEEATo/BQsLRlcGLol2DK1mizABAQEHAQEBAQEjhlOCCIJuhEEWgzSCMQWQfowvggibVIZdj1SEOgJXgQUmHYEKAYJDhBOKBwEBAQ
X-IronPort-AV: E=Sophos;i="5.37,220,1488837600"; d="scan'208";a="689982"
Received: from mail.cs.pub.ro (HELO vmail.cs.pub.ro) ([141.85.227.3]) by vesa.cs.pub.ro with ESMTP; 19 Apr 2017 11:04:47 +0300
Received: from localhost (localhost [127.0.0.1]) by vmail.cs.pub.ro (Postfix) with ESMTP id 72B1D1A6004C; Wed, 19 Apr 2017 11:04:47 +0300 (EEST)
Received: from vmail.cs.pub.ro ([127.0.0.1]) by localhost (vmail.cs.pub.ro [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id VJ0wcTrKF6wl; Wed, 19 Apr 2017 11:04:47 +0300 (EEST)
Received: from vmail.cs.pub.ro (localhost [127.0.0.1]) by vmail.cs.pub.ro (Postfix) with ESMTPS id 54E221A6005A; Wed, 19 Apr 2017 11:04:47 +0300 (EEST)
Received: from [192.168.0.158] (unknown [141.85.233.142]) by vmail.cs.pub.ro (Postfix) with ESMTPSA id 4E2291A6004C; Wed, 19 Apr 2017 11:04:47 +0300 (EEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Costin Raiciu <costin.raiciu@cs.pub.ro>
In-Reply-To: <beacce37-1e58-5844-1ffc-786890a0ef35@uclouvain.be>
Date: Wed, 19 Apr 2017 11:04:47 +0300
Cc: philip.eardley@bt.com, multipathtcp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <262C92B8-A35E-4C46-B2F6-C0A82BEE21AF@cs.pub.ro>
References: <8c5ffa879686472594bfd3db2fa06076@rew09926dag03b.domain1.systemhost.net> <beacce37-1e58-5844-1ffc-786890a0ef35@uclouvain.be>
To: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/gAw39kurjVuXZj4gGZ-9mWsFnME>
Subject: Re: [multipathtcp] Consensus call on potential MPTCP proxy work
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 19 Apr 2017 08:04:54 -0000

> I fully support the work on MPTCP proxies. I would not focus on the current use case (how gateway and two proxies) but more on the importance of :
> 
> - being able to terminate Multipath TCP connections on a proxy somewhere in the network to bond different access networks when the server is not MPTCP capable
> - using 0-rtt, i.e. the proposed solution should not require an additional rtt to create a connection

+ 1.

Also, the solution should be future proof - if the server does support MPTCP, the proxy should simply relay the traffic, and not terminate the connection, allowing the client to directly connect to the server with other subflows.

Best.
Costin