IETF Logo Mail Archive

Re: Next steps for Multipath QUIC

Lucas Pardue <lucaspardue.24.7@gmail.com> Mon, 23 November 2020 18:28 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 815D33A0D40 for <quic@ietfa.amsl.com>; Mon, 23 Nov 2020 10:28:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.052
X-Spam-Level:
X-Spam-Status: No, score=0.052 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] 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 fY8dF8U6DLK5 for <quic@ietfa.amsl.com>; Mon, 23 Nov 2020 10:28:28 -0800 (PST)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (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 BC92E3A0C57 for <quic@ietf.org>; Mon, 23 Nov 2020 10:28:23 -0800 (PST)
Received: by mail-ed1-x52c.google.com with SMTP id cf17so14570375edb.2 for <quic@ietf.org>; Mon, 23 Nov 2020 10:28:23 -0800 (PST)
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=OyVLS4pfcKjjY46szzLc6WYC7jZCHAa3d8Kz6FZq7Bs=; b=ulp/h9gd9xY0wRCy3ZPyhrIcfv71beYIcgrNQfQm/wmDUXP+QOxnIts1pCMfuJWnXy BbRbYnFLqfhW7LJQQcWoCFgnogaG5zHRle4rEMEnrtjdwTOxEtvrpxOwFx9x3vDxZ8/3 2i+vZfwZeswnGuxwE/ASZV6yG2llEqEwtHgiOtE67QMBF9VTSF+ab9mgspWxcXB4NcAN ZdUJrljEBWUdS6tyaIYXmFUbmjq0zylSoW6JmeXJJlBVzM1qbEoIOaby8l5faDccG3G1 YWLu/g/XzbiDaNTD7wTix4rNq5ZEXwqF9FTtilksDRGHzXzCglD6rQllrGzMLNlNCYE4 hkQA==
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=OyVLS4pfcKjjY46szzLc6WYC7jZCHAa3d8Kz6FZq7Bs=; b=LyWtFnGtp8nh0Jk6I3MtsPlBWnFPTOnbgwAgqXn6GSdNlbIiBA4dB8uo0RDAhkNl6O hl4drp6dI3NBODksYgLDZH82yTq096NGeGCjETBIj8ln8yblDsZhbT2D7WiEPQrpIcEv gR24O8YaLP1YO9X6Aq3u2gIm7p3DRfrgGntQhuavy4b990zez73imXj7hKx9o3ulu/uV zwscjCwSX7chGJ0NG4C0aVq2li7ITFgABxR/tFU5TyNZJx1Lbgr1WDsW7YjgzbIqBq3G 1J1iJqbNYAkeArdLSrpF4Bg+DNqouk7DLz85vaD6rYQ8pp8veGC4TXWaWYw8z9yqxdpw pZ4A==
X-Gm-Message-State: AOAM530DJyFleAOoUKc8jMBhkcbxxxIFsKvn9WGwHiYSsuczf+b3Copi 1A/A1601KKYm3PSPJu5NRNORy0E5KubiSqzUrwU=
X-Google-Smtp-Source: ABdhPJzfiZeWuIZ4lXb7x39ZfxMwwhWpIloahHRD5sDXqjyGfh3+sgCk3AwxpA1O02yhrgs+cfHlG62VnHhpUhQ+MXE=
X-Received: by 2002:a50:8f06:: with SMTP id 6mr482906edy.39.1606156102301; Mon, 23 Nov 2020 10:28:22 -0800 (PST)
MIME-Version: 1.0
References: <F2EB47B8-EC64-4792-B38A-D0346714DDAD@eggert.org> <HE1PR07MB3386DFB739D6FAA9602FBCA99BFC0@HE1PR07MB3386.eurprd07.prod.outlook.com> <CAKKJt-c5h3y0GxCgyzFy2EymCN8GFKEJZBQiZbw15ZFFc3sdhQ@mail.gmail.com> <CALGR9obyCi092oVN3SKDyj=jgzF4bQS56rifnKHeF1SYm+qpcg@mail.gmail.com> <CAKKJt-dX4ke8K+Mz5TeKYeSSusLuSB_8SVQkTwniwZ7Av_59bA@mail.gmail.com>
In-Reply-To: <CAKKJt-dX4ke8K+Mz5TeKYeSSusLuSB_8SVQkTwniwZ7Av_59bA@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Mon, 23 Nov 2020 18:28:10 +0000
Message-ID: <CALGR9oYoa0jmFo8zcB4U_4Tbn5r7dWGg+gnxyDcRKF1PwCwMDw@mail.gmail.com>
Subject: Re: Next steps for Multipath QUIC
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ee7e5705b4ca5bb3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YwxR8Wq2uccpFre_3bxNjpC2nYU>
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, 23 Nov 2020 18:28:36 -0000

Hey Spencer,

On Mon, Nov 23, 2020 at 6:00 PM Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> Hi, Lucas,
>
> I agree - sorry if I was unclear. My suspicion, to be confirmed or
> overturned, is that "several multipath use cases" may not mean "all of the
> proposed multipath use cases".
>
> Using my two categories above, I'll be looking especially closely to see
> if a single multipath QUIC design can address use cases in both categories.
>

Thanks for the clarification. As an individual, I think you and I are in
general agreement, turning "unknown unknowns" into "known tradeoffs and
demarkations " seems a nice next step to keep the conversation moving.

Cheers
Lucas

v2.23.0 | Report a Bug | By Email