Re: [multipathtcp] MPTCP implementation feedback for RFC6824bis

V Anil Kumar <anil@csir4pi.in> Fri, 13 December 2019 05:53 UTC

Return-Path: <prvs=24322b142=anil@csir4pi.in>
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 70BE1120807 for <multipathtcp@ietfa.amsl.com>; Thu, 12 Dec 2019 21:53:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 IU0Ow0c-DCRz for <multipathtcp@ietfa.amsl.com>; Thu, 12 Dec 2019 21:52:57 -0800 (PST)
Received: from vastu154.nic.in (vastu154.nic.in [164.100.2.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D65E112026E for <multipathtcp@ietf.org>; Thu, 12 Dec 2019 21:52:56 -0800 (PST)
IronPort-PHdr: =?us-ascii?q?9a23=3A0BmuaRR1A7dEdkT9Lncmof8n09psv+yvbD5Q0Y?= =?us-ascii?q?Iujvd0So/mwa69YhaN2/xhgRfzUJnB7Loc0qyK6vumAD1eqsnd+Fk5M7V0Hy?= =?us-ascii?q?cfjssXmwFySOWkMmbcaMDQUiohAc5ZX0Vk9XzoeWJcGcL5ekGA6ibqtW1aFR?= =?us-ascii?q?rwLxd6KfroEYDOkcu3y/qy+5rOaAlUmTaxe7x/IAi4oAnLq8UbhYpvJqkzxx?= =?us-ascii?q?bGv3BFZ/lYyWR0KFyJgh3y/N2w/Jlt8yRRv/Iu6ctNWrjkcqo7ULJVEi0oP3?= =?us-ascii?q?g668P3uxbDSxCP5mYHXWUNjhVIGQnF4wrkUZr3ryD3q/By2CiePc3xULA0RT?= =?us-ascii?q?Gv5LplRRP0lCsKMSMy/XrJgcJskq1UvBOhpwR+w4HKZoGVKOF+db7Zcd8DWG?= =?us-ascii?q?ZNQtpdWylHD4ihbYUAEvABMP5YoYfjpFUAoxywCxSoBOztxD9FnWX50bEg3u?= =?us-ascii?q?QlCwzKwA4tEtQTu3rUttX1M6ISXPi6w6LV0TjDafJW2TPg44bNbxAhpOuDXa?= =?us-ascii?q?htesfW00YvEQLFjlGLpIP5JDOV1/4NvmeD7+phT+6vimgnphh3rzOyxckskp?= =?us-ascii?q?HEip8Rx1za7yl13Yc4KN6iREJme9KoDoZcuzmHO4Z5WM8uXm9ltSIgxrEbt5?= =?us-ascii?q?O2czIGxIo7yxPZdveJaZKH4gj5W+aUOTp4gXVld6+hiBuq6kigz/H8VtGz0F?= =?us-ascii?q?ZXsipJitnMuW4J1xzU8sWHT+Fy/kal2TqV2ADT7f9ELVo1lardM5Ihw7gwmY?= =?us-ascii?q?QPsUnbAyP7nFv6gLWLekgl+eWk8fnrbq/4qpOBL4N0jxvxMqUqmsyxG+Q4NQ?= =?us-ascii?q?0OUnCB9uS61b3j+Vb0T6lRjv03iKnUv4jaJcUBqq64BQ9Zypwj5AqnDze6zN?= =?us-ascii?q?QYmmEKLFdYeBKDk4jpOknOL+rkDfe/n1SjjC9ryuvHPrL/HpXNIGLPkLD7fb?= =?us-ascii?q?ZyuAZgz18Yzcpe/I5TErFJGPv6QUTx/IjTFhYwKAe06+//ENFwkIgZXDTcLL?= =?us-ascii?q?WeNfbs+XaO5+ZnAPSJbZVd7D/7KvwN7OXvlyMhmBkce//6jtMsdHmkE6E+cA?= =?us-ascii?q?2ian32j4JESD9Ssw=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2ExAADwGfNd/xUBqMBlGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBEQEBAQEBAQEBAQEBgX6BHIMhCoN5kTSJW5FUCQEBAgEBAQE?= =?us-ascii?q?BNwEBhEACgi84EwIDAQwBAQEEAQEBAQEFAwEBAQKFVCAGJgyCOykBg08BBSM?= =?us-ascii?q?aDQgVEhABCAINAQoJIQICDxI2BgsIFIVVA5Ivm3SBMhoCg02EJg2CK4E2gWW?= =?us-ascii?q?DN4cQBoIAgRGDEz6BBIEXhT6CXgSNQ4oFiA2OV0OCOoY/hhiEf4Q+gkKHdoQ?= =?us-ascii?q?aFAOLWJkuj3ABgXqBe004gydQEYMziXwPC4UIiRoJbJAbAQE?=
X-IPAS-Result: =?us-ascii?q?A2ExAADwGfNd/xUBqMBlGQEBAQEBAQEBAQEBAQEBAQEBE?= =?us-ascii?q?QEBAQEBAQEBAQEBgX6BHIMhCoN5kTSJW5FUCQEBAgEBAQEBNwEBhEACgi84E?= =?us-ascii?q?wIDAQwBAQEEAQEBAQEFAwEBAQKFVCAGJgyCOykBg08BBSMaDQgVEhABCAINA?= =?us-ascii?q?QoJIQICDxI2BgsIFIVVA5Ivm3SBMhoCg02EJg2CK4E2gWWDN4cQBoIAgRGDE?= =?us-ascii?q?z6BBIEXhT6CXgSNQ4oFiA2OV0OCOoY/hhiEf4Q+gkKHdoQaFAOLWJkuj3ABg?= =?us-ascii?q?XqBe004gydQEYMziXwPC4UIiRoJbJAbAQE?=
X-IronPort-AV: E=McAfee;i="6000,8403,9469"; a="72742976"
X-IronPort-AV: E=Sophos; i="5.69,308,1571682600"; d="scan'208,217"; a="72742976"
Received: from unknown (HELO mail.gov.in) ([192.168.1.21]) by esahyd04local.nic.in with ESMTP; 13 Dec 2019 11:22:51 +0530
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_rFh1q2Sss3aRPjceIketJQ)"
Received: from nic.in ([192.168.1.21]) by msgfe32.nic.in (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Nov 28 2016)) with ESMTPA id <0Q2F0022TSC2E600@msgfe32.nic.in> for multipathtcp@ietf.org; Fri, 13 Dec 2019 11:22:50 +0530 (IST)
Sender: anil@csir4pi.in
Received: from [192.168.1.21] (Forwarded-For: 14.139.134.20) by msgfe31.nic.in (mshttpd); Fri, 13 Dec 2019 11:22:50 +0530
From: V Anil Kumar <anil@csir4pi.in>
To: Christoph Paasch <cpaasch@apple.com>
Cc: Alan Ford <alan.ford@gmail.com>, MultiPath TCP - IETF WG <multipathtcp@ietf.org>, mptcp Upstreaming <mptcp@lists.01.org>, Mirja Kuehlewind <ietf@kuehlewind.net>
Message-id: <f97420243acd.5df3748a@nic.in>
Date: Fri, 13 Dec 2019 11:22:50 +0530
X-Mailer: Oracle Communications Messenger Express 7.0.5.38.0 64bit (built Nov 28 2016)
Content-language: en
X-Accept-Language: en
Priority: normal
In-reply-to: <49ED222B-9E71-4A8F-A280-2521ED650454@apple.com>
References: <fa671a2f315e.5df04794@nic.in> <49ED222B-9E71-4A8F-A280-2521ED650454@apple.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/01XrD4BZSJhS9tOygVn1gnhDEnM>
Subject: Re: [multipathtcp] MPTCP implementation feedback for RFC6824bis
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: Fri, 13 Dec 2019 05:53:00 -0000

