IETF Logo Mail Archive

Re: Next steps for Multipath QUIC

Behcet Sarikaya <sarikaya2012@gmail.com> Wed, 25 November 2020 15:50 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 036163A18F7 for <quic@ietfa.amsl.com>; Wed, 25 Nov 2020 07:50:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 iMXKo-d1q4_i for <quic@ietfa.amsl.com>; Wed, 25 Nov 2020 07:50:28 -0800 (PST)
Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (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 8DD633A18F5 for <quic@ietf.org>; Wed, 25 Nov 2020 07:50:28 -0800 (PST)
Received: by mail-yb1-xb31.google.com with SMTP id 2so158827ybc.12 for <quic@ietf.org>; Wed, 25 Nov 2020 07:50:28 -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=2BjLah7ynwybKmX0NGMcSQJtcA8PlBwWmY3uvZBD+MA=; b=mLB3mRQkEX/YL5mkIouJXousKc77nXxXTNFGuY6sUHuJRYXiBUUOHXMqqqJSKnWQAz Ufcy05dnPexBmaUHFlCVq7hxUE8hior9OdzXNFZ9J5ik8Dpqle5XNh3liIkxVk+aRB1R sKMVwBTp+YlFE6JNTnv47vM5btpEjw0Rp/b0m4FRLY2bFB/u5fDNAmQkY/f7235QBCcB mP8P1HccvKuJEcG/rmSVUCzt2vwlLxYME1Nebg1y+l1aRSMh3cjek1a1gyl9mPZGJKoz lbLMYUA1S+q19u48wUJG9zW7Ad6jIKo4pKkHJV/6H0pmaVM64YC9yCL7f0bc6arskr7M hegQ==
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=2BjLah7ynwybKmX0NGMcSQJtcA8PlBwWmY3uvZBD+MA=; b=gP502brhuAAT3bIMborsTEUU8e/jnwIe6EzKpCb0J6EFCGtS5WAAlEE5a0jAY2UWzu dXpSoRpO5AHsrjdAhlm0uDLgwoGOjZFpXEt29QbbnC4JDMDPIctSJWrd3oCPQVBvHSfq W3Bp8ZAdxxKlPu+KU0G+4JNIoAqFYIql08FFeeou5NWuGrHReM8n2jTFgUCwZr+pHmdz 83XthlFZFCNJlq7XKC6VXKoLH7Algd8ALk/DkYEzInC7KAa2psAtjBzmTu723wgXSYbO YGvY0LvTrGPOM0cfZm0eK5adRJn/afgsYumurk5OIbbBdRx4Nhfrotfcnuqx5s19zMg2 vVTw==
X-Gm-Message-State: AOAM5316itt2rRdG1kAa7MU2bEQh8SsTy6Nit7gwB8RanFshbGoc66vN rD2y6K4ZMGeOD9PncNX4J08Ly2+ZmLXo2R7gxSg=
X-Google-Smtp-Source: ABdhPJygOWHsxHvCkW3KNodoM8URkbYjp6pTI+9DJLE6PnTsUkg20jRW55zTZ7FK//+BCnfcQEpViumQIgrrEoXeghY=
X-Received: by 2002:a25:41c7:: with SMTP id o190mr6253904yba.324.1606319427749; Wed, 25 Nov 2020 07:50:27 -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> <CAC8QAceewkmDmSFh7-sA4kCaEaL7oJX3JAxxExHwU+44pAsuvQ@mail.gmail.com> <CACpbDcfpEmOkYWQipZy-yTdP=NAiF+ABGrxva0nowRE1xUaOSw@mail.gmail.com>
In-Reply-To: <CACpbDcfpEmOkYWQipZy-yTdP=NAiF+ABGrxva0nowRE1xUaOSw@mail.gmail.com>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Wed, 25 Nov 2020 09:50:16 -0600
Message-ID: <CAC8QAccvSP7iJQ=yB21Ogf_25x-bmFiZKGnQjnhHV4L70h8chw@mail.gmail.com>
Subject: Re: Next steps for Multipath QUIC
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, QUIC WG <quic@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000e30cfc05b4f062b5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/hcDLmoydx_L4Wk8d0aQUe-yLiSA>
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: Wed, 25 Nov 2020 15:50:30 -0000

Hi Jana,


On Tue, Nov 24, 2020 at 10:44 PM Jana Iyengar <jri.ietf@gmail.com> wrote:

> Behcet,
>
> Lucas isn't talking about the status of the drafts, he's suggesting that
> folks experiment with the proposals before we discuss their adoption. I
> support this.
>

That's not how I understood Lucas mail. But I take you word for it even
though not from the chairs :)



> The question of which track will only apply when the wg is considering a
> draft for adoption, and it can be modified after adoption too. There will
> be a time for this bikeshed too, just not yet.
>
>
Yes, that is how it should be.
So we are open, standards track is a possibility.

Let me also say that there is good support for mpquic, Apple, Alibaba,
Tencent, all those support it, implement it and use it.
3GPP CT4 is ready to standardize it once we have an RFC.

So what's not to like?

Behcet

> - jana
>
> On Tue, Nov 24, 2020 at 7:53 AM Behcet Sarikaya <sarikaya2012@gmail.com>
> wrote:
>
>> 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.37.1 | Report a Bug | By Email | System Status