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

[<[e-mail]>]

Hi Phil, 

Great! Thanks. 

I submitted a new version which fixes the nits + rearranged text.  

Cheers,
Med

> -----Message d'origine-----
> De : [e-mail] [mailto:[e-mail]]
> Envoyé : mardi 22 octobre 2019 12:26
> À : BOUCADAIR Mohamed TGI/OLN; [e-mail]
> Cc : [e-mail]
> Objet : RE: [tcpm] I-D Action: draft-ietf-tcpm-converters-12.txt
> 
> Tiny follow-ups below.
> 
> Thanks for your efforts on this, I think we're done
> phil
> 
> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]]
> Sent: 21 October 2019 15:00
> To: Eardley,PL,Philip,TUD1 R <[e-mail]>; Michael.Scharf@hs-
> esslingen.de
> Cc: [e-mail]
> Subject: RE: [tcpm] I-D Action: draft-ietf-tcpm-converters-12.txt
> 
> Hi Phil,
> 
> Thank you for double checking.
> 
> Please see inline.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : [e-mail] [mailto:[e-mail]] Envoyé :
> > lundi 21 octobre 2019 15:10 À : BOUCADAIR Mohamed TGI/OLN;
> > [e-mail] Cc : [e-mail] Objet : RE: [tcpm]
> > I-D Action: draft-ietf-tcpm-converters-12.txt
> >
> 
> [Med] No problem to rearrange the text if you think that is better.
> 
> [phil] thanks, yes I think that would definitely be better.
> 
> >
> 
> [Med] ", e.g., of the token assigned to the MPTCP connection." refers to
> the token defined in MPTCP:
> 
>    Token:  A locally unique identifier given to a multipath connection
>       by a host.  May also be referred to as a "Connection ID".
> 
> Any issue with that?
> 
> [phil]
> Thanks for the pointer.
> 
> I wonder if the following would be better (instead of the "Note that for
> the Multipath TCP case..." paragraph above Figure 8). I'll leave it to you
> to decide.
> 
> Note that for the Multipath TCP (MPTCP) case, a connection between the
> Client and Transport Converter has multiple subflows (each with a different
> IP address and/or port). In the MPTCP specification [ref], at each host an
> MPTCP connection is identified by a token (a one-way hash of the MPTCP
> key). An implementation example of a MPTCP transport session entry
> maintained by a Transport Converter is shown in Figure 7. The entry needs
> to be updated whenever subflows are added to, or deleted from, the MPTCP
> connection. As a reminder, the Convert TLVs are only exchanged during the
> establishment of the initial subflow.
> 
> 
> > 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.>>)
> 
> [Med] D2.2 has already the following text:
> 
>    Adequate forwarding policies are enforced so that traffic destined to
>    an address of such pool is intercepted by the appropriate Transport
>    Converter.
> 
> [phil] I missed that, thanks.
> In the sentence after the one you quote
> << Unlike Appendix D.1, the Transport Converter drops
>    incoming packets which do match an active transport session entry.>>
> 
> I assume it should be: "which do not match"