IETF Logo Mail Archive

Re: [multipathtcp] MPTCP Proxy Current Best Practices

Jordan Melzer <Jordan.Melzer@telus.com> Thu, 02 June 2016 20:08 UTC

Return-Path: <Jordan.Melzer@telus.com>
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 E5D2112D1E8 for <multipathtcp@ietfa.amsl.com>; Thu, 2 Jun 2016 13:08:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.747
X-Spam-Level:
X-Spam-Status: No, score=-5.747 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=Jordan.Melzer@telus.com header.d=telus.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 GMq_HcDv41YH for <multipathtcp@ietfa.amsl.com>; Thu, 2 Jun 2016 13:08:34 -0700 (PDT)
Received: from donder.nssi.telus.com (donder.nssi.telus.com [208.38.59.82]) by ietfa.amsl.com (Postfix) with ESMTP id 1E89312B011 for <multipathtcp@ietf.org>; Thu, 2 Jun 2016 13:08:33 -0700 (PDT)
DomainKey-Signature: s=donder.nssi; d=telus.com; c=nofws; q=dns; h=X-IronPort-Anti-Spam-Filtered: X-IronPort-Anti-Spam-Result:X-IronPort-AV:Received: Received:From:To:Date:Subject:Thread-Topic:Thread-Index: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: acceptlanguage:Content-Type:Content-Transfer-Encoding: MIME-Version; b=kIDXmWRVts5mr2kiZU0noePugMAABBUDFtKqEV6w91Kgx5T9ufhKFFgL FGYUUfD+L6RiHbvQRk097R9e9aHtDY64VZh4I9DJ7gNdbxSxJUf/8/yW3 s3AGmyeiHxLXGrAOUYpsSPV0M+8j+pufVHlVTHLVwV8xs/IB3ohsbkkK1 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2AaAwB9kVBX/5Jjso5egw4sSQ19omSXZIF5Fw2FJEoCgTM4FAEBAQEBAQFlJ4RFAQEBBAEBATcZGxcEAgEIDQQEAQEfCQcnCxQJCAIEARIIAYgmAQQJwkwBAQEBAQEBAwEBAQEBAQEghieETYQjAQEdgyqCLgWOWYlel3iFRI9MHjaEDU8BiUaBNQEBAQ
X-IronPort-AV: E=Sophos;i="5.26,408,1459814400"; d="scan'208";a="523280340"
Received: from unknown (HELO WP40081.corp.ads) ([142.178.99.146]) by donder-o.nssi.telus.com with ESMTP/TLS/AES128-SHA; 02 Jun 2016 20:08:30 +0000
Received: from WP40046.corp.ads ([::1]) by WP40081.corp.ads ([::1]) with mapi; Thu, 2 Jun 2016 14:08:30 -0600
From: Jordan Melzer <Jordan.Melzer@telus.com>
To: "Sargent, Matthew T. (GRC-LCA0)[Peerless Technologies]" <matthew.t.sargent@nasa.gov>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Date: Thu, 02 Jun 2016 14:08:29 -0600
Thread-Topic: MPTCP Proxy Current Best Practices
Thread-Index: AQHRvQXbVk8xTotSe0O575jBG6T+BZ/Wl/kw
Message-ID: <80C0017654A043479F53C41112BE84768979E1F6B2@WP40046.corp.ads>
References: <D37602A6.2B96%matthew.t.sargent@nasa.gov>
In-Reply-To: <D37602A6.2B96%matthew.t.sargent@nasa.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/ZhjUP5g_YJ7j4lOMo_8H2n04YeE>
Subject: Re: [multipathtcp] MPTCP Proxy Current Best Practices
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: Thu, 02 Jun 2016 20:08:37 -0000

Hi Matthew,

As long as your OS kernel supports MPTCP, any proxy works as a TCP to MPTCP proxy.

Eg, if you're on Linux using the UCL MPTCP implementation and you turn on HAProxy as a TCP proxy, it becomes an MPTCP / TCP proxy.  The same should be true of Dante or OpenSSH or whatever else you want to try out.

As there are commercial implementations from a range of vendors that come with support etc., I don't think it would be fair to say there is one best practice!

It's worth noting that the default proxy will also terminate existing MPTCP sessions and convert them to MPTCP, so if this is not a "feature" you want, you may have to work harder.

Apologies if this is off-topic for the list.

Regards,
Jordan

-----Original Message-----
From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of Sargent, Matthew T. (GRC-LCA0)[Peerless Technologies]
Sent: June 2, 2016 03:35 PM
To: multipathtcp@ietf.org
Subject: [multipathtcp] MPTCP Proxy Current Best Practices

Hello all,

I was wondering if anyone on the list has experience deploying an MPTCP proxy and would be willing to discuss the current best practices/proxy deployment options? I have been looking through the mptcp-dev and multipathtcp mailing lists at discussions revolving around MPTCP proxies and it seems like the two general strategies seem to be setting up a SOCKS proxy or using the mptcp-proxy code released by Bell Labs http://www.ietf.org/mail-archive/web/multipathtcp/current/msg01934.html.

Are there other options or more up-to-date code to use? The Bell Labs code is several years old, and I was unsure if using the code is still a viable option at this point or not. Is a SOCKS proxy the go to option? If so, how does an MPTCP capable SOCKS proxy setup differ from setting up a regular TCP SOCKS proxy?

Best,
Matt

_______________________________________________
multipathtcp mailing list
multipathtcp@ietf.org
https://www.ietf.org/mailman/listinfo/multipathtcp

v2.23.0 | Report a Bug | By Email