[multipathtcp] Timestamp option for Multipath TCP

Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be> Thu, 23 March 2017 14:34 UTC

Return-Path: <olivier.bonaventure@uclouvain.be>
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 5A0FB1243FE for <multipathtcp@ietfa.amsl.com>; Thu, 23 Mar 2017 07:34:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level:
X-Spam-Status: No, score=-4.321 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=uclouvain.be
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 XleEE6fG-aWI for <multipathtcp@ietfa.amsl.com>; Thu, 23 Mar 2017 07:34:06 -0700 (PDT)
Received: from smtp2.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 231F11205D3 for <multipathtcp@ietf.org>; Thu, 23 Mar 2017 07:34:06 -0700 (PDT)
Received: from mbpobo.dhcp.info.ucl.ac.be (mbpobo.dhcp.info.ucl.ac.be [130.104.228.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: obonaventure@smtp2.sgsi.ucl.ac.be) by smtp2.sgsi.ucl.ac.be (Postfix) with ESMTPSA id 4A51567DDC0 for <multipathtcp@ietf.org>; Thu, 23 Mar 2017 15:33:58 +0100 (CET)
DKIM-Filter: OpenDKIM Filter v2.9.2 smtp2.sgsi.ucl.ac.be 4A51567DDC0
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1490279638; bh=jTXaJpZRKiEDLdJPJ0wO2G5gYVO0wsn+P1h8K7XyZ00=; h=Reply-To:To:From:Subject:Date; b=I3xMwXd/CFTg8KH1aoXz57W0ZzgnchlgYMKejxAj9Bv4wgnD1R3Y1nveGC9seoGbW /3+B9C1Rj5NWRNxCFqcZeLr/VniVyUT7EYGzQFrwQ1WJelkzkg/QKeW8T/VyoWpf1t o+Wo9VYmhsImPejWZrp0ntseFCBvIFq2PrzMZgBc=
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.99.2 at smtp-2
Reply-To: Olivier.Bonaventure@uclouvain.be
To: multipathtcp <multipathtcp@ietf.org>
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Message-ID: <c030efb2-5a1f-9ec9-a214-c302ebfb151f@uclouvain.be>
Date: Thu, 23 Mar 2017 15:33:57 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; 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-Sgsi-Spamcheck: SASL authenticated,
X-SGSI-Information:
X-SGSI-MailScanner-ID: 4A51567DDC0.A2917
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: olivier.bonaventure@uclouvain.be
X-SGSI-Spam-Status: No
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/MdPOsBE69t_XQfkd3mWgZyY_Cts>
Subject: [multipathtcp] Timestamp option for Multipath TCP
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: Thu, 23 Mar 2017 14:34:08 -0000

Hello,


The standard timestamp option for TCP is defined in RFC7323. It is 
widely implemented and used. It has two main objectives :

- timing measurements
- protection agains wrapped sequence numbers


Given the importance of the second utilisation, RFC7323 has mandated the 
presence of a timestamp option in each segment once negotiated in the 
three-way handshake. For Multipath TCP, the DSN option already protects 
us from PAWS problems and it should not be mandatory to include 
timestamps in each packet sent over a Multipath TCP connection. Given 
the length of the timestamp and DSN options these two options already 
consume a large number of bytes and could limit the number of SACK 
blocks that can be placed inside acknowledgements.

I will only be able to attend the Chicago meeting remotely, but I would 
like to start a discussion on the utilisation of timestamps by Multipath 
TCP on the list. I see two possibilities, but there are possibly more :

1. Ask for a revision of RFC7323 that allows timestamp options to be 
optional in packets of Multipath TCP connections

2. Define a new Multipath TCP option to carry timestamps. The 
utilisation of this option would be included in Multipath TCP and thus 
no option besides MP_CAPABLE would need to be included in the SYN.

Do you have any opinion on these two possibilities ?


Thanks



Olivier