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

Hi Alan, thanks for the updates!
I just would like to check that this version has addressed all remaining
outstanding comments from authers' point of view.
--
Yoshi

On Tue, May 15, 2018 at 2:42 PM Alan Ford <alan.ford@gmail.com> wrote:

> Hi all,
>
> This update to rfc6824bis acts upon the feedback from IETF101 in London.
>
> Specifically:
>
> - Remove the Experimental option specification on request of Olivier (but
> keeping the option type reserved);
> - Move TFO discussion to the Appendix since this is an Experimental
> specification;
> - Add some clarification text regarding processing unexpected ACK numbers
> (which came out of the TFO discussion).
>
> Regards,
> Alan
>
> > On 15 May 2018, at 19:39, internet-drafts@ietf.org wrote:
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the Multipath TCP WG 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-11.txt
> >       Pages           : 76
> >       Date            : 2018-05-15
> >
> > 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 are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-11
> > https://datatracker.ietf.org/doc/html/draft-ietf-mptcp-rfc6824bis-11
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-mptcp-rfc6824bis-11
> >
> >
> > 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
> > multipathtcp@ietf.org
> > https://www.ietf.org/mailman/listinfo/multipathtcp
>
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp
>