Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-07.txt

[Christoph Paasch <[e-mail]>]

Hello,

On 28/10/16 - 21:25:21, Alan Ford wrote:
> Hi all,
> 
> This small rev to rfc6824bis applies the two changes proposed by Fabien which had support on the list:
> 
> - The flag on MP_CAPABLE to say “do not connect back to this address” (proposal 1/5)
> - The echo flag to make ADD_ADDR reliable (proposal 2/5)
> 
> The “do not use this address unless nothing else is available (proposal 3/5) did not appear to have much support on the list so has been left out for now.

I still support this proposal :)


Christoph

> 
> Proposals 4 and 5 are MIA so have not been added at this stage ;-)
> 
> Cheers,
> Alan
> 
> > On 28 Oct 2016, at 21:22, [e-mail] wrote:
> > 
> > 
> > A New Internet-Draft is available from the on-line Internet-Drafts directories.
> > This draft is a work item of the Multipath TCP of the IETF.
> > 
> >        Title           : TCP Extensions for Multipath Operation with Multiple Addresses
> >        Authors         : Alan Ford
> >                          Costin Raiciu
> >                          Mark Handley
> >                          Olivier Bonaventure
> >                          Christoph Paasch
> > 	Filename        : draft-ietf-mptcp-rfc6824bis-07.txt
> > 	Pages           : 73
> > 	Date            : 2016-10-28
> > 
> > Abstract:
> >   TCP/IP communication is currently restricted to a single path per
> >   connection, yet multiple paths often exist between peers.  The
> >   simultaneous use of these multiple paths for a TCP/IP session would
> >   improve resource usage within the network and, thus, improve user
> >   experience through higher throughput and improved resilience to
> >   network failure.
> > 
> >   Multipath TCP provides the ability to simultaneously use multiple
> >   paths between peers.  This document presents a set of extensions to
> >   traditional TCP to support multipath operation.  The protocol offers
> >   the same type of service to applications as TCP (i.e., reliable
> >   bytestream), and it provides the components necessary to establish
> >   and use multiple TCP flows across potentially disjoint paths.
> > 
> >   This document specifies v1 of Multipath TCP, obsoleting v0 as
> >   specified in RFC6824 [RFC6824] through clarifications and
> >   modifications primarily driven by deployment experience.
> > 
> > 
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-mptcp-rfc6824bis/
> > 
> > There's also a htmlized version available at:
> > https://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-07
> > 
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-mptcp-rfc6824bis-07
> > 
> > 
> > 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/
> > 
> > _______________________________________________
> > multipathtcp mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/multipathtcp
> 
> _______________________________________________
> multipathtcp mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/multipathtcp