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

Olivier Bonaventure <> Wed, 19 April 2017 08:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8DBED13156E for <>; Wed, 19 Apr 2017 01:19:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Status: No, score=-4.321 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id d7EYT_jZ_xVW for <>; Wed, 19 Apr 2017 01:19:14 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 250B313156C for <>; Wed, 19 Apr 2017 01:19:14 -0700 (PDT)
Received: from [] (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: by (Postfix) with ESMTPSA id A1D4867DB04; Wed, 19 Apr 2017 10:19:04 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.9.2 A1D4867DB04
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=selucl; t=1492589945; bh=Hrn8OTr52WPCZUoBQR71vltp5vYkSN43+BHWQCP/dIE=; h=Reply-To:Subject:References:To:Cc:From:Date:In-Reply-To; b=qt9xoznTsbYCxPMG4B1AzkmvM8p0kW4OOJnQ+VbgyUFoS4LKPPP1N5MtH8LTH/nsY X056BqRd4FJcoFQOqr3ss5jbcfnUoOiApeVo/sBKG2fMOCGCw631t+Pvj0pt0ecS7B pHIu0zidvLpu8hxP1XxcQ6tvDZDbTQ6VPO3Op0QE=
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.99.2 at smtp-6
References: <> <> <>
To: Costin Raiciu <>
From: Olivier Bonaventure <>
Message-ID: <>
Date: Wed, 19 Apr 2017 10:19:04 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Sgsi-Spamcheck: SASL authenticated,
X-SGSI-MailScanner-ID: A1D4867DB04.A5213
X-SGSI-MailScanner: Found to be clean
X-SGSI-Spam-Status: No
Archived-At: <>
Subject: Re: [multipathtcp] Consensus call on potential MPTCP proxy work
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-path extensions for TCP <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 19 Apr 2017 08:19:15 -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.

Since the proxy is explict, the client creates an MPTCP connection to 
the proxy and the proxy creates another MPTCP connection to the final 
server. Since the proxy was the destination of the SYN, it cannot simply 
relay the traffic, but it should indicate to the client that the server 
supports MPTCP so that the next connection established by the client 
towards this server can directly bypass the proxy. This information 
about the MPTCP support on the final server could be part of the 
signalling information contained in the payload of the SYN+ACK