Hi Christoph,

Thanks for your reply. Please see inline.

On 12/12/19 12:52 AM, Christoph Paasch  <cpaasch@apple.com> wrote: 
> 
> 
> 
> 
> 
> Hello,
> 
> 
> 
> 
> > 
> > On Dec 10, 2019, at 12:04 PM, V Anil Kumar <anil@csir4pi.in> wrote:
> > 
> > 
> > Hi Alan, 
> > 
> > 
> > 
> > Please see inline.
> > 
> > On 12/06/19 09:28 PM,  Alan Ford  <alan.ford@gmail.com> wrote: 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Hi all,
> > > 
> > > 
> > > 
> > > 
> > > Following on from the discussion of implementation feedback with Christoph, I propose the following edits to RFC6824bis - which is currently in AUTH48 - as clarifications.
> > > 
> > > 
> > > 
> > > 
> > > ADs, please can you confirm you consider these edits sufficiently editorial to fit into AUTH48.
> > > 
> > > 
> > > 
> > > 
> > > WG participants, please speak up if you have any concerns.
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Edit 1, clarifying reliability of MP_CAPABLE
> > > 
> > > 
> > > 
> > > 
> > > Change the sentence reading:
> > > 
> > > 
> > > 
> > > 
> > >  The SYN with MP_CAPABLE occupies the first octet of data sequence space, although this does not need to be acknowledged at the connection level until the first data is sent (see Section 3.3).
> > > 
> > > 
> > > 
> > > 
> > > To:
> > > 
> > > 
> > > 
> > > 
> > >  The SYN with MP_CAPABLE occupies the first octet of data sequence space, and this MUST be acknowledged at the connection level at or before the time the first data is sent or received (see Section 3.3).
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 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).
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > In my personal opinion either one of these edits would be sufficient for making the point, however clearly this has caused some confusion amongst the implementor community so making both these changes should make it absolutely clear as to the expected behaviour here.
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Edit 2, mapping constraint
> > > 
> > > 
> > > 
> > > 
> > > 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:
> > > 
> > > 
> > > 
> > > 
> > >  A Data Sequence Mapping MUST appear on a TCP segment which is covered by the mapping. 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.
> > > 
> > > 
> > > 
> > > 
> > >  
> > > 
> > 
> > As far as I understand, the proposed change introduces a “MUST” to insist that the map in a segment must cover at least some data in the segment. But the document does not talk anything about the rational behind it. I guess it is purely an 
> > 
> > ease of implementation?
> > 
> > 
> 
> 
> For two reasons:
> 
> 1. Ease of implementation
> 2. If an implementation tries to "remember" early mappings, it is not clear how many of these an implementation can hold. Thus, the sender does not know how many early mappings he can send. So, it is hard for a sender to do the right thing.
> 
> 
> > 
> > 
> > 
> > I think the design/format of the Data Sequence Mapping permits the map to stand independent of the data being carried in a segment. So, as long as an implementation is willing to deal with the complexity of storing and processing late and early mappings (with respect to the data arrival), it could be permitted provided that the received map is for an in-window data.
> > 
> > 
> 
> 
> What is the concrete use-case for such early mappings? What are the benefits of it? I think that if we want to enable such implementation-complexity, we need a compelling use-case with a big benefit.
> 
> 
>  
> 

