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

From: <[email-masked]>
Date: Wed, 7 Dec 2016 13:11:33 +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:[email-masked]] De la part de
> [email-masked]
> Envoyé : mercredi 7 décembre 2016 14:03
> À : [email-masked]
> 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
> [email-masked]
> 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