Re: [multipathtcp] [tcpm] Working group acceptance of draft-bonaventure-mptcp-converters ?

[Yuchung Cheng <[e-mail]>]

On Mon, Dec 4, 2017 at 11:51 PM, Olivier Bonaventure <
[e-mail]> wrote:

> Yuchung,
>
>>
>>> My position is as follows:
>>>      - I don't think this doc should be adopted by the WG
>>>
>> I too do not support the adoption for similar reasons above, even
>> though I'd love to see more usage of TFO and MPTCP.
>>
>> TFO today is still facing bad middle-boxes issues and
>> demands extreme conservative heuristics to deploy (see last
>> presentation by Praveen in tcpm). Ultimately they need to be
>> applied by either the client or the proposed converters.
>>
>
> Recent measurements show indeed that TFO does not work everywhere.
> However, there is a very large fraction of all the deployed IP networks
> where TFO works perfectly. The documented problems with TFO affect clients
> willing to use TFO to reach any server over the Internet. This is not the
> deployment scenario for the converters. Converters will either be deployed
> in networks that have been configured to support TFO or where clients
> always pass through the same (pool of) converters. In this case, a client
> can easily verify whether the path towards its converter is safe for TFO.
> If not, the conversion service would be disabled on this client.

Oliviier / Med:

You are right that the converters can be engineered to work well on
TFO-friendly paths, and do not interfere other TFO deployment. I was only
pointing that the middle-box issues may restrict the 0-RTT benefit. I
should make this clear: my comments about TFO isn't the reason to reject
adoption. My rationale for the objection is similar to Joe's points.


>
>
>
> Olivier
>
> --
>
> ------------------------------
> DISCLAIMER.
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
> This message contains confidential information and is intended only for the
> individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system. If you are not the intended recipient
> you are notified that disclosing, copying, distributing or taking any
> action in reliance on the contents of this information is strictly
> prohibited.
>