IETF Logo Mail Archive

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

Lucas Pardue <lucaspardue.24.7@gmail.com> Mon, 19 October 2020 21:31 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 6165D3A0AA9; Mon, 19 Oct 2020 14:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.053
X-Spam-Level:
X-Spam-Status: No, score=0.053 tagged_above=-999 required=5 tests=[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 76n1i490Bs2z; Mon, 19 Oct 2020 14:31:34 -0700 (PDT)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 0991F3A0AA3; Mon, 19 Oct 2020 14:31:33 -0700 (PDT)
Received: by mail-ed1-x532.google.com with SMTP id l24so805630edj.8; Mon, 19 Oct 2020 14:31:33 -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=813ZClw+UkMPOsES3lCGUt4UinSWcGhEjIhr0nUJvis=; b=nZzHue4WlR0D3povrmeo1qwgyUtp8JfUVaVVplbyw6NWOgb2uUwhHopsx8vGfj/F9c RoyhpdIlaySzj6U0rHz/0sH5Q73a9TEW733OJ33w89bnnSldH9mOaOQrKV9edPkW9JbI vH1tSyd2BTlnVPTpr3lF/G22r4i2dUtH8oZD/FhaSqTbzDgL6k7dpanUONspg/xvWRXX m4MU5tTLOvzAdaaTysPoUVij+2WVRg3rMckttMUW9GY2ecm7OIwdfdCVAsnuQ/CwUsd3 0YqeLySNFOYXJbKCm/deNlgKIxykIwbAjj3D5Wbal1gNHuER0b3e8s1dy3GDhWVyzY2L SFlQ==
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=813ZClw+UkMPOsES3lCGUt4UinSWcGhEjIhr0nUJvis=; b=AoTQAm5mG6DF9nK7sum+2udouZmrt3lO8hNPRbtzo8DPznGBOxbk2+baomalhL6Vyu rOFI4YmwG0PtpNoB7ed3jGqW+0VwGqBrQ0t9yJawpDUHkRfcwtoVm0r8gQ6lItPgQMko vBWD7rd+OAL2LftN3Iepo6POpbhyhhwwBjUEnsmZz2gbdnz8NKoWFOeY/upSIs+iC5yu yVpe8lVSlefJwJ8+GVposo+GoUnILTlrSW+pokYK/uE9cx+SPMzI00f7n+tYKSbO/1Iv ncbSiCecRRz3Di5tR92oBb+h5DjILSejm3o9qEuJ5CgtaLZtbK78GpAPUyNV18qq1j1c 37uw==
X-Gm-Message-State: AOAM530uokdgobbjeHC/k6qftC6CHtkPCZY1AGK5qp+93MyBIP4voC3c iCeQBe/4T8LCDKX3TS/g+9EgIYNzajB8oCuqRNlzJcv9
X-Google-Smtp-Source: ABdhPJw47By2T6HJlg8Q6/QHwUt14l6zv0hTq+trTEdfaJa/bORuCU7/qkhXtUjnzoJYa7M1we/P3Iw9+Lt0JcSxvlA=
X-Received: by 2002:aa7:d3d0:: with SMTP id o16mr1881557edr.47.1603143092498; Mon, 19 Oct 2020 14:31:32 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dsZNdcMAvzmYCtVNNf8QUAbjcdDDYovATMrffpGL0HVQ@mail.gmail.com> <CALGR9oZZQJ6EH53H91DgoX2oiy40FhFnSzURkLANMYwRqPMCsA@mail.gmail.com> <9f64df7409ce1487779c80069b578456@mail.gmail.com>
In-Reply-To: <9f64df7409ce1487779c80069b578456@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Mon, 19 Oct 2020 22:31:25 +0100
Message-ID: <CALGR9oZAr0jPYDJQVnJ3c2+G6xgV-SUFRMofutcggp76sEbPww@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="0000000000008d759905b20cd617"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/GAPjlNUFh1uWQO0vJDZeGTK3vXc>
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:31:35 -0000

On Mon, 19 Oct 2020, 22:25 Florin Baboescu, <florin.baboescu@broadcom.com>
wrote:

> 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.
>

What packets are you talking about here? Why does in-order delivery matter?
TCP and QUIC are designed to accommodate reordering. But QUIC specifically
offers no ordering guarantees across different streams.

Cheers
Lucas



>

v2.23.0 | Report a Bug | By Email