IETF Logo Mail Archive

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

Lars Eggert <lars@eggert.org> Tue, 20 October 2020 13:53 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 C21BA3A0BDE; Tue, 20 Oct 2020 06:53:43 -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 I3ns4qPnVJUj; Tue, 20 Oct 2020 06:53:42 -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 75D363A0BE4; Tue, 20 Oct 2020 06:53:42 -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 BE434607BB6; Tue, 20 Oct 2020 16:53:25 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1603202005; bh=qdowjqpjXoFF9lCAWDAgbfqTxniUfgnWcS7OwZNRBH0=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=MNRoYw/ZP7aSRtFojKMp3/8J5fBTFjLpjtkWjS5H60JCJeXIlQeWTfKRxBO3k9swL Ef0qTM9u6VbnxW7ybFsWwDVWBEG6IUulrjtdVQ5TUMB0/h45jaN2FroGObVyR/4hX1 uxnp4hBpNVFA7FWa/Z77U8KmrX7nrnw5RTLHEMIw=
From: Lars Eggert <lars@eggert.org>
Message-Id: <7F319D03-DC5E-46C1-98AF-9331705E0A4F@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_333B6F89-F988-414C-8E81-5FCC394B1A02"; 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:53:25 +0300
In-Reply-To: <7EA5E534-9F62-4460-A86D-E06A276850CC@ericsson.com>
Cc: "Flinck, Hannu (Nokia - FI/Espoo)" <hannu.flinck@nokia-bell-labs.com>, Florin Baboescu <florin.baboescu@broadcom.com>, WG Chairs <quic-chairs@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Lucas Pardue <lucaspardue.24.7@gmail.com>, IETF QUIC WG <quic@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> <9DAF136B-92E4-4F4F-8684-F951F0574B86@eggert.org> <7EA5E534-9F62-4460-A86D-E06A276850CC@ericsson.com>
X-MailScanner-ID: BE434607BB6.A154F
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/o2n-V7eQwIZmsy2_JhdovxouS7Y>
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:53:44 -0000

Hi,

On 2020-10-20, at 16:46, Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org> wrote:
> 
> I guess the requirement for this are that QUIC can use two paths simultaneously and that data send within one stream but transmitted over two paths are delivered in order.

I think this is exactly at the level of detail that is useful at this stage, and nicely identifies what QUICv1 can and cannot do.

> Not sure what other requirements you would expect to see at this stage?

I don't expect anything :-) It's up the proponents of the different use cases to state their requirements in this  way. If ATSSS required nothing else than what you stated above, you'd be done.

Thanks,
Lars

v2.23.0 | Report a Bug | By Email