Re: [multipathtcp] RFC6824bis edits based on implementation feedback

Matthieu Baerts <matthieu.baerts@tessares.net> Tue, 04 February 2020 13:28 UTC

Return-Path: <matthieu.baerts@tessares.net>
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 C1B861200F5 for <multipathtcp@ietfa.amsl.com>; Tue, 4 Feb 2020 05:28:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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=tessares-net.20150623.gappssmtp.com
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 QpwquDylZWK0 for <multipathtcp@ietfa.amsl.com>; Tue, 4 Feb 2020 05:28:48 -0800 (PST)
Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 956D1120020 for <multipathtcp@ietf.org>; Tue, 4 Feb 2020 05:28:47 -0800 (PST)
Received: by mail-wr1-x42e.google.com with SMTP id k11so23008373wrd.9 for <multipathtcp@ietf.org>; Tue, 04 Feb 2020 05:28:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tessares-net.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=NSZKfXRjeGx3J8zsNYfuG/GhkGnaEDe0NV92aKI50Nk=; b=j2PkukH5L6M7/PgJEp4AHSgw9EfJ6lR3OiEgB1+PEq+boPEKTPx92+UECeOarn/ipL 54lDubFbAr9axkBKwHf+5R8Dy88X6aCjMUh5ceDej1Wt/G5z9nsWdZusy9qvaNEaJt0U koMpsJG0Vjdf6oJVIc6lcH3u6OKwGRv03sTpQbH/Xq0d5ogLjgYiZAPGDRRce8ID6XTT cWQFlsnVTCBXCEsrOZHWu9R/j8DlvXS8SrDxcRxqGhDGKj0c+S/PIcJsAm7fIenafDzq NmKoVnJ3wRda1CxHRcC2gCXfVlVFjnVfIItT33/NF4FdQCY8wA5G/xoiWFBMCzGe6IwD OstQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=NSZKfXRjeGx3J8zsNYfuG/GhkGnaEDe0NV92aKI50Nk=; b=Riy3aErAL3oB/z2nmdHFo+s8uiDEy0GR5YLuQG3JIrfiRs92L/nUxPrIk2/rPHeehZ znHgSrYV1ilZntTuYZWFUZObXfxDBqQ8taQJI6sm60DRrn0R+bmH5QhxpKpjq4qmwo4P jYtNgkVTJcGhtgIWrbLdutNZxikqkpvlxFpmLgWj4Tfj0YeASsAMZ9rUMOVf0TfxcWPj GIr8aY78Hp3aRs3Hvh9oqpDDJesXQZ54h1oPhhB1t4rZUAu+9gvTVrbE5M2m+ELSZlL/ SNMvvoGX+hfrWTs7xMMTqBRAPnhA4gvVpM/7LdGQ/kJy034haKWLO56M6QnAsYsG7P0g B4PQ==
X-Gm-Message-State: APjAAAXuFjg74IF7HIgTYQscGthEcKevowUQcEydA2wmdWf2wAAYLu9/ 6Vp7NKQ17Fz8m6wzudrGgxq44mQaxSnizw==
X-Google-Smtp-Source: APXvYqytajkokx/reU49w0sLajDwGNG2CaXu4XkxVlRC65DFYpDe/JZpFp2P6r9PZNsSEN2wuFP6ig==
X-Received: by 2002:a5d:550f:: with SMTP id b15mr21922381wrv.196.1580822925290; Tue, 04 Feb 2020 05:28:45 -0800 (PST)
Received: from tsr-lap-08.nix.tessares.net (hag0-main.tessares.net. [87.98.252.165]) by smtp.gmail.com with ESMTPSA id 5sm27404483wrc.75.2020.02.04.05.28.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 04 Feb 2020 05:28:44 -0800 (PST)
To: Alan Ford <alan.ford@gmail.com>, Yoshifumi Nishida <nsd.ietf@gmail.com>
Cc: multipathtcp <multipathtcp@ietf.org>
References: <C36D742F-6D76-48FA-B6D8-44DE484A9E2C@gmail.com> <882106347.533187.1578939921488@csir4pi.in> <CAAK044RLsJCFWfeP4XAzMmMhUqH1hCnDs94-3Zkrj3QkJeVx7g@mail.gmail.com> <146023054.25180934.1580661581660@csir4pi.in> <CAAK044QBO4Bjby=fkEiuQ-f-zuZG1Q=8H0p1kJoUaxyjzod3Cg@mail.gmail.com> <83C89953-EDAE-4B0C-B73B-9E88BAF3C927@gmail.com>
From: Matthieu Baerts <matthieu.baerts@tessares.net>
Message-ID: <ec681f60-23f9-c934-b2fc-306584fec645@tessares.net>
Date: Tue, 4 Feb 2020 14:28:44 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <83C89953-EDAE-4B0C-B73B-9E88BAF3C927@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/APOYs2pwx7W3zRIh8DrTqgkyeFs>
Subject: Re: [multipathtcp] RFC6824bis edits based on implementation feedback
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 04 Feb 2020 13:28:51 -0000

