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

Lars Eggert <lars@eggert.org> Thu, 15 October 2020 16:37 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 830783A08FF for <quic@ietfa.amsl.com>; Thu, 15 Oct 2020 09:37:03 -0700 (PDT)
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 JSbz9vSK_DyV for <quic@ietfa.amsl.com>; Thu, 15 Oct 2020 09:37:02 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (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 C81C83A08EB for <quic@ietf.org>; Thu, 15 Oct 2020 09:37:01 -0700 (PDT)
Received: from [IPv6:2a00:ac00:4000:400:688b:8d7c:4372:a795] (unknown [IPv6:2a00:ac00:4000:400:688b:8d7c:4372:a795]) (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 EC77A613A61; Thu, 15 Oct 2020 19:36:49 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1602779810; bh=k89hXleuQbApXPH/E4v00hSeEVQEz/PPQC0NqTj3J8k=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=i2E8RLqRc4hJOYsQk0D8hOJze4AyEB7v0rA2gorLoxKxYRfKz+vyZHb9IJsYlA5OO oCKVCj4KvHXPTp3vAFLC42OWciO12ZdEJcPJkvAmNYW5qBVXYX4XSE7VKjf2IDQgJo DayHH881kbqBGUEpYrVae1o17fPuBOvbS3teU9F8=
From: Lars Eggert <lars@eggert.org>
Message-Id: <3E816D76-3BE3-4E5F-8ADC-C3A27AEAE58A@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_A3158C84-8486-4973-8329-FF9277B06970"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: Interim meeting request for slides on multipath QUIC use cases and requirements
Date: Thu, 15 Oct 2020 19:36:47 +0300
In-Reply-To: <b4f9a623-d5e1-f3c9-3601-d70790c963fc@inf.ethz.ch>
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, QUIC WG <quic@ietf.org>, Perrig Adrian <adrian.perrig@inf.ethz.ch>
To: Cyrill Krähenbühl <cyrill.kraehenbuehl@inf.ethz.ch>
References: <CALGR9oaJ4Zi=gZd4hrxFyR2TgL40c43pnTDk9=7GtN3Oz-ezdA@mail.gmail.com> <b4f9a623-d5e1-f3c9-3601-d70790c963fc@inf.ethz.ch>
X-MailScanner-ID: EC77A613A61.A4DAE
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/3QwtIUTjn_LEktaDe6KjkfCH0TI>
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: Thu, 15 Oct 2020 16:37:04 -0000

Hi,

On 2020-10-15, at 19:17, Cyrill Krähenbühl <cyrill.kraehenbuehl@inf.ethz.ch> wrote:
> In this context, we see two topics of potential interest. First, multipath scheduling, which has a large impact on the performance of a multipath transport protocol, becomes challenging since we might not be able to continuously probe 10+ (or even 100+) paths to infer which paths to send traffic on.
> 
> Second, the SCION architecture can offer additional information for paths, for instance AS-level information, lower bound on end-to-end path latency, expected bandwidth, etc. An interesting challenge is how to expose this path information to applications or transport protocols, so that path optimization is possible for instance for different QUIC streams.
...
> If the working group is interested and this use case has not already been discussed in the group, I would be happy to give a short introduction in the interim meeting.

thanks for the offer!

There are all kinds of interesting research questions related to multipath in general and for QUIC in particular, including the ones you outline above.

The reason we're scheduling the interim is to help us decide if the QUIC working group should start any standards activity in the multipath space, and more concretely, what the desired (= currently missing) functionality is that will need standardization. A key focus of interest are the large deployments of IETF QUIC that are currently being planned or are already underway. I'm not sure to what degree a presentation on research challenges would inform that decision?

Thanks,
Lars