IETF Logo Mail Archive

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

Florin Baboescu <florin.baboescu@broadcom.com> Mon, 19 October 2020 21:25 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 D99373A0A82 for <quic@ietfa.amsl.com>; Mon, 19 Oct 2020 14:25:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[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 4Tdnl9dY321o for <quic@ietfa.amsl.com>; Mon, 19 Oct 2020 14:25:49 -0700 (PDT)
Received: from mail-oi1-x230.google.com (mail-oi1-x230.google.com [IPv6:2607:f8b0:4864:20::230]) (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 639C23A0A81 for <quic@ietf.org>; Mon, 19 Oct 2020 14:25:49 -0700 (PDT)
Received: by mail-oi1-x230.google.com with SMTP id 16so1628146oix.9 for <quic@ietf.org>; Mon, 19 Oct 2020 14:25:49 -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=Zo6AV8zOBu6twN1aTRwm2heNYZH/yNaqc0NAiCHLhZs=; b=bg0noEL4hV8+5MSCdF1TJLmh+gtoC8brWdMykpTwEWuNzrhq9vBZKxtJB9fo1JXh76 juuNhykUKBgDu8HLuISxxDeO/DnZB9bINkAR/OyEV+hjgaJrK+yBzaUP1by64lFOTZmX KGij+NqunTfpGhWLUiPpWSirgTeyLicVyxJ6s=
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=Zo6AV8zOBu6twN1aTRwm2heNYZH/yNaqc0NAiCHLhZs=; b=hRzh/sMrxEapGFUR3VMHu27zYshCNTFVEcXjU0mtjVFU/IKauwK5+92y9uF3yA1U01 oW09VXNALpUnlm7Y9Eqr6FV57WUGWSaaepggZGGhZ7f6cjqc4Y3Wv/UBwA1/rBtOXVaV k9vWUDDqCeBDyfqt9f+pBm+AlpsNRNtrM95uOtLSEKE5rC2KUmqTQcP2SlRlShxB94As o0r8MXQ0Iu0gUIXNcbVARi3K987e/vOvMKmAUjuNvtNLLyu5o0c/LyGWa8W+s6vCDeNh +MgAktGdq9pBiq5KS1rGIC6H28JsNQ7t/11b1QhzDbb+4JTWJvtccrbRg+Rr2JvFsjXK I9kw==
X-Gm-Message-State: AOAM531Cej+SxVYPOnOBsM37f5GWP9YJs0Pj7A90b88j79xAKfIg42kY a+oqpPYbT2Cza2S4BXN9FDTM5yVev2nh9HwalbCTXIlTaeM=
X-Google-Smtp-Source: ABdhPJztRkDL7cOWesV+OfHUUJjfNR3HuFYzwmPMznMKF2dBC6Y0TxUge/+g0dG5XrKnp8ABJ/SzUdr0XbVa2TDB7aA=
X-Received: by 2002:a05:6808:2:: with SMTP id u2mr1001172oic.170.1603142748356; Mon, 19 Oct 2020 14:25:48 -0700 (PDT)
From: Florin Baboescu <florin.baboescu@broadcom.com>
References: <CAKKJt-dsZNdcMAvzmYCtVNNf8QUAbjcdDDYovATMrffpGL0HVQ@mail.gmail.com> <CALGR9oZZQJ6EH53H91DgoX2oiy40FhFnSzURkLANMYwRqPMCsA@mail.gmail.com>
In-Reply-To: <CALGR9oZZQJ6EH53H91DgoX2oiy40FhFnSzURkLANMYwRqPMCsA@mail.gmail.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQIDOVvnGttNmsY4wUCzRnXyYgGoNAIKTEhBqTX3JZA=
Date: Mon, 19 Oct 2020 14:25:45 -0700
Message-ID: <9f64df7409ce1487779c80069b578456@mail.gmail.com>
Subject: RE: Uploaded "Why Multipath QUIC?" for 2020-10 Interim
To: Lucas Pardue <lucaspardue.24.7@gmail.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: 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="00000000000010dc4e05b20cc2f5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/cC4aCWuhUI_4awaDrp1LeJFdFQA>
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: Mon, 19 Oct 2020 21:25:51 -0000

Hi Lucas,

Based on how the ATSSS-LL sender is implemented, in-order delivery of the
packets may not be guaranteed at the receiver side once multiple paths are
used.

-Florin





*From:* Lucas Pardue [mailto:lucaspardue.24.7@gmail.com]
*Sent:* Monday, October 19, 2020 2:21 PM
*To:* Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
*Cc:* WG Chairs <quic-chairs@ietf.org>; IETF QUIC WG <quic@ietf.org>;
Florin Baboescu <florin.baboescu@broadcom.com>; Flinck, Hannu (Nokia -
FI/Espoo) <hannu.flinck@nokia-bell-labs.com>
*Subject:* Re: Uploaded "Why Multipath QUIC?" for 2020-10 Interim



Hi Spencer,



Thank you!



Perhaps because it's late in the day here but I don't understand the
mention of in-order delivery requirements wrt ATSSS-LL. Can you elaborate?
*Is that* a requirement of multipath?



Cheers

Lucas



On Mon, 19 Oct 2020, 22:15 Spencer Dawkins at IETF, <
spencerdawkins.ietf@gmail.com> wrote:

Dear Chairs,



I uploaded https://github.com/quicwg/wg-materials/pull/160 for Florin.



Please let us know if you have any questions or comments.



Best,



Spencer

v2.23.0 | Report a Bug | By Email