Re: Next steps for Multipath QUIC

Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com> Fri, 20 November 2020 09:40 UTC

Return-Path: <mikkelfj@gmail.com>
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 3C1673A11E0 for <quic@ietfa.amsl.com>; Fri, 20 Nov 2020 01:40:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ocddPIOqqxIC for <quic@ietfa.amsl.com>; Fri, 20 Nov 2020 01:40:01 -0800 (PST)
Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (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 E06D93A1198 for <quic@ietf.org>; Fri, 20 Nov 2020 01:40:00 -0800 (PST)
Received: by mail-yb1-xb2a.google.com with SMTP id o144so8007569ybg.7 for <quic@ietf.org>; Fri, 20 Nov 2020 01:40:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to; bh=D/CskksYxh5RvIOeme6NpEvTmxYQ1RFHzv1lk1S5Z9o=; b=cHFRJyPT9OoDt+xaV15i8RzMrHlbhNCPmiz6bfdz2EF8L3n37Bzq5P8VFjq5vFSYEP wtrsvKYbRiqSaDFYzosJFo3fg02DAMriQJjsrZvic3R/q1pABJ3g66WwpiuCX0ImW7zv o22hV8PlK9ycQSje1jo4y7B+msoh2Hg1IpfB0ij9nCb5cq29BUplF9SXhnhS5QoLJFxq ZLP4gmKbqFXdRKo4DVmb8sPhAoI4KehDg/0c4KIJ5onY1WFg/k08/VE15cEOenm51a85 aiJfsyn9Zxzw6b569GGie06EdcZuHSzTY3I8uX4EOEeZvGWDi0g7U1+SPrndwDw13Wzv Ob3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to; bh=D/CskksYxh5RvIOeme6NpEvTmxYQ1RFHzv1lk1S5Z9o=; b=TN8SJQfaRzQ6Sdpv7j8GZYpTTVGa7SdYpP1dNAqW7s7m03rSukFiBapnvaz738gDRW W6L5fbvtahHPZkovRow7uixrLZ+YAShsqGC7YhzsXlcuPBE2wZgkJfNbe88Y+Ffe6zJf 7qxs5H7gmVEVCx5ioNs3eaT8P870QS57Dag6eIvKAuMtgydLOhICDJAPC1nnP9CSHR73 mwSwfBwtVGShS1w8cg47Q+2PYPa3wJEMizboJiig4tn9S01+bzAf28EfXY02RgAN9ZGQ PzwRcaFTt2r9M+UVYPDOQzJ2iCCqFSSIzL5auxAG8fPa0XYXFZcLT4sTMcDFKoAmv0Ba xAJg==
X-Gm-Message-State: AOAM531B2y7oFd6KeAKQRGREeuoNgyLKHvM2DCPFL4LAdwnlh0ooGaO1 McnKM5M7+eIyyGSg7OX/8Fcj+PngHDWLcivdbjIydnlpZ98=
X-Google-Smtp-Source: ABdhPJyPr3MLnDCEcXHDwBfNeLEzpSxuCmElzhldoAIJVOt+bWDrhbdz7VvKZwJ71NXWqZ5me4wqp7zItZ33oSK0auI=
X-Received: by 2002:a25:c60a:: with SMTP id k10mr24050744ybf.113.1605865199974; Fri, 20 Nov 2020 01:39:59 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 20 Nov 2020 01:39:59 -0800
From: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
In-Reply-To: <F2EB47B8-EC64-4792-B38A-D0346714DDAD@eggert.org>
References: <F2EB47B8-EC64-4792-B38A-D0346714DDAD@eggert.org>
MIME-Version: 1.0
Date: Fri, 20 Nov 2020 01:39:59 -0800
Message-ID: <CAN1APddGC6fvhDNu_p0LPnYVMMb6Y_Quxg-PqrhHoDYsXSFHuA@mail.gmail.com>
Subject: Re: Next steps for Multipath QUIC
To: Lars Eggert <lars@eggert.org>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cd3d1c05b486a0ce"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-iRiOALq3upBOZlFAyKwTSUnAS4>
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:40:02 -0000

I believe it is good to have experimental results as extensions, or
otherwise, fleshing out the various concepts before committing to anything.

One aspect that isn’t clear to me is the symmetri of multipath, and also
for migration post V1.
I for one would like to see more symmetri for data center deployments, at
least for multipath.

Mikkel


On 20 November 2020 at 10.30.39, Lars Eggert (lars@eggert.org) wrote:

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