IETF Logo Mail Archive

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

"Sargent, Matthew T. (GRC-LCA0)[Peerless Technologies]" <matthew.t.sargent@nasa.gov> Wed, 19 April 2017 13:38 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 AE032129537 for <multipathtcp@ietfa.amsl.com>; Wed, 19 Apr 2017 06:38:12 -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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nasa.gov
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 q0bZQ91mguzK for <multipathtcp@ietfa.amsl.com>; Wed, 19 Apr 2017 06:38:07 -0700 (PDT)
Received: from ndmsvnpf104.ndc.nasa.gov (NDMSVNPF104.ndc.nasa.gov [198.117.0.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D1F112956D for <multipathtcp@ietf.org>; Wed, 19 Apr 2017 06:38:04 -0700 (PDT)
X-Comment: SPF check N/A for local connections - client-ip=198.117.1.199; helo=ndjsppt105.ndc.nasa.gov; envelope-from=matthew.t.sargent@nasa.gov; receiver=multipathtcp@ietf.org
DKIM-Filter: OpenDKIM Filter v2.11.0 ndmsvnpf104.ndc.nasa.gov 093C340913B7
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nasa.gov; s=letsgomars; t=1492609083; bh=Y6MKw0DEVg4+TPnaMpNTQMCyVJuTEkmlsqY56cdb1bI=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=FpPZZRA3A3fCWXnP/oNc9HRb4Pw2hnmGyk+ZD1HhP1oWM/9AVvB5Mko1A1IzFgDu4 ZgY2CObhgzftO80Y8e2uEtR+dezZQ93jYYh4th4agcDXSqCbqKCLvLE0beKBsPb/eB T4eR1K3D3uvvSlDU+vwBDtDiBZ8D1/TGPFxDLy9LkkE4tkeWGPNGHIoa8u40Df3uLo GXwpNwiS6erDjGiaLSxRVEijf8yvAw6a+FCiHkzSmwdZYjyBSaTR3leX0ed4a4KTEb PwJZ04LYdjcSFaDYKvVZyITCfMKC214EnYqcenOsRBoxenEhIC2I0GW32VhHRigZ/H B6NrVaD1o5jqg==
Received: from ndjsppt105.ndc.nasa.gov (ndjsppt105.ndc.nasa.gov [198.117.1.199]) by ndmsvnpf104.ndc.nasa.gov (Postfix) with ESMTP id 093C340913B7; Wed, 19 Apr 2017 08:38:03 -0500 (CDT)
Received: from pps.filterd (ndjsppt105.ndc.nasa.gov [127.0.0.1]) by ndjsppt105.ndc.nasa.gov (8.16.0.20/8.16.0.20) with SMTP id v3JDWmlr008912; Wed, 19 Apr 2017 08:38:02 -0500
Received: from ndjscht112.ndc.nasa.gov (ndjscht112-pub.ndc.nasa.gov [198.117.1.212]) by ndjsppt105.ndc.nasa.gov with ESMTP id 29x6fyrpnu-1; Wed, 19 Apr 2017 08:38:02 -0500
Received: from NDJSMBX102.ndc.nasa.gov ([169.254.5.9]) by NDJSCHT112.ndc.nasa.gov ([198.117.1.182]) with mapi id 14.03.0319.002; Wed, 19 Apr 2017 08:38:01 -0500
From: "Sargent, Matthew T. (GRC-LCA0)[Peerless Technologies]" <matthew.t.sargent@nasa.gov>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
CC: "philip.eardley@bt.com" <philip.eardley@bt.com>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: [multipathtcp] Consensus call on potential MPTCP proxy work
Thread-Index: AdK4HBNY1jXzvDFKRxmRsHBM53IcbgAZ8zuAAB4TboAAD/kHAA==
Date: Wed, 19 Apr 2017 13:38:00 +0000
Message-ID: <90A6EE89-D089-46C1-980F-9DE5DE2B07B7@nasa.gov>
References: <8c5ffa879686472594bfd3db2fa06076@rew09926dag03b.domain1.systemhost.net> <02572A11-A7D5-49D2-A31A-61B575613DF3@nasa.gov> <787AE7BB302AE849A7480A190F8B933009E5041F@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E5041F@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
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: <CFAB2B037D02EB46B24540BE556AAA53@mail.nasa.gov>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-19_11:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/Y67kXEp9YLbfHRlaV31NkXkHyYo>
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 13:38:13 -0000

Hi Med,

> On Apr 19, 2017, at 2:00 AM, mohamed.boucadair@orange.com wrote:
> 
> Hi Matt, 
> 
> Yes, I confirm. 
> 
> * Native MPTCP connections can be established directly without involving a proxy. 
> * If the client is not MPTCP-capable but the server is MPTCP-capable, the communication leg between the proxy and that server will be placed using MPTCP. 
> 

I am not sure I understand how you maintain native MPTCP connections in the dual proxy case.

I am assuming a network that is set up like you have on slide 10. 1 address on the client, 1 address on the server, multiple paths are "hidden" by the MCP's.

Do you mean to claim that installing MPTCP on the client and server will result in an MPTCP connection that "works" in the sense that it will contain multiple subflows to use the available paths in the network? How would this work without additional signaling?

Sorry if I am missing something obvious here.

Thanks,
Matt

v2.23.0 | Report a Bug | By Email