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

[<[e-mail]>]

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 : [e-mail] [mailto:[e-mail]]
> Envoyé : vendredi 10 mars 2017 08:52
> À : Wim Henderickx; Luis M. Contreras; [e-mail]; 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