IETF Logo Mail Archive

Re: Next steps for Multipath QUIC

Behcet Sarikaya <sarikaya2012@gmail.com> Tue, 24 November 2020 15:52 UTC

Return-Path: <sarikaya2012@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 249903A11A7 for <quic@ietfa.amsl.com>; Tue, 24 Nov 2020 07:52:46 -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 5IqN2sG070cy for <quic@ietfa.amsl.com>; Tue, 24 Nov 2020 07:52:44 -0800 (PST)
Received: from mail-yb1-xb2f.google.com (mail-yb1-xb2f.google.com [IPv6:2607:f8b0:4864:20::b2f]) (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 CD72C3A11D1 for <quic@ietf.org>; Tue, 24 Nov 2020 07:52:44 -0800 (PST)
Received: by mail-yb1-xb2f.google.com with SMTP id 2so19653525ybc.12 for <quic@ietf.org>; Tue, 24 Nov 2020 07:52:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=e8+8rlYTITABqDzU5v6exx7nP6hxjv/iePMhhQLpC0Y=; b=p66inVQPPz3OMwCtr77pryUzkouDuPanjU9CQS7BjeHgu5Kz/5g6wdQxEdSSWub22c HwAaR0wg6Z66z7hPgzEx8cjOJu7ABvnkq94FYKiUFYfAyFEVQbZigSv8Mcjbm17Seg9t CB6qmqb1byreYtLZ0IwLYD2CX5J6xrM4n4QhG4Ttg356QKYiU5eQCjW5J4zS6iFRxnDB hdAeCQ004PJcJ/rw8UQK+EINtneZUcXXLnwbfaILTsl83ihFVEMYhCVqnbQCZKMmvZaS p1X72vdHTt7Y8CcS8JaD/YL/quneJx/Hfeq5BIhFpzxAkJ+sEWipDOW/vbqEmZl/z6cl 9YWw==
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:reply-to :from:date:message-id:subject:to:cc; bh=e8+8rlYTITABqDzU5v6exx7nP6hxjv/iePMhhQLpC0Y=; b=G80txV66QrXyFjM/NPvKuHPatRiWHRVlZ75A9iJ/pu1T1INBPS03XIL58hfTrgnqKr bRc8g6Sm/iC6TyNa18ov4fBjJTbBweJFEaAiZf6+AKRjOqMdHMUb+K8/nOy4IdiogLFq WjpzW68E+iukV4J9ymW1OfUykjZOG48MWfX3fdb9EjWrRmQC+4kpZqRKIE9xm6fDrSks vbZGKPb7JY5AoUnBiJgWyLV1vWN/ntq9K++kA4VDdk8r5q4rWWsK/WSD+3fL53MbszUr dUiZaXPL9weJ0eJsZ6yANZJaGbY7iQrYPQTL8X2z8YrinWf8Tr5/xCp142MaBE77NbIQ 05MQ==
X-Gm-Message-State: AOAM532FYHBoJlrQN+rauvGHR+UElSH/PMmQ62eWKuJPQHq8pqu7vMAR pnIwW6DCICmHs/ucPLFgGTeNLWRi15x6w5mTRAs=
X-Google-Smtp-Source: ABdhPJyDue4oXVg8r65jmOB6YJV7nMiKy1UTfIkZEf0EH+uYPfG0kO+wdnKGlRjmFsUHjlybaXmvLlQU+13ubnC+vPg=
X-Received: by 2002:a25:d416:: with SMTP id m22mr6893596ybf.318.1606233164123; Tue, 24 Nov 2020 07:52:44 -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> <CALGR9oYoa0jmFo8zcB4U_4Tbn5r7dWGg+gnxyDcRKF1PwCwMDw@mail.gmail.com>
In-Reply-To: <CALGR9oYoa0jmFo8zcB4U_4Tbn5r7dWGg+gnxyDcRKF1PwCwMDw@mail.gmail.com>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Tue, 24 Nov 2020 09:52:32 -0600
Message-ID: <CAC8QAceewkmDmSFh7-sA4kCaEaL7oJX3JAxxExHwU+44pAsuvQ@mail.gmail.com>
Subject: Re: Next steps for Multipath QUIC
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002c90c405b4dc4dc1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/8HAiOoi_mbCAUTu503DY9sp8SMg>
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, 24 Nov 2020 15:52:53 -0000

Hi Lucas,

I think your offer is a good step forward. Thanks.

But I am unable to understand why you want to restrict the intended status
to Experimental?

BTW I checked all 3 multipath drafts and all of them ask for standards
track status.

What is wrong with multipath that warrants downgrading its status?

Behcet

On Mon, Nov 23, 2020 at 12:30 PM Lucas Pardue <lucaspardue.24.7@gmail.com>
wrote:

> 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