Preparing for discussion on what to do about the multipath extension milestone (was: Re: IETF Last Call for QUIC)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Sun, 27 September 2020 16:08 UTC

Return-Path: <spencerdawkins.ietf@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 555183A0FF5 for <quic@ietfa.amsl.com>; Sun, 27 Sep 2020 09:08:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 YwtRw-7Kv-jT for <quic@ietfa.amsl.com>; Sun, 27 Sep 2020 09:07:58 -0700 (PDT)
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 1C2833A1074 for <quic@ietf.org>; Sun, 27 Sep 2020 09:07:54 -0700 (PDT)
Received: by mail-yb1-xb2a.google.com with SMTP id 67so5992575ybt.6 for <quic@ietf.org>; Sun, 27 Sep 2020 09:07:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=DIci5qu/XRjvlgwtKTRQ5B3AJqQX8NI+O0QJl+qn2qA=; b=IQzhgJhpL7NLb4Bo8j4lGdyjqWKJAL+ybaVzQczuXA0R4CgqzhuBMKzaLEig8Yq0Id x+4Ub9ytFh8QBFFZ3rVua4Su9DrcIvGYf73yyREl7RDxCCGe9vaZSTxafwTSNEt8meHX V0jzR7tc0ESjOA4hr2Yh9Y9IBvIMsd4erQHPWfSAgwhmdumEerMUgk4pjx1jNbsmKrm7 v6oQckPWtAEdnbG4VABP7fjl1FYPfhdlIu/Vni228Jrrmjz4x+hAmZWnyA0mFHeg3i7T yq2R4uy6h4rBXUBfy8B6X5Bp1icUojNem8XNT2qAV3uBqSKIiB4AbkxYbSdNuu9oHsUF X6Bg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=DIci5qu/XRjvlgwtKTRQ5B3AJqQX8NI+O0QJl+qn2qA=; b=eDq2/OMnBZqFL2SdgGge8nHA4kb25uzK+ywp8/DWWUGs04cSZuQlSaQgw9pMRFTTgx ZN0+BCvPeri+gnntV4QVvSq+8TPfKYBYmekCC6J3HdGkzp0GxpHVpWWF7HkzU1JZZDws s9wXW61TzrHpFsr7i7/E6R1BiAeNfWzJnQ78ej8nRR5Vb4xDNpTlSyA+dKqYb5ESGSiO rKqRKew9Jhpfd/fbY5shqXzzAMG3oD1RJ/2J5kC/QMhO/zNNbubu2uoaXroepw6qtkuR tHDPqJfwmJPXZOLxhLlZkqwpQgGobEKJC8FY0W/K5ZwK7TSk+cWCs/j1IDlvNiDHixJK bOjQ==
X-Gm-Message-State: AOAM530WrQF6BFnnXv8NTSFraKpH/I9yQkWwTtV+NxHDrpnG8fwfDQu5 ic9nLWVhUpLSj1t4CjGaBLCFfWxuGT0Cwqa7y2U12kus
X-Google-Smtp-Source: ABdhPJyJAejMt7CjoOvhWaMtoX8f4hzhhvEOzkNuryM1XyBv2D60U842L3S1LeGcjZ8wdef/nUiJ9sT7SqiCRH+We0U=
X-Received: by 2002:a25:3752:: with SMTP id e79mr9940052yba.154.1601222873100; Sun, 27 Sep 2020 09:07:53 -0700 (PDT)
MIME-Version: 1.0
References: <F0A5E38D-4117-4729-BFF8-72D97CAA9908@eggert.org>
In-Reply-To: <F0A5E38D-4117-4729-BFF8-72D97CAA9908@eggert.org>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sun, 27 Sep 2020 11:07:27 -0500
Message-ID: <CAKKJt-e=+XLZhNWqaG9YSLTRqyQRvDc-dagUSkFwHOByFwZ++Q@mail.gmail.com>
Subject: Preparing for discussion on what to do about the multipath extension milestone (was: Re: IETF Last Call for QUIC)
To: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008eb62c05b04dc094"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/cjjI9-uP6WXVI8p28pcTcq8vS-E>
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: Sun, 27 Sep 2020 16:08:02 -0000

Dear QUIC working group,

On Fri, Sep 25, 2020 at 5:00 AM Lars Eggert <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 :-).

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.

- 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).

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.

Thanks!

Spencer