IETF Logo Mail Archive

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

Florin Baboescu <florin.baboescu@broadcom.com> Tue, 20 October 2020 01:07 UTC

Return-Path: <florin.baboescu@broadcom.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 DA5E43A1393 for <quic@ietfa.amsl.com>; Mon, 19 Oct 2020 18:07:28 -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, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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 (1024-bit key) header.d=broadcom.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 t2uE8jgW2Sj9 for <quic@ietfa.amsl.com>; Mon, 19 Oct 2020 18:07:27 -0700 (PDT)
Received: from mail-ot1-x336.google.com (mail-ot1-x336.google.com [IPv6:2607:f8b0:4864:20::336]) (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 34CFA3A1396 for <quic@ietf.org>; Mon, 19 Oct 2020 18:07:27 -0700 (PDT)
Received: by mail-ot1-x336.google.com with SMTP id h62so64532oth.9 for <quic@ietf.org>; Mon, 19 Oct 2020 18:07:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc; bh=jNHyZJcH8zR5UZgCSaJ9Z63v+YuP0qAmvZ22txxKGDg=; b=OE2aEErAp23wi2ISMy26gwxaHQhpV6k5KYhZln608jagRw372KrDvSvEkZJwOJf5M/ ZexfXRlebD9UTIl5gxc7TZ5VL9bTuNf6uy0rsybkwoiFeX+z+AunxnX3rG3Xml9AJHTk nynpCe70LqSTiFoj00lJEmeCoVtueCLPOza6c=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc; bh=jNHyZJcH8zR5UZgCSaJ9Z63v+YuP0qAmvZ22txxKGDg=; b=nYxHvaTnC+h3X6kK694gYEyJm61F5ncbpkjD5Wc9Ear3qP0YhNx6BXC894Y4L+PQUP TS5RgVUuMPXMtxyqB8Aswx6s+wpJ/tEHvBXEKSIsXd7EGWwgjfEjoaQ/M0sldyifqsxl vbKmQKe/3I+8RTIxgPzSjOePz6K58P+68SUx/hFSKGcva3fIJPnK9LnbMF9Z379gkiFi nPLbpGazS5XFa3unKpN/kGuKA3x6pZouGOTRGoafGPhHmMdiDF+NOxdynhV14tUCOGBO INbMxj8FJF4oOcEVtK1eRjo/QTJ0liKhLEwyxBLcfsJF34LtfRmmrv3TBmWrgSsPDy1n kPEw==
X-Gm-Message-State: AOAM5335OFvK6KGgBLpnUTGRFxIMTgktkLSOyqaLxsTbzomcW0loz8K1 XO7w0Io0FzzvTpTpdxHKDxSRSm7JhD2DpHovGkC+cw==
X-Google-Smtp-Source: ABdhPJy/eHmyI7melPc40hGRQz8Uvqvy0ENumgiMB1EOfLpIsq5puwItrsZdjYDAuR7tyG1hz+vbzbGICp40oTS6FeU=
X-Received: by 2002:a9d:604e:: with SMTP id v14mr168165otj.234.1603156046271; Mon, 19 Oct 2020 18:07:26 -0700 (PDT)
From: Florin Baboescu <florin.baboescu@broadcom.com>
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>
In-Reply-To: <CALGR9obXp3c_mcy_bMK7Gm9wp-hL7to_tmw7QOvu4uZXwp2Q_A@mail.gmail.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQIDOVvnGttNmsY4wUCzRnXyYgGoNAIKTEhBAcrDzREClKKXiwH6OC14AtZpjHMByhoaGwMbadvDqMWFOeA=
Date: Mon, 19 Oct 2020 18:07:23 -0700
Message-ID: <b21cef53ea19af7a2084fbe8824ff665@mail.gmail.com>
Subject: RE: Uploaded "Why Multipath QUIC?" for 2020-10 Interim
To: Lucas Pardue <lucaspardue.24.7@gmail.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/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="000000000000ae3d4805b20fda62"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/unu-0Eq24vufwa4fTGxJtUqLpz4>
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:07:29 -0000

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.



-Florin





*From:* Lucas Pardue [mailto:lucaspardue.24.7@gmail.com]
*Sent:* Monday, October 19, 2020 5:51 PM
*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>
*Subject:* Re: Uploaded "Why Multipath QUIC?" for 2020-10 Interim



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