[multipathtcp] Question on Data Sequence Mapping

Rao Shoaib <rao.shoaib@oracle.com> Tue, 16 May 2017 00:41 UTC

Return-Path: <rao.shoaib@oracle.com>
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 31C2A124BFA for <multipathtcp@ietfa.amsl.com>; Mon, 15 May 2017 17:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.522
X-Spam-Level:
X-Spam-Status: No, score=-1.522 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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] 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 DSaX8Xw-ZFnj for <multipathtcp@ietfa.amsl.com>; Mon, 15 May 2017 17:41:55 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (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 61CE112EAFC for <multipathtcp@ietf.org>; Mon, 15 May 2017 17:39:19 -0700 (PDT)
Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id v4G0dIDd019068 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <multipathtcp@ietf.org>; Tue, 16 May 2017 00:39:18 GMT
Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by userv0021.oracle.com (8.14.4/8.14.4) with ESMTP id v4G0dHCp017250 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <multipathtcp@ietf.org>; Tue, 16 May 2017 00:39:18 GMT
Received: from abhmp0013.oracle.com (abhmp0013.oracle.com [141.146.116.19]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id v4G0dHGB004687 for <multipathtcp@ietf.org>; Tue, 16 May 2017 00:39:17 GMT
Received: from [192.168.1.29] (/67.188.214.158) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 15 May 2017 17:39:17 -0700
To: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
From: Rao Shoaib <rao.shoaib@oracle.com>
Message-ID: <2a1aa330-f004-577e-93b4-0c93726e33d9@oracle.com>
Date: Mon, 15 May 2017 17:39:12 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Source-IP: userv0021.oracle.com [156.151.31.71]
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/0fiIjuPlfTvDDv_p2kap04GNfYw>
Subject: [multipathtcp] Question on Data Sequence Mapping
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
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, 16 May 2017 00:41:57 -0000

Hi,

Section 3.3.1 of RFC 6824 says

The data sequence mapping specifies a mapping from subflow sequence 
space to data sequence space. This is expressed in terms of starting 
sequence numbers for the subflow and the data level, and a length of 
bytes for which this mapping is valid.

<...>

A mapping is fixed, in that the subflow sequence number is bound to the 
data sequence number after the mapping has been processed. A sender MUST 
NOT change this mapping after it has been declared;

Does it mean that I can not map the data sequence to another (higher) 
TCP sequence number on the same flow.

The reason I am asking this is that if this is allowed  TCP and MPTCP 
processing can be separated on the recv side. For example, TCP could 
accept the packet but MPTCP could reject it. Since data level ack would 
not be sent the peer would retransmit, possibly using the same flow but 
with a different mapping so that TCP would accept the packet.

Is this legal to do and if not than why ?

Regards,

Rao