Re: Interim meeting request for slides on multipath QUIC use cases and requirements

Martin Duke <martin.h.duke@gmail.com> Wed, 14 October 2020 15:48 UTC

Return-Path: <martin.h.duke@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 EDF1B3A0F4F for <quic@ietfa.amsl.com>; Wed, 14 Oct 2020 08:48:46 -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 Gdslbb2FXiDi for <quic@ietfa.amsl.com>; Wed, 14 Oct 2020 08:48:45 -0700 (PDT)
Received: from mail-il1-x12a.google.com (mail-il1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (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 845DD3A0F4C for <quic@ietf.org>; Wed, 14 Oct 2020 08:48:45 -0700 (PDT)
Received: by mail-il1-x12a.google.com with SMTP id r10so5704689ilm.11 for <quic@ietf.org>; Wed, 14 Oct 2020 08:48:45 -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=kEPSPFO+7xBhgxrE1je9ud1OHBtJQRxi6pa7lsA6JXI=; b=smj8PoSJtUDi8xwcFwmFKWN9sIUGAbsjYbHF+44zU3HYjPaJIE7qsCbR8W89ZHQlyJ ihLPYo4U5mnA5YfYqCx8Hh2O9igLEgmon0JFe3FtAcKw+3O94FSh1ZbhUOumSiozqLBr YmYDN1QQRmFpT+WIieFvzl65nofL5BNTjkaASO+S6FHzo/VAi4v2rwnfFZ6bCseUn7q1 k1mTWa6Tl7KYoYqjBeP3++D4vUeukOMv3lmlafYMTaNZzLuZb0kXfEkJV9+VK04SEJnM lotQ8GeNPqRTOhwHa4CBsaY7kyEXUNf/56/HdI/YSh6LEcA36P5RCLzvENh4irPnN7CR xNVg==
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=kEPSPFO+7xBhgxrE1je9ud1OHBtJQRxi6pa7lsA6JXI=; b=Ivcr0YQznU0sVgo/URrwvmBRzJj7vl1AjElDBdURmN5YhOcF8ty7RSOBvFBH0EMGyX jR27JtzordZ7wbKlihwk8gXywyyY8iSWmqNqxBdA0fpJ9NZ3Gm7OD8URTNQ5O5f/WkD4 /sXWNwK3N1571LTiUE+M/AmwdZLbonS0oAxXDtfxr7DoUfJ7Ml6QYakn00G6jhbU0Lws oSXYwvHwgieeCmn4HOQMjIewmupQ8rHRE6M7MxjyOkhR1Ti6K18dchPvmOFLZYtlMBeY 6iNwvvGUNpSw6u4auvXeJ1nLbZiLmK9JbTmNSiq1a91DGCzt7+C6+NCk+JzCh5X7CMTb NCsw==
X-Gm-Message-State: AOAM532Xyv8g2XpabhAyxkaq+4wqpKFMBj8tPHE85TIiAj7axNisQvSR 6ot4r+iEY5soDc5I0/k2rK9o/YE8cg1b9ZGglUyOqPyBTnI=
X-Google-Smtp-Source: ABdhPJwgGYyOLq1R7VI44f1dzoasy8FZZxlGJThVOWnGfcYcumH2SBA7eqLWco+x9kFVn+SFwqNHMDL395xTu06/mBA=
X-Received: by 2002:a92:d808:: with SMTP id y8mr4440980ilm.249.1602690524656; Wed, 14 Oct 2020 08:48:44 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9oaJ4Zi=gZd4hrxFyR2TgL40c43pnTDk9=7GtN3Oz-ezdA@mail.gmail.com> <CAKKJt-f72oH5ng44U-QjA6jRHtamsTQfdm8a69zn14AneafUXg@mail.gmail.com> <B35AD30B-3184-4ADE-B2EC-877965E4DAB6@eggert.org> <331dca8f-3f95-e9f2-c10e-ab8199d43b36@erg.abdn.ac.uk>
In-Reply-To: <331dca8f-3f95-e9f2-c10e-ab8199d43b36@erg.abdn.ac.uk>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Wed, 14 Oct 2020 08:48:33 -0700
Message-ID: <CAM4esxThPUCfXY8mDOwLM7EKpfEUPwhu7WWSNDGwxiYo8ih96w@mail.gmail.com>
Subject: Re: Interim meeting request for slides on multipath QUIC use cases and requirements
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Cc: Lars Eggert <lars@eggert.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>, Lucas Pardue <lucaspardue.24.7@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000006838a105b1a3772c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/o2DNFcFEmc0pjCNUpOD39CPv4h8>
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: Wed, 14 Oct 2020 15:48:47 -0000

Gorry, that is my understanding as well. If we don't have failover, we've
messed up in some way.

On Wed, Oct 14, 2020 at 3:23 AM Gorry Fairhurst <gorry@erg.abdn.ac.uk>
wrote:

> Maybe it's just me - but I would be super-interesting in checking that I
> really understand what the migration feature of QUIC would give us if
> there was a change in connectivity.
>
> Am I correct, in seeing QUIC as already having (or nearly having) a path
> failover method - similar to SCTP failover? ... where multiple paths are
> kept alive, but only one path is used at a time for data. Can some
> problems be solved by a simple failover method?
>
> To me multipath, is where performance optimisation questions are solved
> - such as how to have simultaneous use of capacity across multiple paths
> (some people call this bonding), or scheduling across paths to
> minimising the delay, or one of many other metrics.
>
> Just a thought on what might be useful to me to see in some slides ....
> perhaps before we delive into the details of policies and scheduling.
>
> Gorry
>
>
> On 14/10/2020 10:45, Lars Eggert wrote:
> > Hi,
> >
> > On 2020-10-13, at 18:35, Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
> >> I'd like to do one or two slides, five minutes max, on the multipath
> modes that are under discussion in 3GPP SA2, from my perspective as an
> individual.
> > I think that would be helpful, and so far there are no other offers to
> summarize those use case requirements.
> >
> >> When do you need the slides?
> > Monday at the latest?
> >
> > Thanks,
> > Lars
>
>
>