[multipathtcp] MPTCP Proxy Current Best Practices
"Sargent, Matthew T. (GRC-LCA0)[Peerless Technologies]" <matthew.t.sargent@nasa.gov> Thu, 02 June 2016 19:35 UTC
Return-Path: <matthew.t.sargent@nasa.gov>
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 6A9FB12D58D for <multipathtcp@ietfa.amsl.com>; Thu, 2 Jun 2016 12:35:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.627
X-Spam-Level:
X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, 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 h953LvNk2jY7 for <multipathtcp@ietfa.amsl.com>; Thu, 2 Jun 2016 12:35:06 -0700 (PDT)
Received: from ndmsvnpf104.ndc.nasa.gov (NDMSVNPF104.ndc.nasa.gov [198.117.0.154]) by ietfa.amsl.com (Postfix) with ESMTP id 6370712D567 for <multipathtcp@ietf.org>; Thu, 2 Jun 2016 12:35:05 -0700 (PDT)
Received: from ndmsppt103.ndc.nasa.gov (ndmsppt103.ndc.nasa.gov [198.117.0.68]) by ndmsvnpf104.ndc.nasa.gov (Postfix) with ESMTP id CD7044016669 for <multipathtcp@ietf.org>; Thu, 2 Jun 2016 14:35:04 -0500 (CDT)
Received: from NDMSCHT101.ndc.nasa.gov (ndmscht101-pub.ndc.nasa.gov [198.117.0.201]) by ndmsppt103.ndc.nasa.gov (8.15.0.59/8.15.0.59) with ESMTP id u52JZ4Se032497 for <multipathtcp@ietf.org>; Thu, 2 Jun 2016 14:35:04 -0500
Received: from NDMSMBX102.ndc.nasa.gov ([169.254.7.138]) by NDMSCHT101.ndc.nasa.gov ([198.117.0.201]) with mapi id 14.03.0294.000; Thu, 2 Jun 2016 14:35:04 -0500
From: "Sargent, Matthew T. (GRC-LCA0)[Peerless Technologies]" <matthew.t.sargent@nasa.gov>
To: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: MPTCP Proxy Current Best Practices
Thread-Index: AQHRvQXbVk8xTotSe0O575jBG6T+BQ==
Date: Thu, 02 Jun 2016 19:35:03 +0000
Message-ID: <D37602A6.2B96%matthew.t.sargent@nasa.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [139.88.44.39]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E29247C4106D794DADAE0988149166A0@mail.nasa.gov>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-06-02_09:, , signatures=0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/KlHY2X34UJfwhE_eFpCvH7nHaYg>
Subject: [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 19:35:09 -0000
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] MPTCP Proxy Current Best Practices Sargent, Matthew T. (GRC-LCA0)[Peerless Technologies]
- Re: [multipathtcp] MPTCP Proxy Current Best Pract… Jordan Melzer