Re: [tcpm] I-D Action: draft-ietf-tcpm-converters-12.txt

[<[e-mail]>]

Med,
Thanks for creating these new pieces of text, I think they're helpful and it's looking good!

Comments:
Section 3.3
<<User data is unambiguously distinguished from Convert TLVs by a Transport Converter owing to the Total Length field in the Convert messages>>
Better:
User data is unambiguously distinguished from Convert TLVs by a Transport Converter by the Convert Fixed Header (Figure 12) in the Convert messages

In Section 3.3, I think you should move the text about MPTCP out of S3.3 (into S3.4, maybe with some renumbering of S3.4 & 3.5 to make a section about mptcp)
[this is the text "Note that for the Multipath TCP case..." to the Figure 8 caption and the bullet "In reference to Figure 8"]
Reason: handle the general case first, then the MPTCP variant. 

<< Note that for the Multipath TCP case, the Transport Converter identifies an MPTCP connection by means, e.g., of the token assigned to the MPTCP connection.>>
If I get it right, this is nothing to do with the token defined in MPTCP, but is simply an identifier internal to the Converter (to help it keep together entries for the same Client). Ie this token is not seen on the wire. Please could you re-phrase the para and the definition of "token" in the Figure 8 caption. 

Section 4.1
In the Figure 12 caption, I suggest deleting "-Sized" (so: "Figure 12: The Fixed Header of the Convert Protocol" or even "Figure 12: The Convert Fixed Header")

Section D.2
Appendix D.1 has a final paragraph which doesn't appear at the end of D.2 (<<The Transport Converter must be on the forwarding path of incoming traffic.>>)
I assume the same text is true for the IPv4 address sharing model. I suggest adding a comment at the end of D.2 that the same considerations apply (or repeating the paragraph, possibly with "IP address" changed to "IP address prefix")
I also suggest changing the title "IPv4 Address Sharing" to "Address Sharing"

Best wishes,
phil


-----Original Message-----
From: [e-mail] [mailto:[e-mail]] 
Sent: 04 October 2019 16:20
To: Eardley,PL,Philip,TUD1 R <[e-mail]>; Scharf, Michael ([e-mail]) <[e-mail]>
Cc: [e-mail]
Subject: RE: [tcpm] I-D Action: draft-ietf-tcpm-converters-12.txt

Hi Phil, Michael, 

This version implements the suggestions discussed so far: add a new section to discuss data processing once a state is created + appendix to discuss address sharing/preservation modes. 

I think this version solves the concerns raised by Phil. 

Looking forward to advance the document. 

Cheers,
Med

> -----Message d'origine-----
> De : tcpm [mailto:[e-mail]] De la part de internet- 
> [e-mail] Envoyé : vendredi 4 octobre 2019 17:16 À : 
> [e-mail] Cc : [e-mail] Objet : [tcpm] I-D Action: 
> draft-ietf-tcpm-converters-12.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the TCP Maintenance and Minor Extensions 
> WG of the IETF.
> 
>         Title           : 0-RTT TCP Convert Protocol
>         Authors         : Olivier Bonaventure
>                           Mohamed Boucadair
>                           Sri Gundavelli
>                           SungHoon Seo
>                           Benjamin Hesmans
> 	Filename        : draft-ietf-tcpm-converters-12.txt
> 	Pages           : 52
> 	Date            : 2019-10-04
> 
> Abstract:
>    This document specifies an application proxy, called Transport
>    Converter, to assist the deployment of TCP extensions such as
>    Multipath TCP.  This proxy is designed to avoid inducing extra delay
>    when involved in a network-assisted connection (that is, 0-RTT).
> 
>    This specification assumes an explicit model, where the proxy is
>    explicitly configured on hosts.
> 
>    -- Editorial Note (To be removed by RFC Editor)
> 
>    Please update these statements with the RFC number to be assigned to
>    this document: [This-RFC]
> 
>    Please update TBA statements with the port number to be assigned to
>    the 0-RTT TCP Convert Protocol.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tcpm-converters/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-tcpm-converters-12
> https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-converters-12
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-tcpm-converters-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/
> 
> _______________________________________________
> tcpm mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/tcpm