IETF Logo Mail Archive

Re: Uploaded "Why Multipath QUIC?" for 2020-10 Interim

Lars Eggert <lars@eggert.org> Tue, 20 October 2020 13:23 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 ED73C3A0B45; Tue, 20 Oct 2020 06:23:16 -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 6CDqUPDyRppt; Tue, 20 Oct 2020 06:23:16 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 9D94C3A0B56; Tue, 20 Oct 2020 06:23:15 -0700 (PDT)
Received: from [IPv6:2a00:ac00:4000:400:1daf:e4b6:4a47:5414] (unknown [IPv6:2a00:ac00:4000:400:1daf:e4b6:4a47:5414]) (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 460A3607B38; Tue, 20 Oct 2020 16:23:03 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1603200183; bh=9NcZrv9hvQtIrEY3PW/HNAEoXuB2XwOdYEvwi++jN1Y=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=Gtt4wAQfoqLhkCICMxLEl6B2S/gHs3r55AAB1aftk+8nVFlK4NIM12GERH4zW+UHE 6RFcUjSGQJscwOMQiJ5lF0umpWtGvD9GNUqRbSlcdPY0N2pgfyv0OxypkRyZF54yif 6sz1FavCi/lFjT/2kERxQBdfXN38wmsNkzhRM3xk=
From: Lars Eggert <lars@eggert.org>
Message-Id: <9DAF136B-92E4-4F4F-8684-F951F0574B86@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_7C81CC29-EE9E-44D1-8323-C262BD859BFB"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: Uploaded "Why Multipath QUIC?" for 2020-10 Interim
Date: Tue, 20 Oct 2020 16:23:00 +0300
In-Reply-To: <B165784B-0EE4-4C48-B961-CFDF5968AF6A@ericsson.com>
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, Florin Baboescu <florin.baboescu@broadcom.com>, "Flinck, Hannu (Nokia - FI/Espoo)" <hannu.flinck@nokia-bell-labs.com>, IETF QUIC WG <quic@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, WG Chairs <quic-chairs@ietf.org>
To: Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org>
References: <CAKKJt-dsZNdcMAvzmYCtVNNf8QUAbjcdDDYovATMrffpGL0HVQ@mail.gmail.com> <CALGR9oZZQJ6EH53H91DgoX2oiy40FhFnSzURkLANMYwRqPMCsA@mail.gmail.com> <9f64df7409ce1487779c80069b578456@mail.gmail.com> <CALGR9oZAr0jPYDJQVnJ3c2+G6xgV-SUFRMofutcggp76sEbPww@mail.gmail.com> <247b76fe75ecb025f09713869e18c255@mail.gmail.com> <CALGR9oZ_q+nS9HYoJ-2uk4KxuUazVkZxx_5ynxdO4o01z0GttQ@mail.gmail.com> <d0b4f0ee546852dc35ae38d224208b9d@mail.gmail.com> <CALGR9obXp3c_mcy_bMK7Gm9wp-hL7to_tmw7QOvu4uZXwp2Q_A@mail.gmail.com> <b21cef53ea19af7a2084fbe8824ff665@mail.gmail.com> <CALGR9oYUhEHjjBLvGjZ9ctVKgUN-KqA9DB2_TjLxa_ZF-c-DVw@mail.gmail.com> <B165784B-0EE4-4C48-B961-CFDF5968AF6A@ericsson.com>
X-MailScanner-ID: 460A3607B38.A4828
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7XZSqi_G9G5mKHp-gXkCUf0RBuc>
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: Tue, 20 Oct 2020 13:23:17 -0000

Hi,

On 2020-10-20, at 16:13, Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org> wrote:
> I though we are at the step where we collect use cases in order to understand if there is a need and support for MP support in QUIC

exactly. But in order to have a discussion on this, we need to hear from the proponents of those use cases what functionality they are missing in QUICv1.

> (rather than going into requirement for how multipath support would be realized).

But requirements are not about the "how" - that was exactly Lucas' point. Requirements are about "what". So statements along the lines of "my use case requires the ability to fail over a connection to a different path", etc. would be informative. Saying "my use case requires draft-deconinck" less so (for example).

> We could also talk more about requirement but I think that’s better for a later discussion and would maybe need more than 5 minutes.

I'd hope not? Because if there is a long shopping list of requirements for new QUIC functionality to support a particular use case, that'd look to some as a pretty convincing case that maybe QUIC isn't really a suitable starting technology.

Thanks,
Lars

v2.23.0 | Report a Bug | By Email