Re: Preparing for discussion on what to do about the multipath extension milestone

Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be> Tue, 29 September 2020 20:11 UTC

Return-Path: <olivier.bonaventure@uclouvain.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38D543A1134 for <quic@ietfa.amsl.com>; Tue, 29 Sep 2020 13:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.313
X-Spam-Level:
X-Spam-Status: No, score=-2.313 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.213, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=uclouvain.be
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 TgucAPSV9cDA for <quic@ietfa.amsl.com>; Tue, 29 Sep 2020 13:11:45 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70098.outbound.protection.outlook.com [40.107.7.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 082343A097C for <quic@ietf.org>; Tue, 29 Sep 2020 13:11:41 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=XStDAkcI2XBd7oAuTHrAJatiAjLlZb3ODTn4vNIn+pDI5zhl3QGHrPsqUfwVVbg25IN2WpXC8H3Ay7L3L/5SrRaV40c1RFqebiufkgotNtAb4PJwkv/3NnkhZd0As3oOLfpvr9h32iouosrZXKxk+NnUNr9ANsYw+CgUBOa1RY5hRPGEKTvVBwy78ZhVqcARHO8t1d4yg1JbzW2fYjphalIf9E+DWDaKHIYyHXnANF9BhvDrn3ZZLaNfWKqtC4YSsawD0I44mmQxegGK9eckTcBBhocvmihZJwaiSM30XqEBD3LndoU0otvSwGwKrrqaAYm1iCdAUNwXEJ+MueRFgA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Lex0RJa13aNDM0gVOy8GotKFUvS/HG5Ba8K2sgxdoKA=; b=iXvT+TY0Y0QatupBhnRcyrAPjLgNkWZMPHOh3XQ21Z16G2pId8spykJEjpvsPtPX2/dITGdif/Ee7iSRfQHNGofxYF31OGxf3xcmO2hp8804aCgNyA1HxCnldrg8+lTVYh4zUwerVwMZbvruhIe1307o7W46mBLO+pIVkfdtaa0zbflc9X8gJmKyq5a71+2IrcEqabR9ab36kcmyMrsu59+dBy1D4gDcmhfl0Le1nNX/8Tl0Uz2pv8Hzyw6AviuCebZkFrxSmhQ2/mT2TI3NHN46iH6wJvOXyM3e+DcMhj3PK7KEjzuvW00Qcx3rJuE/i0xD7LVUCOE8bKiNT4fp5Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=uclouvain.be; dmarc=pass action=none header.from=uclouvain.be; dkim=pass header.d=uclouvain.be; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uclouvain.be; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Lex0RJa13aNDM0gVOy8GotKFUvS/HG5Ba8K2sgxdoKA=; b=qv3F3xFlNTmrYKQXbXpOdVPbJsk9UyJILHr/+0El/irX3jW2uOTuvdUi+jGCFTw5Z6vRccRNVlGI1InJc0m1Z1Exj1MZV4RCohzBxixgZC9BP3QAnmXuHyLvkbuDJIRBZaslNHiC/soUZw0BhipkqWgrmBDgtJqQwxdM9NctI4g=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=uclouvain.be;
Received: from AM7PR03MB6642.eurprd03.prod.outlook.com (2603:10a6:20b:1bf::6) by AM6PR03MB5125.eurprd03.prod.outlook.com (2603:10a6:20b:83::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3412.24; Tue, 29 Sep 2020 20:11:38 +0000
Received: from AM7PR03MB6642.eurprd03.prod.outlook.com ([fe80::1cd6:a808:56a3:e868]) by AM7PR03MB6642.eurprd03.prod.outlook.com ([fe80::1cd6:a808:56a3:e868%6]) with mapi id 15.20.3412.029; Tue, 29 Sep 2020 20:11:38 +0000
Reply-To: Olivier.Bonaventure@uclouvain.be
Subject: Re: Preparing for discussion on what to do about the multipath extension milestone
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, QUIC WG <quic@ietf.org>
References: <F0A5E38D-4117-4729-BFF8-72D97CAA9908@eggert.org> <CAKKJt-e=+XLZhNWqaG9YSLTRqyQRvDc-dagUSkFwHOByFwZ++Q@mail.gmail.com>
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Message-ID: <78651438-2fce-ba67-4f44-4228bbc79a75@uclouvain.be>
Date: Tue, 29 Sep 2020 22:11:37 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.12.0
In-Reply-To: <CAKKJt-e=+XLZhNWqaG9YSLTRqyQRvDc-dagUSkFwHOByFwZ++Q@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr-classic
Content-Transfer-Encoding: 8bit
X-ClientProxiedBy: AM3PR05CA0114.eurprd05.prod.outlook.com (2603:10a6:207:2::16) To AM7PR03MB6642.eurprd03.prod.outlook.com (2603:10a6:20b:1bf::6)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from mbpobo-2.local (2a02:2788:484:585:c51f:12fb:f270:5ef4) by AM3PR05CA0114.eurprd05.prod.outlook.com (2603:10a6:207:2::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3412.22 via Frontend Transport; Tue, 29 Sep 2020 20:11:38 +0000
X-Originating-IP: [2a02:2788:484:585:c51f:12fb:f270:5ef4]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 0642ffd1-ad54-4077-ca94-08d864b3df9c
X-MS-TrafficTypeDiagnostic: AM6PR03MB5125:
X-Microsoft-Antispam-PRVS: <AM6PR03MB5125FF578996E326CAEB398286320@AM6PR03MB5125.eurprd03.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8273;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: kPEoIpCWwkf8Mrmo3/O+tMmhxYgjX/Q8/6jP6I9jSsKP9+87ih7KvkUhzLaNzG8mjM9rbAPlAiFZugZDYRdcg3D07VKWU45YF5dNHaTKPwN7bXyC0FeTVv3xAd3GtVhABofuKNgfvUyGyFMLGO3Zk9KdZ+V0XwtgRBBrOea8t9UGcGxG3i0BHZGmVbc8MNc3ZebiqFl1SfBB7XSqtA1Fj1ouMqWZpAfFgXdqcbTDgcNMJwsYX874wNXdWVoy+tYeAWbBx62dHU/TAZQNLqSHDZjXYiMi03fvj+kqpw4bVRCGbbb2KexbbL89+/S+i1C/xowerKijMGkQpG6joAWy8pB2uX0lcXHGIwF8mg/PLalQVlVdzL6Q3JhlIcHm4nPXKHL7vnu5JckjkAr7zjsEMJeiLk/48lAU+jtpYPjAPZYfzFHsKYkGZ1PXJfVRjz2k
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM7PR03MB6642.eurprd03.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(346002)(39860400002)(376002)(366004)(396003)(136003)(31686004)(2906002)(186003)(36756003)(316002)(786003)(110136005)(31696002)(8936002)(16526019)(6506007)(2616005)(6486002)(8676002)(52116002)(5660300002)(3450700001)(83380400001)(66556008)(86362001)(6512007)(66946007)(66476007)(478600001)(43740500002); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: ymGvIC8UZznYGEbJcp+NjeWqbRG8RvPvADAPMBYBC9VF7HIqlm+JNid8Ak/0AheuM+jjKEer2boERnV1lxpbP5B9EBqIOR55oGcudKy4ZhOWf0qb1qRPZ8QytcjHPnw9iYfock3gGNMhYaHXPZNIw4ZjRYXDGp9sjuMoG1YGW2PZGdpsgdcU6BHgfID/vT2oHgm1KKeXoriQRW0HQSVDU5dwWfkBBK0uTGZg30RkjKd9tm49js+vl1IEPKlJieTebWACbcb29DQaGFn8/a02YzAlH2TrWWF/OyjOTPXnXlCxYtVeF+9fcJaiy4tbdDJPqLlyXhCc83hnhwAmNQ+T04Bvtk84q9G60vUDsqMnek9AGHki7KoBK++DLhR4VIIljrdHgryeorVCHGp1GYla1+u8CI3B0ct/e3WbDjsAQJ9OgBpswlezTTR1wx49e8xw4XqwcwSfWDcoT/rbyLKo0XikapXcfDxLEh34g5S9lViSAuthcjwnSmLKKe5JA98ZoCTDQ9MfVF/b3o1Quo3lbeb3K77OOoUKI8fFwC5YWtpBuVoCw306+eqMMIfzNfv68nHknJwbustqTk3nbngaprrxJV9npmROaft0YIGIL7Lh/BFwpmmxnvZMUCekakkA3EusKQeXWOObz4VLsYjAm8MLwgMIbtwdfuvyn+a/0uLDFr0e27titVnIknDAwYLNBPBNgRntmirEaC3Xfm9TMg==
X-OriginatorOrg: uclouvain.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 0642ffd1-ad54-4077-ca94-08d864b3df9c
X-MS-Exchange-CrossTenant-AuthSource: AM7PR03MB6642.eurprd03.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 29 Sep 2020 20:11:38.7837 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 7ab090d4-fa2e-4ecf-bc7c-4127b4d582ec
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: UHkGJA9TJWZGNRcC972UEUAHPnTgXjSl6SLXseBwDDwIVlp+SKxwDqthFQalj2Va7bZT55YEOR/2UtcHo1ImzF+IDBTjfLVvSIKEXqKB4OUaBmU7Y6TBnDD4/0/Fks56
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR03MB5125
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/pQ7ufMCG8tfqKUlz_-_yqFm-gYA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Sep 2020 20:11:47 -0000

Spencer,
> 
> On Fri, Sep 25, 2020 at 5:00 AM Lars Eggert <lars@eggert.org 
> <mailto:lars@eggert.org>> wrote:
> 
>     In parallel to progressing the "base drafts" towards RFC
>     publications, the WG should now also begin to pick up the pace on
>     our other adopted work items (ops drafts, extensions, etc.)
> 
>     One important other discussion item is what to do about the
>     multipath extension milestone, which some have suggested should be
>     dropped, while others still show interest to pursue it.
> 
> 
> So, I'd like to understand the suggestion to drop this milestone, before 
> I start trying to discuss that suggestion :-).

I'd like to understand this as well.
> 
> In conversations with individual folk, I've heard these concerns about 
> QUIC multipath:
> 
> - Whether it will be possible to evaluate multipath performance at 
> scale, both for evaluating proposals and testing implementations.

We already have plenty of experience with MPTCP with several large 
deployments, including :

- MPTCP on all iPhones since 2013 with a growing number of applications
- MPTCP on Android smartphones in South Korea for WiFi/4G offload
- MPTCP in hybrid access networks that are used by different network 
operators to combine xDSL and LTE

Multipath extensions to QUIC would be applicable in these different use 
cases

> - The complexity involved in making decisions dynamically about which 
> path to send a given packet on (which could be a research topic, given 
> certain constraints and goals).

The packet scheduling problem is a much simpler problem in multipath 
transport protocol than congestion control. I would not consider this as 
a research topic given all the experience we have with MPTCP

> If I've misunderstood or misquoted, my apologies, of course. Please 
> correct me.
> 
> What other concerns do people have? I'd like to get all the objections 
> out at the beginning of the discussion.

Same for me


Olivier