Consider a case where a MPTCP connection consists of two subflows, and the data segments are scheduled for transmission in the order shown below below.  


 



Subflow-1: segment-1 segment-3 segment-5 segment-6 

 bytes:1-100 bytes:201-300 bytes:401-500 bytes:501-600 

 no map map for 1-100 map for 401-600 no map 


 


 



Subflow-2: segment-2 segment-4 segment-7 segment-8 

 bytes: 101-200 bytes:301-400 bytes: 601-700 bytes:701-800  

 map for 101-200 map for 301-400 map for 601-800 no map 

  

In the above case, the map for data in segment-1 is included in segment-3. Further, segment-3 cannot combine/cover the data in segment-1 and segment-3 in a "single map", as the data sequence space is not continuous, i.e., some in between data (segment-2) is mapped and transmitted through subflow-2. Here, the map in segment-3 does not even partially cover the data it carries. 


 

Both RFC 6824 and the 6824-bis do not restrict the above scenario, and I guess the change proposed now does not permit this to happen. 


 

Best regards, 


 

Anil 



> 
> 
> 
> 
> 
> 
> 
> That's the reason why we (the MPTCP-upstreaming community) vouch to have this case restricted.
> 
> 
> 
> Cheers,
> Christoph
> 
> 
> 
> 
> 
> > 
> > 
> > 
> > 
> > 
> > 
> > Anil 
> > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Best regards,
> > > 
> > > Alan
> > > 
> > > 
> > >  
> > > 
> > 
> > 
> 
> 
> 
> 
>  
>