[multipathtcp] TR: I-D Action: draft-nam-mptcp-deployment-considerations-01.txt

<mohamed.boucadair@orange.com> Wed, 07 December 2016 13:15 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 C24741299DF for <multipathtcp@ietfa.amsl.com>; Wed, 7 Dec 2016 05:15:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.515
X-Spam-Level:
X-Spam-Status: No, score=-5.515 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=-2.896, 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 0p3vudhXtYHV for <multipathtcp@ietfa.amsl.com>; Wed, 7 Dec 2016 05:15:13 -0800 (PST)
Received: from relais-inet.orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 349241299C3 for <multipathtcp@ietf.org>; Wed, 7 Dec 2016 05:11:35 -0800 (PST)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id C2A84C0497 for <multipathtcp@ietf.org>; Wed, 7 Dec 2016 14:11:33 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.13]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id 955261A006D for <multipathtcp@ietf.org>; Wed, 7 Dec 2016 14:11:33 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM6D.corporate.adroot.infra.ftgroup ([fe80::54f9:a6c3:c013:cbc7%19]) with mapi id 14.03.0319.002; Wed, 7 Dec 2016 14:11:33 +0100
From: <mohamed.boucadair@orange.com>
To: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: I-D Action: draft-nam-mptcp-deployment-considerations-01.txt
Thread-Index: AQHSUIpONQuBaGyH2UCmYp8DkH9OnqD8c/EQ
Date: Wed, 7 Dec 2016 13:11:33 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009DCA6F6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <148111579370.13598.17631444757073795074.idtracker@ietfa.amsl.com>
In-Reply-To: <148111579370.13598.17631444757073795074.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/k5UR4j4eLVVKhd-q7aSiMdrOrPc>
Subject: [multipathtcp] TR: I-D Action: draft-nam-mptcp-deployment-considerations-01.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: Wed, 07 Dec 2016 13:15:14 -0000

Dear all, 

A new version of this draft is available online. This version integrates the comments raised on the mailing list, in particular:
 
* Add a new section to cover the DC proxy case
* Clarify the need to distinguish proxied MPTCP connections vs. native ones. 
* Add a new section to discuss how the proxy can be offloaded in favor of e2e communications. 
* Add some text to document complications that may arise if the proxy is removed blindly for the path when both client and server are MPTCP-capable. 

I would like to thank Alan for many offline discussions. Much appreciated!

I do think this version is stable to consider WG adoption. 

As always comments, questions and suggestions are more than welcome.

Cheers,
Med

> -----Message d'origine-----
> De : I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part de
> internet-drafts@ietf.org
> Envoyé : mercredi 7 décembre 2016 14:03
> À : i-d-announce@ietf.org
> Objet : I-D Action: draft-nam-mptcp-deployment-considerations-01.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 
>         Title           : Network-Assisted MPTCP: Use Cases, Deployment
> Scenarios and Operational Considerations
>         Authors         : Mohamed Boucadair
>                           Christian Jacquenet
>                           Olivier Bonaventure
>                           Wim Henderickx
>                           Robert Skog
> 	Filename        : draft-nam-mptcp-deployment-considerations-01.txt
> 	Pages           : 29
> 	Date            : 2016-12-07
> 
> Abstract:
>    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.  MPTCP Conversion Points (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 describes Network-Assisted MPTCP uses cases, deployment
>    scenarios, and operational considerations.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-nam-mptcp-deployment-
> considerations/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-nam-mptcp-deployment-considerations-01
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-nam-mptcp-deployment-
> considerations-01
> 
> 
> 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.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt