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

Yuchung Cheng <ycheng@google.com> Tue, 05 December 2017 20:56 UTC

Return-Path: <ycheng@google.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C518128768 for <tcpm@ietfa.amsl.com>; Tue, 5 Dec 2017 12:56:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id exgO0ucYZfVw for <tcpm@ietfa.amsl.com>; Tue, 5 Dec 2017 12:56:38 -0800 (PST)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AA87128896 for <tcpm@ietf.org>; Tue, 5 Dec 2017 12:56:24 -0800 (PST)
Received: by mail-wm0-x22c.google.com with SMTP id y82so20488697wmg.1 for <tcpm@ietf.org>; Tue, 05 Dec 2017 12:56:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fpmmGnDocJS9VKY0eLlR0EN4v8cQBnNdnf6vj1uh/4Y=; b=mlAIifq3YQ4nDuh9PfaCFo8073eEF1sV/y2jumAq8CBns7j8xp++zPKJ5g/BTXG2Mv b6TOmd5pPdb1Uf8pRWzbZigTPQpsdAAp8d6U8wYBWR4cU+hB9rfq/CYTDcANX/lhvazB SrmRpus5YRhJNv6NFWy9q7hNWvVCjLCAdXoyMo4P0l2Kvaet1AALb47WIN4nrYvNMIP1 12GBed3y56/lyt477tuBDFRmmlPlfpDx+X/sJfjCRwXF/eTnNgl+RW3PeKLLV2jopSjY XWJxDY2YOzVeh8Gir6ryJ8tk54jsxcLv1fcmIrvzFTcdUGpXT/fVb7R7QJt32GzStmVI UgvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fpmmGnDocJS9VKY0eLlR0EN4v8cQBnNdnf6vj1uh/4Y=; b=J9c9/3O1qNNVFDnf6uMIUqz+wqNADGAOhm+LGBLRkWSK3YkNa4fZU3OqhU2Z9eHbvI Oi6zs7i6cCQeq7owDOq5Oc+zL+uEI6yPqdwsLaEwlU6juDbWzFByoVwyG2GzIRRDbg7v bJ189yTd1YHq2wUxdowZBfe+ltAfju/T2Ls2wHR4VtYZjbe59chLmS5wez7rjmN0oX+1 hjv5pLobQxZ1HImFEbNxcFUBl/OuyAxO3sHfesO9KwlYNf5ckH9gm5QdbJlGvOrjNFqJ wzE9tGBiZpxyRpoLNbzUg9Kg+DtvryOhk5JVYWYb9RIasSNotslbtbvnbmrfULRHrzb/ 77kQ==
X-Gm-Message-State: AKGB3mJ/+iTDjW4Nrm5Reme4DWR048eNDs3y0k8m5vqX7lRdaRCV0Hhg 5DXy8zdEQEa30bsRMezK5dM/mpjVwu6IVz/hDhvj5Q==
X-Google-Smtp-Source: AGs4zMbGx4ewPAzubKnhn0b0AyDWVqW1rOG6rtraxKGlfMBRLnr1ldDHIRHxxcq7nDGT9Sv+FPDAPWjCZr/pSDI+ZGE=
X-Received: by 10.28.150.20 with SMTP id y20mr10294203wmd.118.1512507382671; Tue, 05 Dec 2017 12:56:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.48.200 with HTTP; Tue, 5 Dec 2017 12:55:41 -0800 (PST)
In-Reply-To: <13548b17-2f8c-aef8-ea38-3065e1723488@tessares.net>
References: <AM5PR0701MB25475FD66E9553F2947DD22C933F0@AM5PR0701MB2547.eurprd07.prod.outlook.com> <AM5PR0701MB25470B276B0889170FC309FE933F0@AM5PR0701MB2547.eurprd07.prod.outlook.com> <1d4eda72-b822-c8b5-1207-d52ce2e3fe62@strayalpha.com> <CAK6E8=f0GG+Y45NqQ3zb_ChFWpWZ4mS5sgeQVPO7e0zmTbOyeA@mail.gmail.com> <13548b17-2f8c-aef8-ea38-3065e1723488@tessares.net>
From: Yuchung Cheng <ycheng@google.com>
Date: Tue, 05 Dec 2017 12:55:41 -0800
Message-ID: <CAK6E8=dNfYp1u3QvhtqSLn9CzVqTEj6FJ_Ms2WmjgzkQGWkacQ@mail.gmail.com>
To: Olivier Bonaventure <olivier.bonaventure@tessares.net>
Cc: Joe Touch <touch@strayalpha.com>, multipathtcp <multipathtcp@ietf.org>, "tcpm@ietf.org" <tcpm@ietf.org>
Content-Type: multipart/alternative; boundary="001a114b3c94444a51055f9e117e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/djbB-DFR0L06IBhA51mZCKRdd4E>
Subject: Re: [tcpm] [multipathtcp] Working group acceptance of draft-bonaventure-mptcp-converters ?
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Dec 2017 20:56:40 -0000

On Mon, Dec 4, 2017 at 11:51 PM, Olivier Bonaventure <
olivier.bonaventure@tessares.net> 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.
>