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

[Sayee Kompalli Chakravartula <[e-mail]>]

Olivier,
I think I started on the wrong foot discussing solution first before requesting the group to discuss merits of disabling the DSS Option.
A solution that I thought of will not work in all scenarios, so I need to think of a more robust solution. But before we can do that, I would love to hear others of their opinion on disabling the DSS Option. If there is consensus, we can certainly work out a solution. I'm yet to write up my not to elegant solution:(

Sayee


-----Original Message-----
From: Olivier Bonaventure [mailto:[e-mail]] 
Sent: Wednesday, April 12, 2017 3:16 PM
To: Sayee Kompalli Chakravartula; [e-mail]
Subject: Re: [multipathtcp] A question related to MPTCP control overhead

Sayee,

> 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.

MPTCP as defined in RFC6824 supports both make-before-break and break-before-make, i.e. the second subflow can be established at any time, either before or after the failure of the initial one. With your design, you force a make-before-break, this means that something has to be done (namely start uses DSS) before being able to create the second subflow. This is annoying because failover is one of the nice features of Multipath TCP.


> 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.

I fear that a solution that tries to avoid DSS when there is a single subflow and uses DSS as soon as there are two subflows would be very difficult to use. How do the client and the server agree that there are one or more subflows ? At a given time, they might have a different view of the state of the Multipath TCP connection.


Olivier