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

Alan,
Looks good.

1. the list of changes /reasons compared with rfc6824 not included. I can submit as separate draft, if you prefer to inclusion in your doc.

2. I  made a comment on Fig 12 (just checking you meant to ignore it - don’t mind!)

And in Fig 12
|        Truncated HMAC (8 octets, if length > 10 octets)       |

Could this be made more straightforward? Ie spell out when length is >10 octets ie IPv6 (if I understand it). This also seems to mean that IPv4 doesn’t include the HMAC, is this right??

3. I made a comment on Section 2:  Need to add sub-sections on closing subflow & fast close & fallback
Would be nice, but I won't insist if it's too much work

Thanks
phil

-----Original Message-----
From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of Alan Ford
Sent: 03 October 2018 15:26
To: multipathtcp <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-12.txt

Hi all,

I believe this new version addresses all last call/review comments we received for rfc6824bis, with the exception of adding a possible “changes since RFC6824” section.

Could all reviewers please check this new version and ensure we have handled your review comments appropriately?

Many thanks,
Alan

> On 3 Oct 2018, at 15:23, 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-12.txt
> 	Pages           : 80
> 	Date            : 2018-10-03
> 
> 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-12
> https://datatracker.ietf.org/doc/html/draft-ietf-mptcp-rfc6824bis-12
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mptcp-rfc6824bis-12
> 
> 
> 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