IETF Logo Mail Archive

Next steps for Multipath QUIC

Lars Eggert <lars@eggert.org> Fri, 20 November 2020 09:30 UTC

Return-Path: <lars@eggert.org>
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 8D6A93A1B00 for <quic@ietfa.amsl.com>; Fri, 20 Nov 2020 01:30:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=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=eggert.org
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 Ki6EE6b3nIOu for <quic@ietfa.amsl.com>; Fri, 20 Nov 2020 01:30:21 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 BCE253A1383 for <quic@ietf.org>; Fri, 20 Nov 2020 01:30:21 -0800 (PST)
Received: from [IPv6:2a00:ac00:4000:400:b9ed:9d2d:94cd:1d3c] (unknown [IPv6:2a00:ac00:4000:400:b9ed:9d2d:94cd:1d3c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id A876D607C26 for <quic@ietf.org>; Fri, 20 Nov 2020 11:30:13 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1605864613; bh=pD8yu+vGsrr6hPS4eKJjE5sRTxB+QFlL3GbnNbArJyM=; h=From:Subject:Date:To; b=Gj3HjriDG2lsnQhRAi13XZ3vzVWA5FR1z7OEP+h2Z9EZkF03IsL4WaBzr0J44XOOf 6MJV8YI1H3NareZyE5YVtbtRNu8gUPo/fZZZ7BJrMSMSIlJGc25HXsud3gtMiArwyw qcWyETvzM0cbuoAVK0jMVamvNl7SGugGFwPdyszA=
From: Lars Eggert <lars@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_464F5758-A908-4ECE-96C4-7DF23F111F96"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Next steps for Multipath QUIC
Message-Id: <F2EB47B8-EC64-4792-B38A-D0346714DDAD@eggert.org>
Date: Fri, 20 Nov 2020 11:30:13 +0200
To: QUIC WG <quic@ietf.org>
X-MailScanner-ID: A876D607C26.A199B
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/rcPf7u9AHIGwNr6j0ZqrqFujVvk>
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: Fri, 20 Nov 2020 09:30:24 -0000

Hi,

Lucas and me got asked what we'd see as the next steps for multipath support for QUIC. Here's our current thinking:

The QUIC WG remains the default venue for continued open discussion of multipath experiments and results. The goal for this discussion is to help steer towards identifying whether a multipath design can emerge that

(1) addresses a number of the use cases discussed during the interim, or new use cases that are similarly motivated

(2) sees implementation and experimentation/deployment interest from a number of production stacks

(3) is (as much as possible) a minimally-scoped extension to QUIC v1 that cleanly integrates with its concepts and other adopted extensions

Until this has happened, we think it'd be premature to adopt one of the individual multipath designs that have been proposed as a WG work item.

We hope this provides some clarification.

Thanks,
Lars and Lucas

v2.23.0 | Report a Bug | By Email