[multipathtcp] TR: New Version Notification for draft-boucadair-mptcp-plain-mode-10.txt

<mohamed.boucadair@orange.com> Fri, 10 March 2017 08:43 UTC

Return-Path: <mohamed.boucadair@orange.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 86CC4126B6D for <multipathtcp@ietfa.amsl.com>; Fri, 10 Mar 2017 00:43:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 3FAj5exaWeLf for <multipathtcp@ietfa.amsl.com>; Fri, 10 Mar 2017 00:43:28 -0800 (PST)
Received: from relais-inet.orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1FE21293D9 for <multipathtcp@ietf.org>; Fri, 10 Mar 2017 00:43:28 -0800 (PST)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr26.francetelecom.fr (ESMTP service) with ESMTP id 4F088205D1 for <multipathtcp@ietf.org>; Fri, 10 Mar 2017 09:43:27 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.63]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id 2E4541A005F for <multipathtcp@ietf.org>; Fri, 10 Mar 2017 09:43:27 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM6E.corporate.adroot.infra.ftgroup ([fe80::f5a7:eab1:c095:d9ec%18]) with mapi id 14.03.0319.002; Fri, 10 Mar 2017 09:43:26 +0100
From: <mohamed.boucadair@orange.com>
To: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: New Version Notification for draft-boucadair-mptcp-plain-mode-10.txt
Thread-Index: AQHSmXM5/PFqyseR0E+evJeosOHWg6GNtcAw
Date: Fri, 10 Mar 2017 08:43:26 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009E214F1@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <148913232809.5852.12101301305757163816.idtracker@ietfa.amsl.com>
In-Reply-To: <148913232809.5852.12101301305757163816.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/uqzSitnSFVsV4WUbrBhLcgRQy0Y>
Subject: [multipathtcp] TR: New Version Notification for draft-boucadair-mptcp-plain-mode-10.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.17
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, 10 Mar 2017 08:43:30 -0000

Dear all, 

A new version of the draft is available online. This version integrates the comments that were raised on the mailing list. 
We had many off-line discussions with Alan, this version is the outcome of those discussion. The main changes are:

* MP_CONVERT object does not consume anymore the MPTCP option codepoints space.
* A new MPTCP option (MP_PREFER_PROXY) is defined to demux native connections vs proxied one when the implicit mode is in use.
* MCPs are now able to detect if remote MCPs do not support MP_CONVERT
* Only TCP is covered
* Interference with TFO are discussed 

Comments, questions, and suggestions are always welcome.

Cheers,
Med

> -----Message d'origine-----
> De : internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Envoyé : vendredi 10 mars 2017 08:52
> À : Wim Henderickx; Luis M. Contreras; stefano.secci@lip6.fr; Wouter
> Cloetens; Suresh Vinapamula; Denis Behaghel; BOUCADAIR Mohamed IMT/OLN;
> Suresh Vinapamula; Robert Skog; Luis Contreras; JACQUENET Christian
> IMT/OLN; Bart Peirens; Ullrich Meyer; Denis Behaghel; Olivier Bonaventure;
> SungHoon Seo; Stefano Secci
> Objet : New Version Notification for draft-boucadair-mptcp-plain-mode-
> 10.txt
> 
> 
> A new version of I-D, draft-boucadair-mptcp-plain-mode-10.txt
> has been successfully submitted by Mohamed Boucadair and posted to the
> IETF repository.
> 
> Name:		draft-boucadair-mptcp-plain-mode
> Revision:	10
> Title:		Extensions for Network-Assisted MPTCP Deployment Models
> Document date:	2017-03-09
> Group:		Individual Submission
> Pages:		25
> URL:            https://www.ietf.org/internet-drafts/draft-boucadair-
> mptcp-plain-mode-10.txt
> Status:         https://datatracker.ietf.org/doc/draft-boucadair-mptcp-
> plain-mode/
> Htmlized:       https://tools.ietf.org/html/draft-boucadair-mptcp-plain-
> mode-10
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-boucadair-mptcp-
> plain-mode-10
> 
> Abstract:
>    Because of the lack of Multipath TCP (MPTCP) support at the server
>    side, some service providers now consider a network-assisted model
>    that relies upon the activation of a dedicated function called MPTCP
>    Conversion Point (MCP).  Network-Assisted MPTCP deployment models are
>    designed to facilitate the adoption of MPTCP for the establishment of
>    multi-path communications without making any assumption about the
>    support of MPTCP by the communicating peers.  MCPs located in the
>    network are responsible for establishing multi-path communications on
>    behalf of endpoints, thereby taking advantage of MPTCP capabilities
>    to achieve different goals that include (but are not limited to)
>    optimization of resource usage (e.g., bandwidth aggregation), of
>    resiliency (e.g., primary/backup communication paths), and traffic
>    offload management.
> 
>    This document specifies extensions for Network-Assisted MPTCP
>    deployment models.
> 
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat