IETF Logo Mail Archive

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

Lucas Pardue <lucaspardue.24.7@gmail.com> Tue, 20 October 2020 00:51 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 76EFC3A1307; Mon, 19 Oct 2020 17:51:10 -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 wr1dLSIt3yxl; Mon, 19 Oct 2020 17:51:09 -0700 (PDT)
Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (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 09D403A1306; Mon, 19 Oct 2020 17:51:09 -0700 (PDT)
Received: by mail-ej1-x629.google.com with SMTP id x7so152441eje.8; Mon, 19 Oct 2020 17:51:08 -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=SEYhEBj/FJEKjuXMsoIi4ctp0tgD+BSu1sy683kTMSI=; b=R+82h/tQoNOtwdsXvQPdsIj0qakucehGJgirudyKgOdEGfgYq46QR2uCDO/JGqx2SN 9obtTH/WezhkmictTgLnIkHtzWyPc2p47fV5AGBeAPxpO9tZdFE5dT7z2JtUotSLtpHz 6iMHEfr3qN/N8sfQd957ZDmMpHpR2lBEjWAm892nTvVhrClewhJUQwIuCfrOFajuUJqb gI9QA71W7hVa96jyGnyGVMKRg6OumIXEROUuGU9lBWo0cWKfpTTH6U4pwYslaj+XlUTS XiczLRZvlfubrdCuLXXRnjeDFjs3u19RxXg3WWtzbNoxpLnggP5Uhyzt+I5Cav+6blkr 9Pdg==
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=SEYhEBj/FJEKjuXMsoIi4ctp0tgD+BSu1sy683kTMSI=; b=RW8RpVoExMrRF5pJsR0PQ46mlUKXI1Mw97gfQCu2D/f4XUhOoddV6tJnc0ZA0NK243 INIOJJiPtRFfETBZlBInBYhG8ALkGGSWteB2yo7h3UdU5tkTGCnio1ii/lTaAS0iSEyk m4ugBit9xZmn9GZQ7cvDYkInMktrO+9rkLW9rIcYD5mxGW8+bH1UmZkpkA6NbduGvjBs ElGYtcEFBitbxOM2yRgjzR///tptNcc5TQ0MyntCg2v8IrQ5RogfBX+O12OoUf3uXS85 TmGLd2Lu9JoVG6kU8sar0QCM9gnusCX5HhzTiN2QTTJIoUNMjNIVXIkj15MJuQtqhjIs YaQA==
X-Gm-Message-State: AOAM533isy4KbtuP4qQS4EGzrEMa6ZlQeZTXl5uDyQwtpyEFyBB5j5fO uZfJOUxU2As4RXz1OJq/pU+Lvw7BOEw1VqDi6HU=
X-Google-Smtp-Source: ABdhPJzzm2w9kSrwMKK1qfG3HukdZ3cEp7rrI5nDP8l8A51vzYF8N4roPUs2OwIMfKAzKSV84ioO7fYp56++RMhuv7A=
X-Received: by 2002:a17:907:94d2:: with SMTP id dn18mr566704ejc.374.1603155067653; Mon, 19 Oct 2020 17:51:07 -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>
In-Reply-To: <d0b4f0ee546852dc35ae38d224208b9d@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Tue, 20 Oct 2020 01:51:00 +0100
Message-ID: <CALGR9obXp3c_mcy_bMK7Gm9wp-hL7to_tmw7QOvu4uZXwp2Q_A@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="00000000000053df3105b20fa035"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/JBUtwkzrWxRiNW5FQyLi1XzUnxs>
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 00:51:11 -0000

Hi,

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

> Hi Lucas,
>
> When you say “Is it the intention to map QoS flows to QUIC streams?” In
> short I can say yes. If it is available.  I consider though this to be an
> orthogonal discussion to the multipath one and I believe it to be dependent
> onto the current progress with the QUIC tunneling draft.
>

It can't be orthogonal. We need to understand what your requirements  of
the QUIC transport are. QUIC presently defines two methods to carry data in
a connection streams and datagrams. How those map to multipath for your
needs is the question here.

There are many QUIC tunneling drafts. Can you be more specific?

Cheers
Lucas

>
>

v2.23.0 | Report a Bug | By Email