IETF Logo Mail Archive

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

Lucas Pardue <lucaspardue.24.7@gmail.com> Tue, 20 October 2020 01:26 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 9D2A73A08DC; Mon, 19 Oct 2020 18:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 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, 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 fxA6-PLwX7vV; Mon, 19 Oct 2020 18:26:27 -0700 (PDT)
Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) (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 88EDB3A08C3; Mon, 19 Oct 2020 18:26:26 -0700 (PDT)
Received: by mail-ej1-x62d.google.com with SMTP id h24so235775ejg.9; Mon, 19 Oct 2020 18:26:26 -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=QSytR1dIbRLf0GnarXUofbSleORbq0sbo+ETV/TvMrc=; b=DZ3DiH+COve80HDujFJkAOo95/fZr1BCF10m5T5DmzMTtcIRH51KxRb+PX9alc54K3 lWpcxxDmmL7ecrXG3ATV5eqaL6mzoVpHiAZvzR00f3nrgIlx/pJ5qgo6u9jjE9ogHJ9Z rwY2TjZN6SEeeBgDKiiuj7JlA6Iru+WipItLVoHf/0F6/zWMw1HqkFSf7KMreBzWjZvE Gl/RbciHZ/zniZUQYRzC0MO1Ah7BqZE+ibbbE630H/O7PT3YDGuHM9h7W7KkhuxynKtz yGuY+bErS+KD3QAgCT8k+sFOUF37kSEGeZPLnI/VHF8PcI9TJPPp1hu9rmD/NcO9O66Y UqDQ==
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=QSytR1dIbRLf0GnarXUofbSleORbq0sbo+ETV/TvMrc=; b=f/3bEOF/12Z9iNpWGRtm3ZuCmWS0vYEiKTa/DYqsPOuU8IO0KryyTaVd2BzwhY3Ngb iBz7LRYK7lrDqOxstfpLZ2Sb+Y4bEEP/593tTG1Zzmm+C5BXYVDzCk9tvxA29mRjrM4Y rEI/LHV0e/TvK64/u+5STBnUU6eGONd2AHGPM5Gnf0qa5NQoe+8Oa6T6opHT93fOQ9ra OVSjd7mNFVF0htHAppVgms13xxIoZ0xOnfv+sqo87AMysF9vHCaFWHhHhuUxsrYrTNqc hoOl46ecB7XHYDvRax6cnhwJ0q/Uj+czWNko9d6Oblys2cge9O9jcPuUOCwJFWdGuqc9 H8cg==
X-Gm-Message-State: AOAM5312JtoiIak/5NCwRCis1IlD3QJWiCrviJojPJOhaa0T5yZaSXSG DnW8e+ncIi4SABCnooDCHLJyjEMIZqaObs4sqqw=
X-Google-Smtp-Source: ABdhPJzyQ1Vqjq5YDei3wvphskzD2tllK+ZThu7SVWY6k5Q0iqbmo8m5cJCcou/tjD/13GdPztdfzmlbbLfLBJmCMAg=
X-Received: by 2002:a17:906:114a:: with SMTP id i10mr646727eja.301.1603157184987; Mon, 19 Oct 2020 18:26:24 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <b21cef53ea19af7a2084fbe8824ff665@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Tue, 20 Oct 2020 02:26:18 +0100
Message-ID: <CALGR9oYUhEHjjBLvGjZ9ctVKgUN-KqA9DB2_TjLxa_ZF-c-DVw@mail.gmail.com>
Subject: Re: Uploaded "Why Multipath QUIC?" for 2020-10 Interim
To: Florin Baboescu <florin.baboescu@broadcom.com>
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, WG Chairs <quic-chairs@ietf.org>, IETF QUIC WG <quic@ietf.org>, "Flinck, Hannu (Nokia - FI/Espoo)" <hannu.flinck@nokia-bell-labs.com>
Content-Type: multipart/alternative; boundary="00000000000087c73705b2101e3e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fD3pL9W6tX_gNPMQEHTxL3WyBQM>
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 01:26:29 -0000

Hey Florin,

On Tue, 20 Oct 2020, 02:07 Florin Baboescu, <florin.baboescu@broadcom.com>
wrote:

> Lucas,
>
>
>
> There are currently three MPQUIC based proposals which are in discussion
> with different variations in regard to what is transported and how it is
> transported. This is why I’m not commiting to clearly indicating one mode
> of transport or another.
>
> From my side we are happy in advancing the work in
> draft-piraux-quic-tunnel and use it as base of our solution.
>
>
>
Nominating any draft as a solution is solutionizing. We've asked for clear
requirements and non-requirements of the QUIC transport. The slides that
Spencer submitted have use cases but no clear requirements.

The reason this is important is because the IETF MASQUE WG is already
working on tunneling with QUIC.

We need to unpick the layers of overlap to understand what work the QUIC WG
is being asked to consider taking on.

Cheers
Lucas

>
>

v2.23.0 | Report a Bug | By Email