Hi all,

First, thank you all for having contributed all these years to make 
clear MPTCP RFCs.

I'm sorry to interrupt the discussions with my message but because it 
seems there are still some opened questions related to these changes, I 
would like to express my view from the implementer side.

As a maintainer of both the MPTCP Linux out-of-tree implementation and 
the new MPTCP Linux upstream one, I fully endorse both changes.

The first one avoids confusions while the second one avoids senders to 
generate segments that are not supported by the two MPTCP Linux 
implementations and certainly by most/all existing ones. Accepting such 
Data Segment Mappings are not supported and will probably never be 
because it is complex, middleboxes don't seem to modify packets to have 
a situation like that and it can be a source of security issues. 
Avoiding senders to create such mappings would avoid issues if most 
network stacks don't implement this specific support for technical reasons.

Thank you Alan for taking care of this!

Cheers,
Matt

On 04/02/2020 13:12, Alan Ford wrote:
> Hi Yoshi,
> 
> The proposed new text enforces a mapping to be sent on a packet whose 
> subflow sequence number is included within the mapping provided. This 
> does not directly contradict with the MAY case. Indeed this scenario 
> could easily happen if there is a 20 byte packet followed by a 10 byte 
> packet. The first 10 bytes of the first packet are covered by the 
> mapping on packet 1, then the remaining 10 bytes and the following 10 
> bytes are covered by the mapping on packet 2. That would be valid.
> 
> To re-iterate, the primary purpose of this proposed text is to stop 
> people sending mappings before they are needed.
> 
> Best regards,
> Alan
> 
>> On 4 Feb 2020, at 07:38, Yoshifumi Nishida <nsd.ietf@gmail.com 
>> <mailto:nsd.ietf@gmail.com>> wrote:
>>
>> Hi Anil,
>>
>> Thanks for pointing it out. I overlooked this one.
>> This looks an interesting point.
>>
>> It seems to me that whether RST is happen or not depends on the size 
>> of receive window according to the text.
>> If the receive window size is big enough to accommodate segment 1 and 
>> segment 3, the text "Implementations MAY hold onto such unmapped data 
>> for a short while in the expectation that a mapping will arrive 
>> shortly. " can be applied to the segment 1. As a result, the segment 1 
>> won't be discarded.
>> However, this might be contradict with the new texts Alan proposed? 
>> Or, am I missing something?
>>
>> Thanks,
>> --
>> Yoshi
>>
>>
>>
>> On Sun, Feb 2, 2020 at 8:42 AM V Anil Kumar <anil@csir4pi.in 
>> <mailto:anil@csir4pi.in>> wrote:
>>
>>     Hi Yoshi,
>>
>>     Thanks for this point. In fact, I had initially not thought of a
>>     scenario, where the map is being delivered through a retransmitted
>>     data packet while its first transmission did not include the map.
>>     Now I am just seeing the document (RFC 6824-bis) in this context.
>>
>>     My understanding is that in scenarios like what I described in my
>>     previous mail, RST is likely to happen whether we explicitly state
>>     so or not. Please see the paragraph containing the below text in
>>     RFC 6824-bis.
>>
>>     "If a mapping for that subflow-level sequence space does not
>>     arrive within a receive window of data, that subflow SHOULD be
>>     treated as broken, closed with a RST, and any unmapped data
>>     silently discarded."
>>
>>     if we assume that the map is included while retransmitting the
>>     data (even though the first transmission did not contain the map
>>     for some reasons),  we could argue that RST could be avoided
>>     provided that the retransmission is triggered within a receive
>>     window of data. But the question here would be how and when will
>>     the retransmission take place. In this case, the subflow may not
>>     initiate the retransmission of data by its own (i.e., no
>>     retransmission due to three duplicate ACKs or RTO expiry at
>>     subflow level) as there is no segment loss at subflow level
>>     sequence space. So there could be a high possibility of RST
>>     happening even before the map delivery through retransmission.
>>
>>     With regards,
>>
>>     Anil
>>     ------------------------------------------------------------------------
>>     *From: *"Yoshifumi Nishida" <nsd.ietf@gmail.com
>>     <mailto:nsd.ietf@gmail.com>>
>>     *To: *"V Anil Kumar" <anil@csir4pi.in <mailto:anil@csir4pi.in>>
>>     *Cc: *"alan ford" <alan.ford@gmail.com
>>     <mailto:alan.ford@gmail.com>>, "multipathtcp"
>>     <multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>>
>>     *Sent: *Saturday, February 1, 2020 3:39:51 AM
>>     *Subject: *Re: [multipathtcp] RFC6824bis edits based on
>>     implementation feedback
>>
>>     Hi Anil,
>>
>>     I have a question about your proposed text.
>>     I am actually wondering if we really want to terminate connection
>>     here.
>>
>>     The packets without proper mappings will be treated as invalid and
>>     will be discarded.
>>     If an implementation failed to attach proper mapping for some
>>     reasons (e.g. option space), it might be able to attach the proper
>>     one when it retransmits the packets. This also looks ok to me.
>>
>>     I don't have strong preference for this. But, do we have a reason
>>     to terminate connection?
>>
>>     Thanks,
>>     --
>>     Yoshi
>>
>>     On Mon, Jan 13, 2020 at 10:28 AM V Anil Kumar <anil@csir4pi.in
>>     <mailto:anil@csir4pi.in>> wrote:
>>
>>         Hi,
>>
>>         I have some points related to the  modifications (Change 2)
>>         being proposed on data sequence map. Please see them inline.
>>         Though I am putting forward the below points, if the consensus
>>         is in favour of the proposed change for reducing
>>         implementation complexity, I am also OK with that as well.
>>
>>         ------------------------------------------------------------------------
>>         *From: *"alan ford" <alan.ford@gmail.com
>>         <mailto:alan.ford@gmail.com>>
>>         *To: *multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
>>         *Sent: *Thursday, January 2, 2020 4:21:32 AM
>>         *Subject: *[multipathtcp] RFC6824bis edits based on
>>         implementation feedback
>>
>>         Hi all,
>>         We’d love to get this to a state of completion as soon as
>>         possible, and to this end I am starting a new thread on this
>>         topic. In discussion with the chairs, it /is /possible to make
>>         the desired changes in AUTH48 as long as there is WG
>>         consensus. The discussion so far has been fairly limited in
>>         terms of participation.
>>
>>         I would ask the chairs please if it was possible to specify a
>>         time bound for this discussion and a default conclusion.
>>
>>         Regarding the changes, in summary, there are two areas where
>>         changes have been requested by the implementation community.
>>         As we are the IETF we obviously have strong focus on “running
>>         code” and so ease of implementing standards-compliant code is
>>         strongly desirable. However, we do not wish to reduce
>>         functionality agreed by the IETF community if it is considered
>>         a required feature by the community.
>>
>>
>>         *Change 1*
>>         *
>>         *
>>         Change the sentence reading:
>>
>>         /   If B has data to send first, then the reliable delivery of
>>         the ACK + MP_CAPABLE can be inferred by the receipt of this
>>         data with an MPTCP Data Sequence Signal (DSS) option (Section
>>         3.3).
>>         /
>>         To:
>>
>>         /   If B has data to send first, then the reliable delivery of
>>         the ACK + MP_CAPABLE is ensured by the receipt of this data
>>         with an MPTCP Data Sequence Signal (DSS) option (Section 3.3)
>>         containing a DATA_ACK for the MP_CAPABLE (which is the first
>>         octet of the data sequence space).
>>         /
>>         What this means:
>>
>>         The current text is concerned only with ensuring a path is
>>         MPTCP capable, and so only cares that DSS option occurs on a
>>         data packet. However, the MP_CAPABLE option is defined to
>>         occupy the first octet of data sequence space and thus, if
>>         analogous to TCP, must be acknowledged. >From an
>>         implementation point of view it would make sense not to have
>>         this hanging around forever and instead define it is
>>         acknowledged at the connection level as soon as received. This
>>         change ensures the first data packet also DATA_ACKs this
>>         MP_CAPABLE octet.
>>
>>
>>         *Change 2*
>>         *
>>         *
>>         Change the sentence reading:
>>
>>         /   A Data Sequence Mapping does not need to be included in
>>         every MPTCP packet, as long as the subflow sequence space in
>>         that packet is covered by a mapping known at the receiver./
>>
>>         To:
>>
>>         /   The mapping provided by a Data Sequence Mapping MUST apply
>>         to some or all of the subflow sequence space in the TCP
>>         segment which carries the option. It does not need to be
>>         included in every MPTCP packet, as long as the subflow
>>         sequence space in that packet is covered by a mapping known at
>>         the receiver.
>>         /
>>         What this means:
>>
>>         The current text does not place any restrictions on where a
>>         mapping could appear. In theory a sender could define a
>>         thousand different mappings up front, send them all, and
>>         expect a receiver to store this and reassemble data according
>>         to these mappings as it arrives. Indeed, this was never
>>         explicitly disallowed since it “might have been useful”. The
>>         implementation community, however, has expressed concerns over
>>         the difficulty of implementing this open-endedly. How many
>>         mappings is it reasonable to store? Is there a DoS risk here?
>>         Instead, it has been requested that thee specification
>>         restricts the placement of the DSS option to being within the
>>         subflow sequence space to which it applies.
>>
>>         Below are my comments on this. I had shared some of these
>>         points in a previous thread that you had initiated in the same
>>         context.
>>
>>         Transmitting large number of non-contiguous data sequence maps
>>         could be a misbehaviour (map-flooding), though it is not clear
>>         whether this can go to the extent of causing a potential DoS
>>         to the data receiver. So some sort of restriction on this
>>         could be useful.  One approach could be to insist that the
>>         data sender should ensure that the map being transmitted is
>>         for in-window data, as per the receiver advertised window. A
>>         receiver should anyhow be willing to store the maps for
>>         in-window data to deal with packet loss. For example, when a
>>         window of data segments (say 1 to 64) is transmitted, each
>>         carrying its corresponding map, and segment-1 is lost, the
>>         maps for the remaining 63 need to be stored till the lost
>>         segment is retransmitted. Of course, in this case the maps
>>         will be stored at the receiver side along with their
>>         corresponding data. But the need to store multiple maps for
>>         in-window data would still be there.
>>
>>         The problem with the proposed change (restriction) is that a
>>         data sender may find it difficult, in case a need arise to
>>         slightly delay the map delivery by few segments, i.e., sending
>>         some data first without map, and then send the corresponding
>>         map in a later segment, as shown below:
>>
>>         subflow-1:      segment-1                   segment-3         
>>                   segment-4                       segment-7
>>                               bytes:1-100                
>>         bytes:201-300              bytes:301-400                
>>         bytes:601-700
>>                               no map                        map for
>>         1-100              map for 201-400             map for 601-700
>>
>>
>>
>>         subflow-2:       segment-2                  segment-5        
>>                     segment-6                       segment-8
>>                                bytes: 101-200          
>>         bytes:401-500               bytes: 501-600              
>>          bytes:701-800
>>                                map for 101-200       map for 401-600  
>>                  no map                            map for 701-800
>>
>>
>>         In the above case, segment-1 goes without map and its map is
>>         included later in segment-3, the next data segment in the same
>>         subflow. Further,  in the above scheduling pattern, the map in
>>         segment-3 cannot cover the  data in segment-1 and segment-3,
>>         as some  data in between (segment-2) is transmitted through
>>         another subflow.  With the proposed change, the map in
>>         segment-3 will become invalid and this will eventually break
>>         subflow-1, though this could be a corner case.
>>
>>         The question at this stage is why would segment-1 be
>>         transmitted without its map. In the case of bidirectional data
>>         transfer, there could be a need to pack both timestamp and
>>         SACK  options in a data segment, i.e., piggybacking of  SACK
>>         with data. If we consider that timestamp takes 12 bytes and
>>         SACK, even with single block,  takes another 10 bytes, the
>>         remaining 18 bytes option space is not adequate to carry data
>>         sequence signal with map, especially when DSN is 64 bit long.
>>         So the delivery of either of the two (SACK or map) would be
>>         delayed.
>>
>>         As far as I understand, RFC 2018 (TCP Selective
>>         Acknowledgement Options) implies that SACK should not be
>>         delayed. It states "If sent at all, SACK options SHOULD be
>>         included in all ACKs which do not ACK the highest sequence
>>         number in the data receiver's queue". It also says "If data
>>         receiver generates SACK options under any circumstance, it
>>         SHOULD generate them under all permitted circumstances".   So,
>>         as part of meeting the RFC 2018 requirements, if the
>>         combination of SACK and timestamp is given preference over
>>         DSS, data segments could be transmitted without their map.
>>
>>         Another case of delaying map could arise if the data sender
>>         prefers to send ADD_ADDR option, instead of map, in a data
>>         segment. It is nice that ADD_ADDR option can be delivered
>>         reliably in a pure ACK, but I think this is not the case with
>>         DSS at present.
>>
>>         If we adopt the proposed change, I think it might also be
>>         helpful to spell out how the receiver is supposed to behave,
>>         if it gets maps not meeting the MUST condition in the proposed
>>         change.  For example termination of the subflow with MP_TCPRST
>>         option (section 3.6 in RFC 6824-bis) with appropriate reason
>>         code and T flag value to intimate the data sender the cause
>>         for subflow termination.
>>         With regards,
>>
>>         Anil
>>
>>         Please can members of the WG express whether they are happy
>>         with these changes, or concerned.
>>
>>         Best regards,
>>         Alan
>>
>>
>>         _______________________________________________
>>         multipathtcp mailing list
>>         multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
>>         https://www.ietf.org/mailman/listinfo/multipathtcp
>>
>>
>>
>>         _______________________________________________
>>         multipathtcp mailing list
>>         multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
>>         https://www.ietf.org/mailman/listinfo/multipathtcp
>>
>>
>>
>>
> 
> 
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp
> 

-- 
Matthieu Baerts | R&D Engineer
matthieu.baerts@tessares.net
Tessares SA | Hybrid Access Solutions
www.tessares.net
1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium