Re: [tcpm] WGLC for draft-ietf-tcpm-converters-08

[<[e-mail]>]

Med,
Thanks, just following up a couple of points.
> 
> S4.1 title
> "fixed header" - is "fixed" needed?

[Med] It is fixed because it is present in all convert messages. Do you prefer "common" ?

[phil] I'd prefer if you explicitly stated that all Convert messages have this header. 
In fact, I think you could start Section 4 with text to capture the key points:
"This section describes the messages that are exchanged between a Client and a Transport Converter. All Convert protocol messages MUST be sent on a SYN, ACK or SYN-ACK, to port [tba]. All Convert protocol messages MUST be sent as the first bytes of the bytestream and MUST use the header shown in Figure 9 and described in Section 4.1, followed by the message itself using the generic TLV format shown in Figure 10 and described in Section 4.2. "

> 
> " Transport Converter SHOULD include in this
>    list the TCP options that it accepts from Clients and that it
>    includes the SYN packets that it sends to initiate connections."
> I couldn't parse the second part of the sentence ("and that it...")
> 

[Med] Changed to:

" A Transport Converter SHOULD include in
this list the TCP options that it accepts from Clients; these options are 
included by the Transport Converter in the SYN packets that it sends to initiate connections."

Better? 

[phil] Yes. Instead of "are included" you could say MUST /SHOULD /MAY


> Section 6
> This section actually only discusses one type of middlebox (removes SYN).
> Can the discussion be widened slightly

[Med] This section only focuses on SYN/SYN-ACK because these are used by the Convert protocol.

Do you have in mind a particular case (specific to the Convert protocol) that may be problematic?

[phil] the section only discusses removal of SYN, and not other ways a middlebox could interfere with the SYN/ACK. 

Thanks
phil