Re: [multipathtcp] A question related to MPTCP control overhead

Sayee Kompalli Chakravartula <> Fri, 14 April 2017 11:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 67937129AF2 for <>; Fri, 14 Apr 2017 04:33:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DHvM3FOaT_nN for <>; Fri, 14 Apr 2017 04:33:10 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 150EB129BC4 for <>; Fri, 14 Apr 2017 04:33:09 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id DET33616; Fri, 14 Apr 2017 11:33:07 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 14 Apr 2017 12:33:06 +0100
Received: from ([]) by ([::1]) with mapi id 14.03.0301.000; Fri, 14 Apr 2017 17:03:03 +0530
From: Sayee Kompalli Chakravartula <>
To: "" <>, "Sargent, Matthew T. (GRC-LCA0)[Peerless Technologies]" <>
CC: "" <>
Thread-Topic: [multipathtcp] A question related to MPTCP control overhead
Thread-Index: AdKux4amd3XFz/fSRoiWehKw99KRVgAruciAAHFvuLAAGcM3gABJPHoQ//+sEQD//iJhoIADcW0A//6ugnCABC4/AP//iGhA
Date: Fri, 14 Apr 2017 11:33:02 +0000
Message-ID: <5C068B455EB58047BBD492DA2B0829FA3763E0C7@blreml501-mbs>
References: <5C068B455EB58047BBD492DA2B0829FA3763ADD5@blreml501-mbs> <> <5C068B455EB58047BBD492DA2B0829FA3763CB68@blreml501-mbs> <> <5C068B455EB58047BBD492DA2B0829FA3763D266@blreml501-mbs> <> <5C068B455EB58047BBD492DA2B0829FA3763D85B@blreml501-mbs> <> <5C068B455EB58047BBD492DA2B0829FA3763DA5D@blreml501-mbs> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.58F0B374.0117, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: a0463539eab111a4ad5997dd5aeeadcd
Archived-At: <>
Subject: Re: [multipathtcp] A question related to MPTCP control overhead
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: Fri, 14 Apr 2017 11:33:13 -0000

I got the point, and thanks for the clarification. I were under the impression that existence of MPTCP connection implies that existence of at least one subflow, which clearly cannot be true always as your corner case illustrates.


-----Original Message-----
From: Olivier Bonaventure [] 
Sent: Friday, April 14, 2017 3:21 PM
To: Sayee Kompalli Chakravartula; Sargent, Matthew T. (GRC-LCA0)[Peerless Technologies]
Subject: Re: [multipathtcp] A question related to MPTCP control overhead


>> If the connection is closed using the FIN bit: Let us represent a SN as x_{i,j} where the subscript i denotes the type of sequence space (SSN or DSN) and the subscript j gives the subflow ID. Let x_{DSN, SF2} be the DSN of the last byte transmitted before FIN is sent on SF2 and that x_{DSN, SF1} be the last DSN mapped to SF1 before the DSS Option is disabled by the sender. In this context we need to consider two possibilities: x_{DSN, SF1} < x_{DSN, SF2} and x_{DSN, SF1} >= x_{DSN, SF2}. Now consider the case x_{DSN, SF1} < x_{DSN, SF2}. When a data byte is received on SF1 that is not covered by DSN we know where to place that data byte with respect to the data byte whose DSN is x_{DSN, SF1} using subflow sequence number of the data byte. Because, eventually, data bytes need to be ordered based on DSN before releasing to the application layer we still need to decide where to place this data byte at the connection-level with respect to x_{DSN, SF2}, and this is where the protocol will run into ambiguity: whether to place the data byte before or after x_{DSN, SF2}. This will lead to protocol dead-lock. Next, we consider the possibility x_{DSN, SF1} >= x_{DSN, SF2}. Here we do not have the ambiguity present in the previous context. The received data byte on SF1 will have to be placed to the right of both x_{DSN, SF1} as well as x_{DSN, SF2} and the actual placement on SF1 will be determined by the SSN of the data byte.
>> The above analysis helps us to decide how and when DSS Option can be disabled. After sending the FIN on SF2, continue sending the DSS option on SF1 until the largest DSN used on SF1 is at least as large as x_{DSN, SF2} and the state variable NUM_SUBFLOW has transitioned to 1, and then disable the DSS Option. To describe the receiver behaviour, the receiver expects to continue to receive data bytes covered with DS mapping on SF1 until the largest DSN mapped to SF1 is at least as large as x_{DSN, SF2}. After then, starting with the first received byte that is not covered with DSN, the receiver will understand that the sender has disabled DS mapping on SF1.
>> At this point, I like to believe that defining a new Option Subtype or utilizing an unused bit in the DSS option will be fruitful.
>> Except in some specific scenarios, like a data center, I don't think a device can know in advance if second interface becomes available during the connection. So if the users goes with TCP then he is at disadvantage because he cannot utilize additional interfaces when they become available. If he opens MPTCP connection hoping that new interfaces may become available in the future, until then the connection has to incur control overhead due to redundant DSS Option.
>> As a first-cut solution I think we should allow a MPTCP connection not to use the DSS option until it opens the second subflow. To keep things simple, we may say that once DSS Option is enabled it will be enforced until the MPTCP connection is closed.
> On smartphones a solution would need to support break-before-make to 
> be useful. This means that we cannot terminate the subflow with a FIN 
> before deciding to switch to the utilisation of DSS. This fact, 
> coupled with middleboxes that can transparently add/remove data from 
> the bytestream make the problem difficult to solve
> <<Sayee>> Can you please elaborate on this scenario, as I do not seems to get what you were implying?

A very annoying corner case is the following one :

A smartphone creates an MPTCP connection over WiFi. The three-way-handshake is done correctly. After a few seconds, the smartphone sends some data but it has moved out of reach of the WiFi network and it does not receive acknowledgements for this data. From the information exchanged over the WiFi, the smartphone cannot know whether the data has been received by the server or not.

The smartphone then opens a subflow over the LTE interface. Once the subflow is established, it can be used to send data with the DSS option. 
Note that during the three-way handshake for the initial subflow, the client and the server have agreed on the initial sequence numbers for the two directions of the transfer. This means that when the first data arrives on the LTE subflow with a DSS option, the server can determine whether this is the first data of the bytestream or other data and then it would need to wait for the first data before delivering it to its application.

If you remove the DSS on the initial subflow, then I do not see any way for the server to cope correctly with this scenario. Note that sequence number randomisation affects the sequence numbers that the smartphones and the server see.