[multipathtcp] Preparing for Prague meeting - things to delete or add to MPTCP protocol bis

<philip.eardley@bt.com> Mon, 06 July 2015 18:01 UTC

Return-Path: <philip.eardley@bt.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF7741A1B19 for <multipathtcp@ietfa.amsl.com>; Mon, 6 Jul 2015 11:01:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 2XAKknM9wENZ for <multipathtcp@ietfa.amsl.com>; Mon, 6 Jul 2015 11:01:26 -0700 (PDT)
Received: from smtpb1.bt.com (smtpb1.bt.com [62.7.242.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDF271A1B30 for <multipathtcp@ietf.org>; Mon, 6 Jul 2015 11:01:25 -0700 (PDT)
Received: from E07HT02-UKBR.domain1.systemhost.net (193.113.197.160) by EVMED01-UKBR.bt.com (10.216.161.31) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 6 Jul 2015 19:01:22 +0100
Received: from rew09926dag03d.domain1.systemhost.net (10.55.202.30) by E07HT02-UKBR.domain1.systemhost.net (193.113.197.160) with Microsoft SMTP Server (TLS) id 8.3.342.0; Mon, 6 Jul 2015 19:01:22 +0100
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by rew09926dag03d.domain1.systemhost.net (10.55.202.30) with Microsoft SMTP Server (TLS) id 15.0.995.29; Mon, 6 Jul 2015 19:01:21 +0100
Received: from rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e]) by rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e%12]) with mapi id 15.00.0995.031; Mon, 6 Jul 2015 19:01:21 +0100
From: philip.eardley@bt.com
To: multipathtcp@ietf.org
Thread-Topic: Preparing for Prague meeting - things to delete or add to MPTCP protocol bis
Thread-Index: AQHQuBC1ogV2Z1ShB0+RXyp9UJJDtJ3Ou0Bj
Date: Mon, 06 Jul 2015 18:01:21 +0000
Message-ID: <1436205703501.53882@bt.com>
References: <1436204168109.20146@bt.com>
In-Reply-To: <1436204168109.20146@bt.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.216.161.24]
Content-Type: multipart/alternative; boundary="_000_143620570350153882btcom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/9zgCsd49UdosT2IRRxrLpKwmnfg>
Subject: [multipathtcp] Preparing for Prague meeting - things to delete or add to MPTCP protocol bis
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 06 Jul 2015 18:01:28 -0000

Hi,

In the Prague meeting, we aim to move forward the protocol bis doc (to meeting our Cahrter objetive for a standards track version of RFC6824)



One topic we'd like to discuss is if there's anything that should be deleted from or added to the current draft, <https://tools.ietf.org/wg/mptcp/draft-ietf-mptcp-rfc6824bis/> https://tools.ietf.org/wg/mptcp/draft-ietf-mptcp-rfc6824bis/ - based on operational and implementation experience.



Any proposals?



Looking at the (expired) draft summarising the various implementations,

https://tools.ietf.org/html/draft-eardley-mptcp-implementations-survey-02

one thing that may be worth discussing is whether we need both 4 & 8 byte Data ack & DSS

<<   All implementations support 4 bytes "Data ACK" and "Data sequence
   number" fields, and will interoperate with an implementation sending
   8 bytes.  Implementation 1 uses only 4 bytes fields; if an
   implementation sends an 8 byte data sequence number it replies with a
   4 byte data ack.

>>



I don't think the implementation survey suggests that there's anything else worth considering deleting - are there any other proposals?



As to things to add, there are a few proposals for some (minor?) additions in the recent set of drafts from Olivier Bonaventure and team.



Since we have a lot more requests for presentation time than it's possible to squeeze into the meeting, it would be excellent to have discussion on the list before the meeting, about anything that should be added to, or deleted from, the current rfc6824bis, before we progress it to WG last call.



thanks!