Re: [Webtransport] Confirming Consensus on WebTransport protocols

David Schinazi <dschinazi.ietf@gmail.com> Mon, 15 February 2021 21:34 UTC

Return-Path: <dschinazi.ietf@gmail.com>
X-Original-To: webtransport@ietfa.amsl.com
Delivered-To: webtransport@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C97953A11A6 for <webtransport@ietfa.amsl.com>; Mon, 15 Feb 2021 13:34:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 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_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 82nvzAgmQ-ME for <webtransport@ietfa.amsl.com>; Mon, 15 Feb 2021 13:34:55 -0800 (PST)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (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 7FA783A11A7 for <webtransport@ietf.org>; Mon, 15 Feb 2021 13:34:55 -0800 (PST)
Received: by mail-pf1-x430.google.com with SMTP id y25so1629741pfp.5 for <webtransport@ietf.org>; Mon, 15 Feb 2021 13:34:55 -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; bh=7RHweS/5eZXeGf3LgH3Ve4PXKpYQ83oJvsppUi1+t/Y=; b=Lzw6nwpvVcgCc3B5a7Ja4rORFsZt5/0NbKUzuaJjbCAQJ5hlJNOGQ6HIbN+UZk8A4P aeBNSBig0GArKjqaEsQX9a5sNb8FsE6XAzL0NFyQIN2fwf8opBkQH3X730AHTxjoPMN9 73FKKNqwFZpb9CaNJAZjFmpVvJVM6j+OO5BayhuK8utalf7NBbDIraH63n77BMrNDKGH 0oVHEkz2XZvJ8DjLbzh5/8N20uzRWMnPEuDIjCSY8TWa0R4O2TFW6D0Dx1VecdDoxGmt yo+yi84SHCWLSXTjoi2TnzsNXTCVCb7vOwDw9Ffrl8rPEniLgHp3RAsKJbyyI8nLQL+z eUHg==
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; bh=7RHweS/5eZXeGf3LgH3Ve4PXKpYQ83oJvsppUi1+t/Y=; b=lCRTxPif1GkpiWERwiksWWVjm1Z9k9VfHpo2sMxK4XHuMTBUb5hSfHboSjGyIlxY2j +dzt1yM6B2v9WFyw3fPCJeksLixKPjqVawtAtALTfeDf2VXYc6OYs9Y8zgDSuOpUZMq2 s1LlA0ER2tEO3GMCwT4qxFesYOdXvLJl0NKqXwM00RIyZ/qy8+IiVtyLTsaCvbjdFtt1 URVoDWoOFGaZ2OeOe8kcb0MsINu/ipquYGbVxZQ3s15t622pcWqp61Kz2hKhK67pPpQ1 MUOGLz/7S3WBmDWjvBQSVNPQ74UpVdVOim5NknJJDk1Qenc1i6xRRmzDmpzgaegTQh/V VsXQ==
X-Gm-Message-State: AOAM531ttm4IbfJwToqFokwijluTH3NCvzSASRq4FPw1cNSexkoRVEQt Lfeoq4rrC5bw+R9O7ibwf6gTzuww80hACHXVVNA5PX/TfEI=
X-Google-Smtp-Source: ABdhPJw6d4U9xWHsDMpDli3ny0IAiy1Mh5lg7nfDs72HydDnTz0O8dfxgyErOABHqoBVSQ+yDsu0j4lBeHOGSNAKt/k=
X-Received: by 2002:aa7:9e82:0:b029:1ec:c566:50b2 with SMTP id p2-20020aa79e820000b02901ecc56650b2mr585237pfq.22.1613424894572; Mon, 15 Feb 2021 13:34:54 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <CAPDSy+4REQypGw2=_R0OGWPdUL20ZB4gnS2jqnsyU+D1pCscCQ@mail.gmail.com>
In-Reply-To: <CAPDSy+4REQypGw2=_R0OGWPdUL20ZB4gnS2jqnsyU+D1pCscCQ@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Mon, 15 Feb 2021 13:34:43 -0800
Message-ID: <CAPDSy+70YVUHSd_cmhzCAZz-UgDku2sC2OX3fhjaDyNosJm=0g@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b67c1805bb66c1bd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/Aj7jvjDdJ3iAW_L0zgFv7jzLwxk>
Subject: Re: [Webtransport] Confirming Consensus on WebTransport protocols
X-BeenThere: webtransport@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <webtransport.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webtransport>, <mailto:webtransport-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/webtransport/>
List-Post: <mailto:webtransport@ietf.org>
List-Help: <mailto:webtransport-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webtransport>, <mailto:webtransport-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2021 21:35:00 -0000

Hi everyone,

In the last 2.5 weeks of the adoption call, the chairs received
multiple indications of support, and no objections. We therefore
declare consensus: draft-vvv-webtransport-http3 has now been
adopted by the WEBTRANS WG.

The chairs will work with the author to move the GitHub
repository under our WG organization.

Thanks,
David

On Wed, Jan 27, 2021 at 4:16 PM David Schinazi <dschinazi.ietf@gmail.com>
wrote:

> Hi WebTransport enthusiasts,
>
> This consensus is now confirmed: for the foreseeable future,
> the WEBTRANS working group will focus on building a single
> UDP-based protocol for WebTransport, and that protocol will
> run atop HTTP/3.
>
> Our next step is to adopt a document that matches this
> description. The only matching proposal that has been
> discussed on this list so far is Victor's
> "WebTransport over HTTP/3" individual draft:
> https://tools.ietf.org/html/draft-vvv-webtransport-http3
>
> We are therefore placing this document in a call for adoption.
>
> Please reply to this email stating whether you support adoption
> of draft-vvv-webtransport-http3 by the WEBTRANS WG. Note
> that WG adoption does not indicate consensus on the contents
> of the document, only that it's a reasonable starting point for
> us to start working on. As such, please DO NOT send comments
> about the technical details of the draft on this email thread - please
> create a separate email thread on <webtransport@ietf.org> or open
> a GitHub issue at <https://github.com/vasilvv/webtransport/issues>.
>
> As usual, if you believe that we should not adopt this document,
> please state why. In our last meeting we've noted some concerns
> around pooling for example, and we plan on discussing those as
> a working group once the document is adopted.
>
> This adoption call will last for two weeks until 2021-02-10.
>
> Thanks,
> David
>
> On Tue, Jan 12, 2021 at 9:25 AM David Schinazi <dschinazi.ietf@gmail.com>
> wrote:
>
>> Hi WebTransport enthusiasts,
>>
>> Today we had an interim of the IETF WEBTRANS WG,
>> where we reached consensus in the (virtual) room on
>> the following questions:
>>
>> Question 1: number of protocols
>>     Should the working group adopt only one UDP-based transport?
>>     1A: only one transport (QUIC or HTTP/3)
>>     1B: multiple transports (QUIC and HTTP/3)
>>
>> The consensus was option 1A.
>>
>> Additionally, we noted that this does not preclude us from
>> building a second protocol at a later date if new information
>> emerges.
>>
>> Question 2: UDP-based protocols
>>     Which UDP-based option should we adopt as a starting
>>     point for WebTransport protocol?
>>     2A: WebTransport over HTTP/3
>>     2B: WebTransport over QUIC directly (separate ALPN)
>>
>> The consensus was option 2A.
>>
>> Additionally, we discussed pooling and decided that we would
>> not allow pooling in WebTransport over HTTP/3 for now, due
>> to the complexities of pooling.
>>
>> We'd like to confirm this consensus on the list. If you disagree
>> with these points, please reply on the list. If you do so, please
>> state how strongly you feel - whether you are expressing a
>> preference, or an imperative. Please also provide as much
>> detail as possible to explain your position. Please also respond
>> if you support this consensus - a simple "I support this consensus"
>> email to the list would be helpful.
>>
>> We'll be running this consensus call for two weeks, please reply
>> before 2021-01-26, the chairs will determine consensus on that date.
>>
>> Thanks,
>> David
>>
>