Re: [multipathtcp] Submitted drafts

<philip.eardley@bt.com> Thu, 09 July 2015 15:45 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 556181B2AA8 for <multipathtcp@ietfa.amsl.com>; Thu, 9 Jul 2015 08:45:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level:
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 elGVusoeGPaV for <multipathtcp@ietfa.amsl.com>; Thu, 9 Jul 2015 08:45:14 -0700 (PDT)
Received: from smtpb1.bt.com (smtpb1.bt.com [62.7.242.141]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D0811B2AA3 for <multipathtcp@ietf.org>; Thu, 9 Jul 2015 08:45:14 -0700 (PDT)
Received: from EPDAG01C-UKBR.domain1.systemhost.net (193.113.197.204) by EVMED05-UKBR.bt.com (10.216.161.37) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 9 Jul 2015 16:45:12 +0100
Received: from rew09926dag03a.domain1.systemhost.net (10.55.202.18) by EPDAG01C-UKBR.domain1.systemhost.net (193.113.197.204) with Microsoft SMTP Server (TLS) id 15.0.995.29; Thu, 9 Jul 2015 16:45:11 +0100
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by rew09926dag03a.domain1.systemhost.net (10.55.202.18) with Microsoft SMTP Server (TLS) id 15.0.995.29; Thu, 9 Jul 2015 16:45:11 +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; Thu, 9 Jul 2015 16:45:11 +0100
From: philip.eardley@bt.com
To: Olivier.Bonaventure@uclouvain.be, multipathtcp@ietf.org
Thread-Topic: [multipathtcp] Submitted drafts
Thread-Index: AQHQuljwYGvn+70fnkqHopUyfKqQSJ3TR2nQ
Date: Thu, 09 Jul 2015 15:45:10 +0000
Message-ID: <cdbfab2b826949a5bf4f824358a995dc@rew09926dag03b.domain1.systemhost.net>
References: <559E8D85.2060603@uclouvain.be>
In-Reply-To: <559E8D85.2060603@uclouvain.be>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.55.202.233]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/plzHGGxSbGmoIBejLtRCKndfzVo>
Subject: Re: [multipathtcp] Submitted drafts
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: Thu, 09 Jul 2015 15:45:20 -0000

Olivier and colleagues,

Thanks for all the work. 

Please comment on the drafts - for instance, what things are worth adding to the protocol bis?

phil

> -----Original Message-----
> From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of
> Olivier Bonaventure
> Sent: 09 July 2015 16:05
> To: multipathtcp
> Subject: [multipathtcp] Submitted drafts
> 
> Hello,
> 
> 
> During the last week we have written and submitted several drafts that
> could be of interest for the working group :
> 
> * https://www.ietf.org/internet-drafts/draft-ietf-mptcp-experience-
> 02.txt
> 
> This is a revised version of the Use case and experience draft that is
> part of the WG charter. We've taken into account most of the comments
> received in June and have added some text on the utilisation of MPTCP
> proxies.
> 
> *
> https://www.ietf.org/internet-drafts/draft-bonaventure-mptcp-exp-
> option-00.txt
> 
> This draft proposes a standard encoding for experimental MPTCP options.
> Given the small number of MPTCP options, it is important to allow
> experimenters to use MPTCP options without wasting this limited
> ressource.
> 
> https://www.ietf.org/internet-drafts/draft-bonaventure-mptcp-timestamp-
> 01.txt
> 
> This is an example of the utilisation of experimental options to encode
> a timestamp option
> 
> * https://www.ietf.org/internet-drafts/draft-bonaventure-mptcp-addr-
> 00.txt
> 
> This draft discusses some issues with the advertisement of addresses in
> Multipath TCP and proposes a small modification to the handling of the
> address identifiers of the initial subflow to simplify implementations.
> It also shows how the reverse DNS can be used as an alternative to
> ADD_ADDR to announce the addresses of servers. This technique is
> already
> used for multipath-tcp.org
> 
> * https://www.ietf.org/internet-drafts/draft-bonaventure-mptcp-backup-
> 00.txt
> 
> This draft discusses some issues with the support of backup subflows in
> the existing Multipath TCP specification. In RFC6824 backup subflows
> work well when a subflow completely stops, but not when a subflow
> experiences huge losses.
> 
> *
> https://www.ietf.org/internet-drafts/draft-bonaventure-mptcp-long-
> options-00.txt
> 
> There have been many discussions on the TCPM working group about
> extending the space for TCP options in the TCP header. In this draft,
> we
> explore several ways of changing the DSS option to allow Multipath TCP
> to support long options.
> 
> 
> Comments on any of those drafts are of course welcome. Some will be
> presented quickly in Prague but we won't probably have time to discuss
> all of them
> 
> Olivier
> 
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp