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

["Sargent, Matthew T. (GRC-LCA0)[Peerless Technologies]" <[e-mail]>]

Hi Sayee,

I am not quite sure I understand how you are keeping sequence numbers straight for the case where you drop from 2 subflows to 1 subflow and want to stop using the DSS. Could you provide some details? What do you do when there is outstanding data on the subflow that goes away?

Thanks,
Matt


> On Apr 11, 2017, at 9:33 AM, Sayee Kompalli Chakravartula <[e-mail]> wrote:
> 
> Dear Olivier,
> I read through the paper "Are TCP Extensions Middlebox-prrof?", and especially focused on the Section 3.3 on Multipath TCP and midleboxes. My comments are as follows:
> 
> 1. Regarding middleboxes removing options from non-SYN segments:
> Currently, MPTCP handles this issue by attaching MPTCP option to every segment in the first window worth of data. An appropriate behaviour is defined for the sender and receiver to fallback to TCP in case middlebox removes the MPTCP option.
> 
> In my proposal I say that, instead of appending MPTCP option to segments in the first window worth of data, we defer appending the MPTCP option to segments to a later time just before we establish the second flow and as described below.
> 
> We will define an additional state variable DSS_RCV at both the sender and the receiver. At the beginning, this state variable will be initialized to false at both the ends. Now assume that the state variable NUM_SUBFLOW = 1 and DSS_RCV = false at the sender side and that the sender has send the DSS option for the first time. When DSS option is received with its state variable NUM_SUBFLOW = 1 and DSS_RCVD = false, the receiver will understand that the sender has decided to utilize the DSS option, and so it will update its state variable DSS_RCV = true and will ACK the segment that carried the DSS option with its own DSS option. When the sender receives ACK containing DSS option it will update its state variable DSS_RCV = true. Assuming that middlebox removes the DSS option included by the sender, the receiver will acknowledge the segment without DSS option. Because the ACK segment does carry DSS option the sender will fall back.
> 
> 2. To cope with sequence number randomizers:
> The same approach works with my proposal too, but with one little observation. Whenever the state variable NUM_SUBFLOW transitions from two to one, all the DSS related information is discarded, i.e., the space of DSNs and the mapping are removed from the protocol control block. But, when the state variable NUM_SUBFLOW again transitions from one to two, the space of DSNs will be created to establish mapping between SSS and DSS with one little difference: unlike when the MPTCP connection is established, for the subflow 1 we will not map the first DSN to subflow sequence zero but to the running subflow SN at that time. 
> 
> 3. Regarding middlebox performing segment splitting or coalescing:
> This behaviour of middlebox poses as much risk to my way of doing things as it does to the existing MPTCP specification. Because the existing mitigation does not depend on whether we continue to support DSNs on MPTCP connection consisting of just one subflow, the same solution will continue to work whether or not we support DSS for MPTCP connection consisting of just one subflow.
> 
> 4. ALG modifying the data stream by adding or removing bytes from the payload:
> This issue is relevant when a MPTCP option is included in a segment, and the same protocol behaviour will work in my case too.
> 
> I haven't prepared a detailed write-up to share with IETF folks, which I will do once I am fairly confident that I have worked out all corner cases.
> 
> Sayee