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

Lucas Pardue <lucaspardue.24.7@gmail.com> Fri, 02 October 2020 23:56 UTC

Return-Path: <lucaspardue.24.7@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 82D3E3A1760 for <quic@ietfa.amsl.com>; Fri, 2 Oct 2020 16:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 aYpstnZQE91r for <quic@ietfa.amsl.com>; Fri, 2 Oct 2020 16:56:33 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 281603A1757 for <quic@ietf.org>; Fri, 2 Oct 2020 16:56:33 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id l24so3489514edj.8 for <quic@ietf.org>; Fri, 02 Oct 2020 16:56:33 -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 :cc; bh=eaMLX636VTw5n0bJx0TlWJfZRcJDi1ov2fDVqmICSLs=; b=Ox8f5HnlVWTThgodF26anSDNrwRpmsgFroj1mIzjCT4Tj4Ep0T47gfRF900LUHGwA6 wUPu0HHYF67vLHzs45w3YHsvbHVrUMr4rrMxc9R1QsITO8lMDSHp+TAjGeGdcgUquOeT UX8icoe6LT9cATirpJOV5jeGw1mk9LRX54xW9VvBr3qf136MsCZesCxHiuEpo/PLw9i+ zR0qThOJje37LiRiE7xUo4c6eyyjRIRl6UsMq3xpAEZjJdrK2V4SgJNBJJAJcE5oq1Yt i6EUnfXjSEy9n3o9lfb6U1r73td9NZNL6ks3DFK9QvqZKAqMTdhVzuGbnA/mvKt9N9kH a5ew==
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:cc; bh=eaMLX636VTw5n0bJx0TlWJfZRcJDi1ov2fDVqmICSLs=; b=JFvPwxvapuRhBR9AzT1ComblbRueJ82c02eKbMtC2ODocR1FLNCuIQLoctH7PLXGzP onpYivBaJt1GaTYRSRmEgFPXQTuIgeMKTyW9BwglqEhGqkBsshGf4dsII4/wBOFMicoh viTSowBJOyFpFXVZ7rGvmHrXWRCErPJZ6juJ0FzHyF26Ar8u2fYpMyUl8z//z3e+CjCh ENGi/sFy9pXm39Dja/DzeyCrfUKMYesv8hAVq6zHwQsI/4BMHkw3u1g6tzm4jFG1DyvQ pgV5HFXbiZObipQI3G+iRK3EjeTAa42D6AUe8Z8uhVil4saMwfMGlGcXpvydwkZ+0k+4 7G/Q==
X-Gm-Message-State: AOAM531ymlX0g4uUi1ZVzmQ+XXiOeMe2LqkgNnAfILEKppA/goKJQgNf uDvXmGV4RyXArc7eI83aJVo7O9sOFQTYA2mkSeI=
X-Google-Smtp-Source: ABdhPJx9wThQJj39C6y46nyyRs7Q8xRtYX2hAZjL8opgkbeom/P0Qxza+NBEzC9U0z2k+1F2UOduYYu8XUP8jBImF3I=
X-Received: by 2002:a50:ce06:: with SMTP id y6mr5386042edi.273.1601682991725; Fri, 02 Oct 2020 16:56:31 -0700 (PDT)
MIME-Version: 1.0
References: <F0A5E38D-4117-4729-BFF8-72D97CAA9908@eggert.org> <CAKKJt-e=+XLZhNWqaG9YSLTRqyQRvDc-dagUSkFwHOByFwZ++Q@mail.gmail.com> <78651438-2fce-ba67-4f44-4228bbc79a75@uclouvain.be> <CADdTf+hOACZ1x=d8SV-aX0f3vc+_fyqTziRqi5gi+nJgppaz8A@mail.gmail.com> <CAKcm_gNF=0gwrPt=Mr1P=dF_-wmXfz-OJkavFSDe1qrXFeMa4A@mail.gmail.com> <20201002164854.GA2124@MacBook-Pro.local> <CADdTf+heu4DGT8PsF0yL1cknTCB0CiHJ_jBwXZ86ccxL6740qA@mail.gmail.com> <CALGR9ob39AhBQq5kt1tsBp6b3EHy8Aq-PkT_tSX3_hM-u9kYnQ@mail.gmail.com> <20201002232028.GG2124@MacBook-Pro.local>
In-Reply-To: <20201002232028.GG2124@MacBook-Pro.local>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Sat, 03 Oct 2020 00:56:22 +0100
Message-ID: <CALGR9oYUcTeBjNba6xAj0YLJwQc772u6K4H=VBKbG6cRaAjUUQ@mail.gmail.com>
Subject: Re: Preparing for discussion on what to do about the multipath extension milestone
To: Christoph Paasch <cpaasch@apple.com>
Cc: Matt Joras <matt.joras@gmail.com>, QUIC WG <quic@ietf.org>, Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c3bf4805b0b8e131"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qsvDZiwjpJLnjZgZrMqwjRHJS04>
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, 02 Oct 2020 23:56:36 -0000

Thanks Christoph, this is very useful!


On Sat, 3 Oct 2020, 00:20 Christoph Paasch, <cpaasch@apple.com> wrote:

> Hello,
>
> On 10/02/20 - 18:51, Lucas Pardue wrote:
> > +1 to the suggestion to discuss use cases, it is helpful for clarity. And
> > thanks Christoph for sharing some specific ones.
> >
> > For the use cases "Siri" and "Apple Music", since I'm not experienced
> with
> > multipath there's a gap in my understanding of how the proposal in
> > draft-deconinck-quic-multipath would be used to satisfy these use cases.
> > For instance, is the behaviour client-driven, server-driven or does it
> > require coordination?
>
> MPTCP has some limited coordination capabilities. Namely, it allows to
> signal to the peer if a "subflow" (in QUIC-language "uniflow") is using a
> backup-interface (through the backup-bit in the MP_JOIN establishment or
> the
> MP_PRIO-option - in case you want to look it up in the RFC).
>
> That signaling is very limited in MPTCP though. And this is exactly the
> place where MPQUIC can have a significant benefit over MPTCP as it can be
> more
> descriptive on the scheduling because it does not have limitations that the
> TCP-option space has.
>


So maybe I'm still missing it, but the MP-QUIC proposal seems to omit such
a MP_PRIO signal. So the gap I had was wondering if the client needed to
actively bring up or tear down uniflows in order to control the server
sending on a higher-cost cellular network (for however one measures cost).

Although I have drawn parallels with stream prioritization, there is a
difference. The server behaviour of stream prioritization cannot really do
much damage. The server behaviour for the multipath use case seems to be
higher stakes - getting it wrong could hurt end users.

I'm not saying that we have to state a scheduler now, or research one. But
I do wonder why the uniflows proposal does  not simply start with adopting
the same/similar signal that MPTCP already has.

Cheers
Lucas


>