
From nobody Sun Jan  3 17:16:27 2021
Return-Path: <bernard.aboba@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 B3D9F3A14D3 for <webtransport@ietfa.amsl.com>; Sun,  3 Jan 2021 17:16:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.8
X-Spam-Level: *
X-Spam-Status: No, score=1.8 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, PDS_SHORT_SPOOFED_URL=1.997, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 FGBtNwJ_YMC8 for <webtransport@ietfa.amsl.com>; Sun,  3 Jan 2021 17:16:24 -0800 (PST)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 5A9C43A14D1 for <webtransport@ietf.org>; Sun,  3 Jan 2021 17:16:24 -0800 (PST)
Received: by mail-lf1-x135.google.com with SMTP id h205so60826672lfd.5 for <webtransport@ietf.org>; Sun, 03 Jan 2021 17:16:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=u+nYk9nx165e4D4NKincZNabkT4n/mRkx3hK7Vg46LM=; b=jWDZp7rgmACvi3HRXbhkDLCmYweS4K7zJs5x8tS8sQQhgYsDVPej+OR16d2XBRPpkC zhOmwuNe+IL1lG0kySYOkwKMahOX8dPnt/LHX4Ig4Wq5Xaa1tPOsQbA7J5YVjVGEr+NZ 0ZAlaxIESqboF0ssbEj0ImSw+Rhuw/ZtMrcKh2uqnOcFPymA2AYXvPno4qdKZLP/J5gV 50CtwdEeZfEVJ7eU86jb9VPAa39YBPTF6nxFuWMjR0GXJ0POLvxdyYY+RokqfjysZGDj nlzuoqDLxXgGsSrPeoSlEZxDobFQrUVbAfzJxsc9fxAUmWgazPTir2r265Crhvlz9Tbm /n7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=u+nYk9nx165e4D4NKincZNabkT4n/mRkx3hK7Vg46LM=; b=pzgbwpUBHNIfHxRkW+Yhu1RS+Rkpj1ynqeSTadx+Zeax46JontzzBjvdbabW5OZIYP s5sklsj78IP5KooTIn9vB3U1lCo4c4FxABMfkwSbCscmgE0gSq+I+k4b3n1saSe1lD6o DCbfRlcGHhZuwUnRJs1fA+yQcX9Az/HjlMMDdGWdgDp6w52AFGGveljdPcXAXBD/WlKy +IekwaQmfsH5if7KDS3nSO9vloka4FT60B42Te8JcWtNmzmHjLPv0ga8Rbs/VI1mDr6U Fz0flrm0+/cxwu8fuMuC9mAaFFMAfdTJizZ6aoFZWb5SAAFJSkJYOcYPnKEru3Xfur6N ATQQ==
X-Gm-Message-State: AOAM531DMVj/nvJBX9ln4aTyceYm5zDG37IJbYQPYInDdP5u0WLXfr/N jJQGcKadaqlV10GUvqyKCoseMFX0rB9HrZCkdZz+wDDwyJNnUQ==
X-Google-Smtp-Source: ABdhPJwFLji8ayuCpPgsyj75xE6yUdZnzNJ/t2HHfvSzvPTgo/0klZcUqD5mm2z9r5R5ztx+EZmeuNOuEKnT/BI922o=
X-Received: by 2002:ac2:51ab:: with SMTP id f11mr33507662lfk.510.1609722982026;  Sun, 03 Jan 2021 17:16:22 -0800 (PST)
MIME-Version: 1.0
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Sun, 3 Jan 2021 17:16:11 -0800
Message-ID: <CAOW+2dvUmjYXC8Yf9u=qwpJCR22BV_DjQsoOMNwPBOnoockVWA@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000087d1ab05b808d68e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/ioPOA9Ot4m-05h8NpPFFsLAD3N8>
Subject: [Webtransport] Reminder: WEBTRANSPORT WG Meeting January 12, 2021
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, 04 Jan 2021 01:16:26 -0000

--00000000000087d1ab05b808d68e
Content-Type: text/plain; charset="UTF-8"

The IETF WEBTRANS WG will have a 90 minute Virtual Interim Meeting on
Tuesday, January 21, 2021, starting at 8 AM Pacific Time (16:00 UTC) .

The meeting will be held on Google Meet at the following URL:
https://meet.google.com/oqg-iprr-yab
<https://www.google.com/url?q=https://meet.google.com/oqg-iprr-yab&sa=D&source=calendar&usd=2&usg=AOvVaw3V5vwjKG3WBuP9l6HEWcqu>

Agenda is here:
interim-2021-webtrans-01 : webtrans (ietf.org)
<https://datatracker.ietf.org/meeting/interim-2021-webtrans-01/session/webtrans>

--00000000000087d1ab05b808d68e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">The IETF WEBTRANS WG wil=
l have a 90 minute Virtual Interim Meeting on Tuesday, January 21, 2021, st=
arting at 8 AM Pacific Time (16:00 UTC) .<div><br></div><div>The meeting wi=
ll be held on Google Meet at the following URL:=C2=A0</div><div><a href=3D"=
https://www.google.com/url?q=3Dhttps://meet.google.com/oqg-iprr-yab&amp;sa=
=3DD&amp;source=3Dcalendar&amp;usd=3D2&amp;usg=3DAOvVaw3V5vwjKG3WBuP9l6HEWc=
qu" id=3D"gmail-ow832" style=3D"color:rgb(26,115,232);font-family:Roboto,He=
lvetica,Arial,sans-serif;font-size:14px;background-color:rgb(241,243,244)">=
https://meet.google.com/oqg-iprr-yab</a><br></div><div><br></div><div>Agend=
a is here:=C2=A0</div><div><a href=3D"https://datatracker.ietf.org/meeting/=
interim-2021-webtrans-01/session/webtrans">interim-2021-webtrans-01 : webtr=
ans (ietf.org)</a><br></div><div><br></div><div><br></div></div></div></div=
>

--00000000000087d1ab05b808d68e--


From nobody Mon Jan  4 15:20:30 2021
Return-Path: <bernard.aboba@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 C77123A0A4C for <webtransport@ietfa.amsl.com>; Mon,  4 Jan 2021 15:20:28 -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 hAzgg9k9Q7mt for <webtransport@ietfa.amsl.com>; Mon,  4 Jan 2021 15:20:27 -0800 (PST)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 2D21E3A0A4A for <webtransport@ietf.org>; Mon,  4 Jan 2021 15:20:27 -0800 (PST)
Received: by mail-lf1-x129.google.com with SMTP id o17so68421250lfg.4 for <webtransport@ietf.org>; Mon, 04 Jan 2021 15:20:27 -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=4mijP5B1gfWFh8OICja3Zx99JXt++gSyYYPdM02rDc0=; b=cZTxc3l0IM2Of/olwyMUMaKGYDgBEKcz4BZBsMzroMHyTvjnYgAiRmfr9+1T/Og8Nw BGJZ+vQgXbdkB+vZJgp+dmkwnqzkM6yf1xTH9YzC58CBPwbLaji38UhyYi0i24jk29QN O0a1Y/4x0uqMSvQNu/OFc+ey1WcqPL3iTFSTIAHfsXm9Yv5nCgh0LPKXx7nFJRuH21of WU3nKYKwBgMZJohG3XWrGgzZ3aTrIezLwYzgAgZmW17EBalpkpgecqnVLd1DoiIhlhYF GpmPIsfSHe3zOADusY9G8RRKPGYAsfWxRV0zRHwOA4AEPJTkHWzhRgjEWVwra+zF+U8J fcgg==
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=4mijP5B1gfWFh8OICja3Zx99JXt++gSyYYPdM02rDc0=; b=jQ7Hpdaj2AqR8X2d1TJQkhTUTyVYaRPswL2xfLzb5BXF/0Mpf9AsftYunlH/yhv5Z/ XtsntxZu0KM0tTza3Lu8nxViQolC4Smvk+H+uq76GAIfd64vJcjh12oZUk8FEWzRkCMI KwEXNdtpUSJqpo/C+1jKslT/XH9HylSDM9Gk58VhJOca+omHys0VRoC55o6nYT6MX+fZ FbYruWjZSEnlKGWMdkEM+Nx8t1aX8a1Xb3AxgoUoPWvkPL6m7NkYA5KgL4zYnwydASfj CKXVJE6pDwz+PLZbVQQ0a9V5qo/r9xvCrGFMbGg368jc0vrjOM02yGIBrtAjvywAtgy9 JDbw==
X-Gm-Message-State: AOAM530JuIwgf6LAQId+HjdlfWKvoAtrc9jBv5rtVc4rN+Yj6cdi5jNR CiNR0QsdcP5VeP/6kL9ZWZ0vj9TiPSz9cofyHkqk/3tuZZIQpg==
X-Google-Smtp-Source: ABdhPJzgwIq/ongLmF/odC/nWfrwd77aMmWDcQ/4Vtt6631LhPhWq3PMR31RpCfcRULX3ZF9v7jB8nGFpCcKtIAmkAg=
X-Received: by 2002:a2e:87c4:: with SMTP id v4mr38550435ljj.413.1609802425047;  Mon, 04 Jan 2021 15:20:25 -0800 (PST)
MIME-Version: 1.0
References: <CAOW+2dvUmjYXC8Yf9u=qwpJCR22BV_DjQsoOMNwPBOnoockVWA@mail.gmail.com>
In-Reply-To: <CAOW+2dvUmjYXC8Yf9u=qwpJCR22BV_DjQsoOMNwPBOnoockVWA@mail.gmail.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Mon, 4 Jan 2021 15:20:15 -0800
Message-ID: <CAOW+2dvDzT7Wva5sFvLc9xpiV=_hwZHsXKKoWncxGsbbwbSphA@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b41f7305b81b55a7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/0uZbZ83cY09ab60VyrAyfXpZpQs>
Subject: Re: [Webtransport] Reminder: WEBTRANSPORT WG Meeting January 12, 2021
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, 04 Jan 2021 23:20:29 -0000

--000000000000b41f7305b81b55a7
Content-Type: text/plain; charset="UTF-8"

My apologies for an error in the previous email.  The IETF WEBTRANS WG will
have a 90 minute Virtual Meeting on Tuesday, January 12, 2021 starting at 8
AM Pacific Time (16:00 UTC).  This is NEXT WEEK!

A list of interim meeting dates for IETF WGs is available here:
https://datatracker.ietf.org/meeting/upcoming





On Sun, Jan 3, 2021 at 5:16 PM Bernard Aboba <bernard.aboba@gmail.com>
wrote:

> The IETF WEBTRANS WG will have a 90 minute Virtual Interim Meeting on
> Tuesday, January 21, 2021, starting at 8 AM Pacific Time (16:00 UTC) .
>
> The meeting will be held on Google Meet at the following URL:
> https://meet.google.com/oqg-iprr-yab
> <https://www.google.com/url?q=https://meet.google.com/oqg-iprr-yab&sa=D&source=calendar&usd=2&usg=AOvVaw3V5vwjKG3WBuP9l6HEWcqu>
>
> Agenda is here:
> interim-2021-webtrans-01 : webtrans (ietf.org)
> <https://datatracker.ietf.org/meeting/interim-2021-webtrans-01/session/webtrans>
>
>
>

--000000000000b41f7305b81b55a7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">My apologies for an error in the previous email.=C2=A0 The=
 IETF WEBTRANS WG will have a 90 minute Virtual Meeting on Tuesday, January=
 12, 2021 starting at 8 AM Pacific Time (16:00 UTC).=C2=A0 This is NEXT WEE=
K!<div><br></div><div>A list of interim meeting dates for IETF WGs is avail=
able here:=C2=A0</div><div><a href=3D"https://datatracker.ietf.org/meeting/=
upcoming">https://datatracker.ietf.org/meeting/upcoming</a><br></div><div><=
br></div><div><br></div><div><br></div><div><br></div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Jan 3, 2021 =
at 5:16 PM Bernard Aboba &lt;<a href=3D"mailto:bernard.aboba@gmail.com">ber=
nard.aboba@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">The =
IETF WEBTRANS WG will have a 90 minute Virtual Interim Meeting on Tuesday, =
January 21, 2021, starting at 8 AM Pacific Time (16:00 UTC) .<div><br></div=
><div>The meeting will be held on Google Meet at the following URL:=C2=A0</=
div><div><a href=3D"https://www.google.com/url?q=3Dhttps://meet.google.com/=
oqg-iprr-yab&amp;sa=3DD&amp;source=3Dcalendar&amp;usd=3D2&amp;usg=3DAOvVaw3=
V5vwjKG3WBuP9l6HEWcqu" id=3D"gmail-m_-3684906066597449870gmail-ow832" style=
=3D"color:rgb(26,115,232);font-family:Roboto,Helvetica,Arial,sans-serif;fon=
t-size:14px;background-color:rgb(241,243,244)" target=3D"_blank">https://me=
et.google.com/oqg-iprr-yab</a><br></div><div><br></div><div>Agenda is here:=
=C2=A0</div><div><a href=3D"https://datatracker.ietf.org/meeting/interim-20=
21-webtrans-01/session/webtrans" target=3D"_blank">interim-2021-webtrans-01=
 : webtrans (ietf.org)</a><br></div><div><br></div><div><br></div></div></d=
iv></div>
</blockquote></div>

--000000000000b41f7305b81b55a7--


From nobody Fri Jan  8 12:01:27 2021
Return-Path: <bernard.aboba@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 3A6B83A1568 for <webtransport@ietfa.amsl.com>; Fri,  8 Jan 2021 12:01:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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_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 sys-ggV6hroO for <webtransport@ietfa.amsl.com>; Fri,  8 Jan 2021 12:01:22 -0800 (PST)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 7044E3A1491 for <webtransport@ietf.org>; Fri,  8 Jan 2021 12:00:51 -0800 (PST)
Received: by mail-lf1-x12a.google.com with SMTP id l11so25866038lfg.0 for <webtransport@ietf.org>; Fri, 08 Jan 2021 12:00:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=wj/dODdC+zx89Moea4ojQSjpZdDAeijkYLWgsQA9qXw=; b=XLJA/dUM6Cu6LXTBsHgDVrkTJJ2/DQa0WqnHFELzFY4tIqBTpZ7Yooh1yrlHVeAU+Z c5r7J3jxy/4bOfZ2MVyPJdNf1l4joZGE6ySFIgOZnXkVxrKzXqHP9IvwXZV3cmm45obY hQUmKGpr7WAR5ffD6yZenVLp6jxI9eDNUwd2D6gAAarhyOUP8mQ2lvK2hi4I5TX9GHt+ j4U4OPYvtniij51o+Il+ktooXG8kGNx2hO9X+y7f18AfCZhgcxjeGxS1cUxGam1TOQR9 GP2I2spaILTh4OE01xa+P3ViFWIPgGQGX7CngghT4bCiXAdfx7sLa1nezDdj7UWrVW5X L0JA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=wj/dODdC+zx89Moea4ojQSjpZdDAeijkYLWgsQA9qXw=; b=ixHPguGJN50up6W+4Qt8OuelvBXY76EE2CFSDpLQ9VuXqOwsl7NwIynUdV5aRvdY67 fu0em5Pqupm70fGHPFy0jE/LHo62+6Wa9ujaTLCa7Y5cfBtq79L3FDjm0wKhak2lIakV hqQzMx8mITvtNRx3RJ6L+Fd5YewNHSxxVyoOAgUsBGVC4s8fQLW4JxtQKoZHcO1HU5MR mBWCtkVlrJKodprJljJxPb7hTfrIPlHrObc0Yp8sA7zUjwpnGyf4sNAOV9+hUxrBaoII x8h8fsqrWXAR4WHz3IjYeCI6VmqjULuBv6b2PkFXyjySoxkmZNlcGaSNM6CydojbLSo1 0DkQ==
X-Gm-Message-State: AOAM533/6JCDq6T2AtlMomLt4Cmv4JSwZ9XJimaLEXCerUs1hH54RlDN T5IvRze7xbrt6qjodnKs2+uESndtPxNdsvTtvkBNwRw5mEE=
X-Google-Smtp-Source: ABdhPJxvrEf3Stwqyuk5YE8ZPmt6Mdx0LG/9OYxRiXqJirxSCXmsGB9yWHyZVatyNGdXGZmxHb8dY+YwksMicFgzm60=
X-Received: by 2002:ac2:4d2b:: with SMTP id h11mr2477521lfk.218.1610136049113;  Fri, 08 Jan 2021 12:00:49 -0800 (PST)
MIME-Version: 1.0
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Fri, 8 Jan 2021 12:00:39 -0800
Message-ID: <CAOW+2dvCF7UppqSG=7+Mq4w7cBZNWQewhnihU_UM25rMUr8HCw@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003f615605b8690392"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/2MeuDkC4skH67-73NF5yVeq0B1s>
Subject: [Webtransport] Virtual Interim Agenda and Volunteers
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: Fri, 08 Jan 2021 20:01:25 -0000

--0000000000003f615605b8690392
Content-Type: text/plain; charset="UTF-8"

A revised agenda for the WEBTRANS WG Virtual Interim on January 12, 2021 is
available here:
https://datatracker.ietf.org/doc/agenda-interim-2021-webtrans-01-webtrans-01/

We are currently looking for volunteers for Jabber Scribe as well as
Notetakers.

--0000000000003f615605b8690392
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">A revised agenda for the WEBTRANS WG Virtual Interim on Ja=
nuary 12, 2021 is available here:=C2=A0<div><a href=3D"https://datatracker.=
ietf.org/doc/agenda-interim-2021-webtrans-01-webtrans-01/">https://datatrac=
ker.ietf.org/doc/agenda-interim-2021-webtrans-01-webtrans-01/</a><br></div>=
<div><br></div><div>We are currently looking for volunteers for Jabber Scri=
be as well as Notetakers.</div></div>

--0000000000003f615605b8690392--


From nobody Sun Jan 10 13:04:00 2021
Return-Path: <bernard.aboba@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 4D1F53A12BB for <webtransport@ietfa.amsl.com>; Sun, 10 Jan 2021 13:03:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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_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 T0kEAB-RAqcl for <webtransport@ietfa.amsl.com>; Sun, 10 Jan 2021 13:03:58 -0800 (PST)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 B3A9F3A12BA for <webtransport@ietf.org>; Sun, 10 Jan 2021 13:03:57 -0800 (PST)
Received: by mail-lf1-x136.google.com with SMTP id o19so35020289lfo.1 for <webtransport@ietf.org>; Sun, 10 Jan 2021 13:03:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=M6dX5wdsSWxnp+XuDnpCmGbpWzk1zzmr8O/YTgW2Eb4=; b=Qw2fSHO6Qj/FiGk8hb1ZJ/wAzJNMndAikt+vPT2nC03tcoaXrtPFQERBeXes0FCyU0 zr7KsscUGYi51l+VOe88RK1LkOyjeQAlzs9Pj7G0ZthXYZZAwOd0KnqDq8BtgdrqPwho AQiXbtPCh40uliIbAJA0tzh54g/93KoVO1dwxqI64cC1j9HmU8a5Y3mzjmqGY0z6T7ib 1HxXgbReu3MxlZDgAVy1g4ZeWKJYJO7fQzht3gcBcU8Xo0KMk9SFSK30m8UqD2uWi0cX lF5z+JPeyzYfrk7Boz67Lgt26Zuj/LYz4VOsPqinBPueVzYZ8VFdrdT2WgmN7rk9ndgv VUQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=M6dX5wdsSWxnp+XuDnpCmGbpWzk1zzmr8O/YTgW2Eb4=; b=pBmGJ5hEBhXFcsFJxfQ4qhu5pt+zzQ2m2knfbptdgp7YbFFg+eB2Y7tWJ12/jP2RXS iKxJAOtKuThQpq+AuV4TNh46sDktnk0HpzVLdp3b9LUSkJ4YBY2jhOEcaR6swxEgKozg I0Udv6AfZKWsR+9kNVIfL31GKSl+SAihFM9N9MCtSZJB8bBm0HAXw5P1kP/JIUbOOEvk VliUeKgjGh81//L78qO4y/3ELOBkulR7bxbGbD55boFyUiB7Q/HufDk3350K2v2VhndL s3hzjWIvenN6zDH8m5LuhXAGHECPK1F/fIq3ERW6syL9vOo7VnHzSmV/egJoUeqmfjwX 1E+Q==
X-Gm-Message-State: AOAM532gRUrX4YuV6YfikXSd5jzQRz7qnZ+H4bKOUf5W5Vek9Co9MRg3 z4/CSlgvTyzOFsPIN7eebNjkTODVbtGjPoyr3rTx/64gElo=
X-Google-Smtp-Source: ABdhPJwO3I5/5l0jD+CwTLBt9AOVfBJW5tUnPjQQ2lgioa2PBD5LslNuAzX0Ia5gvMPtcGuePU7V9iEfiLJq2neOXdg=
X-Received: by 2002:ac2:46ee:: with SMTP id q14mr6267763lfo.145.1610312635333;  Sun, 10 Jan 2021 13:03:55 -0800 (PST)
MIME-Version: 1.0
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Sun, 10 Jan 2021 13:03:45 -0800
Message-ID: <CAOW+2dsANOTAAZDnOGv5_LpZO5-f5aE8n1OpSzfLy4_CcmxzQQ@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009b3f6605b89220a8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/wR_356kcczlJ6ZnzEMx1S9e8ClU>
Subject: [Webtransport] Virtual Bluesheets for WEBTRANS WG Meeting on Tuesday, January 12, 2021
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: Sun, 10 Jan 2021 21:03:59 -0000

--0000000000009b3f6605b89220a8
Content-Type: text/plain; charset="UTF-8"

Are located here:
CodiMD - Collaborative markdown notes (ietf.org)
<https://codimd.ietf.org/notes-ietf-interim-2021-webtrans-01-webtrans>

Note that a datatracker login is required to sign the virtual bluesheets

--0000000000009b3f6605b89220a8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Are located here:=C2=A0<div><a href=3D"ht=
tps://codimd.ietf.org/notes-ietf-interim-2021-webtrans-01-webtrans">CodiMD =
- Collaborative markdown notes (ietf.org)</a><br></div><div><br></div><div>=
Note that a datatracker login is required to sign the virtual bluesheets</d=
iv></div></div>

--0000000000009b3f6605b89220a8--


From nobody Sun Jan 10 16:15:33 2021
Return-Path: <mt@lowentropy.net>
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 37F2E3A13F0 for <webtransport@ietfa.amsl.com>; Sun, 10 Jan 2021 16:15:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=lowentropy.net header.b=bX7a4NiO; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=WjxA/f06
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 09aBG8jdCRdc for <webtransport@ietfa.amsl.com>; Sun, 10 Jan 2021 16:15:30 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A8C43A13EF for <webtransport@ietf.org>; Sun, 10 Jan 2021 16:15:30 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 033A25C00D8 for <webtransport@ietf.org>; Sun, 10 Jan 2021 19:15:29 -0500 (EST)
Received: from imap10 ([10.202.2.60]) by compute1.internal (MEProxy); Sun, 10 Jan 2021 19:15:29 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:date:from:to:subject:content-type :content-transfer-encoding; s=fm1; bh=IczQypaHwKjL40mEisIuUTGZhb ru/rDDbNUJ/vMy4Ds=; b=bX7a4NiOQvkyOuuGNi5WP92iUcAKzVYc5cmJ6EBFND DTaQQGLysu/KTWE1Tq7aY/Uw3BoTldaeMgTHoPuVncwP/GJuk22Aa7dQBxKki8N9 tqgWN/K6bqG1cdIhIS8Tz4IdoG/HzoSd5xFlcGbiOIYF5fEf3ckU5y8mU9H/NTv6 36Hu7Ol1cHgEjCQNsS7bPXMsWlAgfx65PT+D3iyv6b80nKRQLLbgESqfAljWN/4+ VxUA0tCz4IvBlBnKSrbIOhWzsVrz5pZQh6uRZx9yA31QEjJWFJifOP6Nv1jY3Gh2 Bewaz9aSH0J0QcBKqNzY3O/0R2cdgLu3OKi+OL608OAA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=IczQyp aHwKjL40mEisIuUTGZhbru/rDDbNUJ/vMy4Ds=; b=WjxA/f06rG3mmf1xqWjH38 6cnQQ3CbVRlsgadS39IGU0UnEItjDwXylayr/GIV0CbJjP+Ez8S7ibj9HqHo0BhO vbpyI+hHC7V8BRMbD0B6btCW0TwIR5Q79QIYHHVtASAuoCtKNfE2DWudCEPNcfzB L6J1Hd4gvvuN1mJnxnMJJEIeb6I5OvdHtawsWDZ2x78N9YNlw5UR5N1KAmZewoNO p4+nyBQfxbIHjDOqibYU61ja9ZnACpx8vdirdvavo1TMN6qOAbTeIzNBznBQ0ydn qb8ejZBtEV0nJxLGvw9+f6YxySmrvichmrv8/31HwG5aT+fBLCaqQreqPM/PZQzw ==
X-ME-Sender: <xms:oJj7X87R4-2kUfUoqjKeHAWVGmr9tSv0Wy_nRc07VvX1KckPQWNxAA> <xme:oJj7X96EXU4-vgBFOai8GC9_hx3Mw2Loqp81oHwLwvo3-o6OOpZwSkOxv4SeP-GFV sQkUKfn1ta1_R0n1ag>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrvdehtddgudejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfffhffvufgtgfesthhqre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnheptdeklefffefhueehvdejhf dtieeiudegvdelieevjeeffefgheehfedvteefjeffnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:oJj7X7deOVuiDtmNzyOdp-k0wrWTPO8XkQAzlCT89TYQhHhkp0U-kw> <xmx:oJj7XxIqHaqZHvpudhCSiRpjo9u9fy05K7m2f1F_dd-gW1uSqCO5mg> <xmx:oJj7XwLaEkMS4JkTIBSnL4UVVbuhEpJQY46ADA8JP4JjsWHKjAhWKw> <xmx:oJj7X1Vow_rtcsZbDjR4ZwpOzbNgH7_XFivlj739HtcRRblViQeRsA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 8E33820149; Sun, 10 Jan 2021 19:15:28 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-45-g4839256-fm-20210104.001-g48392560
Mime-Version: 1.0
Message-Id: <45d4958d-1ad5-40d2-8b02-39e5b3a8fcbd@www.fastmail.com>
Date: Mon, 11 Jan 2021 11:15:08 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: webtransport@ietf.org
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/do6GKRKxGb0fYMRVIMAo0bhtU6g>
Subject: [Webtransport] My thoughts on protocol selection
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, 11 Jan 2021 00:15:32 -0000

As the interim is at a time that is hazardous to my health, I thought I =
would share my opinions via email ahead of the meeting.  I will try to b=
e provide explicit positions and rationale for those positions.

The goal is to choose which protocols will support the API.  We've been =
presented with a matrix of 4 options.  On one axis, there are two UDP/QU=
IC-based options and two TCP-based options.  On the other, there are two=
 options that pool webtransport communications (with itself or HTTP), an=
d two options that require a new connection for each session/context/thi=
ngie.  I understand that the non-pooled TCP option is less well defined =
than other options.

My preference is to select a non-pooled option with a websocket-based fa=
llback.  I can live with a pooled approach.

I can see the merits of a pooled approach, both in terms of flexibility,=
 transport use, and other factors.  However, I think that the primary ad=
vantage of a non-pooled option is simplicity.  Implementation complexity=
 is only a small piece, I'm mostly concerned about ensuring that this is=
 a good fit for the sorts of deployment architectures that are used by m=
ost web developers.  My own experience deploying websockets, though admi=
ttedly a little dated now, shows that most developers don't share infras=
tructure with web hosting.   Furthermore, there are more complications t=
o deal with if we touch HTTP: managing inter-protocol prioritization, wh=
ich would be necessary to address in a pooled context, is non-trivial bo=
th from a protocol design perspective and challenging to deploy; identif=
ying connections with URIs in websockets turned out to be a major proble=
m; and likely other issues.  I'm confident that the complexities of a po=
oled approach can be overcome, but I tend to think that that choice woul=
d disproportionately privilege entities with greater engineering resourc=
es.  It would also take longer to standardize.

At the time I write this, Victor hasn't filled in his argument for why a=
 non-pooled protocol implementation is like a pooled implementation, so =
I can't respond to that directly.  Implementation of webtransport in a b=
rowser is likely as weird and atypical as anything else in browser-land,=
 so I'm not anticipating anything revelatory.

No doubt there is a lot more ground to cover here.  Intermediation optio=
ns for websockets are poor (though not non-existent despite some asserti=
ons I've heard) and webtransport is almost certainly the same.  I acknow=
ledge the fact that not addressing pooling could push toward proprietary=
 load balancing/aggregation designs.  However, the primary problem is no=
t lack of intermediation designs at the protocol layer, but the inabilit=
y of intermediaries to interact with the semantics of the data that is b=
eing exchanged.  This is a problem at a level that this working group is=
 not able to deal with.  We should be prepared to deal with any lower-la=
yer intermediation options that arise as we learn more about how this is=
 being deployed, but that is all.

I think that fallback is necessary.  It is true that many large entities=
 and incumbents will have existing infrastructure that they can fall bac=
k on, such that they can treat webtransport as just a way to access a be=
tter-performing transport.  However, not providing fallback would mean t=
hat we're making a deliberate decision to privilege those parties.  As m=
uch as not dealing with TCP would be easy, I have become convinced that =
to not provide a fallback would also be irresponsible.

The specific shape of fallback I am thinking of is a websocket connectio=
n that uses a newly defined "webtransport" (or "wt") subprotocol.  This =
subprotocol will need new affordances for unidirectional streams and dat=
agrams and some way to manage layering streams over the message-based ab=
straction.  Neither of those should be particularly difficult to manage.=


I am opposed to developing more than the two protocols necessary for hig=
h performance (UDP) and fallback (TCP).  I'm prepared for time to prove =
me wrong, but I would prefer to come to that realization through experie=
nce.

In reviewing slides, I see that Victor has proposed a new URI scheme.  I=
 think that this is sensible.  Not so much for the stated reasons, which=
 are fine, but more because it means we can use SVCB.  We might even con=
sider disallowing the use of A/AAAA with this new protocol.  The one pro=
blem I might anticipate with that is difficulty of doing local testing, =
but we're already hard-wiring localhost in other ways.

(Thanks to Bernard for sharing the unfinished slides with me ahead of ti=
me.)

---
Separately, the W3C group met last week and discussed requirements.  Thi=
s is my recollection of the list, which is likely incomplete/wrong to so=
me extent.

The group that met would like to ensure that datagram transport, or a si=
mulation thereof, is available in all options.  Though performance degra=
dation might occur in TCP, that is better than not having the mechanism.=
  Unless there is a stream-based substitute for datagrams (which I think=
 would not be a good idea), connection attempts should fail if the QUIC =
datagram extension cannot be negotiated.

(The API will likely include a flag to disable fallback, but that is not=
 necessarily a protocol-level concern.)

Some anti-requirements: The protocol MUST NOT carry HTTP state mechanism=
s: cookies, authentication.  The protocol MUST NOT use the same client-b=
ased certificates as HTTP.  Webtransport will need some way to integrate=
 with CSP and other policy mechanisms, but that doesn't mean that it nee=
ds to inherit the state management burdens of HTTP on the web.

There was also a lot of discussion about bandwidth estimation for video =
delivery, but I think that the conclusion was that it was hard and it mi=
ght need to be something we table for the moment.


From nobody Mon Jan 11 13:45:39 2021
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: webtransport@ietf.org
Delivered-To: webtransport@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CCCF3A1306; Mon, 11 Jan 2021 13:45:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IESG Secretary <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: webtransport@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161040153428.32343.10276377047534944404@ietfa.amsl.com>
Date: Mon, 11 Jan 2021 13:45:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/SzyLouZfxKQisx49jSssoqQvJsk>
Subject: [Webtransport] WebTransport (webtrans) WG Virtual Meeting: 2021-01-12 CHANGED
X-BeenThere: webtransport@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Jan 2021 21:45:34 -0000

MEETING DETAILS HAVE CHANGED.  SEE LATEST DETAILS BELOW.

The WebTransport (webtrans) WG will hold
a virtual interim meeting on 2021-01-12 from 08:00 to 09:30 America/Los_Angeles (16:00 to 17:30 UTC).

Agenda:
WEBTRANS WG Virtual Interim

January 12, 2021
8:00 AM - 9:30 AM Pacific Time
Meeting URL: https://meet.google.com/yux-tvmm-jpj
Etherpad (and virtual bluesheets):
https://codimd.ietf.org/notes-ietf-interim-2021-webtrans-01-webtrans

1. Preliminaries, Chairs (10 minutes)
Note Well
Jabber Scribe, Note Takers
Speaking Queue Manager (David Schinazi)
Agenda Bash
W3C Update

2. The WebTransport Protocol Zoo, Victor Vasiliev (65 minutes)
https://tools.ietf.org/html/draft-ietf-webtransport-overview
https://tools.ietf.org/html/draft-vvv-webtransport-quic
https://tools.ietf.org/html/draft-vvv-webtransport-http3

3. Hums, Wrap up and Summary, Chairs &amp; ADs (15 minutes)

Information about remote participation:
Google Meet: https://meet.google.com/yux-tvmm-jpj


From nobody Mon Jan 11 13:52:43 2021
Return-Path: <bernard.aboba@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 7B57D3A1311 for <webtransport@ietfa.amsl.com>; Mon, 11 Jan 2021 13:52:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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_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 SLGQFimgZ1MS for <webtransport@ietfa.amsl.com>; Mon, 11 Jan 2021 13:52:41 -0800 (PST)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 EA0363A1310 for <webtransport@ietf.org>; Mon, 11 Jan 2021 13:52:40 -0800 (PST)
Received: by mail-lj1-x233.google.com with SMTP id p13so613889ljg.2 for <webtransport@ietf.org>; Mon, 11 Jan 2021 13:52:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=GiSY6H4Z2lJo9yAW0Wrxl/7GiM5grwxBii4jtQhQNv8=; b=SxZR8RZYnbrkjGxO/ExOjplh+5+WG/CWdIis3A7IWUkU/sco1z/3BzSTlhwhhiQaHV +S2PEJ9Y0hCzXK6fL1PtnOkNbONMs3IXxKX0lxInjoMijn9TkmqpPRe1tSls5vnvgkzM BXvvi5MO03Y0ESM9R6ndSjgliurJdnH6ZVlCEWH7P55AROvCEFPh2ig6Zza6+/cfyrCz H9zoFH9BqH8A+wo3LH7G4TiEf1cIHm+4x6m+EZcse22zVlBJLe2UsjI9zFS/YcSNHBNe /lFv9ZJS2iNofwbxwB44cdu4BBlMDfPkbK3HVAVGx+l+T3LL57twp4J/2pGZ9/3unxmY u20Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=GiSY6H4Z2lJo9yAW0Wrxl/7GiM5grwxBii4jtQhQNv8=; b=CU0bdzIZdaGCvs4Rfj0R7aNHvGxCGJfKChQpYE+cxB2CdExEgWTEUctyTbSS5lgbBG agMincKh9PPdoHQzSDLq9t9JvCBeL34nIxa++owU7sG4h4ckXfp0sNfwaRT4MiY8T5Wj VmaQChBwMGJRXpNTRnKA3IOQBmtU0HZpur2NX8O/pjsn9qHWMNwo/68tJ5eFOCUCMNE1 RTpXi31Ze+Ecu5vpAP4S+G5msYo3F3UT3ScdCncZkGGSeQW1nRcspem17XoM9GNv4W4N mz4nd1Mw/6O4gm9kF7zCGuEYwfTqsrdVokrBre3rq5RMUAp8h9jn1CiknAqjLNbJciVd 1nIw==
X-Gm-Message-State: AOAM533IKQDdOgegdXubhyXzI9KsVOtd52W8L68cChYtb3hB3+3VNeup nkamvIuIxOBrz6tMCtin6y67+fhKpruOQ6SEH6V4DRF+x8k=
X-Google-Smtp-Source: ABdhPJyl8slnEzyREADu5JYDSpI1drUe8eDj4loLMQG57HeVvpuM+3h7+rz8Hswb7TVoIHZETyj5yPPlOI/gzULVdRc=
X-Received: by 2002:a05:651c:316:: with SMTP id a22mr609730ljp.473.1610401958699;  Mon, 11 Jan 2021 13:52:38 -0800 (PST)
MIME-Version: 1.0
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Mon, 11 Jan 2021 13:52:28 -0800
Message-ID: <CAOW+2du7nGKAbjj0095xGtUwgWybm=BA7=FqNXPSdbmYbXeDhA@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b1a95605b8a6ec53"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/DvKVCBdhcjHxYnn-MamWaWhOF_A>
Subject: [Webtransport] IETF WEBTRANS WG Meeting tommorrow
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, 11 Jan 2021 21:52:43 -0000

--000000000000b1a95605b8a6ec53
Content-Type: text/plain; charset="UTF-8"

The IETF WEBTRANS WG will hold a virtual interim meeting tomorrow, January
12, 2021, starting at 8 AM Pacific Time.

In order to better support the meeting, we have changed the meeting URL to
provide Google Meet Enterprise features (such as the ability to join
without requiring a gmail account).

Please use the revised Meeting URL provided on the page with the Agenda and
Virtual Bluesheets:
CodiMD - Collaborative markdown notes (ietf.org)
<https://codimd.ietf.org/notes-ietf-interim-2021-webtrans-01-webtrans>

Other info of potential relevance:

1. Please fill out the virtual bluesheets (IETF datatracker account
required)
2. Volunteers for notetaking (using Etherpad) and Jabber scribe are
solicited (please send email to the Chairs)

--000000000000b1a95605b8a6ec53
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">The IETF WEBTRANS WG will hold a virtual =
interim meeting tomorrow, January 12, 2021, starting at 8 AM Pacific Time.=
=C2=A0<div><br></div><div>In order to better support the meeting, we have c=
hanged the meeting URL to provide Google Meet Enterprise features (such as =
the ability to join without requiring a gmail account).=C2=A0</div><div><br=
></div><div>Please use the revised Meeting URL provided on the page with th=
e Agenda and Virtual Bluesheets:=C2=A0</div><div><a href=3D"https://codimd.=
ietf.org/notes-ietf-interim-2021-webtrans-01-webtrans">CodiMD - Collaborati=
ve markdown notes (ietf.org)</a><br></div><div><br></div><div>Other info of=
 potential relevance:=C2=A0</div><div><br></div><div>1. Please fill out the=
 virtual bluesheets (IETF datatracker account required)</div><div>2. Volunt=
eers for notetaking (using Etherpad) and Jabber scribe are solicited (pleas=
e send email to the Chairs)</div><div><br></div><div><br></div></div></div>

--000000000000b1a95605b8a6ec53--


From nobody Tue Jan 12 05:32:22 2021
Return-Path: <bernard.aboba@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 4E3673A1251 for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 05:32:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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_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 awvJNfpO6jFq for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 05:32:19 -0800 (PST)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 9FD1B3A123E for <webtransport@ietf.org>; Tue, 12 Jan 2021 05:32:18 -0800 (PST)
Received: by mail-lf1-x136.google.com with SMTP id m12so3359559lfo.7 for <webtransport@ietf.org>; Tue, 12 Jan 2021 05:32:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=s+FCCs8Fgz/o+wZSHrofWf6Mf1sCl+XBMaIrhzkxWvo=; b=VL/wv9AUyoMq1pURjXo/NR38JBBIyLelMS91FONnYzrtuIzedBzUwgjxmXs3/dMrqa 6fKCdQf/Tzgf2benQqbB9TzZLWqmXTEJtJJkkX4qRqIoQiWAISC186OeC0osSECBTEvD 387wqmdFJp4s8xuxcZ6Dw7jGhknIOUJs0H3iEHdorUOj/93+o3l/EBiKHJZD12Y/lHAO 1CEfgLprEBlGkgLU44lEpXxgtt0+sD+/N6F4MWpvYvxdXpm0CE9QUMADQ8z7bKu04+nP kIgCecDgALMjVjOzinLXrsECKwGdrlyCc+pXaeJmEaHqoPslL35sJTvLlpxuI3KbT3ke +0jw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=s+FCCs8Fgz/o+wZSHrofWf6Mf1sCl+XBMaIrhzkxWvo=; b=KOnOnE+DkFMtehrKuFKEZy1Mxls6yu1edT47Q3lVVKxyoeHt82qOIOVkoMjSOOJlxm y9Lzzr/K+RMuNIhIKhXRRd8j8j9xTtXhQMUIUeq/TJHbki/4oJ6C2pnbgqGPrteyFNdz IqYkbb+gDPq1dktiJawqftx6HBHY1fxDvzAjh2ussy7Nc6ef0nrVDKqzWhF+/YHbJjQy 7SUYj9hxTwOsgM3zeFoWXdc5OftqWR3w8u55zh7HW1YZT9m6/nqN5fuD5xq/t1i4IGjF lr74cZldBl9V8GGhjnmbQoWpzIurP00vyRq9H90d1+faYnNVHAWKUrQL+wEoUFgpbN/o z9yg==
X-Gm-Message-State: AOAM532yJ46cKh0cKvtIHhHKyCYcSiY+HKFh5zO3uFv1ExUErGdTq+dV 8mqY67bL8NtIkr5lzUaQQ+jgTrM8zveKWrUokEbZpi8FIX8=
X-Google-Smtp-Source: ABdhPJzD02JQMyJQkDwZp12S+BSdxYIpbe63hA/30wDz493T4IxEb/JgrOmfW7n+myvxwBkLkcK0/iDBeQshc4jH/0Y=
X-Received: by 2002:a19:2358:: with SMTP id j85mr2208805lfj.264.1610458334654;  Tue, 12 Jan 2021 05:32:14 -0800 (PST)
MIME-Version: 1.0
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Tue, 12 Jan 2021 05:32:05 -0800
Message-ID: <CAOW+2dtgqWS7wx98v_8=9yj=MaouVLfZ-LJ6NGB2KfdM8CVe3Q@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f675d405b8b40ca4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/jUGOfvXtDMNGtXxhl25hmxnvci4>
Subject: [Webtransport] Today's Virtual Interim Meeting
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: Tue, 12 Jan 2021 13:32:20 -0000

--000000000000f675d405b8b40ca4
Content-Type: text/plain; charset="UTF-8"

Agenda, Virtual Bluesheets and Meeting Parameters are available here:
CodiMD - Collaborative markdown notes (ietf.org)
<https://codimd.ietf.org/notes-ietf-interim-2021-webtrans-01-webtrans>

Meeting materials are here:
interim-2021-webtrans-01 : webtrans (ietf.org)
<https://datatracker.ietf.org/meeting/interim-2021-webtrans-01/session/webtrans>

Meeting operation:

1. Please fill out the virtual bluesheets (Datatracker login required)
2. The meeting will be recorded.
3. Please state your name before speaking.
4. Google Meet will be used for the meeting. Chat  will be used for hums.

--000000000000f675d405b8b40ca4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">Agenda, Virtual Blueshee=
ts and Meeting Parameters are available here:=C2=A0<div><a href=3D"https://=
codimd.ietf.org/notes-ietf-interim-2021-webtrans-01-webtrans">CodiMD - Coll=
aborative markdown notes (ietf.org)</a></div><div><br></div><div>Meeting ma=
terials are here:=C2=A0</div><div><a href=3D"https://datatracker.ietf.org/m=
eeting/interim-2021-webtrans-01/session/webtrans">interim-2021-webtrans-01 =
: webtrans (ietf.org)</a><br></div><div><br></div><div>Meeting operation:=
=C2=A0</div><div><br></div><div>1. Please fill out the virtual bluesheets (=
Datatracker login required)</div><div>2. The meeting will be recorded.</div=
><div>3. Please state your name before speaking.=C2=A0</div><div>4. Google =
Meet will be used for the meeting. Chat=C2=A0 will be used for hums.=C2=A0<=
/div></div></div></div>

--000000000000f675d405b8b40ca4--


From nobody Tue Jan 12 09:26:30 2021
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 DD8D13A0D78 for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 09:26:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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_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 BgwjqAuEx8vW for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 09:26:26 -0800 (PST)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (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 3010E3A0DBC for <webtransport@ietf.org>; Tue, 12 Jan 2021 09:26:02 -0800 (PST)
Received: by mail-pf1-x434.google.com with SMTP id w2so1764343pfc.13 for <webtransport@ietf.org>; Tue, 12 Jan 2021 09:26:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=L9nziwVXvQ5pYel/xCmEQBlh06g1J9XeQlWPq8hOOmI=; b=GZyDsXXVd7Oyk+f6aciSJ3KZhf4xPH/TVKvGTRKI4l+cRAAon+XKC7rDciYGnsc+fQ 1O/78zyZRYiqR0YAjb03nl0uMj/HXe6sYxFRoBkzVzfIhCxefTLvOqFvyoIrgGI13SQm 6otLFiF8yP2kdU/sjfIcChuCs8xIp+SK5XDGU5vP9zt410ZTueANP6drEjLguFczWPKL NiRWPreQXz9KM4nS3ctdPGBa+vWFWjJguHLB+sf8D6njak9mDqlcnOnyBeWJkO2xcyTg 4WYapyxBhgOq4paWJGltJ9MrXLGGfAteo4cO/0RI4cZE9latXd5OWJbWaz5x/Qmq5JhO B2yw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=L9nziwVXvQ5pYel/xCmEQBlh06g1J9XeQlWPq8hOOmI=; b=tMqKGJTgYE8dJ108O7iIopOqL+Ae+saEfeXD4CsuYa2lcihrJv5YAH4sR/Q46F6M7m 7FbUncuAnFCUGqRXH0LpcqA+rDJTZge+Z685cn/jv8rTxBIGtqLDyIyBUwizS2x0sjjh owSzGxU5fXtLr+ob3/kBorPqDKm7Sz8tDj4NHqGakjVZYf1xZbmfk1nVYSQyia93VuyN 1C0QIA+a+Jb85csQvr4gzWYmEOV1G7SyonLOZPX/CzZ2BuNxFs/bsKx0k3bEKw6qsX8J 0sDvidOt+sga5hYdqFJ60fB9jL/o+ZLuUaRTC9g/+Q0JWhrbMhQkdTt8CJuxA5eV35KB zd8w==
X-Gm-Message-State: AOAM532CRquj1YogK9wiuZayfFR/su32QGGY24iuWbIVZg67i4rwfh2v eAJtPxyWIFTSQbhnRokahXZKyqL2ct/7PU/CEa29UZIeKzE=
X-Google-Smtp-Source: ABdhPJyFzbp14wW5qi0HxnA2K/6rMvhEr9H+I6l7/DgInwFTv1yMQEQXaNSpBU7+wk7et237lo+WvqRmma75Y5vgIJo=
X-Received: by 2002:a62:5a86:0:b029:1ae:6b45:b6a9 with SMTP id o128-20020a625a860000b02901ae6b45b6a9mr304439pfb.7.1610472361102; Tue, 12 Jan 2021 09:26:01 -0800 (PST)
MIME-Version: 1.0
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Tue, 12 Jan 2021 09:25:49 -0800
Message-ID: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000001129405b8b75138"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/9k27ZTwBlg9ncsZQXymg-jAfUOA>
Subject: [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: Tue, 12 Jan 2021 17:26:28 -0000

--00000000000001129405b8b75138
Content-Type: text/plain; charset="UTF-8"

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

--00000000000001129405b8b75138
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi WebTransport enthusiasts,<br></div><div><br></div>=
<div>Today we had an interim of the IETF WEBTRANS WG,</div><div>where we re=
ached consensus in the (virtual) room on</div><div>the following questions:=
</div><div><br></div><div>Question 1: number of protocols<br></div><div>=C2=
=A0 =C2=A0 Should the working group adopt only one UDP-based transport?<br>=
=C2=A0 =C2=A0 1A: only one transport (QUIC or HTTP/3)<br>=C2=A0 =C2=A0 1B: =
multiple transports (QUIC and HTTP/3)<br></div><div><br></div><div>The cons=
ensus was option 1A.</div><div><br></div><div>Additionally, we noted that t=
his does not preclude=C2=A0us from</div><div>building a second protocol at =
a later date if new information</div><div>emerges.</div><div><br></div><div=
>Question 2: UDP-based protocols<br></div><div>=C2=A0 =C2=A0 Which UDP-base=
d option should we adopt as a starting</div><div>=C2=A0 =C2=A0 point for We=
bTransport protocol?<br>=C2=A0 =C2=A0 2A: WebTransport over HTTP/3<br>=C2=
=A0 =C2=A0 2B: WebTransport over QUIC directly (separate ALPN)<br></div><di=
v><br></div><div>The consensus was option 2A.<br></div><div><br></div><div>=
Additionally, we discussed pooling and decided that we would</div><div>not =
allow pooling in=C2=A0WebTransport over HTTP/3 for now, due</div><div>to th=
e complexities of pooling.</div><div><br></div><div>We&#39;d like to confir=
m this consensus on the list. If you disagree</div><div>with these points, =
please reply on the list. If you do so, please</div><div>state how strongly=
 you feel - whether you are expressing a</div><div>preference, or an impera=
tive. Please also provide as much</div><div>detail as possible to explain y=
our position. Please also respond</div><div>if you support this consensus -=
 a simple &quot;I support this consensus&quot;</div><div>email to the list =
would be helpful.</div><div><br></div><div>We&#39;ll be running this consen=
sus call for two weeks, please reply</div><div>before 2021-01-26, the chair=
s will determine consensus on that date.</div><div><br></div><div>Thanks,</=
div><div>David</div></div>

--00000000000001129405b8b75138--


From nobody Tue Jan 12 09:32:30 2021
Return-Path: <ianswett@google.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 C380A3A0ED1 for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 09:32:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.971
X-Spam-Level: 
X-Spam-Status: No, score=-17.971 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 oTnBKBL7mmK2 for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 09:32:20 -0800 (PST)
Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (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 C944B3A0E89 for <webtransport@ietf.org>; Tue, 12 Jan 2021 09:32:19 -0800 (PST)
Received: by mail-wr1-x433.google.com with SMTP id m4so1997592wrx.9 for <webtransport@ietf.org>; Tue, 12 Jan 2021 09:32:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DnLXshIdfwu3xgmEMsGn3fYwvoM16hY6gy+HPfqGHGc=; b=IGk8aVkkJNFzb4z06oK3fAHBBSnpBst7YOCSFEVkKitkdDk02LCdErP7aTAmlnHBEa N9gGGA+QMEuN+SJ50Ipl9RRoxd5EDAceCcy3FHbr2LfntXA74hBLKZhrwFtxN1ycl5i2 rdwe/HwSPnat6O5Oh+vFQr4bgQW9fWVdUSET+x80tRdzuhDPp2nyiXM/bdTcupmFfEwQ zexHIj7NWrBC8/VdQJTI9ayIdB+oToo6xRF06GBxGhEb06DmrvZWBin0xkEh/56KQhr8 xMXf039Fjq1Xu/8q2SRRe//JCEbd4l0SGPX420XyWGBGPO17ujafeywd91Ld2Kk6w/GD K+cA==
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=DnLXshIdfwu3xgmEMsGn3fYwvoM16hY6gy+HPfqGHGc=; b=Jpq6ZwORdebXfMjZ9YxgUIyz6e3bp1XNxxzhNNGm9ulWKFxUwFVjji7kgYPiXtaQVk rYDQzepie5pZpO2cyIkPEvJaoFqpTqORrGYFnQqChNgk3DMnJz1C4H8oC9qeIgLeEdvM Wzs1CzKVVkDvV7ekeZoPuZHUrUDV0B5f9AAy0ld8AYLmuIsn/zcYKARTEmqdyi0V9cPI U8UZRqMQA/REQInUUPs129Dlvr34E2oaoO3xjRgRIDf9RIeUQMEhUOsJliQ2Bnq9qKtc m0Do6Uth7QxXYwEsN1Da7nffuweSciTm4jIxkKETVTL0kzbWGjXxATNCJX2NwePdcdA0 xjcQ==
X-Gm-Message-State: AOAM530Ngf2CC2YiWtbtVj5ywxitWkPMidvyErfgRpo8jwrmkURcIyjA K+FufdXLiR5quFNrU6c7YWA50l01wfGM+3jmoh0k9A==
X-Google-Smtp-Source: ABdhPJzmjqDsFQt0sSpmw67vblebWZuWTMTbxBmM1nlGhB9t4ozcdMoMLfU/WAGfcyBl++0y9GS9f47qtt1S5T+4cBU=
X-Received: by 2002:a05:6000:114e:: with SMTP id d14mr4691008wrx.176.1610472738029;  Tue, 12 Jan 2021 09:32:18 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com>
In-Reply-To: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Tue, 12 Jan 2021 12:32:05 -0500
Message-ID: <CAKcm_gMHZxARh8QyvazwwowXkq6FBSkTWg_cWW9f0SvF9OjvgQ@mail.gmail.com>
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000078dbf705b8b767aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/zYsctd8z5jJxfCmyK6WUaVZNHFU>
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: Tue, 12 Jan 2021 17:32:29 -0000

--00000000000078dbf705b8b767aa
Content-Type: text/plain; charset="UTF-8"

I support this consensus.

I do have concerns about the complexity of different types of pooling, but
I'm sure we'll discuss those in the future.

On Tue, Jan 12, 2021 at 12:26 PM 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
> --
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport
>

--00000000000078dbf705b8b767aa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I support this consensus.<div><br></div><div>I do have con=
cerns about the complexity=C2=A0of different types of pooling, but I&#39;m =
sure we&#39;ll discuss those in the future.</div></div><br><div class=3D"gm=
ail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 12, 2021 at 12=
:26 PM David Schinazi &lt;<a href=3D"mailto:dschinazi.ietf@gmail.com">dschi=
nazi.ietf@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><div dir=3D"ltr"><div>Hi WebTransport enthusiasts,<br></=
div><div><br></div><div>Today we had an interim of the IETF WEBTRANS WG,</d=
iv><div>where we reached consensus in the (virtual) room on</div><div>the f=
ollowing questions:</div><div><br></div><div>Question 1: number of protocol=
s<br></div><div>=C2=A0 =C2=A0 Should the working group adopt only one UDP-b=
ased transport?<br>=C2=A0 =C2=A0 1A: only one transport (QUIC or HTTP/3)<br=
>=C2=A0 =C2=A0 1B: multiple transports (QUIC and HTTP/3)<br></div><div><br>=
</div><div>The consensus was option 1A.</div><div><br></div><div>Additional=
ly, we noted that this does not preclude=C2=A0us from</div><div>building a =
second protocol at a later date if new information</div><div>emerges.</div>=
<div><br></div><div>Question 2: UDP-based protocols<br></div><div>=C2=A0 =
=C2=A0 Which UDP-based option should we adopt as a starting</div><div>=C2=
=A0 =C2=A0 point for WebTransport protocol?<br>=C2=A0 =C2=A0 2A: WebTranspo=
rt over HTTP/3<br>=C2=A0 =C2=A0 2B: WebTransport over QUIC directly (separa=
te ALPN)<br></div><div><br></div><div>The consensus was option 2A.<br></div=
><div><br></div><div>Additionally, we discussed pooling and decided that we=
 would</div><div>not allow pooling in=C2=A0WebTransport over HTTP/3 for now=
, due</div><div>to the complexities of pooling.</div><div><br></div><div>We=
&#39;d like to confirm this consensus on the list. If you disagree</div><di=
v>with these points, please reply on the list. If you do so, please</div><d=
iv>state how strongly you feel - whether you are expressing a</div><div>pre=
ference, or an imperative. Please also provide as much</div><div>detail as =
possible to explain your position. Please also respond</div><div>if you sup=
port this consensus - a simple &quot;I support this consensus&quot;</div><d=
iv>email to the list would be helpful.</div><div><br></div><div>We&#39;ll b=
e running this consensus call for two weeks, please reply</div><div>before =
2021-01-26, the chairs will determine consensus on that date.</div><div><br=
></div><div>Thanks,</div><div>David</div></div>
-- <br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport=
</a><br>
</blockquote></div>

--00000000000078dbf705b8b767aa--


From nobody Tue Jan 12 09:34:13 2021
Return-Path: <bernard.aboba@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 934E13A0DEB for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 09:34:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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_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 EwmtWDBzZncI for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 09:34:11 -0800 (PST)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 09C073A0DE4 for <webtransport@ietf.org>; Tue, 12 Jan 2021 09:34:11 -0800 (PST)
Received: by mail-lj1-x235.google.com with SMTP id w26so3767362ljo.4 for <webtransport@ietf.org>; Tue, 12 Jan 2021 09:34:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=Zh5RSNZQgFXTXlEdONY41LrCYNOz0pLBF53P9NfCaJo=; b=iIP89DZlPFQ4bdSBM5CIwQjzjSB3cwtdc/FDWktY1MksYBeaNIvLwWEtQbr2GqCQqS ZQi1lWLlyzUlCwvjfAHSNNO3Vcoe26GIo2yQ2yfoj+1bCwwpr4Sw1i6TxUnodYAUWTcz fnWCC1/ipL7XpHoIk7r4DWMztIU71giwSyIPoq2hDmsnNqxUWpYT1p9T6KvY7qP4KnrH ngj1XioCHI7T8HJi6mIc/yQ3wGMAwrZDyzvGe1MawuwT7KMPV7CyPt7vzWDonuYjDqKa CcmQVLHC3XnRBS1EfPx+ds2ry1l2Rj0r4ndlPA1f4SgrT5kS1ei2oQ473vQ8SxHPiZal giyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Zh5RSNZQgFXTXlEdONY41LrCYNOz0pLBF53P9NfCaJo=; b=k2ijnTqx8rEn5yCrj84gTiEXSV3ECFND1dSWREolZiCmlRfYQ2qf2TWbTMzA08PD6F wbDakESwTXB4V8WWDAXBeGlZj8B5S9mlo+BfAFtgJo8VqTmV4mTJDQSTwKW518jotC1q ME3V2nKX/9FW1GE3UPslZWsF8clzy86gVuNe25LFl/El+4n9KfR+BFEhYbv4QgQB+g14 LudV0gNi0YMopoiFW8XlY6onWApP07fsrfB+7hz9UwQ/OHsiP3EjrTYBsNivTCy8kKSD 8umvnIrpaBbDODSARW/+tkmAacTMZLQt0nKTx5LdX12u5/LK5S7eQWW/J7Gr4OY+Er0a +9mA==
X-Gm-Message-State: AOAM5325wjRVDn3LDfpMHnwnsfA4cmywCdNovtfavlIA0Srh/NsHoYdv 4JYC59J7pZnOXi+fkgfSOP0WHRkTau3jkPS1MvgQaZXCDOA=
X-Google-Smtp-Source: ABdhPJwGn2vrlt/tFTXYid+OYelWT/eaFEfdwfx+z96W9k9g+xap7QqqGuew4ZS9T+wXmwTA40O0stqa7t9egYDTIuM=
X-Received: by 2002:a2e:6e11:: with SMTP id j17mr125307ljc.337.1610472848755;  Tue, 12 Jan 2021 09:34:08 -0800 (PST)
MIME-Version: 1.0
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Tue, 12 Jan 2021 09:33:59 -0800
Message-ID: <CAOW+2duTiV=zxXpL6qyyBCASbtMLNgsBA5vVetrvbHc0f8=K-g@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001218c305b8b76e2c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/0kIX8nK37mdryHjy0r0e_C0Xp8c>
Subject: [Webtransport] Meeting Minutes
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: Tue, 12 Jan 2021 17:34:13 -0000

--0000000000001218c305b8b76e2c
Content-Type: text/plain; charset="UTF-8"

Thanks to today's notetakers (Robin Marx and Spencer Dawkins), minutes of
today's WEBTRANS WG Virtual Interim are now available:
https://datatracker.ietf.org/meeting/interim-2021-webtrans-01/session/webtrans

--0000000000001218c305b8b76e2c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks to today&#39;s notetakers (Robin Marx and Spencer D=
awkins), minutes of today&#39;s WEBTRANS WG Virtual Interim are now availab=
le:=C2=A0<div><a href=3D"https://datatracker.ietf.org/meeting/interim-2021-=
webtrans-01/session/webtrans">https://datatracker.ietf.org/meeting/interim-=
2021-webtrans-01/session/webtrans</a></div><div><br></div></div>

--0000000000001218c305b8b76e2c--


From nobody Tue Jan 12 09:35:48 2021
Return-Path: <bernard.aboba@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 65E933A0DFB for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 09:35:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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_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 vFmQyrewuUuZ for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 09:35:44 -0800 (PST)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 6F6AE3A0DF3 for <webtransport@ietf.org>; Tue, 12 Jan 2021 09:35:44 -0800 (PST)
Received: by mail-lf1-x12f.google.com with SMTP id h205so4600735lfd.5 for <webtransport@ietf.org>; Tue, 12 Jan 2021 09:35: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:from:date:message-id:subject:to :cc; bh=BjoJaijO6ExNrYR0InRxMI3mCQkz+NyLS4ZJd2gzzSk=; b=ellJ64EdnYpgRoOItd32IKYtXzgBd5POzamJ7V8Ov1PpSvABOIIwr29BiKT9CfxDYE lbF8W6a1xTLwYZmRjTlzUmdorQX4d4QJWjfgEk6kUDTn+vI+paeqcsNB9rspi2+y96Si 0fYY/EZi8jIw6/r5Bab7/SWRNMyhgCOrh2QKvoQHE9TmO9gB9aMr4VBRs4Z6aseoo79o is4f4RkZ7HJK1xFGBVnqvcrEOZpJPRTfVkXr6eEZB9FLxxJEfWQVbIih3FRm00Kjq55c 64Pgptb4wXYibzz92n/cQbuu62ZOxKzNa6WG6Tnn8wQz0PktoWxAiIE3gXVVhR2/SoUl ebeQ==
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=BjoJaijO6ExNrYR0InRxMI3mCQkz+NyLS4ZJd2gzzSk=; b=apjihLOJTX7B825aDmYnWPTY1FtAUAnvGYpvaN6f+k0XOjAJJcrERkJhdiUaZD5ZTw f2sTf+N8CDJkcxVW9P+4v/gU2+T9BjZjpm3ONnajNA4nAfIeQBh2YvdWBlv7lpr80tFN ZEx4BuVD61B9qOeMzJDKp+88HVkiUNKF1sVnvKcbE+0jli1kY2g4Dgxn68FnU/cKvAVQ iafBM0o/6jpdGIBnLYSO6wfB0VKWkczCsy/BvUEkBUC17JMhtnLwY5XFSXVe/+SoinAh +/ISmRJIWP+5SuOpQ+Dkj2puOJbd/ip5MBkD6hTFWVtmTx1dmYeop4l1fjCI9ketoXwx DIGg==
X-Gm-Message-State: AOAM533t4qpA/1ooOt7JmCmE81M/sE22DOKhvYHDWYM4BEF6fcObnyZa k8NYn+tY+tEblQAbli21gliAfduQ5QBA1AAPVfY=
X-Google-Smtp-Source: ABdhPJw/znfo4z29l/g5k/J53jbl29JbIb0Rmg6B9mFAmXIauN1mTezsVCJkCPO7LVQYuLsc+kcy3+454oXY+v+XsAI=
X-Received: by 2002:a19:8214:: with SMTP id e20mr29656lfd.16.1610472942148; Tue, 12 Jan 2021 09:35:42 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <CAKcm_gMHZxARh8QyvazwwowXkq6FBSkTWg_cWW9f0SvF9OjvgQ@mail.gmail.com>
In-Reply-To: <CAKcm_gMHZxARh8QyvazwwowXkq6FBSkTWg_cWW9f0SvF9OjvgQ@mail.gmail.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Tue, 12 Jan 2021 09:35:33 -0800
Message-ID: <CAOW+2dt0J3i=Akj4NBbyqSXSzff_ARqe6wV94mDzmYkZN+whjQ@mail.gmail.com>
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: David Schinazi <dschinazi.ietf@gmail.com>, WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a320dd05b8b773a4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/eO6LqBbRUig_kHGnxbgzY6BEZDc>
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: Tue, 12 Jan 2021 17:35:46 -0000

--000000000000a320dd05b8b773a4
Content-Type: text/plain; charset="UTF-8"

I also support the consensus, with concerns about pooling (particularly
pooling of HTTP/3 and H3Transport).

On Tue, Jan 12, 2021 at 9:33 AM Ian Swett <ianswett=
40google.com@dmarc.ietf.org> wrote:

> I support this consensus.
>
> I do have concerns about the complexity of different types of pooling, but
> I'm sure we'll discuss those in the future.
>
> On Tue, Jan 12, 2021 at 12:26 PM 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
>> --
>> Webtransport mailing list
>> Webtransport@ietf.org
>> https://www.ietf.org/mailman/listinfo/webtransport
>>
> --
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport
>

--000000000000a320dd05b8b773a4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I also support the consensus, with concerns about pooling =
(particularly pooling of HTTP/3 and H3Transport).=C2=A0</div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 12, 2021=
 at 9:33 AM Ian Swett &lt;ianswett=3D<a href=3D"mailto:40google.com@dmarc.i=
etf.org">40google.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">I support this consens=
us.<div><br></div><div>I do have concerns about the complexity=C2=A0of diff=
erent types of pooling, but I&#39;m sure we&#39;ll discuss those in the fut=
ure.</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gm=
ail_attr">On Tue, Jan 12, 2021 at 12:26 PM David Schinazi &lt;<a href=3D"ma=
ilto:dschinazi.ietf@gmail.com" target=3D"_blank">dschinazi.ietf@gmail.com</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d=
iv dir=3D"ltr"><div>Hi WebTransport enthusiasts,<br></div><div><br></div><d=
iv>Today we had an interim of the IETF WEBTRANS WG,</div><div>where we reac=
hed consensus in the (virtual) room on</div><div>the following questions:</=
div><div><br></div><div>Question 1: number of protocols<br></div><div>=C2=
=A0 =C2=A0 Should the working group adopt only one UDP-based transport?<br>=
=C2=A0 =C2=A0 1A: only one transport (QUIC or HTTP/3)<br>=C2=A0 =C2=A0 1B: =
multiple transports (QUIC and HTTP/3)<br></div><div><br></div><div>The cons=
ensus was option 1A.</div><div><br></div><div>Additionally, we noted that t=
his does not preclude=C2=A0us from</div><div>building a second protocol at =
a later date if new information</div><div>emerges.</div><div><br></div><div=
>Question 2: UDP-based protocols<br></div><div>=C2=A0 =C2=A0 Which UDP-base=
d option should we adopt as a starting</div><div>=C2=A0 =C2=A0 point for We=
bTransport protocol?<br>=C2=A0 =C2=A0 2A: WebTransport over HTTP/3<br>=C2=
=A0 =C2=A0 2B: WebTransport over QUIC directly (separate ALPN)<br></div><di=
v><br></div><div>The consensus was option 2A.<br></div><div><br></div><div>=
Additionally, we discussed pooling and decided that we would</div><div>not =
allow pooling in=C2=A0WebTransport over HTTP/3 for now, due</div><div>to th=
e complexities of pooling.</div><div><br></div><div>We&#39;d like to confir=
m this consensus on the list. If you disagree</div><div>with these points, =
please reply on the list. If you do so, please</div><div>state how strongly=
 you feel - whether you are expressing a</div><div>preference, or an impera=
tive. Please also provide as much</div><div>detail as possible to explain y=
our position. Please also respond</div><div>if you support this consensus -=
 a simple &quot;I support this consensus&quot;</div><div>email to the list =
would be helpful.</div><div><br></div><div>We&#39;ll be running this consen=
sus call for two weeks, please reply</div><div>before 2021-01-26, the chair=
s will determine consensus on that date.</div><div><br></div><div>Thanks,</=
div><div>David</div></div>
-- <br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport=
</a><br>
</blockquote></div>
-- <br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport=
</a><br>
</blockquote></div>

--000000000000a320dd05b8b773a4--


From nobody Tue Jan 12 10:10:33 2021
Return-Path: <prvs=0646bc3178=afrind@fb.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 90C6E3A0E89 for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 10:10:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level: 
X-Spam-Status: No, score=-2.118 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 (1024-bit key) header.d=fb.com header.b=gwMkzg2I; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=PETvIDTQ
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 jIBW_tKgOBJC for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 10:10:30 -0800 (PST)
Received: from mx0a-00082601.pphosted.com (mx0b-00082601.pphosted.com [67.231.153.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CE733A0E88 for <webtransport@ietf.org>; Tue, 12 Jan 2021 10:10:30 -0800 (PST)
Received: from pps.filterd (m0001303.ppops.net [127.0.0.1]) by m0001303.ppops.net (8.16.0.43/8.16.0.43) with SMTP id 10CI72Uo019805; Tue, 12 Jan 2021 10:10:29 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=0eOFiNuE70Heqe2X7Nk3Gth1XVGDYZSlJ8IvBbiFZCA=; b=gwMkzg2IGsz+zt/ilNaYZBv2gx77rEmpouySpzK1dKniZJEkJ3ksHqDB/oQs337/Z79Q drHTWDRuW4He4jGuP/SSkhcLCgKAWYeegibIm3v6NaBq60/W99pjLOJ93grfJCYRS/sO DY9hM09/BEELTzfMGAi7i3YAbaeG3qtf51I= 
Received: from maileast.thefacebook.com ([163.114.130.16]) by m0001303.ppops.net with ESMTP id 361fp3gg4h-3 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 12 Jan 2021 10:10:28 -0800
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (100.104.31.183) by o365-in.thefacebook.com (100.104.35.174) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Tue, 12 Jan 2021 10:10:27 -0800
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=moR1cwuEaaFo+MO2tQXRP3sr7KaKeRAb25xWGNSubP2B7j7JA3ybZ4Sd+ZKT0QGbVbgNPqOeJwXocs/hymCJHvOsRFRl28hvkUwf6mswyj7aVkNiWd/hxtGz9+z0mKjtnZluPR3IuEmpKj54zFTu2E1FYq5mslc9sTEYgME3Yvs8AUOlp1jp/WVsGQVE+P/zxoIjC7bzI71MdRWrpc78dgkVMjzDhgyrnbQg2Mw1fWgyLzrNJupTcuUmxvgg/Jt3iCHHx76ohznyq6KJIwS/ulfDHPTeApky35k76dzOY/Y7kGZfKYHK+IRzhXsB3oaFtBM1c5K2WEav3k72XauFlA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0eOFiNuE70Heqe2X7Nk3Gth1XVGDYZSlJ8IvBbiFZCA=; b=Gw39EYAMcSMBjrdgDH86fOy5HLYVlRQgQq5dWc4s2y3bEPZsXGShd9Z4Puo/alQHWtQG6uGMy6HBrFKljCsNj1aMTxLAmvbDUGHJlFJoes9/LJN2HSURJGPD8yOS9LCTUJde2j80vKwWk8gFYzHbTFkuAE8hrIpiG0SCag8UrKI23+o1q0gxPLmGbhScVrrpfTfCymsu66TpZvP6w2591XGychICRgl1qp2mn5CvgOLXEroh2ApCB0p7EdrXMTBTnLbpAUBB35anRXARJ3M6TvVfGiSy7fWHo/P17WuGROuLbHiLF1joT6c7cJLtHLwDs1+wcnkl/0dpd8+hjfK9pA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=fb.com; dmarc=pass action=none header.from=fb.com; dkim=pass header.d=fb.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector2-fb-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0eOFiNuE70Heqe2X7Nk3Gth1XVGDYZSlJ8IvBbiFZCA=; b=PETvIDTQRe5N+dt8kCwLb/JmxfUKeMu2cPnEjF8voQ130kkMnkLHsWV1txO/HzYMz6tu9BEtiPOLhE6sy8dzjScNP+kqlUv2TIvZf+844WP29KIPAIW1t6wZadEMCUvGdzt08Dczn7Wr5wnoy/CAMobxsqgB6hm1HxE9wBvQDWc=
Received: from MN2PR15MB3405.namprd15.prod.outlook.com (2603:10b6:208:3f::11) by MN2PR15MB2525.namprd15.prod.outlook.com (2603:10b6:208:129::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3742.6; Tue, 12 Jan 2021 18:10:22 +0000
Received: from MN2PR15MB3405.namprd15.prod.outlook.com ([fe80::b045:b577:108c:f76]) by MN2PR15MB3405.namprd15.prod.outlook.com ([fe80::b045:b577:108c:f76%7]) with mapi id 15.20.3742.012; Tue, 12 Jan 2021 18:10:22 +0000
From: Alan Frindell <afrind@fb.com>
To: David Schinazi <dschinazi.ietf@gmail.com>, WebTransport <webtransport@ietf.org>
Thread-Topic: [Webtransport] Confirming Consensus on WebTransport protocols
Thread-Index: AQHW6QgW3En8/QPJV0mSgKuDoOvwNqojxDYA
Date: Tue, 12 Jan 2021 18:10:22 +0000
Message-ID: <1EE7A63C-E68D-4B70-A8CB-C2A6003AC467@fb.com>
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com>
In-Reply-To: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.44.20121301
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=fb.com;
x-originating-ip: [63.231.38.55]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: aacd8246-fdac-453e-9cfe-08d8b7255456
x-ms-traffictypediagnostic: MN2PR15MB2525:
x-microsoft-antispam-prvs: <MN2PR15MB2525006CB067FB76DB2F1B92A7AA0@MN2PR15MB2525.namprd15.prod.outlook.com>
x-fb-source: Internal
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: MOxJlkiGdWMRjmxAQJ1ohyLqE2aMtUabS3rJe4HG4A52XAfUS62ALzKMIW4p1CdMBhQ7Lm3yTLP10/j9oKghv9bD5L8YPyJi7/ECvs4FkSR5CNpGXMG2nrdxBD9q7hpNlbvcDJ3vlDkw1P0u/for5YiIFcg3XqixqkLATii7peeWmvCIWGIQ/bC45y+yPYld8/VfOwU++xtYIoSeyfUGS8M2WegsoAE4+wCRDZblmftWxTby5Quiuzd1+2jx4d20yWiwC19YUiMECB7JDv7joKhwQBHWEWy7xt84BAy/7qlGUL64DjvInAxZZQZTmcA+1INRz8Ek4Ss9NiDCyQLialJXttY8kAO5Y3bxMWZr3pBGC6xLD27qsChK6/vwDsRr9b6QLVSu/+rLDKgGkHVZHU4ZvdL5GFRscedP9E6JHJhCQTQnE0k4K1PLAMbgAnNZ
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR15MB3405.namprd15.prod.outlook.com; PTR:; CAT:NONE;  SFS:(136003)(366004)(39860400002)(396003)(376002)(346002)(6512007)(71200400001)(316002)(66476007)(91956017)(66446008)(76116006)(5660300002)(83380400001)(64756008)(26005)(186003)(8676002)(36756003)(6486002)(6506007)(53546011)(478600001)(2906002)(2616005)(8936002)(33656002)(110136005)(66556008)(86362001)(66946007)(45980500001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?Ui8rRTljSStXYk1nNHlsT25uTVVzWnJnakIrOHQrSmtPSGhnK2dEaWIwdXBm?= =?utf-8?B?SXVhaWg1OVpNVlFNYjRkZWRnT0Nqd0djdjJnM0k1UThYREU0L0ROVWdnYVZh?= =?utf-8?B?c3NtNzFTOFltT0ZRcGM2T2NpdUJjbE5tRU83RVNpMnJkdjhEMWFSR1RkZ0J4?= =?utf-8?B?bm1pQlJYc2JoR0hzdjhtWUJLWGk3TkVseEFUcEdaTms3TlFXeHNtZ2cwcUFu?= =?utf-8?B?NkVSWnpZTElxWmx4eTQ4MWZtSVhPV2E5YkpDZ0Z3QVUvOHBBREZZV3dFT2ty?= =?utf-8?B?dDYrOUNQN3ZndFk0cDAvSkF6UnJHUENVMlg4QnpQeDkzUm5EWTRnYktVbHl2?= =?utf-8?B?NlJlU1ZGY2RyemlhWGdZci9RYjNFaEZUMVB1NUw4U1R4R1FRL0MwdzAvR0Ez?= =?utf-8?B?R1V1OTRMVVNCOWFGTjNnS3puREl2S0xHQzNIYVJFdHV3aWNDb2dOaWRkYmNG?= =?utf-8?B?K0U3d05ZQ2FtN281R0NJR1kzNTNsaFNNMEJjdUdVWnVTT0Y3WmNxeFlZQmhj?= =?utf-8?B?SGJWNDBWUU9pKzFSZ2M1R3c1N0tReDFxaHl1LzY5NTcrNFQzMjdEeEwrL0lu?= =?utf-8?B?V3U3WkdLL1plUzk4UVlUVm54TFA0OEZqTXVXSThNWHR4WjI2RlJzVUl6YW1w?= =?utf-8?B?WWJuTDNwckZhQWlLSkFwOFYrNkFneElsd3lNanE0OTZsM3d2VmQrc0N1ZTVu?= =?utf-8?B?MDREdlZuRjNyR2pKS2ZEZ2ZjSGtBcmtGM05NalpORFB4R05JNktpU2J5RFpv?= =?utf-8?B?T3pZRTF3UDNCV2pnQkF3THN0ZDZ3WmNGclFtbDlPVE9Rd1BTYmFWVFp4ckVQ?= =?utf-8?B?cC9nK3RsNGpIM2NrS3RvT2Q3d2dac3h1L2xuSm44cGlPbVNqQkR1cmF4NmpR?= =?utf-8?B?L2xJb0xCbmdrUXRwQmJwdmI0VDJVZGtZbFBZVzNvSlB0U2ZhTTBBclVYRHFi?= =?utf-8?B?eGNkNUoxdlFCUTAwdmJJU0tlQzRlcWhkeE91cnoybHN1dStXWVJCdE1qMzBM?= =?utf-8?B?TStnSGVhWnlNMHhNUlBqaEthR3d6V0U3SjljamdEcGpnUWNKMG95N2RQREd1?= =?utf-8?B?RnZiOVVvOHhod1ZGbTRlZG9ab0l2T0M2TllGbVRDZjlXcTVpZVlVcnpQaEdH?= =?utf-8?B?OERvcis4bkRmVXhmdXM0YlJyQ3l4RzgzY2FZdUpXb1ovV3N5R3huU09rOGl2?= =?utf-8?B?V1QwTzRzRGg3STYyWFRkZ0ZoM0F0L3J6eThmMGM1eUtSNE1mV2NWYklrU1hp?= =?utf-8?B?V3VkMVBaZ09vL0ljM2lua084OXAvRnNIVUp2Y1VKUW5TQ2xwalpxcTNXbTRF?= =?utf-8?Q?IuajwWtjjueJR7/jpMHEMYaZ5jUW3/TkX3?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_1EE7A63CE68D4B70A8CBC2A6003AC467fbcom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR15MB3405.namprd15.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: aacd8246-fdac-453e-9cfe-08d8b7255456
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jan 2021 18:10:22.8321 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: QZqrK2pL0sNXP26PImom970LBdt9/fVXze6Hdb2E8OXd5yy3i0xLczcH5x1sBBZH
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR15MB2525
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-12_15:2021-01-12, 2021-01-12 signatures=0
X-Proofpoint-Spam-Details: rule=fb_default_notspam policy=fb_default score=0 suspectscore=0 mlxlogscore=813 phishscore=0 spamscore=0 priorityscore=1501 bulkscore=0 clxscore=1011 mlxscore=0 impostorscore=0 adultscore=0 malwarescore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101120107
X-FB-Internal: deliver
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/RYIU8YQ2ZO7na6OOfFN6ZRgygCE>
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: Tue, 12 Jan 2021 18:10:33 -0000

--_000_1EE7A63CE68D4B70A8CBC2A6003AC467fbcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SSBzdXBwb3J0IHRoZSBjb25zZW5zdXMgb24gUXVlc3Rpb24gMSBhbmQgUXVlc3Rpb24yLg0KDQo+
IEFkZGl0aW9uYWxseSwgd2UgZGlzY3Vzc2VkIHBvb2xpbmcgYW5kIGRlY2lkZWQgdGhhdCB3ZSB3
b3VsZA0Kbm90IGFsbG93IHBvb2xpbmcgaW4gV2ViVHJhbnNwb3J0IG92ZXIgSFRUUC8zIGZvciBu
b3csIGR1ZQ0KdG8gdGhlIGNvbXBsZXhpdGllcyBvZiBwb29saW5nLg0KDQpJIHRoaW5rIHRoaXMg
c3RhdGVtZW50IGlzIHdvcmRlZCB0b28gc3Ryb25nbHkuICBXZSBkaXNjdXNzZWQgcG9vbGluZyBh
bmQgbWFkZSBpdCBjbGVhciB0aGF0IGNob29zaW5nIEgzIGRvZXMgbm90IG1hbmRhdGUgdGhhdCB3
ZSB3aWxsIHN1cHBvcnQgcG9vbGluZy4gTXkgdW5kZXJzdGFuZGluZyBpcyB0aGF0IGl0IHdpbGwg
Y29udGludWUgdG8gYmUgZGlzY3Vzc2VkIGluIHRoZSB3b3JraW5nIGdyb3VwLg0KDQotQWxhbg0K
DQpGcm9tOiBXZWJ0cmFuc3BvcnQgPHdlYnRyYW5zcG9ydC1ib3VuY2VzQGlldGYub3JnPiBvbiBi
ZWhhbGYgb2YgRGF2aWQgU2NoaW5hemkgPGRzY2hpbmF6aS5pZXRmQGdtYWlsLmNvbT4NCkRhdGU6
IFR1ZXNkYXksIEphbnVhcnkgMTIsIDIwMjEgYXQgOToyNiBBTQ0KVG86IFdlYlRyYW5zcG9ydCA8
d2VidHJhbnNwb3J0QGlldGYub3JnPg0KU3ViamVjdDogW1dlYnRyYW5zcG9ydF0gQ29uZmlybWlu
ZyBDb25zZW5zdXMgb24gV2ViVHJhbnNwb3J0IHByb3RvY29scw0KDQpIaSBXZWJUcmFuc3BvcnQg
ZW50aHVzaWFzdHMsDQoNClRvZGF5IHdlIGhhZCBhbiBpbnRlcmltIG9mIHRoZSBJRVRGIFdFQlRS
QU5TIFdHLA0Kd2hlcmUgd2UgcmVhY2hlZCBjb25zZW5zdXMgaW4gdGhlICh2aXJ0dWFsKSByb29t
IG9uDQp0aGUgZm9sbG93aW5nIHF1ZXN0aW9uczoNCg0KUXVlc3Rpb24gMTogbnVtYmVyIG9mIHBy
b3RvY29scw0KICAgIFNob3VsZCB0aGUgd29ya2luZyBncm91cCBhZG9wdCBvbmx5IG9uZSBVRFAt
YmFzZWQgdHJhbnNwb3J0Pw0KICAgIDFBOiBvbmx5IG9uZSB0cmFuc3BvcnQgKFFVSUMgb3IgSFRU
UC8zKQ0KICAgIDFCOiBtdWx0aXBsZSB0cmFuc3BvcnRzIChRVUlDIGFuZCBIVFRQLzMpDQoNClRo
ZSBjb25zZW5zdXMgd2FzIG9wdGlvbiAxQS4NCg0KQWRkaXRpb25hbGx5LCB3ZSBub3RlZCB0aGF0
IHRoaXMgZG9lcyBub3QgcHJlY2x1ZGUgdXMgZnJvbQ0KYnVpbGRpbmcgYSBzZWNvbmQgcHJvdG9j
b2wgYXQgYSBsYXRlciBkYXRlIGlmIG5ldyBpbmZvcm1hdGlvbg0KZW1lcmdlcy4NCg0KUXVlc3Rp
b24gMjogVURQLWJhc2VkIHByb3RvY29scw0KICAgIFdoaWNoIFVEUC1iYXNlZCBvcHRpb24gc2hv
dWxkIHdlIGFkb3B0IGFzIGEgc3RhcnRpbmcNCiAgICBwb2ludCBmb3IgV2ViVHJhbnNwb3J0IHBy
b3RvY29sPw0KICAgIDJBOiBXZWJUcmFuc3BvcnQgb3ZlciBIVFRQLzMNCiAgICAyQjogV2ViVHJh
bnNwb3J0IG92ZXIgUVVJQyBkaXJlY3RseSAoc2VwYXJhdGUgQUxQTikNCg0KVGhlIGNvbnNlbnN1
cyB3YXMgb3B0aW9uIDJBLg0KDQpBZGRpdGlvbmFsbHksIHdlIGRpc2N1c3NlZCBwb29saW5nIGFu
ZCBkZWNpZGVkIHRoYXQgd2Ugd291bGQNCm5vdCBhbGxvdyBwb29saW5nIGluIFdlYlRyYW5zcG9y
dCBvdmVyIEhUVFAvMyBmb3Igbm93LCBkdWUNCnRvIHRoZSBjb21wbGV4aXRpZXMgb2YgcG9vbGlu
Zy4NCg0KV2UnZCBsaWtlIHRvIGNvbmZpcm0gdGhpcyBjb25zZW5zdXMgb24gdGhlIGxpc3QuIElm
IHlvdSBkaXNhZ3JlZQ0Kd2l0aCB0aGVzZSBwb2ludHMsIHBsZWFzZSByZXBseSBvbiB0aGUgbGlz
dC4gSWYgeW91IGRvIHNvLCBwbGVhc2UNCnN0YXRlIGhvdyBzdHJvbmdseSB5b3UgZmVlbCAtIHdo
ZXRoZXIgeW91IGFyZSBleHByZXNzaW5nIGENCnByZWZlcmVuY2UsIG9yIGFuIGltcGVyYXRpdmUu
IFBsZWFzZSBhbHNvIHByb3ZpZGUgYXMgbXVjaA0KZGV0YWlsIGFzIHBvc3NpYmxlIHRvIGV4cGxh
aW4geW91ciBwb3NpdGlvbi4gUGxlYXNlIGFsc28gcmVzcG9uZA0KaWYgeW91IHN1cHBvcnQgdGhp
cyBjb25zZW5zdXMgLSBhIHNpbXBsZSAiSSBzdXBwb3J0IHRoaXMgY29uc2Vuc3VzIg0KZW1haWwg
dG8gdGhlIGxpc3Qgd291bGQgYmUgaGVscGZ1bC4NCg0KV2UnbGwgYmUgcnVubmluZyB0aGlzIGNv
bnNlbnN1cyBjYWxsIGZvciB0d28gd2Vla3MsIHBsZWFzZSByZXBseQ0KYmVmb3JlIDIwMjEtMDEt
MjYsIHRoZSBjaGFpcnMgd2lsbCBkZXRlcm1pbmUgY29uc2Vuc3VzIG9uIHRoYXQgZGF0ZS4NCg0K
VGhhbmtzLA0KRGF2aWQNCg==

--_000_1EE7A63CE68D4B70A8CBC2A6003AC467fbcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <FADCBCAB27BC2B498AA4A10FBC6D1FAC@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCWZvbnQtc2l6
ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5FbWFp
bFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6
IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVs
dA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBw
YWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4w
aW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9
DQotLT48L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYzQzEi
IHZsaW5rPSIjOTU0RjcyIiBzdHlsZT0id29yZC13cmFwOmJyZWFrLXdvcmQiPg0KPGRpdiBjbGFz
cz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgc3VwcG9ydCB0aGUgY29u
c2Vuc3VzIG9uIFF1ZXN0aW9uIDEgYW5kIFF1ZXN0aW9uMi48YnI+DQo8YnI+DQomZ3Q7IEFkZGl0
aW9uYWxseSwgd2UgZGlzY3Vzc2VkIHBvb2xpbmcgYW5kIGRlY2lkZWQgdGhhdCB3ZSB3b3VsZDxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+bm90IGFsbG93IHBvb2xpbmcgaW4m
bmJzcDtXZWJUcmFuc3BvcnQgb3ZlciBIVFRQLzMgZm9yIG5vdywgZHVlPG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj50byB0aGUgY29tcGxleGl0aWVzIG9mIHBvb2xpbmcuPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgdGhpbmsgdGhpcyBzdGF0ZW1lbnQgaXMgd29yZGVkIHRv
byBzdHJvbmdseS4mbmJzcDsgV2UgZGlzY3Vzc2VkIHBvb2xpbmcgYW5kIG1hZGUgaXQgY2xlYXIg
dGhhdCBjaG9vc2luZyBIMyBkb2VzIG5vdCBtYW5kYXRlIHRoYXQgd2Ugd2lsbCBzdXBwb3J0IHBv
b2xpbmcuIE15IHVuZGVyc3RhbmRpbmcgaXMgdGhhdCBpdCB3aWxsIGNvbnRpbnVlIHRvIGJlIGRp
c2N1c3NlZCBpbiB0aGUgd29ya2luZyBncm91cC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+LUFs
YW48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEu
MHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2siPkZyb206IDwvc3Bhbj48
L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2siPldlYnRyYW5zcG9y
dCAmbHQ7d2VidHJhbnNwb3J0LWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7IG9uIGJlaGFsZiBvZiBEYXZp
ZCBTY2hpbmF6aSAmbHQ7ZHNjaGluYXppLmlldGZAZ21haWwuY29tJmd0Ozxicj4NCjxiPkRhdGU6
IDwvYj5UdWVzZGF5LCBKYW51YXJ5IDEyLCAyMDIxIGF0IDk6MjYgQU08YnI+DQo8Yj5UbzogPC9i
PldlYlRyYW5zcG9ydCAmbHQ7d2VidHJhbnNwb3J0QGlldGYub3JnJmd0Ozxicj4NCjxiPlN1Ympl
Y3Q6IDwvYj5bV2VidHJhbnNwb3J0XSBDb25maXJtaW5nIENvbnNlbnN1cyBvbiBXZWJUcmFuc3Bv
cnQgcHJvdG9jb2xzPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SGkgV2ViVHJhbnNwb3J0IGVudGh1c2lhc3RzLDxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Ub2RheSB3
ZSBoYWQgYW4gaW50ZXJpbSBvZiB0aGUgSUVURiBXRUJUUkFOUyBXRyw8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPndoZXJlIHdlIHJlYWNoZWQgY29u
c2Vuc3VzIGluIHRoZSAodmlydHVhbCkgcm9vbSBvbjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+dGhlIGZvbGxvd2luZyBxdWVzdGlvbnM6PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlF1ZXN0aW9u
IDE6IG51bWJlciBvZiBwcm90b2NvbHM8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJzcDsgU2hvdWxkIHRoZSB3b3JraW5nIGdyb3Vw
IGFkb3B0IG9ubHkgb25lIFVEUC1iYXNlZCB0cmFuc3BvcnQ/PGJyPg0KJm5ic3A7ICZuYnNwOyAx
QTogb25seSBvbmUgdHJhbnNwb3J0IChRVUlDIG9yIEhUVFAvMyk8YnI+DQombmJzcDsgJm5ic3A7
IDFCOiBtdWx0aXBsZSB0cmFuc3BvcnRzIChRVUlDIGFuZCBIVFRQLzMpPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoZSBjb25zZW5zdXMgd2Fz
IG9wdGlvbiAxQS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+QWRkaXRpb25hbGx5LCB3ZSBub3RlZCB0aGF0IHRoaXMgZG9lcyBub3QgcHJlY2x1
ZGUmbmJzcDt1cyBmcm9tPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5idWlsZGluZyBhIHNlY29uZCBwcm90b2NvbCBhdCBhIGxhdGVyIGRhdGUgaWYg
bmV3IGluZm9ybWF0aW9uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5lbWVyZ2VzLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5RdWVzdGlvbiAyOiBVRFAtYmFzZWQgcHJvdG9jb2xzPG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7
IFdoaWNoIFVEUC1iYXNlZCBvcHRpb24gc2hvdWxkIHdlIGFkb3B0IGFzIGEgc3RhcnRpbmc8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAm
bmJzcDsgcG9pbnQgZm9yIFdlYlRyYW5zcG9ydCBwcm90b2NvbD88YnI+DQombmJzcDsgJm5ic3A7
IDJBOiBXZWJUcmFuc3BvcnQgb3ZlciBIVFRQLzM8YnI+DQombmJzcDsgJm5ic3A7IDJCOiBXZWJU
cmFuc3BvcnQgb3ZlciBRVUlDIGRpcmVjdGx5IChzZXBhcmF0ZSBBTFBOKTxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGUgY29uc2Vuc3VzIHdh
cyBvcHRpb24gMkEuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPkFkZGl0aW9uYWxseSwgd2UgZGlzY3Vzc2VkIHBvb2xpbmcgYW5kIGRlY2lkZWQg
dGhhdCB3ZSB3b3VsZDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+bm90IGFsbG93IHBvb2xpbmcgaW4mbmJzcDtXZWJUcmFuc3BvcnQgb3ZlciBIVFRQ
LzMgZm9yIG5vdywgZHVlPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj50byB0aGUgY29tcGxleGl0aWVzIG9mIHBvb2xpbmcuPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPldlJ2QgbGlrZSB0byBjb25m
aXJtIHRoaXMgY29uc2Vuc3VzIG9uIHRoZSBsaXN0LiBJZiB5b3UgZGlzYWdyZWU8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPndpdGggdGhlc2UgcG9p
bnRzLCBwbGVhc2UgcmVwbHkgb24gdGhlIGxpc3QuIElmIHlvdSBkbyBzbywgcGxlYXNlPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5zdGF0ZSBob3cg
c3Ryb25nbHkgeW91IGZlZWwgLSB3aGV0aGVyIHlvdSBhcmUgZXhwcmVzc2luZyBhPG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5wcmVmZXJlbmNlLCBv
ciBhbiBpbXBlcmF0aXZlLiBQbGVhc2UgYWxzbyBwcm92aWRlIGFzIG11Y2g8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPmRldGFpbCBhcyBwb3NzaWJs
ZSB0byBleHBsYWluIHlvdXIgcG9zaXRpb24uIFBsZWFzZSBhbHNvIHJlc3BvbmQ8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPmlmIHlvdSBzdXBwb3J0
IHRoaXMgY29uc2Vuc3VzIC0gYSBzaW1wbGUgJnF1b3Q7SSBzdXBwb3J0IHRoaXMgY29uc2Vuc3Vz
JnF1b3Q7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5lbWFpbCB0byB0aGUgbGlzdCB3b3VsZCBiZSBoZWxwZnVsLjxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5XZSdsbCBiZSBydW5uaW5nIHRoaXMg
Y29uc2Vuc3VzIGNhbGwgZm9yIHR3byB3ZWVrcywgcGxlYXNlIHJlcGx5PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5iZWZvcmUgMjAyMS0wMS0yNiwg
dGhlIGNoYWlycyB3aWxsIGRldGVybWluZSBjb25zZW5zdXMgb24gdGhhdCBkYXRlLjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3MsPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5EYXZpZDxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_1EE7A63CE68D4B70A8CBC2A6003AC467fbcom_--


From nobody Tue Jan 12 10:15:14 2021
Return-Path: <ekinnear@apple.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 A1A783A0FD7 for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 10:15:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.369
X-Spam-Level: 
X-Spam-Status: No, score=-2.369 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 MbBeVBa8vp0u for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 10:15:06 -0800 (PST)
Received: from nwk-aaemail-lapp02.apple.com (nwk-aaemail-lapp02.apple.com [17.151.62.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 228463A0F5E for <webtransport@ietf.org>; Tue, 12 Jan 2021 10:15:04 -0800 (PST)
Received: from pps.filterd (nwk-aaemail-lapp02.apple.com [127.0.0.1]) by nwk-aaemail-lapp02.apple.com (8.16.0.43/8.16.0.42) with SMTP id 10CI9aTP010851; Tue, 12 Jan 2021 10:15:00 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=4tk7fIPiI9QtJmkZ7K9ykGJH83GJWfNSC8DYMb3/Jk8=; b=rKdWfnHdvp3FbmEww4f1NUNTtLWfKaQPzfQgFmEo1SrdBGX6pcaksNC50qhbT4ab+jd4 g2/5cIbUu8+FG69xH9o9UhiZu7xDZ7RvIsbTDAXX7wcvXnrZEIR59EwIf6YIirKp0kZ0 yrP1QS7EgHnyaqm/mLcp3b+HTu1X/yxvXId3SH1NskWXA46zRw0j3N3ZYueN0wTuoBcE +rshFSJ2HYzhEhBdjfGAKj2W5TTPHhDSdLXhKoZT808Z7ZQuwHwq2uZCbUBlfYj/KAXg +s9HisBICHZxLRnZDIV+BrNdsctCEMTPOypG47O25QoYaXwNftRkwI8DsWMvtQEgKhWi XA== 
Received: from rn-mailsvcp-mta-lapp01.rno.apple.com (rn-mailsvcp-mta-lapp01.rno.apple.com [10.225.203.149]) by nwk-aaemail-lapp02.apple.com with ESMTP id 35y9xmfsmu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 12 Jan 2021 10:15:00 -0800
Received: from rn-mailsvcp-mmp-lapp03.rno.apple.com (rn-mailsvcp-mmp-lapp03.rno.apple.com [17.179.253.16]) by rn-mailsvcp-mta-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec  3 2020)) with ESMTPS id <0QMU00OYG2OZLGI0@rn-mailsvcp-mta-lapp01.rno.apple.com>;  Tue, 12 Jan 2021 10:14:59 -0800 (PST)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp03.rno.apple.com by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.6.20200729 64bit (built Jul 29 2020)) id <0QMU00L002EJTB00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Tue, 12 Jan 2021 10:14:59 -0800 (PST)
X-Va-A: 
X-Va-T-CD: dc254b15e9c02e5b63b37c4d340c19c3
X-Va-E-CD: 4ed4f33e0687dabe1b06172a3ab84b82
X-Va-R-CD: 4c92cd742ca1261c688b326f07bb1224
X-Va-CD: 0
X-Va-ID: e453b3dc-2726-44bd-9669-a63a45914f76
X-V-A: 
X-V-T-CD: dc254b15e9c02e5b63b37c4d340c19c3
X-V-E-CD: 4ed4f33e0687dabe1b06172a3ab84b82
X-V-R-CD: 4c92cd742ca1261c688b326f07bb1224
X-V-CD: 0
X-V-ID: 824d2aaf-54f7-47ec-9075-9a88c375faa1
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-12_15:2021-01-12, 2021-01-12 signatures=0
Received: from [17.235.36.77] (unknown [17.235.36.77]) by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.6.20200729 64bit (built Jul 29 2020)) with ESMTPSA id <0QMU010RN2OY8X00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Tue, 12 Jan 2021 10:14:58 -0800 (PST)
From: Eric Kinnear <ekinnear@apple.com>
Message-id: <C4FFF30E-A8D6-4471-8FC4-C6C4A00ED679@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_BCFE2131-7DF1-401A-98CA-90CB9C397984"
MIME-version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Tue, 12 Jan 2021 10:14:57 -0800
In-reply-to: <1EE7A63C-E68D-4B70-A8CB-C2A6003AC467@fb.com>
Cc: David Schinazi <dschinazi.ietf@gmail.com>, WebTransport <webtransport@ietf.org>
To: Alan Frindell <afrind=40fb.com@dmarc.ietf.org>
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <1EE7A63C-E68D-4B70-A8CB-C2A6003AC467@fb.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-12_15:2021-01-12, 2021-01-12 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/VtrPNVqqXhdC2Eb8Mki6NfE-SzY>
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: Tue, 12 Jan 2021 18:15:13 -0000

--Apple-Mail=_BCFE2131-7DF1-401A-98CA-90CB9C397984
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I support this consensus.=20

To Alan=E2=80=99s point, I=E2=80=99d expect that we=E2=80=99ll continue =
to discuss pooling, but that we=E2=80=99re not committing to delivering =
something that supports pooling without further identifying the =
complexities involved and designing something which sufficiently =
resolves those concerns. (As would be reasonable for any protocol =
feature.)

Thanks,
Eric


> On Jan 12, 2021, at 10:10 AM, Alan Frindell =
<afrind=3D40fb.com@dmarc.ietf.org> wrote:
>=20
> I support the consensus on Question 1 and Question2.
>=20
> > 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.
> =20
> I think this statement is worded too strongly.  We discussed pooling =
and made it clear that choosing H3 does not mandate that we will support =
pooling. My understanding is that it will continue to be discussed in =
the working group.
> =20
> -Alan
> =20
> From: Webtransport <webtransport-bounces@ietf.org> on behalf of David =
Schinazi <dschinazi.ietf@gmail.com>
> Date: Tuesday, January 12, 2021 at 9:26 AM
> To: WebTransport <webtransport@ietf.org>
> Subject: [Webtransport] Confirming Consensus on WebTransport protocols
> =20
> Hi WebTransport enthusiasts,
> =20
> Today we had an interim of the IETF WEBTRANS WG,
> where we reached consensus in the (virtual) room on
> the following questions:
> =20
> 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)
> =20
> The consensus was option 1A.
> =20
> Additionally, we noted that this does not preclude us from
> building a second protocol at a later date if new information
> emerges.
> =20
> 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)
> =20
> The consensus was option 2A.
> =20
> 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.
> =20
> 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.
> =20
> We'll be running this consensus call for two weeks, please reply
> before 2021-01-26, the chairs will determine consensus on that date.
> =20
> Thanks,
> David
> --=20
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport


--Apple-Mail=_BCFE2131-7DF1-401A-98CA-90CB9C397984
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">I =
support this consensus.&nbsp;<div class=3D""><br class=3D""></div><div =
class=3D"">To Alan=E2=80=99s point, I=E2=80=99d expect that we=E2=80=99ll =
continue to discuss pooling, but that we=E2=80=99re not committing to =
delivering something that supports pooling without further identifying =
the complexities involved and designing something which sufficiently =
resolves those concerns. (As would be reasonable for any protocol =
feature.)</div><div class=3D""><br class=3D""></div><div =
class=3D"">Thanks,</div><div class=3D"">Eric</div><div class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jan 12, 2021, at 10:10 AM, Alan Frindell &lt;<a =
href=3D"mailto:afrind=3D40fb.com@dmarc.ietf.org" =
class=3D"">afrind=3D40fb.com@dmarc.ietf.org</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" class=3D""><div class=3D"WordSection1" style=3D"page: =
WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><div style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D"">I support the consensus on Question 1 and =
Question2.<br class=3D""><br class=3D"">&gt; Additionally, we discussed =
pooling and decided that we would<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D"">not allow pooling in&nbsp;WebTransport over =
HTTP/3 for now, due<o:p class=3D""></o:p></div><div style=3D"margin: =
0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">to =
the complexities of pooling.<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></div><div =
style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D"">I think this statement is worded too =
strongly.&nbsp; We discussed pooling and made it clear that choosing H3 =
does not mandate that we will support pooling. My understanding is that =
it will continue to be discussed in the working group.<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">-Alan<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"border-style: solid none =
none; border-top-width: 1pt; border-top-color: rgb(181, 196, 223); =
padding: 3pt 0in 0in;" class=3D""><div style=3D"margin: 0in; font-size: =
11pt; font-family: Calibri, sans-serif;" class=3D""><b class=3D""><span =
style=3D"font-size: 12pt;" class=3D"">From:<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b><span =
style=3D"font-size: 12pt;" class=3D"">Webtransport &lt;<a =
href=3D"mailto:webtransport-bounces@ietf.org" =
class=3D"">webtransport-bounces@ietf.org</a>&gt; on behalf of David =
Schinazi &lt;<a href=3D"mailto:dschinazi.ietf@gmail.com" =
class=3D"">dschinazi.ietf@gmail.com</a>&gt;<br class=3D""><b =
class=3D"">Date:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Tuesday, January 12, =
2021 at 9:26 AM<br class=3D""><b class=3D"">To:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>WebTransport &lt;<a =
href=3D"mailto:webtransport@ietf.org" =
class=3D"">webtransport@ietf.org</a>&gt;<br class=3D""><b =
class=3D"">Subject:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>[Webtransport] =
Confirming Consensus on WebTransport protocols<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div class=3D""><div =
style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D"">Hi WebTransport enthusiasts,<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Today =
we had an interim of the IETF WEBTRANS WG,<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">where we =
reached consensus in the (virtual) room on<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">the =
following questions:<o:p class=3D""></o:p></div></div><div class=3D""><div=
 style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></div></div><div =
class=3D""><div style=3D"margin: 0in; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Question 1: number of protocols<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">&nbsp; =
&nbsp; Should the working group adopt only one UDP-based transport?<br =
class=3D"">&nbsp; &nbsp; 1A: only one transport (QUIC or HTTP/3)<br =
class=3D"">&nbsp; &nbsp; 1B: multiple transports (QUIC and HTTP/3)<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">The =
consensus was option 1A.<o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0in; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Additionally, we noted that this does not preclude&nbsp;us =
from<o:p class=3D""></o:p></div></div><div class=3D""><div =
style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D"">building a second protocol at a later date if =
new information<o:p class=3D""></o:p></div></div><div class=3D""><div =
style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D"">emerges.<o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0in; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Question 2: UDP-based protocols<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">&nbsp; =
&nbsp; Which UDP-based option should we adopt as a starting<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">&nbsp; =
&nbsp; point for WebTransport protocol?<br class=3D"">&nbsp; &nbsp; 2A: =
WebTransport over HTTP/3<br class=3D"">&nbsp; &nbsp; 2B: WebTransport =
over QUIC directly (separate ALPN)<o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0in; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">The =
consensus was option 2A.<o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0in; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Additionally, we discussed pooling and decided that we =
would<o:p class=3D""></o:p></div></div><div class=3D""><div =
style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D"">not allow pooling in&nbsp;WebTransport over =
HTTP/3 for now, due<o:p class=3D""></o:p></div></div><div class=3D""><div =
style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D"">to the complexities of pooling.<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">We'd =
like to confirm this consensus on the list. If you disagree<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">with =
these points, please reply on the list. If you do so, please<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">state how =
strongly you feel - whether you are expressing a<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">preference,=
 or an imperative. Please also provide as much<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">detail as =
possible to explain your position. Please also respond<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">if you =
support this consensus - a simple "I support this consensus"<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">email to =
the list would be helpful.<o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0in; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">We'll =
be running this consensus call for two weeks, please reply<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">before =
2021-01-26, the chairs will determine consensus on that date.<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Thanks,<o:p class=3D""></o:p></div></div><div class=3D""><div =
style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D"">David<o:p =
class=3D""></o:p></div></div></div></div><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">--<span class=3D"Apple-converted-space">&nbsp;</span></span><br=
 style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Webtransport mailing =
list</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D""><a =
href=3D"mailto:Webtransport@ietf.org" =
class=3D"">Webtransport@ietf.org</a></span><br style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D""><a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" =
class=3D"">https://www.ietf.org/mailman/listinfo/webtransport</a></span></=
div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_BCFE2131-7DF1-401A-98CA-90CB9C397984--


From nobody Tue Jan 12 10:29:11 2021
Return-Path: <kixelated@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 9ED6C3A0ED1 for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 10:29:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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_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 c-R5OnyXUI1e for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 10:29:07 -0800 (PST)
Received: from mail-ot1-x32f.google.com (mail-ot1-x32f.google.com [IPv6:2607:f8b0:4864:20::32f]) (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 8CCCE3A0ECE for <webtransport@ietf.org>; Tue, 12 Jan 2021 10:29:07 -0800 (PST)
Received: by mail-ot1-x32f.google.com with SMTP id x13so3187875oto.8 for <webtransport@ietf.org>; Tue, 12 Jan 2021 10:29:07 -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=OHCf9J5Rb09vbqKV8s7A+lJFGN0fZDoCB3i94nb2LIw=; b=MnYxtrjVNiE/xghZMoIV3LH527b3knHIwFIILl0xZ8CX+FwoZ7Rwp8hMVVEna+JSr0 QkDbsF6rZpfKnse6sDSKg2gUxnQgMj8Hd0M3kF7C4AmL1oFm24BhqTGKksnFQTSueQxX DtH1nBPDPafG+G6uGwHoWxYrCJcdqf57TdUlw3VwmEJn+z3/jw/528jrCesxFdCNL8QM eGUgF23e2L4H8qu5lAhrPzAU/LdqJoteMO8ZR1LNREHCN6paFnMngtsej9n2Wu4IpYtw GJIDby5NARUwrKaWTCzHs+NhTp9crymg4dIkTD4JxUW4vfitp6yeQMkt1sNg7TTHEvp0 vbeA==
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=OHCf9J5Rb09vbqKV8s7A+lJFGN0fZDoCB3i94nb2LIw=; b=slAo20W0TII20rZIGUXxvdclRxZ+VlWZMgfWj4/AVhovZWAemnu9Mg0HREAfmamp75 N0BiVgqAgBMTAQld0PDIgFOZ2F0X2Nj0OG5orPmTnLX8zzoEozbW3ZSyMCOHMxRBQ6EP pnlI/2n0BjBJ93WI8XxK/SagWmpo3qDbcnpNazNaQU4OpHzFtjbCyaww27dEXuJwQJX9 wpMUYfnLisg8p+7tqGa8k2VmIfLKgzP9VYAP7ydfPJMy35ItmwXWeGytXmVFxGW978Vk 3a3kVZCIEQJF85AurmJwMDkyzyL86wKX4BBxGjcWwhB7j/+gdWMPNf8wSdSNH+x3fnYr uEdg==
X-Gm-Message-State: AOAM531RIS5Eu6LzI979+HxYiVeuIAimaFSUfy672u0aA+ouCO4Mlaip SzKyb7Jxinuzel8mUV7eiDEYxlAkhlwXKEqzaUwRjrpfjRM=
X-Google-Smtp-Source: ABdhPJzb//KXxSDQqtdqvAvJ+awDxC6ny3o3d9eMGBA18dVG5pEu8uN966yubKuvQPWay0Q2sChgz/Pi348MzVN+qOw=
X-Received: by 2002:a9d:c01:: with SMTP id 1mr475303otr.107.1610476146736; Tue, 12 Jan 2021 10:29:06 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <1EE7A63C-E68D-4B70-A8CB-C2A6003AC467@fb.com> <C4FFF30E-A8D6-4471-8FC4-C6C4A00ED679@apple.com>
In-Reply-To: <C4FFF30E-A8D6-4471-8FC4-C6C4A00ED679@apple.com>
From: Luke Curley <kixelated@gmail.com>
Date: Tue, 12 Jan 2021 10:28:55 -0800
Message-ID: <CAHVo=Z=aP-OsgE87JGYT7xAjLLrgHKpa-16wtvpoCJp7F_209g@mail.gmail.com>
To: Eric Kinnear <ekinnear=40apple.com@dmarc.ietf.org>
Cc: Alan Frindell <afrind=40fb.com@dmarc.ietf.org>,  David Schinazi <dschinazi.ietf@gmail.com>, WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a5413905b8b83280"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/0PyDxiArXuEJq2seoc1-iwygwAg>
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: Tue, 12 Jan 2021 18:29:10 -0000

--000000000000a5413905b8b83280
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Yeah, I want to reaffirm that my vote for HTTP/3 was tied to the removal of
pooling. The current Http3Transport draft is more complex than it needs to
be in order to support pooling, which is a fringe optimization at best.

On Tue, Jan 12, 2021 at 10:15 AM Eric Kinnear <ekinnear=3D
40apple.com@dmarc.ietf.org> wrote:

> I support this consensus.
>
> To Alan=E2=80=99s point, I=E2=80=99d expect that we=E2=80=99ll continue t=
o discuss pooling, but
> that we=E2=80=99re not committing to delivering something that supports p=
ooling
> without further identifying the complexities involved and designing
> something which sufficiently resolves those concerns. (As would be
> reasonable for any protocol feature.)
>
> Thanks,
> Eric
>
>
> On Jan 12, 2021, at 10:10 AM, Alan Frindell <
> afrind=3D40fb.com@dmarc.ietf.org> wrote:
>
> I support the consensus on Question 1 and Question2.
>
> > 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.
>
> I think this statement is worded too strongly.  We discussed pooling and
> made it clear that choosing H3 does not mandate that we will support
> pooling. My understanding is that it will continue to be discussed in the
> working group.
>
> -Alan
>
> *From: *Webtransport <webtransport-bounces@ietf.org> on behalf of David
> Schinazi <dschinazi.ietf@gmail.com>
> *Date: *Tuesday, January 12, 2021 at 9:26 AM
> *To: *WebTransport <webtransport@ietf.org>
> *Subject: *[Webtransport] Confirming Consensus on WebTransport protocols
>
> 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
> --
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport
>
>
> --
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport
>

--000000000000a5413905b8b83280
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Yeah, I want to reaffirm that my vote for HTTP/3 was tied =
to the removal of pooling. The current Http3Transport draft is more complex=
 than=C2=A0it needs to be in order to support pooling, which is a fringe op=
timization at best.<div></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Tue, Jan 12, 2021 at 10:15 AM Eric Kinnear=
 &lt;ekinnear=3D<a href=3D"mailto:40apple.com@dmarc.ietf.org" target=3D"_bl=
ank">40apple.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div>I support this consensus.=C2=A0<div><=
br></div><div>To Alan=E2=80=99s point, I=E2=80=99d expect that we=E2=80=99l=
l continue to discuss pooling, but that we=E2=80=99re not committing to del=
ivering something that supports pooling without further identifying the com=
plexities involved and designing something which sufficiently resolves thos=
e concerns. (As would be reasonable for any protocol feature.)</div><div><b=
r></div><div>Thanks,</div><div>Eric</div><div><br><div><br><blockquote type=
=3D"cite"><div>On Jan 12, 2021, at 10:10 AM, Alan Frindell &lt;<a href=3D"m=
ailto:afrind=3D40fb.com@dmarc.ietf.org" target=3D"_blank">afrind=3D40fb.com=
@dmarc.ietf.org</a>&gt; wrote:</div><br><div><div style=3D"font-family:Helv=
etica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight=
:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transfo=
rm:none;white-space:normal;word-spacing:0px;text-decoration:none"><div styl=
e=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-serif">I support th=
e consensus on Question 1 and Question2.<br><br>&gt; Additionally, we discu=
ssed pooling and decided that we would<u></u><u></u></div><div style=3D"mar=
gin:0in;font-size:11pt;font-family:Calibri,sans-serif">not allow pooling in=
=C2=A0WebTransport over HTTP/3 for now, due<u></u><u></u></div><div style=
=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-serif">to the comple=
xities of pooling.<u></u><u></u></div><div style=3D"margin:0in;font-size:11=
pt;font-family:Calibri,sans-serif"><u></u>=C2=A0<u></u></div><div style=3D"=
margin:0in;font-size:11pt;font-family:Calibri,sans-serif">I think this stat=
ement is worded too strongly.=C2=A0 We discussed pooling and made it clear =
that choosing H3 does not mandate that we will support pooling. My understa=
nding is that it will continue to be discussed in the working group.<u></u>=
<u></u></div><div style=3D"margin:0in;font-size:11pt;font-family:Calibri,sa=
ns-serif"><u></u>=C2=A0<u></u></div><div style=3D"margin:0in;font-size:11pt=
;font-family:Calibri,sans-serif">-Alan<u></u><u></u></div><div style=3D"mar=
gin:0in;font-size:11pt;font-family:Calibri,sans-serif"><u></u>=C2=A0<u></u>=
</div><div style=3D"border-style:solid none none;border-top-width:1pt;borde=
r-top-color:rgb(181,196,223);padding:3pt 0in 0in"><div style=3D"margin:0in;=
font-size:11pt;font-family:Calibri,sans-serif"><b><span style=3D"font-size:=
12pt">From:<span>=C2=A0</span></span></b><span style=3D"font-size:12pt">Web=
transport &lt;<a href=3D"mailto:webtransport-bounces@ietf.org" target=3D"_b=
lank">webtransport-bounces@ietf.org</a>&gt; on behalf of David Schinazi &lt=
;<a href=3D"mailto:dschinazi.ietf@gmail.com" target=3D"_blank">dschinazi.ie=
tf@gmail.com</a>&gt;<br><b>Date:<span>=C2=A0</span></b>Tuesday, January 12,=
 2021 at 9:26 AM<br><b>To:<span>=C2=A0</span></b>WebTransport &lt;<a href=
=3D"mailto:webtransport@ietf.org" target=3D"_blank">webtransport@ietf.org</=
a>&gt;<br><b>Subject:<span>=C2=A0</span></b>[Webtransport] Confirming Conse=
nsus on WebTransport protocols<u></u><u></u></span></div></div><div><div st=
yle=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-serif"><u></u>=C2=
=A0<u></u></div></div><div><div><div style=3D"margin:0in;font-size:11pt;fon=
t-family:Calibri,sans-serif">Hi WebTransport enthusiasts,<u></u><u></u></di=
v></div><div><div style=3D"margin:0in;font-size:11pt;font-family:Calibri,sa=
ns-serif"><u></u>=C2=A0<u></u></div></div><div><div style=3D"margin:0in;fon=
t-size:11pt;font-family:Calibri,sans-serif">Today we had an interim of the =
IETF WEBTRANS WG,<u></u><u></u></div></div><div><div style=3D"margin:0in;fo=
nt-size:11pt;font-family:Calibri,sans-serif">where we reached consensus in =
the (virtual) room on<u></u><u></u></div></div><div><div style=3D"margin:0i=
n;font-size:11pt;font-family:Calibri,sans-serif">the following questions:<u=
></u><u></u></div></div><div><div style=3D"margin:0in;font-size:11pt;font-f=
amily:Calibri,sans-serif"><u></u>=C2=A0<u></u></div></div><div><div style=
=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-serif">Question 1: n=
umber of protocols<u></u><u></u></div></div><div><div style=3D"margin:0in;f=
ont-size:11pt;font-family:Calibri,sans-serif">=C2=A0 =C2=A0 Should the work=
ing group adopt only one UDP-based transport?<br>=C2=A0 =C2=A0 1A: only one=
 transport (QUIC or HTTP/3)<br>=C2=A0 =C2=A0 1B: multiple transports (QUIC =
and HTTP/3)<u></u><u></u></div></div><div><div style=3D"margin:0in;font-siz=
e:11pt;font-family:Calibri,sans-serif"><u></u>=C2=A0<u></u></div></div><div=
><div style=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-serif">Th=
e consensus was option 1A.<u></u><u></u></div></div><div><div style=3D"marg=
in:0in;font-size:11pt;font-family:Calibri,sans-serif"><u></u>=C2=A0<u></u><=
/div></div><div><div style=3D"margin:0in;font-size:11pt;font-family:Calibri=
,sans-serif">Additionally, we noted that this does not preclude=C2=A0us fro=
m<u></u><u></u></div></div><div><div style=3D"margin:0in;font-size:11pt;fon=
t-family:Calibri,sans-serif">building a second protocol at a later date if =
new information<u></u><u></u></div></div><div><div style=3D"margin:0in;font=
-size:11pt;font-family:Calibri,sans-serif">emerges.<u></u><u></u></div></di=
v><div><div style=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-ser=
if"><u></u>=C2=A0<u></u></div></div><div><div style=3D"margin:0in;font-size=
:11pt;font-family:Calibri,sans-serif">Question 2: UDP-based protocols<u></u=
><u></u></div></div><div><div style=3D"margin:0in;font-size:11pt;font-famil=
y:Calibri,sans-serif">=C2=A0 =C2=A0 Which UDP-based option should we adopt =
as a starting<u></u><u></u></div></div><div><div style=3D"margin:0in;font-s=
ize:11pt;font-family:Calibri,sans-serif">=C2=A0 =C2=A0 point for WebTranspo=
rt protocol?<br>=C2=A0 =C2=A0 2A: WebTransport over HTTP/3<br>=C2=A0 =C2=A0=
 2B: WebTransport over QUIC directly (separate ALPN)<u></u><u></u></div></d=
iv><div><div style=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-se=
rif"><u></u>=C2=A0<u></u></div></div><div><div style=3D"margin:0in;font-siz=
e:11pt;font-family:Calibri,sans-serif">The consensus was option 2A.<u></u><=
u></u></div></div><div><div style=3D"margin:0in;font-size:11pt;font-family:=
Calibri,sans-serif"><u></u>=C2=A0<u></u></div></div><div><div style=3D"marg=
in:0in;font-size:11pt;font-family:Calibri,sans-serif">Additionally, we disc=
ussed pooling and decided that we would<u></u><u></u></div></div><div><div =
style=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-serif">not allo=
w pooling in=C2=A0WebTransport over HTTP/3 for now, due<u></u><u></u></div>=
</div><div><div style=3D"margin:0in;font-size:11pt;font-family:Calibri,sans=
-serif">to the complexities of pooling.<u></u><u></u></div></div><div><div =
style=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-serif"><u></u>=
=C2=A0<u></u></div></div><div><div style=3D"margin:0in;font-size:11pt;font-=
family:Calibri,sans-serif">We&#39;d like to confirm this consensus on the l=
ist. If you disagree<u></u><u></u></div></div><div><div style=3D"margin:0in=
;font-size:11pt;font-family:Calibri,sans-serif">with these points, please r=
eply on the list. If you do so, please<u></u><u></u></div></div><div><div s=
tyle=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-serif">state how=
 strongly you feel - whether you are expressing a<u></u><u></u></div></div>=
<div><div style=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-serif=
">preference, or an imperative. Please also provide as much<u></u><u></u></=
div></div><div><div style=3D"margin:0in;font-size:11pt;font-family:Calibri,=
sans-serif">detail as possible to explain your position. Please also respon=
d<u></u><u></u></div></div><div><div style=3D"margin:0in;font-size:11pt;fon=
t-family:Calibri,sans-serif">if you support this consensus - a simple &quot=
;I support this consensus&quot;<u></u><u></u></div></div><div><div style=3D=
"margin:0in;font-size:11pt;font-family:Calibri,sans-serif">email to the lis=
t would be helpful.<u></u><u></u></div></div><div><div style=3D"margin:0in;=
font-size:11pt;font-family:Calibri,sans-serif"><u></u>=C2=A0<u></u></div></=
div><div><div style=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-s=
erif">We&#39;ll be running this consensus call for two weeks, please reply<=
u></u><u></u></div></div><div><div style=3D"margin:0in;font-size:11pt;font-=
family:Calibri,sans-serif">before 2021-01-26, the chairs will determine con=
sensus on that date.<u></u><u></u></div></div><div><div style=3D"margin:0in=
;font-size:11pt;font-family:Calibri,sans-serif"><u></u>=C2=A0<u></u></div><=
/div><div><div style=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-=
serif">Thanks,<u></u><u></u></div></div><div><div style=3D"margin:0in;font-=
size:11pt;font-family:Calibri,sans-serif">David<u></u><u></u></div></div></=
div></div><span style=3D"font-family:Helvetica;font-size:12px;font-style:no=
rmal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text=
-align:start;text-indent:0px;text-transform:none;white-space:normal;word-sp=
acing:0px;text-decoration:none;float:none;display:inline">--<span>=C2=A0</s=
pan></span><br style=3D"font-family:Helvetica;font-size:12px;font-style:nor=
mal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-=
align:start;text-indent:0px;text-transform:none;white-space:normal;word-spa=
cing:0px;text-decoration:none"><span style=3D"font-family:Helvetica;font-si=
ze:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;lette=
r-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white=
-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inli=
ne">Webtransport mailing list</span><br style=3D"font-family:Helvetica;font=
-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;le=
tter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;wh=
ite-space:normal;word-spacing:0px;text-decoration:none"><span style=3D"font=
-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal=
;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;=
text-transform:none;white-space:normal;word-spacing:0px;text-decoration:non=
e;float:none;display:inline"><a href=3D"mailto:Webtransport@ietf.org" targe=
t=3D"_blank">Webtransport@ietf.org</a></span><br style=3D"font-family:Helve=
tica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:=
normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transfor=
m:none;white-space:normal;word-spacing:0px;text-decoration:none"><span styl=
e=3D"font-family:Helvetica;font-size:12px;font-style:normal;font-variant-ca=
ps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-in=
dent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decor=
ation:none;float:none;display:inline"><a href=3D"https://www.ietf.org/mailm=
an/listinfo/webtransport" target=3D"_blank">https://www.ietf.org/mailman/li=
stinfo/webtransport</a></span></div></blockquote></div><br></div></div>-- <=
br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport=
</a><br>
</blockquote></div>

--000000000000a5413905b8b83280--


From nobody Tue Jan 12 12:40:34 2021
Return-Path: <morten@steinwurf.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 54F563A11BE for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 12:40:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.158
X-Spam-Level: 
X-Spam-Status: No, score=-2.158 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 K9VLvh87WNDj for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 12:40:30 -0800 (PST)
Received: from mailout-taastrup.gigahost.dk (mailout-taastrup.gigahost.dk [46.183.139.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29FD33A11C1 for <webtransport@ietf.org>; Tue, 12 Jan 2021 12:40:29 -0800 (PST)
Received: from mailout.gigahost.dk (mailout.gigahost.dk [89.186.169.112]) by mailout-taastrup.gigahost.dk (Postfix) with ESMTP id 1882F1883FC5 for <webtransport@ietf.org>; Tue, 12 Jan 2021 20:40:28 +0000 (UTC)
Received: from smtp.gigahost.dk (smtp.gigahost.dk [89.186.169.109]) by mailout.gigahost.dk (Postfix) with ESMTP id 0BD8F7806AB for <webtransport@ietf.org>; Tue, 12 Jan 2021 20:40:28 +0000 (UTC)
Received: by smtp.gigahost.dk (Postfix, from userid 1000) id EEEE19421972; Tue, 12 Jan 2021 20:40:27 +0000 (UTC)
X-Screener-Id: f8b5956341cafa01bc0fc2c7b7d4a245e1dff3de
Received: from [192.168.1.184] (D4709446.rev.sefiber.dk [212.112.148.70]) by smtp.gigahost.dk (Postfix) with ESMTPSA id CE24E9421970 for <webtransport@ietf.org>; Tue, 12 Jan 2021 20:40:27 +0000 (UTC)
To: webtransport@ietf.org
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <1EE7A63C-E68D-4B70-A8CB-C2A6003AC467@fb.com> <C4FFF30E-A8D6-4471-8FC4-C6C4A00ED679@apple.com> <CAHVo=Z=aP-OsgE87JGYT7xAjLLrgHKpa-16wtvpoCJp7F_209g@mail.gmail.com>
From: "Morten V. Pedersen" <morten@steinwurf.com>
Message-ID: <dcf8a612-8d2f-f796-35c0-fb471166cf48@steinwurf.com>
Date: Tue, 12 Jan 2021 21:40:27 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <CAHVo=Z=aP-OsgE87JGYT7xAjLLrgHKpa-16wtvpoCJp7F_209g@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------C97B7A4C9086EABEEF7A9F95"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/i5bNbNHLHjKB9SGZh2F4047s1Yg>
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: Tue, 12 Jan 2021 20:40:32 -0000

This is a multi-part message in MIME format.
--------------C97B7A4C9086EABEEF7A9F95
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

I'm sorry for being uninformed here. But does this preclude unreliable 
datagram support from an application point of view. I.e. will users of 
Webtransport be able to send unreliable datagrams when using 
Webtransport over HTTP/3?

All the best,
Morten

On 12/01/2021 19.28, Luke Curley wrote:
> Yeah, I want to reaffirm that my vote for HTTP/3 was tied to the 
> removal of pooling. The current Http3Transport draft is more complex 
> than it needs to be in order to support pooling, which is a fringe 
> optimization at best.
>
> On Tue, Jan 12, 2021 at 10:15 AM Eric Kinnear 
> <ekinnear=40apple.com@dmarc.ietf.org 
> <mailto:40apple.com@dmarc.ietf.org>> wrote:
>
>     I support this consensus.
>
>     To Alan’s point, I’d expect that we’ll continue to discuss
>     pooling, but that we’re not committing to delivering something
>     that supports pooling without further identifying the complexities
>     involved and designing something which sufficiently resolves those
>     concerns. (As would be reasonable for any protocol feature.)
>
>     Thanks,
>     Eric
>
>
>>     On Jan 12, 2021, at 10:10 AM, Alan Frindell
>>     <afrind=40fb.com@dmarc.ietf.org
>>     <mailto:afrind=40fb.com@dmarc.ietf.org>> wrote:
>>
>>     I support the consensus on Question 1 and Question2.
>>
>>     > 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.
>>     I think this statement is worded too strongly.  We discussed
>>     pooling and made it clear that choosing H3 does not mandate that
>>     we will support pooling. My understanding is that it will
>>     continue to be discussed in the working group.
>>     -Alan
>>     *From:*Webtransport <webtransport-bounces@ietf.org
>>     <mailto:webtransport-bounces@ietf.org>> on behalf of David
>>     Schinazi <dschinazi.ietf@gmail.com <mailto:dschinazi.ietf@gmail.com>>
>>     *Date:*Tuesday, January 12, 2021 at 9:26 AM
>>     *To:*WebTransport <webtransport@ietf.org
>>     <mailto:webtransport@ietf.org>>
>>     *Subject:*[Webtransport] Confirming Consensus on WebTransport
>>     protocols
>>     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
>>     --
>>     Webtransport mailing list
>>     Webtransport@ietf.org <mailto:Webtransport@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/webtransport
>>     <https://www.ietf.org/mailman/listinfo/webtransport>
>
>     -- 
>     Webtransport mailing list
>     Webtransport@ietf.org <mailto:Webtransport@ietf.org>
>     https://www.ietf.org/mailman/listinfo/webtransport
>     <https://www.ietf.org/mailman/listinfo/webtransport>
>
>

--------------C97B7A4C9086EABEEF7A9F95
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>I'm sorry for being uninformed here. But does this preclude
      unreliable datagram support from an application point of view.
      I.e. will users of Webtransport be able to send unreliable
      datagrams when using Webtransport over HTTP/3?</p>
    <p>All the best, <br>
      Morten<br>
    </p>
    <div class="moz-cite-prefix">On 12/01/2021 19.28, Luke Curley wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHVo=Z=aP-OsgE87JGYT7xAjLLrgHKpa-16wtvpoCJp7F_209g@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Yeah, I want to reaffirm that my vote for HTTP/3
        was tied to the removal of pooling. The current Http3Transport
        draft is more complex than it needs to be in order to support
        pooling, which is a fringe optimization at best.</div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Tue, Jan 12, 2021 at 10:15
          AM Eric Kinnear &lt;ekinnear=<a
            href="mailto:40apple.com@dmarc.ietf.org" target="_blank"
            moz-do-not-send="true">40apple.com@dmarc.ietf.org</a>&gt;
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div>I support this consensus. 
            <div><br>
            </div>
            <div>To Alan’s point, I’d expect that we’ll continue to
              discuss pooling, but that we’re not committing to
              delivering something that supports pooling without further
              identifying the complexities involved and designing
              something which sufficiently resolves those concerns. (As
              would be reasonable for any protocol feature.)</div>
            <div><br>
            </div>
            <div>Thanks,</div>
            <div>Eric</div>
            <div><br>
              <div><br>
                <blockquote type="cite">
                  <div>On Jan 12, 2021, at 10:10 AM, Alan Frindell &lt;<a
                      href="mailto:afrind=40fb.com@dmarc.ietf.org"
                      target="_blank" moz-do-not-send="true">afrind=40fb.com@dmarc.ietf.org</a>&gt;
                    wrote:</div>
                  <br>
                  <div>
                    <div
style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
                      <div
                        style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">I
                        support the consensus on Question 1 and
                        Question2.<br>
                        <br>
                        &gt; Additionally, we discussed pooling and
                        decided that we would</div>
                      <div
                        style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">not
                        allow pooling in WebTransport over HTTP/3 for
                        now, due</div>
                      <div
                        style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">to
                        the complexities of pooling.</div>
                      <div
                        style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> </div>
                      <div
                        style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">I
                        think this statement is worded too strongly.  We
                        discussed pooling and made it clear that
                        choosing H3 does not mandate that we will
                        support pooling. My understanding is that it
                        will continue to be discussed in the working
                        group.</div>
                      <div
                        style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> </div>
                      <div
                        style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">-Alan</div>
                      <div
                        style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> </div>
                      <div style="border-style:solid none
                        none;border-top-width:1pt;border-top-color:rgb(181,196,223);padding:3pt
                        0in 0in">
                        <div
                          style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"><b><span
                              style="font-size:12pt">From:<span> </span></span></b><span
                            style="font-size:12pt">Webtransport &lt;<a
                              href="mailto:webtransport-bounces@ietf.org"
                              target="_blank" moz-do-not-send="true">webtransport-bounces@ietf.org</a>&gt;
                            on behalf of David Schinazi &lt;<a
                              href="mailto:dschinazi.ietf@gmail.com"
                              target="_blank" moz-do-not-send="true">dschinazi.ietf@gmail.com</a>&gt;<br>
                            <b>Date:<span> </span></b>Tuesday, January
                            12, 2021 at 9:26 AM<br>
                            <b>To:<span> </span></b>WebTransport &lt;<a
                              href="mailto:webtransport@ietf.org"
                              target="_blank" moz-do-not-send="true">webtransport@ietf.org</a>&gt;<br>
                            <b>Subject:<span> </span></b>[Webtransport]
                            Confirming Consensus on WebTransport
                            protocols</span></div>
                      </div>
                      <div>
                        <div
                          style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> </div>
                      </div>
                      <div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">Hi
                            WebTransport enthusiasts,</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> </div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">Today
                            we had an interim of the IETF WEBTRANS WG,</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">where
                            we reached consensus in the (virtual) room
                            on</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">the
                            following questions:</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> </div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">Question
                            1: number of protocols</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> 
                              Should the working group adopt only one
                            UDP-based transport?<br>
                                1A: only one transport (QUIC or HTTP/3)<br>
                                1B: multiple transports (QUIC and
                            HTTP/3)</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> </div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">The
                            consensus was option 1A.</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> </div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">Additionally,
                            we noted that this does not preclude us from</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">building
                            a second protocol at a later date if new
                            information</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">emerges.</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> </div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">Question
                            2: UDP-based protocols</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> 
                              Which UDP-based option should we adopt as
                            a starting</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> 
                              point for WebTransport protocol?<br>
                                2A: WebTransport over HTTP/3<br>
                                2B: WebTransport over QUIC directly
                            (separate ALPN)</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> </div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">The
                            consensus was option 2A.</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> </div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">Additionally,
                            we discussed pooling and decided that we
                            would</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">not
                            allow pooling in WebTransport over HTTP/3
                            for now, due</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">to
                            the complexities of pooling.</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> </div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">We'd
                            like to confirm this consensus on the list.
                            If you disagree</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">with
                            these points, please reply on the list. If
                            you do so, please</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">state
                            how strongly you feel - whether you are
                            expressing a</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">preference,
                            or an imperative. Please also provide as
                            much</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">detail
                            as possible to explain your position. Please
                            also respond</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">if
                            you support this consensus - a simple "I
                            support this consensus"</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">email
                            to the list would be helpful.</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> </div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">We'll
                            be running this consensus call for two
                            weeks, please reply</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">before
                            2021-01-26, the chairs will determine
                            consensus on that date.</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> </div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">Thanks,</div>
                        </div>
                        <div>
                          <div
                            style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">David</div>
                        </div>
                      </div>
                    </div>
                    <span
style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">--<span> </span></span><br
style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
                    <span
style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">Webtransport
                      mailing list</span><br
style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
                    <span
style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline"><a
                        href="mailto:Webtransport@ietf.org"
                        target="_blank" moz-do-not-send="true">Webtransport@ietf.org</a></span><br
style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
                    <span
style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline"><a
href="https://www.ietf.org/mailman/listinfo/webtransport"
                        target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/webtransport</a></span></div>
                </blockquote>
              </div>
              <br>
            </div>
          </div>
          -- <br>
          Webtransport mailing list<br>
          <a href="mailto:Webtransport@ietf.org" target="_blank"
            moz-do-not-send="true">Webtransport@ietf.org</a><br>
          <a href="https://www.ietf.org/mailman/listinfo/webtransport"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/webtransport</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
    </blockquote>
  </body>
</html>

--------------C97B7A4C9086EABEEF7A9F95--


From nobody Tue Jan 12 12:59:10 2021
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 2CDFC3A11F1 for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 12:59:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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_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 gidmHvmgP1YE for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 12:59:06 -0800 (PST)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (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 2EFD23A11F3 for <webtransport@ietf.org>; Tue, 12 Jan 2021 12:59:06 -0800 (PST)
Received: by mail-pg1-x533.google.com with SMTP id c22so2243760pgg.13 for <webtransport@ietf.org>; Tue, 12 Jan 2021 12:59:06 -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=glFhOSGbots3S8/tYsQwJh/6Zo1XC4oD6tlYBttxOjI=; b=lMrcuj5R4JU4ND91EB/Ozz+1t2zjpElD6ye87ia7geijojlMq24D4Cs9e/oZT9JpAb JOTYVezeGYwj4vi0Qc1SwKisusBDmHhH/mwwLqPdB2lZUntfd2/MTffktOyzM6Kd8mYb aV6UzNcOpCYYbnLcpJsKns7IU8out3put+JxG23QKu95KZCrXdr/5CxH7X6+DzYBaAyH t4vy1wWcuVUasU64JJl5KsDVJxmBrHHT88Tq2iFbzgn1T2wzWSejgUGpco/QxtSDYJx5 FWPIucqy3NQ9BwiBE31x9Bky9k1WJf798gV+mx83P5EHs3fM0lgppwhGaOSKQ5oApHZp Z7rg==
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=glFhOSGbots3S8/tYsQwJh/6Zo1XC4oD6tlYBttxOjI=; b=duz3LzimOrkDtaU0V2Kc29QJXR67EjME1HiKNyuRO40wnmpZ7LIa5NSMEkGeYKqGGd ovqdgitSAPhIgnnXvfVeU0EOZx1wNtm39QpaSWtax2qCKJ0+xndywSbae7f8tTacyptK 1VWrixcGJT5bqSRgpm3p/w1a1DZmKD8w2wOYHNKH1U8KDmfC0sP8CZmwqg8+SWQxtr68 6w3tu1rQsAc2aynKvVO+5bxukfbXZnYeYKLYg8jAGLre9fAUpTfwPJeCZu+OmzlbJQHP HVFY7/deJNDszoQTBzrvrD5vjdsZD1ecA9YiDcvSIzypGrn4YLUnEc65leHwVgFw8STV 5gDg==
X-Gm-Message-State: AOAM533L4TJbXP2WNmRs9LgK/+ynmPMv6ZHjvY7K45vibXFXe/Dv58/S vQSwmkBQDDT5/g6UdaJEAeghR4Cfo+VbQQWxUhKva6ob
X-Google-Smtp-Source: ABdhPJy7e4fdurnU9slLk7tK4XV1u8Yz1s/UtZp30lK7aWLv/9yxoHJltNg4mzoBkByBR34LCDfXmha4Mi8Qd35cleg=
X-Received: by 2002:aa7:96d8:0:b029:19e:bc79:cf7 with SMTP id h24-20020aa796d80000b029019ebc790cf7mr996999pfq.22.1610485145483; Tue, 12 Jan 2021 12:59:05 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <1EE7A63C-E68D-4B70-A8CB-C2A6003AC467@fb.com> <C4FFF30E-A8D6-4471-8FC4-C6C4A00ED679@apple.com> <CAHVo=Z=aP-OsgE87JGYT7xAjLLrgHKpa-16wtvpoCJp7F_209g@mail.gmail.com> <dcf8a612-8d2f-f796-35c0-fb471166cf48@steinwurf.com>
In-Reply-To: <dcf8a612-8d2f-f796-35c0-fb471166cf48@steinwurf.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Tue, 12 Jan 2021 12:58:54 -0800
Message-ID: <CAPDSy+6YG2jY5HNyZJk3av1rL4xGcTy24W4BKS9uNxo1h-f-nQ@mail.gmail.com>
To: "Morten V. Pedersen" <morten@steinwurf.com>
Cc: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000033df905b8ba4b8e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/qmMrBSzAvw45EjyL5lD5ZQ8oYaY>
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: Tue, 12 Jan 2021 20:59:08 -0000

--000000000000033df905b8ba4b8e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Morten, Yes WebTransport over HTTP/3 supports unreliable datagrams.

David

On Tue, Jan 12, 2021 at 12:40 PM Morten V. Pedersen <morten@steinwurf.com>
wrote:

> I'm sorry for being uninformed here. But does this preclude unreliable
> datagram support from an application point of view. I.e. will users of
> Webtransport be able to send unreliable datagrams when using Webtransport
> over HTTP/3?
>
> All the best,
> Morten
> On 12/01/2021 19.28, Luke Curley wrote:
>
> Yeah, I want to reaffirm that my vote for HTTP/3 was tied to the removal
> of pooling. The current Http3Transport draft is more complex than it need=
s
> to be in order to support pooling, which is a fringe optimization at best=
.
>
> On Tue, Jan 12, 2021 at 10:15 AM Eric Kinnear <ekinnear=3D
> 40apple.com@dmarc.ietf.org> wrote:
>
>> I support this consensus.
>>
>> To Alan=E2=80=99s point, I=E2=80=99d expect that we=E2=80=99ll continue =
to discuss pooling, but
>> that we=E2=80=99re not committing to delivering something that supports =
pooling
>> without further identifying the complexities involved and designing
>> something which sufficiently resolves those concerns. (As would be
>> reasonable for any protocol feature.)
>>
>> Thanks,
>> Eric
>>
>>
>> On Jan 12, 2021, at 10:10 AM, Alan Frindell <
>> afrind=3D40fb.com@dmarc.ietf.org> wrote:
>>
>> I support the consensus on Question 1 and Question2.
>>
>> > 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.
>>
>> I think this statement is worded too strongly.  We discussed pooling and
>> made it clear that choosing H3 does not mandate that we will support
>> pooling. My understanding is that it will continue to be discussed in th=
e
>> working group.
>>
>> -Alan
>>
>> *From: *Webtransport <webtransport-bounces@ietf.org> on behalf of David
>> Schinazi <dschinazi.ietf@gmail.com>
>> *Date: *Tuesday, January 12, 2021 at 9:26 AM
>> *To: *WebTransport <webtransport@ietf.org>
>> *Subject: *[Webtransport] Confirming Consensus on WebTransport protocols
>>
>> 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
>> --
>> Webtransport mailing list
>> Webtransport@ietf.org
>> https://www.ietf.org/mailman/listinfo/webtransport
>>
>>
>> --
>> Webtransport mailing list
>> Webtransport@ietf.org
>> https://www.ietf.org/mailman/listinfo/webtransport
>>
>
> --
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport
>

--000000000000033df905b8ba4b8e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Morten, Yes WebTransport over HTTP/3 supports unreliabl=
e datagrams.<div><br></div><div>David</div></div><br><div class=3D"gmail_qu=
ote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 12, 2021 at 12:40 PM=
 Morten V. Pedersen &lt;<a href=3D"mailto:morten@steinwurf.com">morten@stei=
nwurf.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
 =20
   =20
 =20
  <div>
    <p>I&#39;m sorry for being uninformed here. But does this preclude
      unreliable datagram support from an application point of view.
      I.e. will users of Webtransport be able to send unreliable
      datagrams when using Webtransport over HTTP/3?</p>
    <p>All the best, <br>
      Morten<br>
    </p>
    <div>On 12/01/2021 19.28, Luke Curley wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">Yeah, I want to reaffirm that my vote for HTTP/3
        was tied to the removal of pooling. The current Http3Transport
        draft is more complex than=C2=A0it needs to be in order to support
        pooling, which is a fringe optimization at best.</div>
      <br>
      <div class=3D"gmail_quote">
        <div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 12, 2021 at 10:15
          AM Eric Kinnear &lt;ekinnear=3D<a href=3D"mailto:40apple.com@dmar=
c.ietf.org" target=3D"_blank">40apple.com@dmarc.ietf.org</a>&gt;
          wrote:<br>
        </div>
        <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div>I support this consensus.=C2=A0
            <div><br>
            </div>
            <div>To Alan=E2=80=99s point, I=E2=80=99d expect that we=E2=80=
=99ll continue to
              discuss pooling, but that we=E2=80=99re not committing to
              delivering something that supports pooling without further
              identifying the complexities involved and designing
              something which sufficiently resolves those concerns. (As
              would be reasonable for any protocol feature.)</div>
            <div><br>
            </div>
            <div>Thanks,</div>
            <div>Eric</div>
            <div><br>
              <div><br>
                <blockquote type=3D"cite">
                  <div>On Jan 12, 2021, at 10:10 AM, Alan Frindell &lt;<a h=
ref=3D"mailto:afrind=3D40fb.com@dmarc.ietf.org" target=3D"_blank">afrind=3D=
40fb.com@dmarc.ietf.org</a>&gt;
                    wrote:</div>
                  <br>
                  <div>
                    <div style=3D"font-family:Helvetica;font-size:12px;font=
-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:no=
rmal;text-align:start;text-indent:0px;text-transform:none;white-space:norma=
l;word-spacing:0px;text-decoration:none">
                      <div style=3D"margin:0in;font-size:11pt;font-family:C=
alibri,sans-serif">I
                        support the consensus on Question 1 and
                        Question2.<br>
                        <br>
                        &gt; Additionally, we discussed pooling and
                        decided that we would</div>
                      <div style=3D"margin:0in;font-size:11pt;font-family:C=
alibri,sans-serif">not
                        allow pooling in=C2=A0WebTransport over HTTP/3 for
                        now, due</div>
                      <div style=3D"margin:0in;font-size:11pt;font-family:C=
alibri,sans-serif">to
                        the complexities of pooling.</div>
                      <div style=3D"margin:0in;font-size:11pt;font-family:C=
alibri,sans-serif">=C2=A0</div>
                      <div style=3D"margin:0in;font-size:11pt;font-family:C=
alibri,sans-serif">I
                        think this statement is worded too strongly.=C2=A0 =
We
                        discussed pooling and made it clear that
                        choosing H3 does not mandate that we will
                        support pooling. My understanding is that it
                        will continue to be discussed in the working
                        group.</div>
                      <div style=3D"margin:0in;font-size:11pt;font-family:C=
alibri,sans-serif">=C2=A0</div>
                      <div style=3D"margin:0in;font-size:11pt;font-family:C=
alibri,sans-serif">-Alan</div>
                      <div style=3D"margin:0in;font-size:11pt;font-family:C=
alibri,sans-serif">=C2=A0</div>
                      <div style=3D"border-style:solid none none;border-top=
-width:1pt;border-top-color:rgb(181,196,223);padding:3pt 0in 0in">
                        <div style=3D"margin:0in;font-size:11pt;font-family=
:Calibri,sans-serif"><b><span style=3D"font-size:12pt">From:<span>=C2=A0</s=
pan></span></b><span style=3D"font-size:12pt">Webtransport &lt;<a href=3D"m=
ailto:webtransport-bounces@ietf.org" target=3D"_blank">webtransport-bounces=
@ietf.org</a>&gt;
                            on behalf of David Schinazi &lt;<a href=3D"mail=
to:dschinazi.ietf@gmail.com" target=3D"_blank">dschinazi.ietf@gmail.com</a>=
&gt;<br>
                            <b>Date:<span>=C2=A0</span></b>Tuesday, January
                            12, 2021 at 9:26 AM<br>
                            <b>To:<span>=C2=A0</span></b>WebTransport &lt;<=
a href=3D"mailto:webtransport@ietf.org" target=3D"_blank">webtransport@ietf=
.org</a>&gt;<br>
                            <b>Subject:<span>=C2=A0</span></b>[Webtransport=
]
                            Confirming Consensus on WebTransport
                            protocols</span></div>
                      </div>
                      <div>
                        <div style=3D"margin:0in;font-size:11pt;font-family=
:Calibri,sans-serif">=C2=A0</div>
                      </div>
                      <div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">Hi
                            WebTransport enthusiasts,</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">=C2=A0</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">Today
                            we had an interim of the IETF WEBTRANS WG,</div=
>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">where
                            we reached consensus in the (virtual) room
                            on</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">the
                            following questions:</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">=C2=A0</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">Question
                            1: number of protocols</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">=C2=A0
                            =C2=A0 Should the working group adopt only one
                            UDP-based transport?<br>
                            =C2=A0 =C2=A0 1A: only one transport (QUIC or H=
TTP/3)<br>
                            =C2=A0 =C2=A0 1B: multiple transports (QUIC and
                            HTTP/3)</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">=C2=A0</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">The
                            consensus was option 1A.</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">=C2=A0</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">Additionally,
                            we noted that this does not preclude=C2=A0us fr=
om</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">building
                            a second protocol at a later date if new
                            information</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">emerges.</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">=C2=A0</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">Question
                            2: UDP-based protocols</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">=C2=A0
                            =C2=A0 Which UDP-based option should we adopt a=
s
                            a starting</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">=C2=A0
                            =C2=A0 point for WebTransport protocol?<br>
                            =C2=A0 =C2=A0 2A: WebTransport over HTTP/3<br>
                            =C2=A0 =C2=A0 2B: WebTransport over QUIC direct=
ly
                            (separate ALPN)</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">=C2=A0</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">The
                            consensus was option 2A.</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">=C2=A0</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">Additionally,
                            we discussed pooling and decided that we
                            would</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">not
                            allow pooling in=C2=A0WebTransport over HTTP/3
                            for now, due</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">to
                            the complexities of pooling.</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">=C2=A0</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">We&#39;d
                            like to confirm this consensus on the list.
                            If you disagree</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">with
                            these points, please reply on the list. If
                            you do so, please</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">state
                            how strongly you feel - whether you are
                            expressing a</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">preference,
                            or an imperative. Please also provide as
                            much</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">detail
                            as possible to explain your position. Please
                            also respond</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">if
                            you support this consensus - a simple &quot;I
                            support this consensus&quot;</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">email
                            to the list would be helpful.</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">=C2=A0</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">We&#39;ll
                            be running this consensus call for two
                            weeks, please reply</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">before
                            2021-01-26, the chairs will determine
                            consensus on that date.</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">=C2=A0</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">Thanks,</div>
                        </div>
                        <div>
                          <div style=3D"margin:0in;font-size:11pt;font-fami=
ly:Calibri,sans-serif">David</div>
                        </div>
                      </div>
                    </div>
                    <span style=3D"font-family:Helvetica;font-size:12px;fon=
t-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:n=
ormal;text-align:start;text-indent:0px;text-transform:none;white-space:norm=
al;word-spacing:0px;text-decoration:none;float:none;display:inline">--<span=
>=C2=A0</span></span><br style=3D"font-family:Helvetica;font-size:12px;font=
-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:no=
rmal;text-align:start;text-indent:0px;text-transform:none;white-space:norma=
l;word-spacing:0px;text-decoration:none">
                    <span style=3D"font-family:Helvetica;font-size:12px;fon=
t-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:n=
ormal;text-align:start;text-indent:0px;text-transform:none;white-space:norm=
al;word-spacing:0px;text-decoration:none;float:none;display:inline">Webtran=
sport
                      mailing list</span><br style=3D"font-family:Helvetica=
;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:norm=
al;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:no=
ne;white-space:normal;word-spacing:0px;text-decoration:none">
                    <span style=3D"font-family:Helvetica;font-size:12px;fon=
t-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:n=
ormal;text-align:start;text-indent:0px;text-transform:none;white-space:norm=
al;word-spacing:0px;text-decoration:none;float:none;display:inline"><a href=
=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@ietf.org</=
a></span><br style=3D"font-family:Helvetica;font-size:12px;font-style:norma=
l;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-al=
ign:start;text-indent:0px;text-transform:none;white-space:normal;word-spaci=
ng:0px;text-decoration:none">
                    <span style=3D"font-family:Helvetica;font-size:12px;fon=
t-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:n=
ormal;text-align:start;text-indent:0px;text-transform:none;white-space:norm=
al;word-spacing:0px;text-decoration:none;float:none;display:inline"><a href=
=3D"https://www.ietf.org/mailman/listinfo/webtransport" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/webtransport</a></span></div>
                </blockquote>
              </div>
              <br>
            </div>
          </div>
          -- <br>
          Webtransport mailing list<br>
          <a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtra=
nsport@ietf.org</a><br>
          <a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" re=
l=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/we=
btransport</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset></fieldset>
    </blockquote>
  </div>

-- <br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport=
</a><br>
</blockquote></div>

--000000000000033df905b8ba4b8e--


From nobody Tue Jan 12 16:02:29 2021
Return-Path: <mt@lowentropy.net>
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 A78133A1497 for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 16:02:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=lowentropy.net header.b=XEbevR9W; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CZltQ2c3
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 NO7E2UQH5q9f for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 16:02:26 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82EBB3A1492 for <webtransport@ietf.org>; Tue, 12 Jan 2021 16:02:26 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E051F5C04BB for <webtransport@ietf.org>; Tue, 12 Jan 2021 19:02:25 -0500 (EST)
Received: from imap10 ([10.202.2.60]) by compute1.internal (MEProxy); Tue, 12 Jan 2021 19:02:25 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=pZV+DNJRSPOgqEpNkU/NnsdthVS9RQK GnloO1MVGRJ0=; b=XEbevR9WCVQQTK08kRoPWdwRWrNj2yWCYfkFsTtf24cD5ut HPu5nyA7Eo74M+el6ZrWqoxWX22ysSkkOi/e4t9tHRrvTCZfLbRNi5d8H8T1QfD2 WEhPPBj9en6l1YCOVrKaB9Lg8sMb1P230uX/aja3fEDtfMDNPb5t9WhwEg+9dSBs jXFkDQR7gJ7GY2+2NEvTtVoY+wuUi3L3IXzuBe6EL6wbX5k1dJ5/SGTuU0eRp/VR sjd+Z2pE8a9JCWarZZI3l2KBpqhc3NT5YgbsP4hliXKvo//wT6md+xLzmQLTK/Ig tarSb6FfbZaNGDFryoR+fCeZxBIzXsS/UjyO1oQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=pZV+DN JRSPOgqEpNkU/NnsdthVS9RQKGnloO1MVGRJ0=; b=CZltQ2c3AYBlkQXkwKmvHi pDqynD9eNri8+L8y4KzzEHyNczJcXcUyVzh9paTKtVSXpInCVmRlnTzVsGm1om/g 9EOCWCyGLOLczW5qjgo3DVtb98NPX9lfQI8HQtSoiBMNuZEAmvxvEOqa6Q7yfUtR S7vCe9S0nEYaPAVoMiTptFInsNhD+7s+zspC67MAoFhThaYD/RAqKUCR+Ja4C0pN 1vVNHINaQrXsXlAu4NMOVfNx9R90ai7B4s/9RFOj3MIb+d/I3v2YwDlnPCYPBPtr 7WHaPD6P89/YuGkZUscZF7oZp0DxWrT+fZDhv9a9rPW2QIip90h2+Y1xK/cwXjqg ==
X-ME-Sender: <xms:kTj-X0VDNOdUbqgnTZ5vOPqphEEpFtJaEACf3LthtZVK_F0I7j_bBA> <xme:kTj-X4m-QodqaPYHIVIcRA7qIg3ht6-Ix7MtWuha2NPIHbTZA7a9cw3wewolX5o3z mDrVXiBJRqopSICKzY>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedukedrtddugddukecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfeekve fhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:kTj-X4aORvrzsPB_h5r54Ltr5GhFqpWZQTnQ1SBx6sBdrkn8HB0Byg> <xmx:kTj-XzV_gtCgSNuy9ocAYlIdngzx4AZgT9Rf5uSMtQrcUyP4zLrc_Q> <xmx:kTj-X-mL-XwTRTx7Gf4vSWuFQrM6A4m4hrCijqIy5OZoyDlSi6kYgg> <xmx:kTj-X6zxzWPPm8AAw41Y2W3PVomWL_2nqxcrrLuxi7pfwLniVMP7ag>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 9A6892007E; Tue, 12 Jan 2021 19:02:25 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-45-g4839256-fm-20210104.001-g48392560
Mime-Version: 1.0
Message-Id: <1003bdcf-dc36-47ce-a4f5-dcfd9b2146b8@www.fastmail.com>
In-Reply-To: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com>
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com>
Date: Wed, 13 Jan 2021 11:02:05 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: webtransport@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/31x7jjNa22hJqDVxT9eDwlL6rOQ>
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: Wed, 13 Jan 2021 00:02:28 -0000

On Wed, Jan 13, 2021, at 04:25, David Schinazi wrote:
> The consensus was option 1A.

Great!

> The consensus was option 2A.

I can live with that.  Can I request a brief summary of the reasons?
 
> 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.

I don't think that this group gets to say that.  If we are using HTTP, then we are using HTTP.  We might decide that in browsers we want to keep the connections separate for $reasons, but I am opposed to saying that.

Unless of course I'm missing context in the same way I missed the meeting.


From nobody Tue Jan 12 21:57:22 2021
Return-Path: <bernard.aboba@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 8D5B33A0BC7 for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 21:57:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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_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 30h6UK0jwrjB for <webtransport@ietfa.amsl.com>; Tue, 12 Jan 2021 21:57:18 -0800 (PST)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 D36403A0C1B for <webtransport@ietf.org>; Tue, 12 Jan 2021 21:57:17 -0800 (PST)
Received: by mail-lj1-x233.google.com with SMTP id b10so1216898ljp.6 for <webtransport@ietf.org>; Tue, 12 Jan 2021 21:57:17 -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=ckELDeWOw6iwSHHlxlR0dZ0NGAbURAFiGN94faXfwYI=; b=CTefxJmsg8sxUbvbM3PcS+s1CX+d64K8VdI9pV5BQunht4KJmpVHahs1QnvSTYOpqo AiSvV7zNQiGHsnIY3VyRaQ23UFzRG91sXswpD9GO8buXE6LsGRaX45Wl4NozMqONlLfG UhPvk4W8YvqsrVdHiau40OgUZve1R8Q86I2PC5oShMe+w+ccAgvOpnIwLALw0bP16sM5 Sh/e3l7M0UysRhMw67AkSC6ZuuNGga1ZTQi5UnQf1kCiZM8gFN3h7jC0kfG8i+hVmsBV QyVS7P5ZbLEEv83vrajgNpb3DDtyq0z59gyYUq8JFQc45JRM82s2X+BhWu4vgyatdk5T 7yuA==
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=ckELDeWOw6iwSHHlxlR0dZ0NGAbURAFiGN94faXfwYI=; b=nDryk4fe54XDy+b4RPNtfKzGOXv+dmBnywdw7GQWWw3qDZFlOSv0WGSKIk+DXBCZ2s URxGuWTAfBSZsD4SZ3RTeOS6VR54LHywJ1d59+U7bQvgLOaZh2oouQvoQyzWeQur5Clj sgZp7jG62F6Fk1ZHfYQd6uy24nZrmCkLQJN8TF7uale49vEYoPq2xWUmXX6Xec2E8anL q+1urN232QZ24KC8cCH78VPWanqnLjBJDCtPECVAiDCWi62dwwtDksXlCA5crSUxPaqV Mf8tM/lnoNEwpElV5f6/AfcUYoFkHH7S1pR0NzYj8OsYWtQ+hwv6Ifs28VKhoig5/hr3 6kXw==
X-Gm-Message-State: AOAM532vdg9mvN2ADaeQKIUAY86Mh20fL+gKN9aFMUhFhABjz02DBfT6 vERYUJLyJtI9Pz5QnaOEg61VHF03tmrMQQMJJT5gwO6gzbg=
X-Google-Smtp-Source: ABdhPJzzhnQbFHW4Oea5K8vrBhYxWAjgmuNntMAgLNUJh9usgroamkVDAi5llbkH1+lRUqqMS76vp9TkZotQ6z9J44U=
X-Received: by 2002:a2e:586:: with SMTP id 128mr215003ljf.273.1610517435345; Tue, 12 Jan 2021 21:57:15 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <1003bdcf-dc36-47ce-a4f5-dcfd9b2146b8@www.fastmail.com>
In-Reply-To: <1003bdcf-dc36-47ce-a4f5-dcfd9b2146b8@www.fastmail.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Tue, 12 Jan 2021 21:57:05 -0800
Message-ID: <CAOW+2dv0=xj1E5m9TN=88EDzfY=xGvEhShR2gq1OQUPF4KUEKw@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a36e5105b8c1cfc3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/jyyIvXyxsbG6qapVzYB3-N9UHqA>
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: Wed, 13 Jan 2021 05:57:21 -0000

--000000000000a36e5105b8c1cfc3
Content-Type: text/plain; charset="UTF-8"

Martin said:

"I don't think that this group gets to say that.  If we are using HTTP,
then we are using HTTP.  We might decide that in browsers we want to keep
the connections separate for $reasons, but I am opposed to saying that.

Unless of course I'm missing context in the same way I missed the meeting."

[BA] The pooling discussion surfaced both API and protocol concerns, and
it  probably would be wise to separate them, because they are the
responsibilities of different groups.

For example, the W3C WebTransport WG may consider API issues with respect
to WebTransport pooling/ There is in fact an open issue (128
<https://github.com/w3c/webtransport/issues/128>) on this, which the WG
considered sufficiently well understood to label "Ready for PR".  I do
think it is possible to develop a PR for that Issue as well as some of the
API concerns raised at the meeting, addressing issues relating to pooling
of WebTransport connections with each other.

That said, the IETF WEBTRANS WG does get to opine on the protocol aspects
of pooling, and a number of concerns have been raised in that area,
particularly with respect to allowing interleaving of  HTTP/3
Request/Responses and WebTransport on the same QUIC connection.  This does
appear complex enough to not be considered "ready for PR" at either the API
or protocol levels. For example:

1. WebTransport requires negotiation of transport parameters (e.g. support
for HTTP/3 datagrams) that would normally not be required for a QUIC
connection used for HTTP/3 Request/Response.  So even if you were to have a
QUIC connection originally negotiated for use with HTTP/3, it would not be
immediateliy suitable for use with WebTransport.

2. Even if you did find a QUIC connection with the appropriate transport
parameters, interleaving HTTP/3 Request/Responses with WebTransport
streams will raise questions about how the protocols work with each other
(e.g. how stream IDs are allocated, as well as flow control,
prioritization, etc.).

Personally, I don't believe that either of these Issues are unsolvable, but
since pooling is an optimization, an argument can be made that the WG
should intiailly focus on more basic concerns.

On Tue, Jan 12, 2021 at 4:02 PM Martin Thomson <mt@lowentropy.net> wrote:

> On Wed, Jan 13, 2021, at 04:25, David Schinazi wrote:
> > The consensus was option 1A.
>
> Great!
>
> > The consensus was option 2A.
>
> I can live with that.  Can I request a brief summary of the reasons?
>
> > 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.
>
> I don't think that this group gets to say that.  If we are using HTTP,
> then we are using HTTP.  We might decide that in browsers we want to keep
> the connections separate for $reasons, but I am opposed to saying that.
>
> Unless of course I'm missing context in the same way I missed the meeting.
>
> --
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport
>

--000000000000a36e5105b8c1cfc3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Martin said:=C2=A0<div><br></div><div>&qu=
ot;I don&#39;t think that this group gets to say that.=C2=A0 If we are usin=
g HTTP, then we are using HTTP.=C2=A0 We might decide that in browsers we w=
ant to keep the connections separate for $reasons, but I am opposed to sayi=
ng that.</div><br><div>Unless of course I&#39;m missing context in the same=
 way I missed the meeting.&quot;</div><div><br></div><div>[BA] The pooling =
discussion surfaced both API and protocol concerns, and it=C2=A0 probably=
=C2=A0would be wise to separate them, because they are the responsibilities=
 of different groups.=C2=A0</div><div><br></div><div>For example, the W3C W=
ebTransport WG may consider API issues with respect to WebTransport pooling=
/ There is in fact an open issue (<a href=3D"https://github.com/w3c/webtran=
sport/issues/128">128</a>) on this, which the WG considered sufficiently we=
ll understood to label &quot;Ready for PR&quot;.=C2=A0 I do think it is pos=
sible to develop a PR for that Issue as well as some of the API concerns ra=
ised at the meeting, addressing issues relating to pooling of WebTransport =
connections with each other.</div><div><br></div><div>That said, the IETF W=
EBTRANS WG does get to opine on the protocol aspects of pooling, and a numb=
er of concerns have been raised in that area, particularly with respect to =
allowing interleaving of=C2=A0 HTTP/3 Request/Responses and WebTransport on=
 the same QUIC connection.=C2=A0 This does appear complex enough to not be =
considered &quot;ready for PR&quot; at either the API or protocol levels. F=
or example:=C2=A0</div><div><br></div><div>1. WebTransport requires negotia=
tion of transport parameters (e.g. support for HTTP/3 datagrams) that would=
 normally not be required for a QUIC connection used for HTTP/3 Request/Res=
ponse.=C2=A0 So even if you were to have a QUIC connection originally negot=
iated for use with HTTP/3, it would not be immediateliy suitable for use wi=
th WebTransport.=C2=A0</div><div><br></div><div>2. Even if you did find a Q=
UIC connection with the appropriate transport parameters, interleaving HTTP=
/3 Request/Responses with WebTransport=C2=A0 streams will raise questions a=
bout how the protocols work with each other (e.g. how stream IDs are alloca=
ted, as well as flow control, prioritization, etc.).=C2=A0</div><div><br></=
div><div>Personally, I don&#39;t believe that either of these Issues are un=
solvable, but since pooling is an optimization, an argument can be made tha=
t the WG should intiailly focus on more basic concerns.</div></div></div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, =
Jan 12, 2021 at 4:02 PM Martin Thomson &lt;<a href=3D"mailto:mt@lowentropy.=
net">mt@lowentropy.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">On Wed, Jan 13, 2021, at 04:25, David Schinazi wrote:=
<br>
&gt; The consensus was option 1A.<br>
<br>
Great!<br>
<br>
&gt; The consensus was option 2A.<br>
<br>
I can live with that.=C2=A0 Can I request a brief summary of the reasons?<b=
r>
<br>
&gt; Additionally, we discussed pooling and decided that we would<br>
&gt; not allow pooling in WebTransport over HTTP/3 for now, due<br>
&gt; to the complexities of pooling.<br>
<br>
I don&#39;t think that this group gets to say that.=C2=A0 If we are using H=
TTP, then we are using HTTP.=C2=A0 We might decide that in browsers we want=
 to keep the connections separate for $reasons, but I am opposed to saying =
that.<br>
<br>
Unless of course I&#39;m missing context in the same way I missed the meeti=
ng.<br>
<br>
-- <br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport=
</a><br>
</blockquote></div>

--000000000000a36e5105b8c1cfc3--


From nobody Wed Jan 13 02:23:57 2021
Return-Path: <mt@lowentropy.net>
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 1B57B3A0C40 for <webtransport@ietfa.amsl.com>; Wed, 13 Jan 2021 02:23:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=lowentropy.net header.b=G6qHjNmE; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=e9WDELQx
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 Hmei47e66aVz for <webtransport@ietfa.amsl.com>; Wed, 13 Jan 2021 02:23:54 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F3A33A0C3B for <webtransport@ietf.org>; Wed, 13 Jan 2021 02:23:54 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B0B1E5C00EB; Wed, 13 Jan 2021 05:23:53 -0500 (EST)
Received: from imap10 ([10.202.2.60]) by compute1.internal (MEProxy); Wed, 13 Jan 2021 05:23:53 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm1; bh=TGKvMXWNhdufiQN7ElFJlxxieAiU M1V+gXDmS6rf7Rs=; b=G6qHjNmExkDWmjG+wox+gTyZJAdt6iCmDAFWtUvCqQz1 faDUvX1kcEfLfWtPVJeLVUarjBG80goJlMiU5PgbmTajVFSxGrBzs5c/zghwq44+ Z1sJH2NzHHVuFgYSgo9iJVhrrI5TmX4bPr6vYPYKvDLE9t3rJbAyF7ec9eCvkONo kjwCVkLjjx21s1fuPNSlCYH6CvAK4elRNA59kGLsxchpIn8b6QRD1qXaBQxfOnsh MaoK9l4ugQj2j/NpgMb7Zy0mbe5rKkojbviYv2b7RGubhyr3048vtkU+f8CdxPb4 Uq58C7PTZ78ImHr+meAZbL5uBS+fStbG8MZ4qNqsFg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=TGKvMX WNhdufiQN7ElFJlxxieAiUM1V+gXDmS6rf7Rs=; b=e9WDELQx7tKM44/1Nj+Yiq zJLItMvmTywO2XQy1EJnlaeh22HUQHiyPgdw8jpkx3jGxlJFO61D6RFPIN5keXef UwfmkKHrYLKZC2iQ+kjL+K5DzSpqOIhnZLDg+awWF6fY3MeYK7hqD7dMCOZkMMXE ip+XCjlXIy5UYdg19zVWE5PSnU1g+1welX//feApP79nsCvIYCEZzdoKU6GbqV5D BXo6ozdAhrvIjto8qOAMZjL25kiiigtE/ikIhynq3p+CCPSnCCLPKmoy0hlZEr1q ACzi94HHPQBt6mD0OcZ9iRGsRhTiFT0Jcr3bg8mprOw/Iq7hPJe3tbU2ROE2SlcA ==
X-ME-Sender: <xms:Ocr-X5cBGHhsGIJD0HPHqBt0NV176wTz2cwOcwwpbJ3sLebxMXGOgw> <xme:Ocr-X3Nz0GR4iWVIYAYKiPDJM-lxX9kulugAxUYzc3qFgvzkbkVK1cvxyr_l-q0Sq YyQ3ApoDTZZ9fxp9HE>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedukedrtdefgdduhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedfofgrrhht ihhnucfvhhhomhhsohhnfdcuoehmtheslhhofigvnhhtrhhophihrdhnvghtqeenucggtf frrghtthgvrhhnpefggfeiueektedtueekiedtgfeiueeijeffiedvtdehiedugefflefh gedtuefhieenucffohhmrghinhephhhtthhpohhrfigvsghtrhgrnhhsphhorhhtrghtth hhrghtphhoihhnthdrshhonecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:Ocr-XyjS3lMxSqG8KFOV8NbV1PDzgw2x-xWqlKOR76Kqhk8QTwqLSw> <xmx:Ocr-Xy_Xcpi6da8Ix8rBn745YM6J6ofmaZIi2vDxuQbnbibh-EXDrA> <xmx:Ocr-X1ud0XOQwUZT9eCkqiN5Y1ItG7NhN-fpytHC0qLLriKxfRLPAw> <xmx:Ocr-X66B9gItRsYVYWLz4h9spgqNvT5od9DsWkTuMS3e2dkJtyPbyQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 5E7B42007E; Wed, 13 Jan 2021 05:23:53 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-45-g4839256-fm-20210104.001-g48392560
Mime-Version: 1.0
Message-Id: <87e320c4-7c8c-47f0-95bb-6c2b2aa8d6cf@www.fastmail.com>
In-Reply-To: <CAOW+2dv0=xj1E5m9TN=88EDzfY=xGvEhShR2gq1OQUPF4KUEKw@mail.gmail.com>
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <1003bdcf-dc36-47ce-a4f5-dcfd9b2146b8@www.fastmail.com> <CAOW+2dv0=xj1E5m9TN=88EDzfY=xGvEhShR2gq1OQUPF4KUEKw@mail.gmail.com>
Date: Wed, 13 Jan 2021 21:23:34 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: "Bernard Aboba" <bernard.aboba@gmail.com>
Cc: WebTransport <webtransport@ietf.org>
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/LAZeQrC7bLkhR7BGuz9H-cyRqis>
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: Wed, 13 Jan 2021 10:23:56 -0000

On Wed, Jan 13, 2021, at 16:57, Bernard Aboba wrote:
> Personally, I don't believe that either of these Issues are unsolvable, 
> but since pooling is an optimization, an argument can be made that the 
> WG should intiailly focus on more basic concerns.

I am was suggesting something different.  This working group should not express an opinion on these matters.  If implementations are willing to engage with these problems, they should be free to do so without some RFC (or Internet-Draft) saying that they should not.  

If we identify constraints based on the web security model, that might be cause for a browser not to attempt pooling.  Web security is sufficiently intricate that that is a distinct possibility.  However, that would be something the W3C working group deals with (I think that's the division of responsibilities here; though that is unclear).  Either way, that should not have a significant effect on the protocol definition, which should not care about this.

In any case, I'm not aware of any reasons that would actively prevent pooling other than those you list, which just amount to "there are some tricky bits".  But that mostly relates to performance and prioritization. The first issue you mention can't be a problem, because a server has to offer all of the webtransport capabilities at the start because it can't know if this is plain HTTP or webtransport at that point.  So I'm left with "prioritization is hard", which isn't exactly news.  Is there anything else?


From nobody Wed Jan 13 07:41:05 2021
Return-Path: <bernard.aboba@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 43C893A114D for <webtransport@ietfa.amsl.com>; Wed, 13 Jan 2021 07:41:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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_FROM=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 6L7Gg4ZcWYvJ for <webtransport@ietfa.amsl.com>; Wed, 13 Jan 2021 07:41:01 -0800 (PST)
Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) (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 9B0EF3A0E60 for <webtransport@ietf.org>; Wed, 13 Jan 2021 07:41:01 -0800 (PST)
Received: by mail-pj1-x1035.google.com with SMTP id md11so1387476pjb.0 for <webtransport@ietf.org>; Wed, 13 Jan 2021 07:41:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:content-transfer-encoding:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=DapYQ1/LnHsuBaHsar4/65vZGXlPtYjRJHMc+02hI+k=; b=EBMLSlrKY+mDqgWNbwf9te8fvr9kxbAya207NSg7Uacv/C8pL8UFn2Cj0Y1+3kDPmr y2NGZzRkkHQ7enDeQ4zTFojDN8ilC/049M1O9rC4bGj5KpVANT+Mc6nq+lszjyZUD+Mr c8D9RWUcwRYP4qpBgP63E2GAng+5Ke1v07DUqftLeIMUCIVUPwXUzgq+YGlXLNhLxSh1 /3QuZYjTTqK4lAykrsT6IQtvKcghZMlM2gd7ct4xrB/ms0wU5eQrmrtuX3gI06AMsspj /c2mBcK+r8AafeEV69I8KCPM5k3h66eA7kGvUjrJnM6QpwPbhd472QsGmsDnYGTGnOjP 8LrQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=DapYQ1/LnHsuBaHsar4/65vZGXlPtYjRJHMc+02hI+k=; b=YkNC3atcxbLbBlMKHZpcSD86FhjvJVvLZ2648FU9MnXuSxJJvqftiuizrgW0gKLmT0 /TcRPyaZJV0oWr0wGwcGBmq+RAcG9UW2CsVIS2qO1nbj1Sbi20/pt6yaVrWa57cKECZB p2cIAPxwip99yrUbBusklNkwiBljKJtAUDtJFAqgxtagV3DomRZ9VvsjvjrgfHWvywYu ED5pH71MsFdgPdZajOxa70y65W3kdwYeS9Zv0T1kfuhJ9idR3ORe9GH1yt+7sXvyRW7Q 6k6N5GShQTkyMy2gUvaMkWxJpnVG2U7o+tDqI+2BsZh+jyKjXf8BGD999zD5Ki8GfwFd T1Bg==
X-Gm-Message-State: AOAM530OaimrZL/We8pZo3xOqbpH3LIQvTpjav9uGY9VyTYOn79BClOr wlzvAwLRDxkpPXvICKCSp+M=
X-Google-Smtp-Source: ABdhPJzy6fPbOVORjivyoS7kxGEBVm8DIdLQSVgkz06hrFkyFu+l3ki/l84G/tsxgr9eE4T+6jWqBQ==
X-Received: by 2002:a17:90b:e88:: with SMTP id fv8mr1542759pjb.126.1610552460716;  Wed, 13 Jan 2021 07:41:00 -0800 (PST)
Received: from ?IPv6:2600:380:7068:497f:39d6:1be0:5545:da89? ([2600:380:7068:497f:39d6:1be0:5545:da89]) by smtp.gmail.com with ESMTPSA id y15sm3192122pju.13.2021.01.13.07.40.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 13 Jan 2021 07:41:00 -0800 (PST)
From: Bernard Aboba <bernard.aboba@gmail.com>
X-Google-Original-From: Bernard Aboba <Bernard.Aboba@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Wed, 13 Jan 2021 07:31:50 -0800
Message-Id: <E130A268-3E30-4C3C-A284-8D9731F968AC@gmail.com>
References: <87e320c4-7c8c-47f0-95bb-6c2b2aa8d6cf@www.fastmail.com>
Cc: WebTransport <webtransport@ietf.org>
In-Reply-To: <87e320c4-7c8c-47f0-95bb-6c2b2aa8d6cf@www.fastmail.com>
To: Martin Thomson <mt@lowentropy.net>
X-Mailer: iPhone Mail (18C66)
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/9zJFMBQ_JFGqYqgBNj-lrTD_LfU>
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: Wed, 13 Jan 2021 15:41:04 -0000

lOn Jan 13, 2021, at 2:23 AM, Martin Thomson <mt@lowentropy.net> wrote:
>=20
> I am was suggesting something different.  This working group should not ex=
press an opinion on these matters.  If implementations are willing to engage=
 with these problems, they should be free to do so without some RFC (or Inte=
rnet-Draft) saying that they should not. =20

[BA] I don=E2=80=99t recall a suggestion to prohibit pooling outright. We di=
scussed API changes to allow an application to request that a WebTransport n=
ot be pooled, as well as a server indication to say =E2=80=9CI do not suppor=
t pooling=E2=80=9D.  Both of these seem achievable.


> If we identify constraints based on the web security model, that might be c=
ause for a browser not to attempt pooling. =20

[BA] That is the crux of Issue 128. Investigating the constraints seems usef=
ul.


From nobody Wed Jan 13 07:44:55 2021
Return-Path: <ianswett@google.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 789413A11BA for <webtransport@ietfa.amsl.com>; Wed, 13 Jan 2021 07:44:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.971
X-Spam-Level: 
X-Spam-Status: No, score=-17.971 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 ueiVi2uAEvQ9 for <webtransport@ietfa.amsl.com>; Wed, 13 Jan 2021 07:44:44 -0800 (PST)
Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) (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 446C93A11C7 for <webtransport@ietf.org>; Wed, 13 Jan 2021 07:44:43 -0800 (PST)
Received: by mail-wm1-x335.google.com with SMTP id a6so2021349wmc.2 for <webtransport@ietf.org>; Wed, 13 Jan 2021 07:44:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=i7BVtFxSoCDmJjQs4NVJha9MXMvVPSHBs9iKXfha38s=; b=QrEpymPcYC68z7n5CMJO8MQut2XMmJ1edQ6VMvNpgaeDJrhgkKTIY/OopkfoDEvTqD hBVIJb+k+WiWNjbn6E1GzBoe/49ayWDUsuVQpxF7UEMBcYyq8oBpjK5qC4To8EFGFkSl mxseFKLRobInWRC7Gz2OjA1TZbf5J5ROytAm2R9kl+1cQHpRAEAHUqvGL1as3681xzgm zI+BRjtIaNx/kjCuRWMXTEbjpMgVWPeuA5JXVOlNTRQj7jCAdXV0mP33PNcdZfqfllNC IOEBueHTIJubTKCkGS9iqKKyiUleI4x8t3xccAD5u3LffGlp6gQG1VsurSfwJIwR7a5U ETtg==
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=i7BVtFxSoCDmJjQs4NVJha9MXMvVPSHBs9iKXfha38s=; b=j7XGGXVAoTxEv3I5byy3LvyLRjHybhUCu43Q2Dp3mXrZ3FqOh/XRzzkySa8ulE1m5s 18iztKjG+TV4VTmW71mY7AGl54iyokv0Vw2DrezZRYGLt64bxp8V6kkHxzc3ND/mh5EP Lc0NpMuAgtCzmMsZDqL9oEthYrEyOQU9GuNL+/hlzXBacgSax+FXw7R5IkkHfqL14FvR pFDoghMiM1H0vVxln5od/0sE/ZN/qPrvDYdKDWa0q8K787tMp2lAdlHAfREkl3R3pOOL YUphNUEvY4dVrr+QpbW8Zf2VUJem8DjR/GJM8Jy0pl2NDGstUWMBSPBO0AJ1nAlVeJLh DwxQ==
X-Gm-Message-State: AOAM5303oY7bwwJ1Lnpqv1VOIVJqmP9wGry2C0eYRLIxsEyl0HUvRE4W TXB17CWW/M1LlAWI2LtOa0SAvfDcvxqmMTYmwYRBpg==
X-Google-Smtp-Source: ABdhPJyQO+JfCyyEHGIaEb701LiB4aiCCql3KdCTKfdsGfB3OmHSTT8SUMPYdjB65DuV84u0j/XtqopalNyyX23+nuk=
X-Received: by 2002:a1c:9a57:: with SMTP id c84mr2652606wme.183.1610552681120;  Wed, 13 Jan 2021 07:44:41 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <1003bdcf-dc36-47ce-a4f5-dcfd9b2146b8@www.fastmail.com>
In-Reply-To: <1003bdcf-dc36-47ce-a4f5-dcfd9b2146b8@www.fastmail.com>
From: Ian Swett <ianswett@google.com>
Date: Wed, 13 Jan 2021 10:44:28 -0500
Message-ID: <CAKcm_gO6VCip7bkrJMjDn4D5sjPMQMRhW2BnV5z6RK+MiUfMkg@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000073b68205b8ca0471"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/nQFSsr0ZbYGbwrp_q93SFu34F1I>
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: Wed, 13 Jan 2021 15:44:54 -0000

--00000000000073b68205b8ca0471
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 12, 2021 at 7:02 PM Martin Thomson <mt@lowentropy.net> wrote:

> On Wed, Jan 13, 2021, at 04:25, David Schinazi wrote:
> > The consensus was option 1A.
>
> Great!
>
> > The consensus was option 2A.
>
> I can live with that.  Can I request a brief summary of the reasons?
>

I asked a question like this during the interim, and I think it'd be worth
clearly documenting the reasons, as I think it'd clarify our direction a
bit.  The one that I clearly recall is that we'd have to re-invent many of
the features that HTTP/3 provides, but I'm not clear why that's the case.

>
> > 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.
>
> I don't think that this group gets to say that.  If we are using HTTP,
> then we are using HTTP.  We might decide that in browsers we want to keep
> the connections separate for $reasons, but I am opposed to saying that.
>

I suspect you're right.

I'd like to call out that there are two things which could be referred to
as 'pooling'.  One is using a single connection for HTTP/3 and WebTransport
at the same time.  The other is support for multiple WebTransport sessions
inside a single connection.  This latter type of 'pooling' is part of what
makes Http3Transport more complex than QuicTransport.  Was there ever an
explicit question about whether multiple sessions on a single connection
are necessary or even useful?  In retrospect, we were picking between two
transports as well as two different feature sets and it might be worth
splitting them apart.


> Unless of course I'm missing context in the same way I missed the meeting.
>
> --
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport
>

--00000000000073b68205b8ca0471
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 12, 2021 at 7:02 PM Marti=
n Thomson &lt;<a href=3D"mailto:mt@lowentropy.net">mt@lowentropy.net</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed,=
 Jan 13, 2021, at 04:25, David Schinazi wrote:<br>
&gt; The consensus was option 1A.<br>
<br>
Great!<br>
<br>
&gt; The consensus was option 2A.<br>
<br>
I can live with that.=C2=A0 Can I request a brief summary of the reasons?<b=
r></blockquote><div><br></div><div>I asked a question like this during the =
interim, and I think it&#39;d be worth clearly documenting the reasons, as =
I think it&#39;d clarify our direction a bit.=C2=A0 The one that I clearly =
recall is that we&#39;d have to re-invent many of the features that HTTP/3 =
provides, but I&#39;m not clear why that&#39;s the case.</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex">
<br>
&gt; Additionally, we discussed pooling and decided that we would<br>
&gt; not allow pooling in WebTransport over HTTP/3 for now, due<br>
&gt; to the complexities of pooling.<br>
<br>
I don&#39;t think that this group gets to say that.=C2=A0 If we are using H=
TTP, then we are using HTTP.=C2=A0 We might decide that in browsers we want=
 to keep the connections separate for $reasons, but I am opposed to saying =
that.<br></blockquote><div><br></div><div>I suspect you&#39;re right.</div>=
<div><br></div><div>I&#39;d like to call out that there are two things whic=
h could be referred to as &#39;pooling&#39;.=C2=A0 One is using a single co=
nnection for HTTP/3 and WebTransport at the same time.=C2=A0 The other is s=
upport for multiple WebTransport sessions inside a single connection.=C2=A0=
 This latter type of &#39;pooling&#39; is part of what makes Http3Transport=
=C2=A0more complex than QuicTransport.=C2=A0 Was there ever an explicit que=
stion about whether multiple sessions on a single connection are necessary =
or even useful?=C2=A0 In retrospect, we were picking between two transports=
 as well as two different feature sets and it might be worth splitting them=
 apart.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x">
<br>
Unless of course I&#39;m missing context in the same way I missed the meeti=
ng.<br>
<br>
-- <br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport=
</a><br>
</blockquote></div></div>

--00000000000073b68205b8ca0471--


From nobody Wed Jan 13 08:45:06 2021
Return-Path: <lucaspardue.24.7@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 AEFE53A11BE for <webtransport@ietfa.amsl.com>; Wed, 13 Jan 2021 08:45:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 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, 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 drMaVpdVhhKr for <webtransport@ietfa.amsl.com>; Wed, 13 Jan 2021 08:45:03 -0800 (PST)
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 B68933A11BC for <webtransport@ietf.org>; Wed, 13 Jan 2021 08:45:02 -0800 (PST)
Received: by mail-ed1-x532.google.com with SMTP id g1so1994749edu.4 for <webtransport@ietf.org>; Wed, 13 Jan 2021 08:45:02 -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=GILOD9yNAZYu2/y28sC5cCfkFzpm03oEN0cxx2CrSfs=; b=pqe8CU3RZUFvRcQnbbTdCKNg/FtGFI1VR2vkjxY0jbIMVoewP13ttNPMzAAjYE35b6 AdxlyBrB322JsZviMhNi6rcaKbl9c5lx6cLjzYpbLqxNpX4tqmzqZsS96nkHNIoAzkIm OIGRodpH9OAdU9JNTL5N7iBKOP4oQPwpx/NYQ4cfpBFME3qIXn/OCMVLzqYAnUmEfsuk KXKuhHl+AqJtirtY9MMo5hMscbvvobI6JhD0qZUPxIa4eIIMorPMj20zPWtZiQOtTH1y dzSxq8EJXcGWPh5B53LqtIBfluFr7SHGbkh2ecn7RY6LaNJQq5BjtmYeJvlqtxezT9Qw PuHw==
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=GILOD9yNAZYu2/y28sC5cCfkFzpm03oEN0cxx2CrSfs=; b=nQPyIQlZuJ6K3ddgfOiExedpWw9JWdHRdyaULDkZaQO8vl1FBIO5xlZWbBhtBgaI1g rhhNqhYfPiQR4P8VkB/22EAsEVoaL9r+/eoNw0i0+XCktBBkPcIrqvSESeQGDB01hwOC pagFpZC7F10m9RZ2TAylwHI0gsFWR0V0elK4ZP0eZ2QZ6Mn62U5GmtbC81oVAdwAz/8m sePo6B7/Fa6WCHlyzuyPPMK2k8Fb2aTaSBMwpw5tiGg1sS31wUp1SYhSN5A4MOJQ4Wd0 1SnLZxsc6ybMt4EOPU8AJm2ixTd80ohyDk40jMUEveZVAgaV1PcjWEOrQo+x3/zApM5l bsgQ==
X-Gm-Message-State: AOAM531wSNohWpBb/77xRDXK9MzqcTFqpIEBu4aNErj8CI5DnhVe/P1e BZNPpQAhU2qQt7IiRiMDnp9kjyLFSirilAchseRpfyQy+Dk=
X-Google-Smtp-Source: ABdhPJxQpcZAjgEnn4JSGpeXo9GPoE4XVVsehmwHAGa+7UrYJMdi1ycN71EWM8j0heKtWH18ojIJY/+CVGkbIFjhPXk=
X-Received: by 2002:a05:6402:c4:: with SMTP id i4mr2466516edu.152.1610556301213;  Wed, 13 Jan 2021 08:45:01 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <1003bdcf-dc36-47ce-a4f5-dcfd9b2146b8@www.fastmail.com> <CAKcm_gO6VCip7bkrJMjDn4D5sjPMQMRhW2BnV5z6RK+MiUfMkg@mail.gmail.com>
In-Reply-To: <CAKcm_gO6VCip7bkrJMjDn4D5sjPMQMRhW2BnV5z6RK+MiUfMkg@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Wed, 13 Jan 2021 16:44:49 +0000
Message-ID: <CALGR9obUHRn9Y-eXZjnUMQU22ZnLcw0RLs7FhrrrZOd9OM63yA@mail.gmail.com>
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: Martin Thomson <mt@lowentropy.net>, WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003984d405b8cadc27"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/sLpcMae3TcnTLUWSASusg5Ucu6Y>
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: Wed, 13 Jan 2021 16:45:06 -0000

--0000000000003984d405b8cadc27
Content-Type: text/plain; charset="UTF-8"

Hi Ian,

On Wed, Jan 13, 2021 at 3:46 PM Ian Swett <ianswett=
40google.com@dmarc.ietf.org> wrote:

>
>
> On Tue, Jan 12, 2021 at 7:02 PM Martin Thomson <mt@lowentropy.net> wrote:
>
>> On Wed, Jan 13, 2021, at 04:25, David Schinazi wrote:
>> > The consensus was option 1A.
>>
>> Great!
>>
>> > The consensus was option 2A.
>>
>> I can live with that.  Can I request a brief summary of the reasons?
>>
>
> I asked a question like this during the interim, and I think it'd be worth
> clearly documenting the reasons, as I think it'd clarify our direction a
> bit.  The one that I clearly recall is that we'd have to re-invent many of
> the features that HTTP/3 provides, but I'm not clear why that's the case.
>

I made a comment along those lines. It was mainly motivated by Victor's PR
"Refactor client indication into a full header exchange" see
https://github.com/vasilvv/webtransport/pull/18. AFAICT this is merged into
the editors copy of draft-vvv-webtransport-quic but there is no published
I-D with this change in. Victor please correct me if I'm wrong.

Not that I'm not questioning whether the motivation behind needing more
flexibility of the client indication. But it highlights that we'll discover
more things that are needed or nice to have and require additions. My
concern is that inventing something that is similar to HTTP headers but not
actually HTTP is duplication and brings risks that we need to mirror the
engineering and design effort that has already gone into HTTP. As an
implementer, it seems better to reuse HTTP semantics (i.e code I have
already, or libraries) than to invent another HTTP-alike.

Cheers,

Lucas

--0000000000003984d405b8cadc27
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Ian,<br></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 13, 2021 at 3:46 PM Ian Swett =
&lt;ianswett=3D<a href=3D"mailto:40google.com@dmarc.ietf.org">40google.com@=
dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D=
"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 12, 2021 at=
 7:02 PM Martin Thomson &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"=
_blank">mt@lowentropy.net</a>&gt; wrote:<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex">On Wed, Jan 13, 2021, at 04:25, David Schinazi wro=
te:<br>
&gt; The consensus was option 1A.<br>
<br>
Great!<br>
<br>
&gt; The consensus was option 2A.<br>
<br>
I can live with that.=C2=A0 Can I request a brief summary of the reasons?<b=
r></blockquote><div><br></div><div>I asked a question like this during the =
interim, and I think it&#39;d be worth clearly documenting the reasons, as =
I think it&#39;d clarify our direction a bit.=C2=A0 The one that I clearly =
recall is that we&#39;d have to re-invent many of the features that HTTP/3 =
provides, but I&#39;m not clear why that&#39;s the case.</div></div></div><=
/blockquote><div><br></div><div>I made a comment along those lines. It was =
mainly motivated by Victor&#39;s PR &quot;Refactor client indication into a=
 full header exchange&quot; see=C2=A0 <br></div><div><a href=3D"https://git=
hub.com/vasilvv/webtransport/pull/18">https://github.com/vasilvv/webtranspo=
rt/pull/18</a>. AFAICT this is merged into the editors copy of draft-vvv-we=
btransport-quic but there is no published I-D with this change in. Victor p=
lease correct me if I&#39;m wrong.</div><div><br></div><div>Not that I&#39;=
m not questioning whether the motivation behind needing more flexibility of=
 the client indication. But it highlights that we&#39;ll discover more thin=
gs that are needed or nice to have and require additions. My concern is tha=
t inventing something that is similar to HTTP headers but not actually HTTP=
 is duplication and brings risks that we need to mirror the engineering and=
 design effort that has already gone into HTTP. As an implementer, it seems=
 better to reuse HTTP semantics (i.e code I have already, or libraries) tha=
n to invent another HTTP-alike.</div><div><br></div><div>Cheers,</div><div>=
<br></div><div>Lucas<br></div></div></div>

--0000000000003984d405b8cadc27--


From nobody Wed Jan 13 09:16:33 2021
Return-Path: <prvs=06473b7c3c=afrind@fb.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 C17693A1215; Wed, 13 Jan 2021 09:16:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level: 
X-Spam-Status: No, score=-2.118 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 (1024-bit key) header.d=fb.com header.b=cJa73gj5; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=TQZrTkbS
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 tUCqeLlQyMKt; Wed, 13 Jan 2021 09:16:29 -0800 (PST)
Received: from mx0a-00082601.pphosted.com (mx0a-00082601.pphosted.com [67.231.145.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 101DD3A1208; Wed, 13 Jan 2021 09:16:28 -0800 (PST)
Received: from pps.filterd (m0148461.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 10DGwSFP022130; Wed, 13 Jan 2021 09:16:28 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=2hDHHzfJ2FrJNFzZ3UMzxQ+MagBq0+TgqJzPTKUk3UA=; b=cJa73gj5C+rppjAVm+8mCBAP09qXWrpqVG1QfqBmVNfPGH9oK9q8A08o4YEbsJXyH7fv lUzZs6P5zLYAq9LUX/FrdO0z4MDNuaSVBT9uS/sssEVf9TU13a8LmnhxC+GlhqM1KMOH oEDgymMDzaq+Lpo4jhivn8Q/lGmO1Ym2xCQ= 
Received: from maileast.thefacebook.com ([163.114.130.16]) by mx0a-00082601.pphosted.com with ESMTP id 361fppe7rs-19 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 13 Jan 2021 09:16:28 -0800
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (100.104.31.183) by o365-in.thefacebook.com (100.104.36.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Wed, 13 Jan 2021 09:16:27 -0800
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=V3XMZTuE+KuFJ9UT4zcql+AjEzkliezTnR3wx3sSLiKfbbQwrDiHANN+co7FLVrwVxCEC9Is18RdPnFeeDktt5W/OG1lajwuOb2MaeZqacQgG929XiZM4iPDbyDSF1ISl3qtNUZtjgmuVGdFMh68jYc6cUK7limIwV91rktN11svy4WqEnJSwb7Moxm9pO3az8aaJmiWnTx3u/JxTHB1U0RXgAUAs4FrLA/jTESk0mw6RSjo5ipgNAhnIT4uKlZza09xx9zCM7MupHU3VxUNR9CYYKKAtLs5pE6/+2jWulkkti9PrlvcY1ps9duzpZtuK8Pe5WhLOKXz3XNLdqqxKg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2hDHHzfJ2FrJNFzZ3UMzxQ+MagBq0+TgqJzPTKUk3UA=; b=PlYlq95GpXn7j2C3KBRNp65TpWQDYiHr2o6X4PpnZ4tmP880+vMkbgdlJ8BcsaPIX0XvkvjMrRgPmtWJrZqZMQgr/PmYxxWxG22oyTj1PxVG5v7/l9ctavU00MSvS7TDlnxVlvkugk1LyFezCKqEQg3TwFfa60eIcCR+yxf280TbsQVtsRK0hJqUsueEO1YyURt5LZRtqpC+FNbU/ZJ5TpnCSxI+IHjOtiMeLvz0KL8BARqmiWJqQWgY2LAIY6Y12Wh0Srf5rCaO9UxKFE3cdJZbJ8zoywwzXJxTXLubh8vCzhhTivnAxgxhJg4w2SARih7sB4AqJ7oXXaJ3/7fOpQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=fb.com; dmarc=pass action=none header.from=fb.com; dkim=pass header.d=fb.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector2-fb-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2hDHHzfJ2FrJNFzZ3UMzxQ+MagBq0+TgqJzPTKUk3UA=; b=TQZrTkbSUXCBq7fvoM+VibXts5Gra1C92WrS/l9cfThZ/rno98NfVAqV57cTh8XC1kZzib08m/dLlZKUm0JCRHg7CuUqBeRoz6v3VMHOkGqshWrhMPpVNEFFEbTzyrjNchOfB1s5mEeen47UC0ArGq0l6cx5GSfGjvuH4/39VBQ=
Received: from MN2PR15MB3405.namprd15.prod.outlook.com (2603:10b6:208:3f::11) by MN2PR15MB3391.namprd15.prod.outlook.com (2603:10b6:208:a2::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3721.19; Wed, 13 Jan 2021 17:16:25 +0000
Received: from MN2PR15MB3405.namprd15.prod.outlook.com ([fe80::b045:b577:108c:f76]) by MN2PR15MB3405.namprd15.prod.outlook.com ([fe80::b045:b577:108c:f76%7]) with mapi id 15.20.3742.012; Wed, 13 Jan 2021 17:16:25 +0000
From: Alan Frindell <afrind@fb.com>
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Martin Thomson <mt@lowentropy.net>
CC: WebTransport <webtransport@ietf.org>
Thread-Topic: [Webtransport] Confirming Consensus on WebTransport protocols
Thread-Index: AQHW6QgW3En8/QPJV0mSgKuDoOvwNqokrJeAgAEHTAD//5OTAA==
Date: Wed, 13 Jan 2021 17:16:25 +0000
Message-ID: <C3FE8766-978C-413B-B4AC-F21DFE842F46@fb.com>
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <1003bdcf-dc36-47ce-a4f5-dcfd9b2146b8@www.fastmail.com> <CAKcm_gO6VCip7bkrJMjDn4D5sjPMQMRhW2BnV5z6RK+MiUfMkg@mail.gmail.com>
In-Reply-To: <CAKcm_gO6VCip7bkrJMjDn4D5sjPMQMRhW2BnV5z6RK+MiUfMkg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.44.20121301
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=fb.com;
x-originating-ip: [63.231.38.55]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d57a3758-8624-4728-933f-08d8b7e6f4e3
x-ms-traffictypediagnostic: MN2PR15MB3391:
x-microsoft-antispam-prvs: <MN2PR15MB33919A921CA24F499063414DA7A90@MN2PR15MB3391.namprd15.prod.outlook.com>
x-fb-source: Internal
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 2sGjSoPEZMjRoHVQQk/AhE8Jz5Zon6wJ20WfTDTzqdQj/A6uat2DdzzENPBOYjUOPOeODIZmwBwHqOg3iV4pZw1dENu5O7VX92kqI3P3rjLSkqr2CBjF+e8vRVv81+orJxKcXHOtPyhCdQKGbetoFUskEQVgDzvnzUXOq+7bqxtiVphoVvLJwWLiho4P+asm1xMyRxMGErb7wyqeCVjvnTawpXoR91bFJIz8oPexFPk4xg/zsdsTeTt3V2XW+nqEYQimimNCt+5VRpluntIZOtwG4m63GzoSJy8EcI4vZ4Wv/BHi5Omxm2fiVTjAmEuRy/1y9v0NpzIoeF3vRrsBaCj88XfR5h6IuID2uDEN26UDrXagSUzeXll2u4Rq/0Q2sXL26l2EN5MctNTtt3acpnwzHEFd5IUZljJgR9BwmXOz9zHLKXNiUWBG2k7AqTq0
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR15MB3405.namprd15.prod.outlook.com; PTR:; CAT:NONE;  SFS:(346002)(366004)(376002)(39860400002)(396003)(136003)(36756003)(4326008)(2906002)(83380400001)(6486002)(76116006)(6512007)(5660300002)(91956017)(2616005)(316002)(64756008)(66446008)(8676002)(6506007)(186003)(26005)(71200400001)(66476007)(4744005)(86362001)(33656002)(8936002)(478600001)(66556008)(110136005)(66946007)(45980500001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?bXFCSW11Ty9YOGcrQ2taR0ticGE3UjlBdGFtWWh3MVZpaEtMOEdFK1J1VnAy?= =?utf-8?B?blYwVmI5N2p4M2V0UVVLWWc2YjZldVltalE2VVBaR2hKd2dPaG9CcUc3MEFv?= =?utf-8?B?YWJ4eHRYZ0t5MC9raHJtQVZmbGNYZ09hL1lLZXd2b0YvbEcwZVdiK29rSEpJ?= =?utf-8?B?QTRvWU1FckliVm91bDlOemFDaHE3K1FTaWtqVmkxK1JRUFFkNmtQTldpMlVG?= =?utf-8?B?REdCaytzVDVLV3lKT1VFeVR4Sy82QXc5ZzdMMUs5aXFmTlRmMFpnWnpWejVT?= =?utf-8?B?dlk2blZ4YTR0N0p1cmZqdUtJVWpac01ILzhLeDE1VTBKcHo3ZkpWZXNRWWMr?= =?utf-8?B?aDh5T25la0t0MDNoTlFIM0pJdkIzTzI0K2RsblBlYWsrOWxWU0xxTEpyeXpp?= =?utf-8?B?UCtVa3BlVEx1RTh2Wm42ZDdla0NhQVBwYVduVUZwamp6ZEVLUlRaRlRGamlZ?= =?utf-8?B?YURqWTJveGMrZlNmcG95WnA1eGNISWRSR0UyNGZRMk9OODlmbEhpSjEzVmVa?= =?utf-8?B?QXJaeFlDNE1PcnpEOGFPWGRnNi85dmd4dWcvQWZMalpnSVJTc0NvTnRiZE5P?= =?utf-8?B?cS9DL0hHWjkveEEwQWpKTitmRnhlWWwrOWpFT3ZINzhVTGJmR0VaTEk2NDRu?= =?utf-8?B?aWRDN05OT3N3S2RKM0pHT3FJaDVpYisrb0lJY29pTEExcHpKWXQyRjNVaEFQ?= =?utf-8?B?QzNvVC8rMkV4cFhVbjlqbjgyUHhLUzd5SjR1Q0NIMFZZKzNnWGEvK09rSml0?= =?utf-8?B?KzMvK1ppTUQrZW1sSjFuNDhlQWxNMVdKMExxTXAxL0hOb09NNU9STUF3YTFW?= =?utf-8?B?Nit0QWcrcXo0Z2o0NmFBR2xTT2o3RmtzYThua1RndDMvM2hmQ0RqSFFlaENK?= =?utf-8?B?bDVOSExaaWNPWTZDYlJuYjlzSWpVdXM3ckEzcks1eVlIS3RJK0FYMlN6VDhx?= =?utf-8?B?SndKRDMxN0VTaGtKdC9Kb2VZZnpNNHIrU1RMZ3Z1eHE1eXNXQXFzclUxU1Bs?= =?utf-8?B?Q3VDeExmOGVjNERkWURwa2phQnhZOXAza0dUaHpvTnM2M01OanBFM1QzbFpk?= =?utf-8?B?YWR0YUgwS2Y1RjcxS0JSS2h0bTdFWUVaWlNvakcyclZ4SWU5elZoVlp6V2li?= =?utf-8?B?M2tRYzZKUWNSSEtpdkNZUCtTUDNQMGlmYW1PVkh1bWd0S2NWQzBTMThQOERo?= =?utf-8?B?WW1TMXlMbDFhVEdydUhrRW80MXNmOUtnRytnTm1TQTZvY1NxU1Zzb1o2WUcx?= =?utf-8?B?b01oZVczTlExei96QVBQNkZVdXE0VGhrQ2dOSXZwUlMyZE84b1h6VmRRRjBr?= =?utf-8?Q?qOwZl2/ra9K5ld9NuDRa0/URWIveN0GpyK?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_C3FE8766978C413BB4ACF21DFE842F46fbcom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR15MB3405.namprd15.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d57a3758-8624-4728-933f-08d8b7e6f4e3
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jan 2021 17:16:25.0811 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: TFV/JDJ9sldLg0qtsL3X706iY1Rh8YHo8VVRlV8LKRQd+fzLc3ULn2zvg4SeRRka
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR15MB3391
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-13_07:2021-01-13, 2021-01-13 signatures=0
X-Proofpoint-Spam-Details: rule=fb_default_notspam policy=fb_default score=0 mlxlogscore=819 mlxscore=0 phishscore=0 spamscore=0 clxscore=1011 bulkscore=0 impostorscore=0 priorityscore=1501 lowpriorityscore=0 suspectscore=0 adultscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101130103
X-FB-Internal: deliver
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/DIaad1m-44u_lQH8_GTt9UnwMjg>
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: Wed, 13 Jan 2021 17:16:32 -0000

--_000_C3FE8766978C413BB4ACF21DFE842F46fbcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

PiBJJ2QgbGlrZSB0byBjYWxsIG91dCB0aGF0IHRoZXJlIGFyZSB0d28gdGhpbmdzIHdoaWNoIGNv
dWxkIGJlIHJlZmVycmVkIHRvIGFzICdwb29saW5nJy4gIE9uZSBpcyB1c2luZyBhIHNpbmdsZSBj
b25uZWN0aW9uIGZvciBIVFRQLzMgYW5kIFdlYlRyYW5zcG9ydCBhdCB0aGUgc2FtZSB0aW1lLiAg
VGhlIG90aGVyIGlzIHN1cHBvcnQgZm9yIG11bHRpcGxlIFdlYlRyYW5zcG9ydCBzZXNzaW9ucyBp
bnNpZGUgYSBzaW5nbGUgY29ubmVjdGlvbi4NCg0KQWJzb2x1dGVseS4gIFF1aWNUcmFuc3BvcnQg
cHJldmVudHMgZXZlbiB0aGUgcG9zc2liaWxpdHkgb2YgcG9vbGluZyBIVFRQIGFuZCBXZWJUcmFu
c3BvcnQgb24gdGhlIHNhbWUgY29ubmVjdGlvbiwgYXMgaXMgZG9uZSB3aXRoIEgyIGFuZCBXZWJT
b2NrZXRzLg0KDQo+IFRoaXMgbGF0dGVyIHR5cGUgb2YgJ3Bvb2xpbmcnIGlzIHBhcnQgb2Ygd2hh
dCBtYWtlcyBIdHRwM1RyYW5zcG9ydCBtb3JlIGNvbXBsZXggdGhhbiBRdWljVHJhbnNwb3J0LiAg
V2FzIHRoZXJlIGV2ZXIgYW4gZXhwbGljaXQgcXVlc3Rpb24gYWJvdXQgd2hldGhlciBtdWx0aXBs
ZSBzZXNzaW9ucyBvbiBhIHNpbmdsZSBjb25uZWN0aW9uIGFyZSBuZWNlc3Nhcnkgb3IgZXZlbiB1
c2VmdWw/DQoNCldlIGhhdmUgdXNlIGNhc2VzIGZvciBwb29saW5nIG11bHRpcGxlIHNlc3Npb25z
IG9uIHRoZSBzYW1lIGNvbm5lY3Rpb24gd2hpY2ggSSBkZXNjcmliZWQgZHVyaW5nIElFVEYgMTA5
LiAgSSBkb27igJl0IHdhbnQgdG8gY29tcGxldGVseSBoaWphY2sgdGhpcyB0aHJlYWQgdG8gZGlz
Y3VzcyB0aGVtLCBob3dldmVyLiAgSeKAmWQgcHJlZmVyIHRvIHdhaXQgdW50aWwgd2UgZmluaXNo
IGNvbmZpcm1pbmcgY29uc2Vuc3VzIG9uIHF1ZXN0aW9ucyAxIGFuZCAyIGJlZm9yZSBkaXZpbmcg
ZGVlcCBpbnRvIHBvb2xpbmcuDQoNCi1BbGFuDQo=

--_000_C3FE8766978C413BB4ACF21DFE842F46fbcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <3A6B3B949D832D41B83B5C7265ADC53C@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCWZvbnQtc2l6
ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5FbWFp
bFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6
IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVs
dA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBw
YWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4w
aW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9
DQotLT48L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZs
aW5rPSJwdXJwbGUiIHN0eWxlPSJ3b3JkLXdyYXA6YnJlYWstd29yZCI+DQo8ZGl2IGNsYXNzPSJX
b3JkU2VjdGlvbjEiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
Jmd0OyBJJ2QgbGlrZSB0byBjYWxsIG91dCB0aGF0IHRoZXJlIGFyZSB0d28gdGhpbmdzIHdoaWNo
IGNvdWxkIGJlIHJlZmVycmVkIHRvIGFzICdwb29saW5nJy4mbmJzcDsgT25lIGlzIHVzaW5nIGEg
c2luZ2xlIGNvbm5lY3Rpb24gZm9yIEhUVFAvMyBhbmQgV2ViVHJhbnNwb3J0IGF0IHRoZSBzYW1l
IHRpbWUuJm5ic3A7IFRoZSBvdGhlciBpcyBzdXBwb3J0IGZvciBtdWx0aXBsZSBXZWJUcmFuc3Bv
cnQgc2Vzc2lvbnMgaW5zaWRlIGENCiBzaW5nbGUgY29ubmVjdGlvbi4mbmJzcDsgPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPkFic29sdXRlbHkuJm5ic3A7IFF1aWNUcmFuc3BvcnQgcHJldmVudHMg
ZXZlbiB0aGUgcG9zc2liaWxpdHkgb2YgcG9vbGluZyBIVFRQIGFuZCBXZWJUcmFuc3BvcnQgb24g
dGhlIHNhbWUgY29ubmVjdGlvbiwgYXMgaXMgZG9uZSB3aXRoIEgyIGFuZCBXZWJTb2NrZXRzLjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mZ3Q7IFRoaXMgbGF0dGVyIHR5cGUgb2YgJ3Bvb2xpbmcn
IGlzIHBhcnQgb2Ygd2hhdCBtYWtlcyBIdHRwM1RyYW5zcG9ydCZuYnNwO21vcmUgY29tcGxleCB0
aGFuIFF1aWNUcmFuc3BvcnQuJm5ic3A7IFdhcyB0aGVyZSBldmVyIGFuIGV4cGxpY2l0IHF1ZXN0
aW9uIGFib3V0IHdoZXRoZXIgbXVsdGlwbGUgc2Vzc2lvbnMgb24gYSBzaW5nbGUgY29ubmVjdGlv
biBhcmUgbmVjZXNzYXJ5IG9yIGV2ZW4gdXNlZnVsPyZuYnNwOw0KPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPldlIGhhdmUgdXNlIGNhc2VzIGZvciBwb29saW5nIG11bHRpcGxlIHNlc3Npb25zIG9u
IHRoZSBzYW1lIGNvbm5lY3Rpb24gd2hpY2ggSSBkZXNjcmliZWQgZHVyaW5nIElFVEYgMTA5LiZu
YnNwOyBJIGRvbuKAmXQgd2FudCB0byBjb21wbGV0ZWx5IGhpamFjayB0aGlzIHRocmVhZCB0byBk
aXNjdXNzIHRoZW0sIGhvd2V2ZXIuJm5ic3A7IEnigJlkIHByZWZlciB0byB3YWl0IHVudGlsIHdl
IGZpbmlzaCBjb25maXJtaW5nIGNvbnNlbnN1cw0KIG9uIHF1ZXN0aW9ucyAxIGFuZCAyIGJlZm9y
ZSBkaXZpbmcgZGVlcCBpbnRvIHBvb2xpbmcuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi1BbGFu
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4N
CjwvaHRtbD4NCg==

--_000_C3FE8766978C413BB4ACF21DFE842F46fbcom_--


From nobody Wed Jan 13 11:24:52 2021
Return-Path: <jri.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 432A83A1057 for <webtransport@ietfa.amsl.com>; Wed, 13 Jan 2021 11:24:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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_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 dSTJbuSMhQBQ for <webtransport@ietfa.amsl.com>; Wed, 13 Jan 2021 11:24:47 -0800 (PST)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 5C3E83A104D for <webtransport@ietf.org>; Wed, 13 Jan 2021 11:24:47 -0800 (PST)
Received: by mail-lj1-x231.google.com with SMTP id b10so3828235ljp.6 for <webtransport@ietf.org>; Wed, 13 Jan 2021 11:24:47 -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=ApMbNEyOnUcMEJtdep6nVV7mmwYu4nbSDpvcM8Widno=; b=QLk3QGx1Hm5MrgbTd29g+36PEM1pF5+QhNtmO6nMuSyWyjyLFejSoc0tpzl5R8RcPj 9gjNRjPrLZm7RxZiOIYD7euTMed8INiOYJaLHDMMQ/T2g3yLy5G0tzgBBYH4pBgd1weS IfsjmFL9HX7xvTrOX9czW40nrbS8RnTgA39CqY79y85V85fWrgM1cEIwtDeDsZCmIVzK g8HZfGqxJqkR6L/a7agn1OZhhZFZ11o9Y29fg7DX7n+n6AYrhNmEz+tsbBPz+hpzIyJF q0fQmcFHH0DjNd9upzkdxZpmmC4JUdY08bvxoqyx7T2VaSi3RpMj8smhpy6T2bIIXJ1u Dm0Q==
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=ApMbNEyOnUcMEJtdep6nVV7mmwYu4nbSDpvcM8Widno=; b=pg8DZxRXQXSzZyDkh6CsccG5Mp0+qYMGcPGmODBCjKdAEt/ghRMEHBiIxUc4J/CR4S DsATzbHxbc33goeWatHbNpNTDxn6FLM+xN0NRWOm2mRWJAs3ez/L9GrFeB48omnumgqF A8PdgSNey7ETFpST5hGwLS1KV7t5bVydeBqKpJFdosq8hHSfJiiTAWKaGD9XND7F7Ylr pxA3THLWURkjOdy9v09lDLyFnUQdAG7y0IcDNF51p4q9kS3uuksSVZa8BalXK/3evmwc OSnItiMS0fzE0iCFF/Au447jAY0BbIwqknzMUubSWTKrPO6vhZUtTsIit01eToNbfSoN Tn5g==
X-Gm-Message-State: AOAM532waG+oxKEzF+Sc9m2yyf4hwvBi6K/ah5mm4Fxe161NBHshramu UWhHj/1WP5wg/ApNWTo4DUsPcUbqskqrxN7TEcrqvL9Y
X-Google-Smtp-Source: ABdhPJyAdj12CEOoln9fa5VltxwQzMP60fVKwLZFkIgWEDNFr6NBvBK1TgVZJoLHKhbBpeBWEhL+uG8Z6tRGGNOK6O0=
X-Received: by 2002:a2e:6c03:: with SMTP id h3mr1596881ljc.360.1610565884833;  Wed, 13 Jan 2021 11:24:44 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <1003bdcf-dc36-47ce-a4f5-dcfd9b2146b8@www.fastmail.com> <CAKcm_gO6VCip7bkrJMjDn4D5sjPMQMRhW2BnV5z6RK+MiUfMkg@mail.gmail.com> <C3FE8766-978C-413B-B4AC-F21DFE842F46@fb.com>
In-Reply-To: <C3FE8766-978C-413B-B4AC-F21DFE842F46@fb.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Wed, 13 Jan 2021 11:24:33 -0800
Message-ID: <CACpbDcfx0j5XDjvefgri=jBUum6vsjOBtKiGOrLz6x2PfJTV3g@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000073f45e05b8cd1774"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/nMw6YI5MwnLeQ2GxMG_1jc0SSZ4>
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: Wed, 13 Jan 2021 19:24:50 -0000

--00000000000073f45e05b8cd1774
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I support the consensus of 1A and 2A.

On Wed, Jan 13, 2021 at 9:16 AM Alan Frindell <afrind=3D
40fb.com@dmarc.ietf.org> wrote:

> > I'd like to call out that there are two things which could be referred
> to as 'pooling'.  One is using a single connection for HTTP/3 and
> WebTransport at the same time.  The other is support for multiple
> WebTransport sessions inside a single connection.
>
>
>
> Absolutely.  QuicTransport prevents even the possibility of pooling HTTP
> and WebTransport on the same connection, as is done with H2 and WebSocket=
s.
>
>
>
> > This latter type of 'pooling' is part of what makes Http3Transport more
> complex than QuicTransport.  Was there ever an explicit question about
> whether multiple sessions on a single connection are necessary or even
> useful?
>
>
>
> We have use cases for pooling multiple sessions on the same connection
> which I described during IETF 109.  I don=E2=80=99t want to completely hi=
jack this
> thread to discuss them, however.  I=E2=80=99d prefer to wait until we fin=
ish
> confirming consensus on questions 1 and 2 before diving deep into pooling=
.
>
>
>
> -Alan
> --
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport
>

--00000000000073f45e05b8cd1774
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I support the consensus of 1A and 2A.</div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 13, 2021=
 at 9:16 AM Alan Frindell &lt;afrind=3D<a href=3D"mailto:40fb.com@dmarc.iet=
f.org">40fb.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex">





<div lang=3D"EN-US" style=3D"overflow-wrap: break-word;">
<div class=3D"gmail-m_-3879700275082941897WordSection1">
<div>
<div>
<div>
<p class=3D"MsoNormal">&gt; I&#39;d like to call out that there are two thi=
ngs which could be referred to as &#39;pooling&#39;.=C2=A0 One is using a s=
ingle connection for HTTP/3 and WebTransport at the same time.=C2=A0 The ot=
her is support for multiple WebTransport sessions inside a
 single connection.=C2=A0 <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Absolutely.=C2=A0 QuicTransport prevents even the po=
ssibility of pooling HTTP and WebTransport on the same connection, as is do=
ne with H2 and WebSockets.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">&gt; This latter type of &#39;pooling&#39; is part o=
f what makes Http3Transport=C2=A0more complex than QuicTransport.=C2=A0 Was=
 there ever an explicit question about whether multiple sessions on a singl=
e connection are necessary or even useful?=C2=A0
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">We have use cases for pooling multiple sessions on t=
he same connection which I described during IETF 109.=C2=A0 I don=E2=80=99t=
 want to completely hijack this thread to discuss them, however.=C2=A0 I=E2=
=80=99d prefer to wait until we finish confirming consensus
 on questions 1 and 2 before diving deep into pooling.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">-Alan<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>

-- <br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport=
</a><br>
</blockquote></div>

--00000000000073f45e05b8cd1774--


From nobody Thu Jan 14 01:02:12 2021
Return-Path: <vasilvv@google.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 B5B853A1378 for <webtransport@ietfa.amsl.com>; Thu, 14 Jan 2021 01:02:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.971
X-Spam-Level: 
X-Spam-Status: No, score=-17.971 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 TzHaXHBlSyV3 for <webtransport@ietfa.amsl.com>; Thu, 14 Jan 2021 01:02:08 -0800 (PST)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 B10683A135C for <webtransport@ietf.org>; Thu, 14 Jan 2021 01:02:07 -0800 (PST)
Received: by mail-lj1-x22c.google.com with SMTP id y22so5557903ljn.9 for <webtransport@ietf.org>; Thu, 14 Jan 2021 01:02:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XhhLo2XYDnDNCRWAyjU9S3idZecyXs27jRh8oZk8nmc=; b=uM7neUYNCykY2ZLurJ7xnNXms42B6BQmgh6IYS6aPF/kC6oG3hxPfVbSDw07i6Gpq7 gwXb3ZJktLX/MC+KpQn9Tu31bKq11KjUTEfKNeBVIHhZe5BkWgSV0FTolVGN6+WyYxlq /zgsCOQQSaEqXnYt0ws6GsyKFchzddOP5xLsFl07ncgCpq5JtlOA1eCrBG1pVIEkjXWh +92IinxFQrC+EhxLc/7fi1PbZT20B7A/v1HjvbasHAemCVYLiULdHnBiwFVvnBm5wHln YEFQMDyqmBOWs7xRLwZRYkSplu0Km0mT4kzxZPBA+KiwkL9hJcXhaURxuB9JvDI/BbEA 5YUQ==
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=XhhLo2XYDnDNCRWAyjU9S3idZecyXs27jRh8oZk8nmc=; b=Qtc+jjmx2sVBmK5d77nXXo+2KwsabI02ZyddS/xXPzb92Q2mbwcMtvvxealduR+Vv6 0S2UgxojwoCt+zZrMV9RUJg1ip9e3dFrPwAllYeFB0F19llm9EDVMO9oP7NA9nneDlFw S7c62mezca9Qi1xGULe0qSPZlXopBUI9AEQ9Ulojr0PzBTu41wVZ0qrVAWAw0kRY+lTw eC5QCTFYVcWKly+jrvqAEGC/COswtEZfiD96iNdTfOLB4UiHGQlQ28x/0/IjCo8Xscxr EjgUlbWCVCJ6v6jIgF6Q6PBo5ks6GRHZfg2EgokeWEdOWOV9PlGJEr1134KXnUgnQ4Su dHyQ==
X-Gm-Message-State: AOAM533K+pD5qclk+dvpCRrZDRe6qYf00CcfigvMpIfO+dYwI7IFmlwW baCCpDGlLalLcidfGtwG6DF0AYgSjJujIlpqJ8gN6KpFbbQ=
X-Google-Smtp-Source: ABdhPJyB7z6MjS4hRk/ahpRwdxPO+dL2RuzNBEZVvPqTR4GUkItm2kYOI2KaqowTDP62BXBc6bmg6rQa9TpOKGbEFgY=
X-Received: by 2002:a2e:b5d8:: with SMTP id g24mr2864550ljn.50.1610614925336;  Thu, 14 Jan 2021 01:02:05 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <1003bdcf-dc36-47ce-a4f5-dcfd9b2146b8@www.fastmail.com>
In-Reply-To: <1003bdcf-dc36-47ce-a4f5-dcfd9b2146b8@www.fastmail.com>
From: Victor Vasiliev <vasilvv@google.com>
Date: Thu, 14 Jan 2021 04:01:54 -0500
Message-ID: <CAAZdMafTH73XmtKnr7ZpScT4aL2OvfjcKy1mEEXBSMDQBqAxCg@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007f2d1d05b8d88277"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/TEmcXCHeSpry4G-DMm_RJK9iah4>
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: Thu, 14 Jan 2021 09:02:11 -0000

--0000000000007f2d1d05b8d88277
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 12, 2021 at 7:02 PM Martin Thomson <mt@lowentropy.net> wrote:

> On Wed, Jan 13, 2021, at 04:25, David Schinazi wrote:
> > The consensus was option 1A.
>
> Great!
>
> > The consensus was option 2A.
>
> I can live with that.  Can I request a brief summary of the reasons?
>

>From my perspective, it's mostly because QuicTransport has been just an
incremental reinvention of HTTP from scratch.


> > 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.
>
> I don't think that this group gets to say that.  If we are using HTTP,
> then we are using HTTP.  We might decide that in browsers we want to keep
> the connections separate for $reasons, but I am opposed to saying that.
>
> Unless of course I'm missing context in the same way I missed the meeting.
>

HTTP pooling is an optimization, so I don't believe it is ever actively
required.

Most of the objections to using HTTP as a transport come from a perceived
requirement to support pooling.  Even outside of design complexity related
to flow control and prioritization, there are cases where web developers
actively benefit from not using pooling (using connection-level stats or
congestion control state for things like ABR).  I believe that it should be
possible to enable/disable pooling WebTransport as a part of settings
negotiation, and I am currently trying to figure out the details of how to
do that.

--0000000000007f2d1d05b8d88277
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 12, 2021 at 7:02 PM Martin Th=
omson &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_blank">mt@lowentr=
opy.net</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">On Wed, Jan 13, 2021, at 04:25, David Sch=
inazi wrote:<br>
&gt; The consensus was option 1A.<br>
<br>
Great!<br>
<br>
&gt; The consensus was option 2A.<br>
<br>
I can live with that.=C2=A0 Can I request a brief summary of the reasons?<b=
r></blockquote><div><br></div><div>From my perspective, it&#39;s mostly bec=
ause=C2=A0QuicTransport has been just an incremental reinvention of HTTP fr=
om scratch.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
&gt; Additionally, we discussed pooling and decided that we would<br>
&gt; not allow pooling in WebTransport over HTTP/3 for now, due<br>
&gt; to the complexities of pooling.<br>
<br>
I don&#39;t think that this group gets to say that.=C2=A0 If we are using H=
TTP, then we are using HTTP.=C2=A0 We might decide that in browsers we want=
 to keep the connections separate for $reasons, but I am opposed to saying =
that.<br>
<br>
Unless of course I&#39;m missing context in the same way I missed the meeti=
ng.<br></blockquote><div><br></div><div>HTTP pooling is an optimization, so=
 I don&#39;t believe it is ever actively required.</div><div><br></div><div=
>Most of the objections to using HTTP as a transport come from a perceived =
requirement to support pooling.=C2=A0 Even outside of design complexity rel=
ated to flow control and prioritization, there=C2=A0are cases where web dev=
elopers actively benefit from not using pooling (using connection-level sta=
ts or congestion control state for things like ABR).=C2=A0 I believe that i=
t should be possible to enable/disable pooling WebTransport as a part of se=
ttings negotiation, and I am currently trying to figure out the details of =
how to do=C2=A0that.</div><div></div></div></div>

--0000000000007f2d1d05b8d88277--


From nobody Thu Jan 14 01:16:00 2021
Return-Path: <yhirano@google.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 8BB153A1372 for <webtransport@ietfa.amsl.com>; Thu, 14 Jan 2021 01:15:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.971
X-Spam-Level: 
X-Spam-Status: No, score=-17.971 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 SHfnCWfgBvDh for <webtransport@ietfa.amsl.com>; Thu, 14 Jan 2021 01:15:57 -0800 (PST)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (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 A71E63A10E8 for <webtransport@ietf.org>; Thu, 14 Jan 2021 01:15:56 -0800 (PST)
Received: by mail-lf1-x12c.google.com with SMTP id v24so372598lfr.7 for <webtransport@ietf.org>; Thu, 14 Jan 2021 01:15:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+jPCcl8Zo0MN+NiY+Z4NBQ97PnG2dP2X7Ftf8PTq1vk=; b=eo0mHyVWx8O7IsyIejH+yyKKIcdkj+wJGev4noQVhSdyJm7gaSk1d5t73i5knToZoE XAeDrVIrF0u+Upm8+uozuSK9iwbrjv3vFopQ0mx0gfoWOes+IC4Z/5u+LH0pKxTemv4r 0OHcct1fON7aHlahClQi8LFtnEuo2HiG5l0wAUwYVWFkI/w+QpR4l2/a2LnKC+fwVpFh EQVWxHFhibd3hwNPZFrztd1fM31MnujJp+pIc7aBiDaOfvXnRnlvn/eVuV94JoEFU392 Jhpa5SMFYTkMzp+3XvC3a6luhS6PH+Ujq60fq16vvYgvgmt8lfoWm+Zyw9ESPDsvEgF4 yVzw==
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=+jPCcl8Zo0MN+NiY+Z4NBQ97PnG2dP2X7Ftf8PTq1vk=; b=P21YF9rgCquxlzVE7wNWKhnuxlITFmY5z7YlxtnDDXg682rPpj96DCErKdj6GXEqc3 i8H1lIvnsQ2Ifj+ZuNqYqYEJUKI6KVZJM3GWfEPQUgIBpAF+CMFPc1KKPKwj6qTjm7aQ 3OfWZvFD9kE7p82yfZjs2KK+S6H0UdpjeUBTiay17r0hF/1PJpLjVHGCp734+uvFupdN JjbUZRch25RrDgfTKuwYSNbWsEhIHztXf6031swkplrBcO9+WUGNZtWPQVsdtm+yuURY 2AcIbtcAgRsYulTa1DnpZrtCDf8eUgfVKY9HJeN7iKNpdTdVfdFMz/UK8wrwAR/MBrDd 4h9w==
X-Gm-Message-State: AOAM533kv/8ELTFhKKQiKTao2q3eGA9CFqIZCYDSyZvK9EfHM4hnc7Kq DLSS6E4bVzK6Yit+76t2W395HfnRZ1AijOfFSv06qg==
X-Google-Smtp-Source: ABdhPJxIsYR7ImAWfDnqUQ6iAbIYhvZFYrdJJ34XQp5ZaQDrkv1mfzLGjhxZ1Ct9NfwOWATXr2PpyvuiDhhzTRUDb/g=
X-Received: by 2002:a19:a06:: with SMTP id 6mr2781542lfk.624.1610615754756; Thu, 14 Jan 2021 01:15:54 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <1003bdcf-dc36-47ce-a4f5-dcfd9b2146b8@www.fastmail.com> <CAAZdMafTH73XmtKnr7ZpScT4aL2OvfjcKy1mEEXBSMDQBqAxCg@mail.gmail.com>
In-Reply-To: <CAAZdMafTH73XmtKnr7ZpScT4aL2OvfjcKy1mEEXBSMDQBqAxCg@mail.gmail.com>
From: Yutaka Hirano <yhirano@google.com>
Date: Thu, 14 Jan 2021 18:15:42 +0900
Message-ID: <CABihn6GJrKjaPZfpdLZ_JW4x5H2imaR4ZTUs0jgwMchJQYmNGg@mail.gmail.com>
To: Victor Vasiliev <vasilvv=40google.com@dmarc.ietf.org>
Cc: Martin Thomson <mt@lowentropy.net>, WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000eee01a05b8d8b3cc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/Yy-zbCxffsUZJs-1E1T1raiMzP8>
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: Thu, 14 Jan 2021 09:15:59 -0000

--000000000000eee01a05b8d8b3cc
Content-Type: text/plain; charset="UTF-8"

I support the consensus.

On Thu, Jan 14, 2021 at 6:02 PM Victor Vasiliev <vasilvv=
40google.com@dmarc.ietf.org> wrote:

> On Tue, Jan 12, 2021 at 7:02 PM Martin Thomson <mt@lowentropy.net> wrote:
>
>> On Wed, Jan 13, 2021, at 04:25, David Schinazi wrote:
>> > The consensus was option 1A.
>>
>> Great!
>>
>> > The consensus was option 2A.
>>
>> I can live with that.  Can I request a brief summary of the reasons?
>>
>
> From my perspective, it's mostly because QuicTransport has been just an
> incremental reinvention of HTTP from scratch.
>
>
>> > 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.
>>
>> I don't think that this group gets to say that.  If we are using HTTP,
>> then we are using HTTP.  We might decide that in browsers we want to keep
>> the connections separate for $reasons, but I am opposed to saying that.
>>
>> Unless of course I'm missing context in the same way I missed the meeting.
>>
>
> HTTP pooling is an optimization, so I don't believe it is ever actively
> required.
>
> Most of the objections to using HTTP as a transport come from a perceived
> requirement to support pooling.  Even outside of design complexity related
> to flow control and prioritization, there are cases where web developers
> actively benefit from not using pooling (using connection-level stats or
> congestion control state for things like ABR).  I believe that it should be
> possible to enable/disable pooling WebTransport as a part of settings
> negotiation, and I am currently trying to figure out the details of how to
> do that.
> --
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport
>

--000000000000eee01a05b8d8b3cc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">I s=
upport the consensus.</div></div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr">On Thu, Jan 14, 2021 at 6:02 PM Victor Vasiliev =
&lt;vasilvv=3D<a href=3D"mailto:40google.com@dmarc.ietf.org">40google.com@d=
marc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 12, 2021 at 7:02=
 PM Martin Thomson &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_blan=
k">mt@lowentropy.net</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Jan 13, 2021, at 04:=
25, David Schinazi wrote:<br>
&gt; The consensus was option 1A.<br>
<br>
Great!<br>
<br>
&gt; The consensus was option 2A.<br>
<br>
I can live with that.=C2=A0 Can I request a brief summary of the reasons?<b=
r></blockquote><div><br></div><div>From my perspective, it&#39;s mostly bec=
ause=C2=A0QuicTransport has been just an incremental reinvention of HTTP fr=
om scratch.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
&gt; Additionally, we discussed pooling and decided that we would<br>
&gt; not allow pooling in WebTransport over HTTP/3 for now, due<br>
&gt; to the complexities of pooling.<br>
<br>
I don&#39;t think that this group gets to say that.=C2=A0 If we are using H=
TTP, then we are using HTTP.=C2=A0 We might decide that in browsers we want=
 to keep the connections separate for $reasons, but I am opposed to saying =
that.<br>
<br>
Unless of course I&#39;m missing context in the same way I missed the meeti=
ng.<br></blockquote><div><br></div><div>HTTP pooling is an optimization, so=
 I don&#39;t believe it is ever actively required.</div><div><br></div><div=
>Most of the objections to using HTTP as a transport come from a perceived =
requirement to support pooling.=C2=A0 Even outside of design complexity rel=
ated to flow control and prioritization, there=C2=A0are cases where web dev=
elopers actively benefit from not using pooling (using connection-level sta=
ts or congestion control state for things like ABR).=C2=A0 I believe that i=
t should be possible to enable/disable pooling WebTransport as a part of se=
ttings negotiation, and I am currently trying to figure out the details of =
how to do=C2=A0that.</div><div></div></div></div>
-- <br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport=
</a><br>
</blockquote></div>

--000000000000eee01a05b8d8b3cc--


From nobody Thu Jan 14 07:34:55 2021
Return-Path: <ianswett@google.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 A77203A1565 for <webtransport@ietfa.amsl.com>; Thu, 14 Jan 2021 07:34:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.971
X-Spam-Level: 
X-Spam-Status: No, score=-17.971 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 XbHHvpUc8J-k for <webtransport@ietfa.amsl.com>; Thu, 14 Jan 2021 07:34:51 -0800 (PST)
Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (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 4E6D83A155A for <webtransport@ietf.org>; Thu, 14 Jan 2021 07:34:51 -0800 (PST)
Received: by mail-wr1-x42d.google.com with SMTP id t16so6215224wra.3 for <webtransport@ietf.org>; Thu, 14 Jan 2021 07:34:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=58/AvykbqMQE4kiUDdr6FFPsf3W/9lMQI3NxUSuRY90=; b=f5Z1AxLc4n74HEaw9JrKkTd8KUzuapnr7oULpKkJIDik+/iZR4QolD9bstFdQVUfB5 mH/lFXJnufLCclaNgA2CjKmVYn6xGwuzvHektZEJeSz8qMR6zXFRO9xJXUSIIeCwIMJU q3DZELhksitiDqgpe/zVahDbgMy4IJEJhnmlv8NgEzjklx7KC2kXF8bpDBmwk2qjzEl3 /5xkRnUUOP/T9iztqflvMV1eQOYF17lQDwQigiyvXQbLHEkSh3VHoXd4N4U8BT01YWsZ cXJrELMqvtWEIf3dakV4tWmWwVa6JadaLdq3JoScX9wXpjgOabO81z+aOLwlFc4xPlUc kkRw==
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=58/AvykbqMQE4kiUDdr6FFPsf3W/9lMQI3NxUSuRY90=; b=tyucXyYEKU9N2Iv5lcCsUjyDs79spGRO8FblRzRcIIm08t87mcbWDRte5N2k2eQ9q5 z/RFIkRSYiSCtStR2xM9Ubu7iAOPGd8zHWa+kqR3pR6FTzKp9W5NJ8X+F4A7Op3Ck9c2 NoqDd11gE2Qde3rc0MFFhDa23rJDtxLp0lDkgt9tP0zulqd5vJE9vjyoy7kIKaB0PPlN MLPGAzl/i4Kps6O1QX0eHPkxN+XSUN/xZpV2xOOtUWnKQwy5I1dEOiD773qNQq8Cpc8B t/WvrhEECyCkW+uT1Cj6Ut9SmL3RHTNr1PO726jUd4m1pEbzGSgrCxmWEypcFV4PgILm jvpw==
X-Gm-Message-State: AOAM532u4ljvhB61h0e3jX3EeTbZDOE1+DkCV/Gx8GU5B20+jDixD7CX POFTgW7fPUdq7Uw4BNZaZaGq5cYH2Q6IdLmwczPuVw==
X-Google-Smtp-Source: ABdhPJwgwIMmlCywkbE7YlmnzuUelE4extkl57aX+RStrZSR/JE9ruOhvD4ZDkVwByOPmkXq6RR2E/46RKFmUmR214Y=
X-Received: by 2002:adf:f707:: with SMTP id r7mr8802316wrp.113.1610638489607;  Thu, 14 Jan 2021 07:34:49 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <1003bdcf-dc36-47ce-a4f5-dcfd9b2146b8@www.fastmail.com> <CAKcm_gO6VCip7bkrJMjDn4D5sjPMQMRhW2BnV5z6RK+MiUfMkg@mail.gmail.com> <CALGR9obUHRn9Y-eXZjnUMQU22ZnLcw0RLs7FhrrrZOd9OM63yA@mail.gmail.com>
In-Reply-To: <CALGR9obUHRn9Y-eXZjnUMQU22ZnLcw0RLs7FhrrrZOd9OM63yA@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Thu, 14 Jan 2021 10:34:37 -0500
Message-ID: <CAKcm_gMaDD7ZGsg5xdaQ01y6DzkWQ+u4k1btFQEL5oLrX7bbxg@mail.gmail.com>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>,  WebTransport <webtransport@ietf.org>, Martin Thomson <mt@lowentropy.net>
Content-Type: multipart/alternative; boundary="000000000000094c8405b8ddff22"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/AEapSOI4JaScCgeZBRFOdbi3Zs8>
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: Thu, 14 Jan 2021 15:34:54 -0000

--000000000000094c8405b8ddff22
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 13, 2021 at 11:45 AM Lucas Pardue <lucaspardue.24.7@gmail.com>
wrote:

> Hi Ian,
>
> On Wed, Jan 13, 2021 at 3:46 PM Ian Swett <ianswett=
> 40google.com@dmarc.ietf.org> wrote:
>
>>
>>
>> On Tue, Jan 12, 2021 at 7:02 PM Martin Thomson <mt@lowentropy.net> wrote:
>>
>>> On Wed, Jan 13, 2021, at 04:25, David Schinazi wrote:
>>> > The consensus was option 1A.
>>>
>>> Great!
>>>
>>> > The consensus was option 2A.
>>>
>>> I can live with that.  Can I request a brief summary of the reasons?
>>>
>>
>> I asked a question like this during the interim, and I think it'd be
>> worth clearly documenting the reasons, as I think it'd clarify our
>> direction a bit.  The one that I clearly recall is that we'd have to
>> re-invent many of the features that HTTP/3 provides, but I'm not clear why
>> that's the case.
>>
>
> I made a comment along those lines. It was mainly motivated by Victor's PR
> "Refactor client indication into a full header exchange" see
> https://github.com/vasilvv/webtransport/pull/18. AFAICT this is merged
> into the editors copy of draft-vvv-webtransport-quic but there is no
> published I-D with this change in. Victor please correct me if I'm wrong.
>
> Not that I'm not questioning whether the motivation behind needing more
> flexibility of the client indication. But it highlights that we'll discover
> more things that are needed or nice to have and require additions. My
> concern is that inventing something that is similar to HTTP headers but not
> actually HTTP is duplication and brings risks that we need to mirror the
> engineering and design effort that has already gone into HTTP. As an
> implementer, it seems better to reuse HTTP semantics (i.e code I have
> already, or libraries) than to invent another HTTP-alike.
>

Thanks, I hadn't seen that PR.

After re-reading the editors copy of both documents, I'm much happier with
Http3Transport than I was yesterday, because I had some misunderstandings.
It also makes me very happy we allow Type-Value frames with no length in
HTTP/3.


>
> Cheers,
>
> Lucas
> --
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport
>

--000000000000094c8405b8ddff22
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 13, 2021 at 11:45 AM Luca=
s Pardue &lt;<a href=3D"mailto:lucaspardue.24.7@gmail.com">lucaspardue.24.7=
@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr"><div>Hi Ian,<br></div><br><div class=3D"gmail_q=
uote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 13, 2021 at 3:46 PM=
 Ian Swett &lt;ianswett=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" ta=
rget=3D"_blank">40google.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr=
"><br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_=
attr">On Tue, Jan 12, 2021 at 7:02 PM Martin Thomson &lt;<a href=3D"mailto:=
mt@lowentropy.net" target=3D"_blank">mt@lowentropy.net</a>&gt; wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Jan 13, 2021,=
 at 04:25, David Schinazi wrote:<br>
&gt; The consensus was option 1A.<br>
<br>
Great!<br>
<br>
&gt; The consensus was option 2A.<br>
<br>
I can live with that.=C2=A0 Can I request a brief summary of the reasons?<b=
r></blockquote><div><br></div><div>I asked a question like this during the =
interim, and I think it&#39;d be worth clearly documenting the reasons, as =
I think it&#39;d clarify our direction a bit.=C2=A0 The one that I clearly =
recall is that we&#39;d have to re-invent many of the features that HTTP/3 =
provides, but I&#39;m not clear why that&#39;s the case.</div></div></div><=
/blockquote><div><br></div><div>I made a comment along those lines. It was =
mainly motivated by Victor&#39;s PR &quot;Refactor client indication into a=
 full header exchange&quot; see=C2=A0 <br></div><div><a href=3D"https://git=
hub.com/vasilvv/webtransport/pull/18" target=3D"_blank">https://github.com/=
vasilvv/webtransport/pull/18</a>. AFAICT this is merged into the editors co=
py of draft-vvv-webtransport-quic but there is no published I-D with this c=
hange in. Victor please correct me if I&#39;m wrong.</div><div><br></div><d=
iv>Not that I&#39;m not questioning whether the motivation behind needing m=
ore flexibility of the client indication. But it highlights that we&#39;ll =
discover more things that are needed or nice to have and require additions.=
 My concern is that inventing something that is similar to HTTP headers but=
 not actually HTTP is duplication and brings risks that we need to mirror t=
he engineering and design effort that has already gone into HTTP. As an imp=
lementer, it seems better to reuse HTTP semantics (i.e code I have already,=
 or libraries) than to invent another HTTP-alike.</div></div></div></blockq=
uote><div><br></div><div>Thanks, I hadn&#39;t seen that PR.</div><div><br><=
/div><div>After re-reading the editors copy of both documents, I&#39;m much=
 happier with Http3Transport than I was yesterday, because I had some misun=
derstandings.=C2=A0 It also makes me very happy we allow Type-Value frames =
with no length in HTTP/3.</div><div>=C2=A0</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div><br=
></div><div>Cheers,</div><div><br></div><div>Lucas<br></div></div></div>
-- <br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport=
</a><br>
</blockquote></div></div>

--000000000000094c8405b8ddff22--


From nobody Wed Jan 27 16:17:06 2021
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: webtransport@ietf.org
Delivered-To: webtransport@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EFFBE3A0F0F; Wed, 27 Jan 2021 16:16:57 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
To: <draft-vvv-webtransport-http3@ietf.org>, <webtrans-chairs@ietf.org>, <webtransport@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161179301789.29442.11569462513475722640@ietfa.amsl.com>
Date: Wed, 27 Jan 2021 16:16:57 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/l4022DBcLzIB9myGUPR8isbEkVo>
Subject: [Webtransport] The WEBTRANS WG has placed draft-vvv-webtransport-http3 in state "Call For Adoption By WG Issued"
X-BeenThere: webtransport@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 28 Jan 2021 00:17:04 -0000

The WEBTRANS WG has placed draft-vvv-webtransport-http3 in state
Call For Adoption By WG Issued (entered by David Schinazi)

The document is available at
https://datatracker.ietf.org/doc/draft-vvv-webtransport-http3/



From nobody Wed Jan 27 16:17:14 2021
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 AFC013A0FEB for <webtransport@ietfa.amsl.com>; Wed, 27 Jan 2021 16:17:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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_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 Ki95Unv6orgH for <webtransport@ietfa.amsl.com>; Wed, 27 Jan 2021 16:17:04 -0800 (PST)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (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 C85463A0FDA for <webtransport@ietf.org>; Wed, 27 Jan 2021 16:17:01 -0800 (PST)
Received: by mail-pg1-x52a.google.com with SMTP id i7so2980314pgc.8 for <webtransport@ietf.org>; Wed, 27 Jan 2021 16:17:01 -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=D2M4kBdLX5OWFSkm3EaGsqyAAhYiyAdT5+33NqEc1/M=; b=sasHDZlGx26tKQA4lqIm/v8qHum0/hoUyQRKTpgdCRQVQ5wv5SUFxGFMU70XBsOEz1 eGMe2Nd4IN4/4UEn/DY98x2IB+t1h9dIbQkIPdfvqM6AzsurK8W02+KZBeJmM+Zm04VT Bg41foFVs9JI28f3vjWHkvxjISv3jOy6ankLJTSOFnzc/UvY15d/dcP7M31HoON96K8D IYg+Vt9I8ljSeBLqnOmb96YLOTiupTSIR/KiS0W+ZVk9roAQzbD0XT8KCr3JB8myYXo/ X0f15eEHeO13cl+UjQP0lxIoM/L6dwHtzRnJZqc+l66og8QoJ7TkqrY6rLv+TiVrLTgg Zq7g==
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=D2M4kBdLX5OWFSkm3EaGsqyAAhYiyAdT5+33NqEc1/M=; b=cH5lwRJna6s00BXqSQwazqFdWMql6jVBSVJu2MCdcZ+GRQXAey38PKH5oy9IZqigke xeiBgB3pI24bPGKhYZvxLPpzX2zJJJRNC8faVgmXm1tKIlHG7E2vfYXFWFDFM7ktlXCf ETh4+/Haen+5SDtPCV/TtfF9maRB5ZlRyhuHo5glRM3GkBH30xRcmZYOw2CBLgtRO6jF YF9qsMaMCJGsSbd9zdnOSiGls3xscZjdXTOzg7Wbh+5U8BJ610/o0ZbEQwsI3CkdL1LI z07c03yec2ug+pXtpBMGjzC1PkSngnzDi13nC2RpCZ5UwoVzXKuMJvOjCQAwB4N1mRwu +4FA==
X-Gm-Message-State: AOAM5306Sax/3evpZwqqFlPJo/qaA5eYjVHvtWkoOIqPTHw6wfaWLYPz TlHX5NlaO99bdLfbdtZP1ZaV9IjcEW0UDaJDw04XJmHAtNE=
X-Google-Smtp-Source: ABdhPJwb7rpQYfwbQUzEpVClrdiJFz/hCCSrL+AtrIydaazqhwJJenXaNPm+bwirxZVLm3ILz4F0YehoUsFl2NlBsso=
X-Received: by 2002:a63:1865:: with SMTP id 37mr13831953pgy.206.1611793021000;  Wed, 27 Jan 2021 16:17:01 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com>
In-Reply-To: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Wed, 27 Jan 2021 16:16:49 -0800
Message-ID: <CAPDSy+4REQypGw2=_R0OGWPdUL20ZB4gnS2jqnsyU+D1pCscCQ@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000077e07505b9eace38"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/kOKkn7qTSCQW3ug0Lbud0ApETQI>
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: Thu, 28 Jan 2021 00:17:13 -0000

--00000000000077e07505b9eace38
Content-Type: text/plain; charset="UTF-8"

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
>

--00000000000077e07505b9eace38
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi WebTransport enthusiasts,<br><div><br></div><div>This c=
onsensus is now confirmed: for the foreseeable=C2=A0future,</div><div>the W=
EBTRANS working group will focus on building a single</div><div>UDP-based p=
rotocol for WebTransport, and that protocol will</div><div>run atop HTTP/3.=
</div><div><br></div><div>Our next step is to adopt a document that matches=
 this</div><div>description. The only matching proposal that has been</div>=
<div>discussed on this list so far is Victor&#39;s</div><div>&quot;WebTrans=
port over HTTP/3&quot; individual draft:</div><div><a href=3D"https://tools=
.ietf.org/html/draft-vvv-webtransport-http3">https://tools.ietf.org/html/dr=
aft-vvv-webtransport-http3</a></div><div><br></div><div>We are therefore=C2=
=A0placing this document in a call for adoption.</div><div><br></div><div>P=
lease reply to this email stating whether you support adoption</div><div>of=
 draft-vvv-webtransport-http3=C2=A0by the WEBTRANS WG. Note</div><div>that =
WG adoption does not indicate consensus on the contents</div><div>of the do=
cument, only that it&#39;s a reasonable starting point for</div><div>us to =
start working on. As such, please DO NOT send comments</div><div>about the =
technical details of the draft on this email thread - please</div><div>crea=
te a separate email thread on=C2=A0&lt;<a href=3D"mailto:webtransport@ietf.=
org">webtransport@ietf.org</a>&gt; or open</div><div>a GitHub issue at &lt;=
<a href=3D"https://github.com/vasilvv/webtransport/issues">https://github.c=
om/vasilvv/webtransport/issues</a>&gt;.</div><div><br></div><div>As usual, =
if you believe that we should not adopt this document,</div><div>please sta=
te why. In our last meeting we&#39;ve noted some concerns</div><div>around =
pooling for example, and we plan on discussing those as</div><div>a working=
 group once the document is adopted.</div><div><br></div><div>This adoption=
 call will last for two weeks until 2021-02-10.</div><div><br></div><div>Th=
anks,</div><div>David</div></div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr">On Tue, Jan 12, 2021 at 9:25 AM David Schinazi &=
lt;<a href=3D"mailto:dschinazi.ietf@gmail.com">dschinazi.ietf@gmail.com</a>=
&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div=
 dir=3D"ltr"><div>Hi WebTransport enthusiasts,<br></div><div><br></div><div=
>Today we had an interim of the IETF WEBTRANS WG,</div><div>where we reache=
d consensus in the (virtual) room on</div><div>the following questions:</di=
v><div><br></div><div>Question 1: number of protocols<br></div><div>=C2=A0 =
=C2=A0 Should the working group adopt only one UDP-based transport?<br>=C2=
=A0 =C2=A0 1A: only one transport (QUIC or HTTP/3)<br>=C2=A0 =C2=A0 1B: mul=
tiple transports (QUIC and HTTP/3)<br></div><div><br></div><div>The consens=
us was option 1A.</div><div><br></div><div>Additionally, we noted that this=
 does not preclude=C2=A0us from</div><div>building a second protocol at a l=
ater date if new information</div><div>emerges.</div><div><br></div><div>Qu=
estion 2: UDP-based protocols<br></div><div>=C2=A0 =C2=A0 Which UDP-based o=
ption should we adopt as a starting</div><div>=C2=A0 =C2=A0 point for WebTr=
ansport protocol?<br>=C2=A0 =C2=A0 2A: WebTransport over HTTP/3<br>=C2=A0 =
=C2=A0 2B: WebTransport over QUIC directly (separate ALPN)<br></div><div><b=
r></div><div>The consensus was option 2A.<br></div><div><br></div><div>Addi=
tionally, we discussed pooling and decided that we would</div><div>not allo=
w pooling in=C2=A0WebTransport over HTTP/3 for now, due</div><div>to the co=
mplexities of pooling.</div><div><br></div><div>We&#39;d like to confirm th=
is consensus on the list. If you disagree</div><div>with these points, plea=
se reply on the list. If you do so, please</div><div>state how strongly you=
 feel - whether you are expressing a</div><div>preference, or an imperative=
. Please also provide as much</div><div>detail as possible to explain your =
position. Please also respond</div><div>if you support this consensus - a s=
imple &quot;I support this consensus&quot;</div><div>email to the list woul=
d be helpful.</div><div><br></div><div>We&#39;ll be running this consensus =
call for two weeks, please reply</div><div>before 2021-01-26, the chairs wi=
ll determine consensus on that date.</div><div><br></div><div>Thanks,</div>=
<div>David</div></div>
</blockquote></div>

--00000000000077e07505b9eace38--


From nobody Wed Jan 27 16:25:29 2021
Return-Path: <lucaspardue.24.7@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 E62BF3A0E21 for <webtransport@ietfa.amsl.com>; Wed, 27 Jan 2021 16:25:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 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, 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 lv-0aMgu0VLp for <webtransport@ietfa.amsl.com>; Wed, 27 Jan 2021 16:25:26 -0800 (PST)
Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) (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 2D3163A0E22 for <webtransport@ietf.org>; Wed, 27 Jan 2021 16:25:26 -0800 (PST)
Received: by mail-ej1-x62f.google.com with SMTP id l9so5264174ejx.3 for <webtransport@ietf.org>; Wed, 27 Jan 2021 16:25:26 -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=VDrRrwoL3bwaSNIuzLhFzB+WAOk6jkuU6Ylx2aqiiAo=; b=OCm28A9DgOibgwbOE+t/04W4EmMhez1T1CPMFR+DmrQ93K36P9S6WEJWUb2ohSUW/f xg/G6VUFRd7nYPDaJz81Xtpzn91flF9jlU+i/rlb3YF1LZ9aMDS9xnD+tC4Nwx5Ejxki tMnaDeISpbADVQU24m4rdbBkNWWItSdLqb2E9L1eIuTpWkBHSbOABCrDnVOs3sUiQXzz 53otgyiqJTXzFGRyNkLFPsMfRkw38WWfi5MqAARcQVqirtRQu8+rSjhntP/9Va6hZ0pC hdA4zBjylLWSc/Gm8AMtN5yX+tW/jhjFNd1lfMlrlVcY5cme4odsJENxDf2ZB+JnS61M Cf1g==
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=VDrRrwoL3bwaSNIuzLhFzB+WAOk6jkuU6Ylx2aqiiAo=; b=ijGrDy2BwWTikP9B3JcCtSRLKryPiOJJi3MTWRfq/WqQSzYkMXtaN9cuGKFooJkFCF 3MfERMEmFPsaMHYzbL9c5VvGF8TsJsSaeqek9BdwIs3A1fLywdBpan6Dpy3bF4af+U+4 /PV9I3CO+t18Jo3jRHYX3aRlGbkFjrRZcyMWcSrKxEghNcSVmA4GfG8P15e4z9tMSqCp mxNPC6w5jGJcoZVpVHYHUWWVE5ObkKKBC8DDV3jlvbR+9AzfDa0jkIHJRhTvoSqHd3aq /1F7OpFesBknyv0HUtB1HGwimAExiWic7Rs0LLi/c3aErECEKJGTtREYbbnvLATsO5/K CftA==
X-Gm-Message-State: AOAM530jApJ2PhimJIM91asSVaJZFdGmOlUGkxU6Ro3OPfH5SooaWsz2 YLD7k92vfPYGUbrVvP+ecbHXg8F+sBMmcw9NkGE=
X-Google-Smtp-Source: ABdhPJwCkGnQQ4WhsPypp6aosXMsbM+UlHBA6obGIt/vMehohsJODLh+A0K1C3z5gx1ZnWHg3AmHPtdDyOwFfTA9L5Y=
X-Received: by 2002:a17:906:c78b:: with SMTP id cw11mr8802061ejb.448.1611793524423;  Wed, 27 Jan 2021 16:25:24 -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: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Thu, 28 Jan 2021 00:25:15 +0000
Message-ID: <CALGR9obEvHogho5vFYkyozudMNOL=FYByvgwUHK22rutMjQwHA@mail.gmail.com>
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000079812005b9eaecbf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/JW5nhuCXX4JHOSnbXEVANlIP53g>
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: Thu, 28 Jan 2021 00:25:28 -0000

--00000000000079812005b9eaecbf
Content-Type: text/plain; charset="UTF-8"

Hi David

On Thu, 28 Jan 2021, 00:17 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.
>

Can you please confirm the draft version that you are issuing an adoption
call for?

The reason I ask is that a new draft was published on January 27 (just
yesterday), while the group discussed an older draft (and even a bit of an
editors copy) during the interim meeting.

Personally, I don't think there is material difference but I think it
benefits the group to be precise here.

Cheers
Lucas

--00000000000079812005b9eaecbf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>Hi David=C2=A0<br><br><div class=3D"gmail_quote"><di=
v dir=3D"ltr" class=3D"gmail_attr">On Thu, 28 Jan 2021, 00:17 David Schinaz=
i, &lt;<a href=3D"mailto:dschinazi.ietf@gmail.com">dschinazi.ietf@gmail.com=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Hi=
 WebTransport enthusiasts,<br><div><br></div><div>This consensus is now con=
firmed: for the foreseeable=C2=A0future,</div><div>the WEBTRANS working gro=
up will focus on building a single</div><div>UDP-based protocol for WebTran=
sport, and that protocol will</div><div>run atop HTTP/3.</div><div><br></di=
v><div>Our next step is to adopt a document that matches this</div><div>des=
cription. The only matching proposal that has been</div><div>discussed on t=
his list so far is Victor&#39;s</div><div>&quot;WebTransport over HTTP/3&qu=
ot; individual draft:</div><div><a href=3D"https://tools.ietf.org/html/draf=
t-vvv-webtransport-http3" target=3D"_blank" rel=3D"noreferrer">https://tool=
s.ietf.org/html/draft-vvv-webtransport-http3</a></div><div><br></div><div>W=
e are therefore=C2=A0placing this document in a call for adoption.</div></d=
iv></blockquote></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">C=
an you please confirm the draft version that you are issuing an adoption ca=
ll for?</div><div dir=3D"auto"><br></div><div dir=3D"auto">The reason I ask=
 is that a new draft was published on January 27 (just yesterday), while th=
e group discussed an older draft (and even a bit of an editors copy) during=
 the interim meeting.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"au=
to">Personally, I don&#39;t think there is material difference but I think =
it benefits the group to be precise here.</div><div dir=3D"auto"><br></div>=
<div dir=3D"auto">Cheers</div><div dir=3D"auto">Lucas</div></div>

--00000000000079812005b9eaecbf--


From nobody Wed Jan 27 16:33:47 2021
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 180993A0E33 for <webtransport@ietfa.amsl.com>; Wed, 27 Jan 2021 16:33:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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_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 HAWtweQTDJiq for <webtransport@ietfa.amsl.com>; Wed, 27 Jan 2021 16:33:43 -0800 (PST)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (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 C6AD33A0DD2 for <webtransport@ietf.org>; Wed, 27 Jan 2021 16:33:43 -0800 (PST)
Received: by mail-pg1-x533.google.com with SMTP id c132so3052073pga.3 for <webtransport@ietf.org>; Wed, 27 Jan 2021 16:33:43 -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=ndWNAh2M3mdvJ47KLi9z+NTQoR8fwXzcO27fsNbKftE=; b=hw7wodwDaelday2Vc0cAc2OJJ+LfSZetEmtNTQZSnJzjVKJcXcKolL9qz1iqpo5SnY RQ8ja+wO2IQaDBNUXicb6QUXbiVKNxnG+fFCoRieLNiQsYxGepb/eozVUE17I1O/GwXB 8lh939ZtRHOXYtpPM/Gw38OL1driJvAk/asEHK/K214jEUh6ZBLACXHtYRzshRbICGtQ lfAO4bMJXJHvu6GEF/Fb4J6Gyuk9OOLcdffbHPr3lty63BWlIsSojKGrs4/SxVjmpZoT Ah9nv7F4PdskSc5pPv96W4YGIkpXEoUvtOPOJijhpyBKq3+UMdoAkqt1IUyvTn1tKE/L oSew==
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=ndWNAh2M3mdvJ47KLi9z+NTQoR8fwXzcO27fsNbKftE=; b=aHld5LCDbZ2GLzorf0fg/z75teBPmzFMQnL1V78Im5rqrohYupZWD9Cg6IsaBHUC9n 9vKMYPNmBzKi8ZCup040Rkbf8ZGgjZmtb/s4zfNOKr1WpsDXa+5ZRWcNYLYQ9NsG3US3 rtWDDpw9hqYpnNgYm38b0mvl42FAl2hCL2r6mJpapw/xPT0Jj7mAcqT32Y9fus7pb8pm qew7VdyrEJwjJgGipFFnPoaTFhndZ4ZivXEJF5XCJcQfUOh2QWYIuqkigHtzG4qdzcD5 XVo2qfuH77m8XETI97uMnxTZt555qHJu3JbJc1L6jDB72BBJOlqAEZP5Q0bruAx+Y7G3 O6hA==
X-Gm-Message-State: AOAM533DYdAST8BmgI0BSscYYq6dJPJk+y4xOu25nVyDINsMdpBIz9BG HGl8rBx6uCn/7VG8zJVspHTo6lrUrb8OY76oeME=
X-Google-Smtp-Source: ABdhPJxyztEGwBZV0clzysbgJvorToSLHLNMmLG+qcDuximkLElGIfBaYxmCZYFvBuqcBKkhgHGQ6csOJEgC+WE4ai4=
X-Received: by 2002:a63:705c:: with SMTP id a28mr14014280pgn.402.1611794023113;  Wed, 27 Jan 2021 16:33:43 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <CAPDSy+4REQypGw2=_R0OGWPdUL20ZB4gnS2jqnsyU+D1pCscCQ@mail.gmail.com> <CALGR9obEvHogho5vFYkyozudMNOL=FYByvgwUHK22rutMjQwHA@mail.gmail.com>
In-Reply-To: <CALGR9obEvHogho5vFYkyozudMNOL=FYByvgwUHK22rutMjQwHA@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Wed, 27 Jan 2021 16:33:31 -0800
Message-ID: <CAPDSy+4i30r0Vo==HnvK6hq6+LDakTPHrd=5nLvifcM8RM8hsg@mail.gmail.com>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000032e7cb05b9eb0a21"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/DcGdLrIk9CZmxOHhy2qyrngRWrs>
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: Thu, 28 Jan 2021 00:33:45 -0000

--00000000000032e7cb05b9eb0a21
Content-Type: text/plain; charset="UTF-8"

Hi Lucas,

The adoption call covers the latest version as of today, which is -03:
https://tools.ietf.org/html/draft-vvv-webtransport-http3-03

David

On Wed, Jan 27, 2021 at 4:25 PM Lucas Pardue <lucaspardue.24.7@gmail.com>
wrote:

> Hi David
>
> On Thu, 28 Jan 2021, 00:17 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.
>>
>
> Can you please confirm the draft version that you are issuing an adoption
> call for?
>
> The reason I ask is that a new draft was published on January 27 (just
> yesterday), while the group discussed an older draft (and even a bit of an
> editors copy) during the interim meeting.
>
> Personally, I don't think there is material difference but I think it
> benefits the group to be precise here.
>
> Cheers
> Lucas
>

--00000000000032e7cb05b9eb0a21
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Lucas,<div><br><div>The adoption call covers the latest=
 version as of today, which is -03:</div><div><a href=3D"https://tools.ietf=
.org/html/draft-vvv-webtransport-http3-03">https://tools.ietf.org/html/draf=
t-vvv-webtransport-http3-03</a><br></div><div><br></div><div>David</div></d=
iv></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_att=
r">On Wed, Jan 27, 2021 at 4:25 PM Lucas Pardue &lt;<a href=3D"mailto:lucas=
pardue.24.7@gmail.com">lucaspardue.24.7@gmail.com</a>&gt; wrote:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto"><div>Hi =
David=C2=A0<br><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gma=
il_attr">On Thu, 28 Jan 2021, 00:17 David Schinazi, &lt;<a href=3D"mailto:d=
schinazi.ietf@gmail.com" target=3D"_blank">dschinazi.ietf@gmail.com</a>&gt;=
 wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr">Hi WebTransport enthusiasts,<br><div><br></div><div>This consensus=
 is now confirmed: for the foreseeable=C2=A0future,</div><div>the WEBTRANS =
working group will focus on building a single</div><div>UDP-based protocol =
for WebTransport, and that protocol will</div><div>run atop HTTP/3.</div><d=
iv><br></div><div>Our next step is to adopt a document that matches this</d=
iv><div>description. The only matching proposal that has been</div><div>dis=
cussed on this list so far is Victor&#39;s</div><div>&quot;WebTransport ove=
r HTTP/3&quot; individual draft:</div><div><a href=3D"https://tools.ietf.or=
g/html/draft-vvv-webtransport-http3" rel=3D"noreferrer" target=3D"_blank">h=
ttps://tools.ietf.org/html/draft-vvv-webtransport-http3</a></div><div><br><=
/div><div>We are therefore=C2=A0placing this document in a call for adoptio=
n.</div></div></blockquote></div></div><div dir=3D"auto"><br></div><div dir=
=3D"auto">Can you please confirm the draft version that you are issuing an =
adoption call for?</div><div dir=3D"auto"><br></div><div dir=3D"auto">The r=
eason I ask is that a new draft was published on January 27 (just yesterday=
), while the group discussed an older draft (and even a bit of an editors c=
opy) during the interim meeting.=C2=A0</div><div dir=3D"auto"><br></div><di=
v dir=3D"auto">Personally, I don&#39;t think there is material difference b=
ut I think it benefits the group to be precise here.</div><div dir=3D"auto"=
><br></div><div dir=3D"auto">Cheers</div><div dir=3D"auto">Lucas</div></div=
>
</blockquote></div>

--00000000000032e7cb05b9eb0a21--


From nobody Wed Jan 27 16:56:20 2021
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: webtransport@ietf.org
Delivered-To: webtransport@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 086093A0F0E for <webtransport@ietf.org>; Wed, 27 Jan 2021 16:56:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <webtransport@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161179537802.1337.2191465712272177032@ietfa.amsl.com>
Date: Wed, 27 Jan 2021 16:56:18 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/O1fTvDiEK3c24kM2qbh4B17q-U4>
Subject: [Webtransport] Milestones changed for webtrans WG
X-BeenThere: webtransport@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 28 Jan 2021 00:56:18 -0000

Changed milestone "Adopt a WebTransport Overview draft as a WG work item",
resolved as "Done", added draft-ietf-webtrans-overview to milestone.

Changed milestone "Adopt a draft defining a WebTransport protocol as a WG
work item", set due date to February 2021 from March 2020.

Changed milestone "Issue WG last call of the WebTransport Overview
document.", set due date to October 2021 from October 2020.

Changed milestone "Issue WG last call on the first WebTransport protocol
document", set due date to March 2022 from January 2021.

URL: https://datatracker.ietf.org/wg/webtrans/about/


From nobody Thu Jan 28 10:34:30 2021
Return-Path: <ianswett@google.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 1B4AD3A1067 for <webtransport@ietfa.amsl.com>; Thu, 28 Jan 2021 10:34:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level: 
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 xIJAncfqcJBK for <webtransport@ietfa.amsl.com>; Thu, 28 Jan 2021 10:34:27 -0800 (PST)
Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) (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 476863A1060 for <webtransport@ietf.org>; Thu, 28 Jan 2021 10:34:27 -0800 (PST)
Received: by mail-wm1-x335.google.com with SMTP id u14so5093548wml.4 for <webtransport@ietf.org>; Thu, 28 Jan 2021 10:34:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BEJC4V/85ZlGXOjkFm1+YEIgSyUGTfFaEXvDb3oItrY=; b=bjT7l4kxg/FLmZEYL6YjeyJh1LlpOwwub3fUybcywoWcucYBBWrbTFwetpAOrWCm77 ndOsiPCjCcsPaNK/z4fy+6+rSz1tkoHslRFsXupeNZKCYQjEu63uQq5SpCMIX1gXCHn/ fqtHiAF/I7w54HLSWw+hBjS8MuNsYobK+w0EJt2VM92MPyk3HpYWvyktDZ3ZhZ8Y/m2Q K+Dk8UkPDXEuif3QHF7V/gEvc91EyaYKKlpDFLfZYgLbKpaLCOt3O19/7rMnw4FinvZ9 hsapBSC6UCj7z2IYt/gBcf0HTCBDq9AEgFoPeOjaFNXA44m5v6QJSFPJNWH47LLtngQq byTw==
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=BEJC4V/85ZlGXOjkFm1+YEIgSyUGTfFaEXvDb3oItrY=; b=BuJdWtFNt8tNXIOmYudNcbSw3MYyGi22WZZWLdOQecpxYoA7m93Q+SDiIgW6hNLkAf xLCmIqaEKVfZwgjznJlRN6fOCL7QmKijpExYTHY5hf2Ooq4X2bZpCzH4m5aEVnIbf31m J2HMzalOagA163Fr93PuW9qKSkaL9kYXwrss5zU9Bz46VItuXealgBoLMb/oa2hted8F h3sR+tEhrORpqTh3T2EYsDArkV99QQOugXrBc40j/b4L3amw8Js9ActW77869pl7QDU/ fw+QIRMO8mmsQzSDNfWVQ27H82D6as4vPYHwdYRFZch0Qhuu+pNdWLr8pjyvi5P0tRL6 I2Eg==
X-Gm-Message-State: AOAM531iNaWwSMov9rgQBXyvV71KKAUUOr181qHgz3QoqmwpDYJs7yRm 9/d3YEJUt7Ugo8mECkhz1v0uPKcwxrSPTl/hMhA58w==
X-Google-Smtp-Source: ABdhPJzPIQg7QneNwXHJfNbUxVVCLQ6N5j3ts7iR5JmavfSr0hMzXWHYRdDM+UeLuixqq54+midBC20pxwA5Y+RDfp0=
X-Received: by 2002:a7b:c854:: with SMTP id c20mr508616wml.127.1611858865355;  Thu, 28 Jan 2021 10:34:25 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <CAPDSy+4REQypGw2=_R0OGWPdUL20ZB4gnS2jqnsyU+D1pCscCQ@mail.gmail.com> <CALGR9obEvHogho5vFYkyozudMNOL=FYByvgwUHK22rutMjQwHA@mail.gmail.com> <CAPDSy+4i30r0Vo==HnvK6hq6+LDakTPHrd=5nLvifcM8RM8hsg@mail.gmail.com>
In-Reply-To: <CAPDSy+4i30r0Vo==HnvK6hq6+LDakTPHrd=5nLvifcM8RM8hsg@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Thu, 28 Jan 2021 13:34:12 -0500
Message-ID: <CAKcm_gPOS_yjM9P_eRMdkuEB8dZumSHwkkxBkdD6Pi3-AdZ_WQ@mail.gmail.com>
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000019632805b9fa230b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/AKJosjAMDYASf8dWYhKKSkD0Zbg>
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: Thu, 28 Jan 2021 18:34:29 -0000

--00000000000019632805b9fa230b
Content-Type: text/plain; charset="UTF-8"

I've read the latest version and support adoption.

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

> Hi Lucas,
>
> The adoption call covers the latest version as of today, which is -03:
> https://tools.ietf.org/html/draft-vvv-webtransport-http3-03
>
> David
>
> On Wed, Jan 27, 2021 at 4:25 PM Lucas Pardue <lucaspardue.24.7@gmail.com>
> wrote:
>
>> Hi David
>>
>> On Thu, 28 Jan 2021, 00:17 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.
>>>
>>
>> Can you please confirm the draft version that you are issuing an adoption
>> call for?
>>
>> The reason I ask is that a new draft was published on January 27 (just
>> yesterday), while the group discussed an older draft (and even a bit of an
>> editors copy) during the interim meeting.
>>
>> Personally, I don't think there is material difference but I think it
>> benefits the group to be precise here.
>>
>> Cheers
>> Lucas
>>
> --
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport
>

--00000000000019632805b9fa230b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;ve read the latest version and support adoption.</di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On W=
ed, Jan 27, 2021 at 7:33 PM David Schinazi &lt;<a href=3D"mailto:dschinazi.=
ietf@gmail.com">dschinazi.ietf@gmail.com</a>&gt; wrote:<br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hi Lucas,<div><br>=
<div>The adoption call covers the latest version as of today, which is -03:=
</div><div><a href=3D"https://tools.ietf.org/html/draft-vvv-webtransport-ht=
tp3-03" target=3D"_blank">https://tools.ietf.org/html/draft-vvv-webtranspor=
t-http3-03</a><br></div><div><br></div><div>David</div></div></div><br><div=
 class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 27=
, 2021 at 4:25 PM Lucas Pardue &lt;<a href=3D"mailto:lucaspardue.24.7@gmail=
.com" target=3D"_blank">lucaspardue.24.7@gmail.com</a>&gt; wrote:<br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto"><div>Hi=
 David=C2=A0<br><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gm=
ail_attr">On Thu, 28 Jan 2021, 00:17 David Schinazi, &lt;<a href=3D"mailto:=
dschinazi.ietf@gmail.com" target=3D"_blank">dschinazi.ietf@gmail.com</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div di=
r=3D"ltr">Hi WebTransport enthusiasts,<br><div><br></div><div>This consensu=
s is now confirmed: for the foreseeable=C2=A0future,</div><div>the WEBTRANS=
 working group will focus on building a single</div><div>UDP-based protocol=
 for WebTransport, and that protocol will</div><div>run atop HTTP/3.</div><=
div><br></div><div>Our next step is to adopt a document that matches this</=
div><div>description. The only matching proposal that has been</div><div>di=
scussed on this list so far is Victor&#39;s</div><div>&quot;WebTransport ov=
er HTTP/3&quot; individual draft:</div><div><a href=3D"https://tools.ietf.o=
rg/html/draft-vvv-webtransport-http3" rel=3D"noreferrer" target=3D"_blank">=
https://tools.ietf.org/html/draft-vvv-webtransport-http3</a></div><div><br>=
</div><div>We are therefore=C2=A0placing this document in a call for adopti=
on.</div></div></blockquote></div></div><div dir=3D"auto"><br></div><div di=
r=3D"auto">Can you please confirm the draft version that you are issuing an=
 adoption call for?</div><div dir=3D"auto"><br></div><div dir=3D"auto">The =
reason I ask is that a new draft was published on January 27 (just yesterda=
y), while the group discussed an older draft (and even a bit of an editors =
copy) during the interim meeting.=C2=A0</div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">Personally, I don&#39;t think there is material difference =
but I think it benefits the group to be precise here.</div><div dir=3D"auto=
"><br></div><div dir=3D"auto">Cheers</div><div dir=3D"auto">Lucas</div></di=
v>
</blockquote></div>
-- <br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport=
</a><br>
</blockquote></div>

--00000000000019632805b9fa230b--


From nobody Thu Jan 28 16:48:47 2021
Return-Path: <prvs=1663374463=afrind@fb.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 ECB553A07DF for <webtransport@ietfa.amsl.com>; Thu, 28 Jan 2021 16:48:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.368
X-Spam-Level: 
X-Spam-Status: No, score=-2.368 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=BDsGfqlx; dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=fb.onmicrosoft.com header.b=aHo/7cqn
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 wqORvQVWs74D for <webtransport@ietfa.amsl.com>; Thu, 28 Jan 2021 16:48:43 -0800 (PST)
Received: from mx0a-00082601.pphosted.com (mx0a-00082601.pphosted.com [67.231.145.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FDDF3A0691 for <webtransport@ietf.org>; Thu, 28 Jan 2021 16:48:43 -0800 (PST)
Received: from pps.filterd (m0109334.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 10T0cFuG028388; Thu, 28 Jan 2021 16:48:42 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=zyRyvfrB8pkjrl6DOvAkq4/t97/HJUnkt9DraS5+Nb8=; b=BDsGfqlxbTKHeIwx/cU1ejsumMWf91dCC5v7Kx+CnEwHQsH/5DXsuFytACMbfUJDuizR 3Jd3COMEYVvQGvdPqwvp3wCAYMoYwniAHTdtm6WmTZtAC0XJIYzr9ckrcnuI4zlwJr47 U33cFzKqcFIeYZGOR//XW+U/S6Mz6YM9S6A= 
Received: from mail.thefacebook.com ([163.114.132.120]) by mx0a-00082601.pphosted.com with ESMTP id 36bb349742-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 28 Jan 2021 16:48:42 -0800
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (100.104.98.9) by o365-in.thefacebook.com (100.104.94.196) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Thu, 28 Jan 2021 16:48:41 -0800
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Zh5WeZnU9MLO3K3IODsumYH9QrwDrz6xIt5nDc+RH1FC25dNgkopOEL62NdOGQBQNMf4SdJHJIYzbUwPYv0W7TiR/H01yPecps3FRMpuEBD2/NympC3lihvppQpTLkd1WINmn6mcHfkgQfuzSdHtnC77L48JEm/dW/MuseQNI/u6IU9f4IjXNQvSl+eaN9b3x3RFlrO1E1qaL3iXL7EwOBRKLQWymPtl/5RpErFQpgMjYd0lLnkiuwsVlUv/mZ1JVzviFDAKEnkPTDu3uD9LdneJXnkI7h1edMUrmvxS+hnBeYuSZnJVOt+JrnwPUdXB6MMyTDyx0HUGKQLlmb5L+A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=BIloP8GnuuXc9gTxHYJJTwPMkXB0cv1wwfoYQ5hlgcg=; b=bP5u7GHwQfqDKpHL0eDFb8vGvd4sHibmDkFP7HsuvmPawCN1boSXzinmyFpAGJWjseUKArpM3Fg2asBvfLFnNZkA9HWADB4rkUk3mv3p9SLIB20SRRu87rmf+G4u0II0WKQMcS5VsBFkRGDFCLDnp3kZUW76lzxxBAxG2X6EbzYzbgfFKPQM5rtoMC3xrt4/Iw3xZqZlg+epp1ISjc3m7LmbKxnBd9tkCKOF8GDSbAvit1hdcSk1CwPv9GFI16y73UqKbK4d+8l17m2DJbhKMzipal5dfhUZjtA/zpHqrRP2VBqEsmBDA5r5pjm2GC3kBdoilClpiokPRwFvPV6xgA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=fb.com; dmarc=pass action=none header.from=fb.com; dkim=pass header.d=fb.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector2-fb-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=BIloP8GnuuXc9gTxHYJJTwPMkXB0cv1wwfoYQ5hlgcg=; b=aHo/7cqne6Wcxb2UspyBLHGxb1LzszGouIa3vOVMxWlGA6u/+VXoMbCV8C7PNUnRcALeGiinFXML7zgD+SGkW2y4kw7xIlSbmxzR+6sAToZGsah7xnIX75mf4zsG1T5b2WX4rCaPlkMIkuQOe/YCjEkNpQ7j3F0NwtLeHYDZ1s4=
Received: from MW3PR15MB3772.namprd15.prod.outlook.com (2603:10b6:303:4c::14) by MWHPR15MB1933.namprd15.prod.outlook.com (2603:10b6:301:59::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.13; Fri, 29 Jan 2021 00:48:40 +0000
Received: from MW3PR15MB3772.namprd15.prod.outlook.com ([fe80::5cc8:8326:be83:7b7c]) by MW3PR15MB3772.namprd15.prod.outlook.com ([fe80::5cc8:8326:be83:7b7c%8]) with mapi id 15.20.3805.016; Fri, 29 Jan 2021 00:48:39 +0000
From: Alan Frindell <afrind@fb.com>
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, David Schinazi <dschinazi.ietf@gmail.com>
CC: WebTransport <webtransport@ietf.org>, Lucas Pardue <lucaspardue.24.7@gmail.com>
Thread-Topic: [Webtransport] Confirming Consensus on WebTransport protocols
Thread-Index: AQHW6QgW3En8/QPJV0mSgKuDoOvwNqo8Q62AgAACW4CAAAJPgIABLfEA///igoA=
Date: Fri, 29 Jan 2021 00:48:39 +0000
Message-ID: <5F32D122-C9FF-41C5-957A-1B94DB9926A7@fb.com>
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <CAPDSy+4REQypGw2=_R0OGWPdUL20ZB4gnS2jqnsyU+D1pCscCQ@mail.gmail.com> <CALGR9obEvHogho5vFYkyozudMNOL=FYByvgwUHK22rutMjQwHA@mail.gmail.com> <CAPDSy+4i30r0Vo==HnvK6hq6+LDakTPHrd=5nLvifcM8RM8hsg@mail.gmail.com> <CAKcm_gPOS_yjM9P_eRMdkuEB8dZumSHwkkxBkdD6Pi3-AdZ_WQ@mail.gmail.com>
In-Reply-To: <CAKcm_gPOS_yjM9P_eRMdkuEB8dZumSHwkkxBkdD6Pi3-AdZ_WQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.45.21011103
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=fb.com;
x-originating-ip: [2620:10d:c090:400::5:f9ae]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: aa79d4cc-0b17-40ae-f757-08d8c3ef9ead
x-ms-traffictypediagnostic: MWHPR15MB1933:
x-microsoft-antispam-prvs: <MWHPR15MB1933A3AE10460D22444A5B76A7B99@MWHPR15MB1933.namprd15.prod.outlook.com>
x-fb-source: Internal
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: S04nhJjZTvt2gFlKn6Z62RShJxawTwtBArNBYyCVVtUB22goB+cjgiu8oVHLSGz74uAmLr7FUhJ4CXsaa1moUich8LF6VhqEUkDIkPx9vvgCP73c63aHfio7jXEohW5W236rPRd8ukY2u0Nrv9EMcR1cqxOQCwBTQTXEjR4tqJNWDssqDe+cyEuZphDGlS7HbLRu7gL9/WUqJna2BdvdPoiP0WV2PHEgOJeZvG/0RJW9rKBU7u8zcwXGH/QjSLH6uwadXLV8EAAuCIJHUnrYgMuU6rxMAg0YHYMAZAEuY4sNjabeYJCTcp6CX2L0nTykNcCZyAQtAloV+TA2Iw+qCpaMrYwbu9OYT2GP484Uu4KDXAeUjrGeXbnUq94jR1fYDcnz3BgJW/71bnY23MOjp6/5VYIpOQaeNFf3GCsRvtPNznL8JPSXhgr9MacDtgAJlvw/eD+4xJtxUS3NjnlWXc6UxUJa3cDbzk4FvcqS2Ru9ngQsK4yktbJ9L5guNAPRzXQ1Mfwb6kglTHyRSh+PJPiVlvw3SUTS3/3t8GBldfnIQQQoLCMdnL8yM5XuSFF3GeOIBj3VrjjKRh8FWdRtasjjbgY0C+/jN80wpdkv6tGdOLIfPvsy/rlQ+BUV32nq9xPIKK/lxbSsi+ZTpKTehw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MW3PR15MB3772.namprd15.prod.outlook.com; PTR:; CAT:NONE;  SFS:(346002)(39860400002)(136003)(366004)(376002)(396003)(6512007)(64756008)(66476007)(8936002)(66946007)(316002)(6506007)(53546011)(83380400001)(2616005)(36756003)(76116006)(4326008)(478600001)(54906003)(5660300002)(966005)(2906002)(71200400001)(66556008)(6486002)(166002)(33656002)(186003)(86362001)(110136005)(66446008)(8676002)(45980500001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?bSsvK3o1aEVqbjByNndnNU42K3dXSnBkbFN1dzFzZVIxaDNhZUZxdHhLcUNJ?= =?utf-8?B?ejJreFROWWZvOUVRd0JKNEhjalN5aEloY3VMQmRKUnkzVU1qNWtmc0cydEE2?= =?utf-8?B?NlBnUm9MZTRYS1FPZ0JtTkxWM2ZVK05RZER2Ry83SitHdkQzc2YwT0lWcVZi?= =?utf-8?B?dHJkWFozdmoxdXA2Z214ZmVZNDA3OG1XdmJ2SEZWb0p3RklCSzRLZHdoZ3dj?= =?utf-8?B?SWJnNmlvK0RLVWpJVkQzOUVHcHZGMmVBV3RtNXJFdzFnK0NpZnlXQWl3SS9K?= =?utf-8?B?bGVscnVYVXlyemNMZ3M4MzFNVVdzM1NkUFkyZWlhaUxTbmJYNmpFQWMvaHFR?= =?utf-8?B?cFZibzVkQm8rOGxGbHZBMitadlkyb0x6cThmQlZRTlFqelc1U29Va1huVVZX?= =?utf-8?B?bWYzYXlUZWU5S1JNSGhRam0xRmxEcUNsc2t3ZWtGQTd1aS9GM203YjAwdm9O?= =?utf-8?B?eWZiSTdEMDR2V2pPNEJCKzJMeVhSNUhlYmZWVzJWOUJUdXdQRnlSeGZwbUxU?= =?utf-8?B?RGhSNVNva0NjcnZZZk91dmZybGlmTW9JVm5wRzgzWk1RNDdrcUEvRmNVcDJ0?= =?utf-8?B?NFF6QUlGSWt4amNuVEQzQyt0SlBlY0ZKNitWNUltM0NUdHpkaExMQ2RuelBG?= =?utf-8?B?UnhxY0pPMFZTUlllQlB0WTNVZmlsRFZoajdRbTlkaGRtcHBvTmNhY3diK0Y5?= =?utf-8?B?U2RnMWNtekRzZ1pzSExqbmFMWlZOMUxVbnJOZSt6d2lqZUN3Vk40MmFkWnlk?= =?utf-8?B?Ly9SNDBXcjBJZHdUb2dBRGFIaGFLcmtuRzl4MHZPaENZOVRoU0xaSXJBazVt?= =?utf-8?B?TGZ0N3ZhbGFva0tBaU9LN05ISFlvR21DVmllNmk2ZzRlTEh0TGNMOXRyNGlQ?= =?utf-8?B?V09jUmdnSkg3c09NWllpODFFMTIzK2VJU3hJQmlQRVZCWGZydE80YzY4eXV6?= =?utf-8?B?SWE3RVVINktUbkhKWTAyME9XOEk1dzU5K29UWENpTmtHcU96V2oxU2hYOHBS?= =?utf-8?B?VFVBalcwVDVpeFpXODdjNXFQMHRYTDMyOHB5M2lwR2w2TFdTOWVpNXhiclk0?= =?utf-8?B?Y2xrWmxMM0Nwb0xVTmhZSnd5eVF5cEdaNm83UFhCME1uOHhCMFJuMTluQ0tN?= =?utf-8?B?dHUrZ1g0VTJ3WXhYS1VITXNaWU9aM1hPcFlwQ1djNldPaHByZi8wN3FRSmpJ?= =?utf-8?B?L3F2ZTV1bWE2TEpyV1BBODRTeGFjSk5CamxPRTl2SlE2UmRxQldHNFZneFhW?= =?utf-8?B?TVJDTUprdm9zKzFRdzY2ZE9jQ1d4N3ZoYXNSMURJbkxmWkROaUxERGtlT0VX?= =?utf-8?B?dUNJTFU3YWdMaVJoaHltejcxaW5ORzB0TjNyRHR3VFlaUlpyM0x0ZlB1eHhN?= =?utf-8?B?c3VEWnFNYm5xaWFYNGp1Ny9XMm45ZlJnMDI2NTdmNmsybnltc3JBcWNNWlFl?= =?utf-8?B?cFlXM3ZnVG1xMnJ3Q3IwWUZjQnRqd3BQczJxSS96NzJCMVJZOFpXWlZCbm9K?= =?utf-8?Q?hhLm9A=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_5F32D122C9FF41C5957A1B94DB9926A7fbcom_"
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MW3PR15MB3772.namprd15.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: aa79d4cc-0b17-40ae-f757-08d8c3ef9ead
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jan 2021 00:48:39.8571 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: /EeA1MjEt9YVQUnm026Gk7ybTHTtbJ0yWI7KggrCxAwoFssjb1BsxVc9W2D1Ew76
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR15MB1933
X-OriginatorOrg: fb.com
X-Proofpoint-UnRewURL: 6 URL's were un-rewritten
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-28_12:2021-01-28, 2021-01-28 signatures=0
X-Proofpoint-Spam-Details: rule=fb_default_notspam policy=fb_default score=0 suspectscore=0 priorityscore=1501 impostorscore=0 malwarescore=0 phishscore=0 mlxlogscore=999 spamscore=0 bulkscore=0 adultscore=0 mlxscore=0 lowpriorityscore=0 clxscore=1015 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101290001
X-FB-Internal: deliver
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/GYUTAbh0NI6AusvrV12DZAgz7F8>
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: Fri, 29 Jan 2021 00:48:45 -0000

--_000_5F32D122C9FF41C5957A1B94DB9926A7fbcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SeKAmXZlIHJlYWQgdGhlIGxhdGVzdCB2ZXJzaW9uIGFuZCBJIHN1cHBvcnQgYWRvcHRpb24uDQoN
CkZyb206IFdlYnRyYW5zcG9ydCA8d2VidHJhbnNwb3J0LWJvdW5jZXNAaWV0Zi5vcmc+IG9uIGJl
aGFsZiBvZiBJYW4gU3dldHQgPGlhbnN3ZXR0PTQwZ29vZ2xlLmNvbUBkbWFyYy5pZXRmLm9yZz4N
CkRhdGU6IFRodXJzZGF5LCBKYW51YXJ5IDI4LCAyMDIxIGF0IDEwOjM0IEFNDQpUbzogRGF2aWQg
U2NoaW5hemkgPGRzY2hpbmF6aS5pZXRmQGdtYWlsLmNvbT4NCkNjOiBXZWJUcmFuc3BvcnQgPHdl
YnRyYW5zcG9ydEBpZXRmLm9yZz4sIEx1Y2FzIFBhcmR1ZSA8bHVjYXNwYXJkdWUuMjQuN0BnbWFp
bC5jb20+DQpTdWJqZWN0OiBSZTogW1dlYnRyYW5zcG9ydF0gQ29uZmlybWluZyBDb25zZW5zdXMg
b24gV2ViVHJhbnNwb3J0IHByb3RvY29scw0KDQpJJ3ZlIHJlYWQgdGhlIGxhdGVzdCB2ZXJzaW9u
IGFuZCBzdXBwb3J0IGFkb3B0aW9uLg0KDQpPbiBXZWQsIEphbiAyNywgMjAyMSBhdCA3OjMzIFBN
IERhdmlkIFNjaGluYXppIDxkc2NoaW5hemkuaWV0ZkBnbWFpbC5jb208bWFpbHRvOmRzY2hpbmF6
aS5pZXRmQGdtYWlsLmNvbT4+IHdyb3RlOg0KSGkgTHVjYXMsDQoNClRoZSBhZG9wdGlvbiBjYWxs
IGNvdmVycyB0aGUgbGF0ZXN0IHZlcnNpb24gYXMgb2YgdG9kYXksIHdoaWNoIGlzIC0wMzoNCmh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC12dnYtd2VidHJhbnNwb3J0LWh0dHAzLTAz
PGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC12dnYtd2VidHJhbnNwb3J0LWh0dHAz
LTAzPg0KDQpEYXZpZA0KDQpPbiBXZWQsIEphbiAyNywgMjAyMSBhdCA0OjI1IFBNIEx1Y2FzIFBh
cmR1ZSA8bHVjYXNwYXJkdWUuMjQuN0BnbWFpbC5jb208bWFpbHRvOmx1Y2FzcGFyZHVlLjI0LjdA
Z21haWwuY29tPj4gd3JvdGU6DQpIaSBEYXZpZA0KT24gVGh1LCAyOCBKYW4gMjAyMSwgMDA6MTcg
RGF2aWQgU2NoaW5hemksIDxkc2NoaW5hemkuaWV0ZkBnbWFpbC5jb208bWFpbHRvOmRzY2hpbmF6
aS5pZXRmQGdtYWlsLmNvbT4+IHdyb3RlOg0KSGkgV2ViVHJhbnNwb3J0IGVudGh1c2lhc3RzLA0K
DQpUaGlzIGNvbnNlbnN1cyBpcyBub3cgY29uZmlybWVkOiBmb3IgdGhlIGZvcmVzZWVhYmxlIGZ1
dHVyZSwNCnRoZSBXRUJUUkFOUyB3b3JraW5nIGdyb3VwIHdpbGwgZm9jdXMgb24gYnVpbGRpbmcg
YSBzaW5nbGUNClVEUC1iYXNlZCBwcm90b2NvbCBmb3IgV2ViVHJhbnNwb3J0LCBhbmQgdGhhdCBw
cm90b2NvbCB3aWxsDQpydW4gYXRvcCBIVFRQLzMuDQoNCk91ciBuZXh0IHN0ZXAgaXMgdG8gYWRv
cHQgYSBkb2N1bWVudCB0aGF0IG1hdGNoZXMgdGhpcw0KZGVzY3JpcHRpb24uIFRoZSBvbmx5IG1h
dGNoaW5nIHByb3Bvc2FsIHRoYXQgaGFzIGJlZW4NCmRpc2N1c3NlZCBvbiB0aGlzIGxpc3Qgc28g
ZmFyIGlzIFZpY3RvcidzDQoiV2ViVHJhbnNwb3J0IG92ZXIgSFRUUC8zIiBpbmRpdmlkdWFsIGRy
YWZ0Og0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXZ2di13ZWJ0cmFuc3BvcnQt
aHR0cDM8aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXZ2di13ZWJ0cmFuc3BvcnQt
aHR0cDM+DQoNCldlIGFyZSB0aGVyZWZvcmUgcGxhY2luZyB0aGlzIGRvY3VtZW50IGluIGEgY2Fs
bCBmb3IgYWRvcHRpb24uDQoNCkNhbiB5b3UgcGxlYXNlIGNvbmZpcm0gdGhlIGRyYWZ0IHZlcnNp
b24gdGhhdCB5b3UgYXJlIGlzc3VpbmcgYW4gYWRvcHRpb24gY2FsbCBmb3I/DQoNClRoZSByZWFz
b24gSSBhc2sgaXMgdGhhdCBhIG5ldyBkcmFmdCB3YXMgcHVibGlzaGVkIG9uIEphbnVhcnkgMjcg
KGp1c3QgeWVzdGVyZGF5KSwgd2hpbGUgdGhlIGdyb3VwIGRpc2N1c3NlZCBhbiBvbGRlciBkcmFm
dCAoYW5kIGV2ZW4gYSBiaXQgb2YgYW4gZWRpdG9ycyBjb3B5KSBkdXJpbmcgdGhlIGludGVyaW0g
bWVldGluZy4NCg0KUGVyc29uYWxseSwgSSBkb24ndCB0aGluayB0aGVyZSBpcyBtYXRlcmlhbCBk
aWZmZXJlbmNlIGJ1dCBJIHRoaW5rIGl0IGJlbmVmaXRzIHRoZSBncm91cCB0byBiZSBwcmVjaXNl
IGhlcmUuDQoNCkNoZWVycw0KTHVjYXMNCi0tDQpXZWJ0cmFuc3BvcnQgbWFpbGluZyBsaXN0DQpX
ZWJ0cmFuc3BvcnRAaWV0Zi5vcmc8bWFpbHRvOldlYnRyYW5zcG9ydEBpZXRmLm9yZz4NCmh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vd2VidHJhbnNwb3J0PGh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vd2VidHJhbnNwb3J0Pg0K

--_000_5F32D122C9FF41C5957A1B94DB9926A7fbcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <33E65DB389FA13408F656BDEBCCA4C30@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCWZvbnQtc2l6
ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBz
cGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsN
Cgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1z
dHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNl
cmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5
cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjEN
Cgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30N
CmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT4NCjwv
aGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIiBzdHls
ZT0id29yZC13cmFwOmJyZWFrLXdvcmQiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPknigJl2ZSByZWFkIHRoZSBsYXRlc3QgdmVyc2lvbiBhbmQgSSBz
dXBwb3J0IGFkb3B0aW9uLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNv
bGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xvcjpibGFjayI+
RnJvbTogPC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xvcjpibGFj
ayI+V2VidHJhbnNwb3J0ICZsdDt3ZWJ0cmFuc3BvcnQtYm91bmNlc0BpZXRmLm9yZyZndDsgb24g
YmVoYWxmIG9mIElhbiBTd2V0dCAmbHQ7aWFuc3dldHQ9NDBnb29nbGUuY29tQGRtYXJjLmlldGYu
b3JnJmd0Ozxicj4NCjxiPkRhdGU6IDwvYj5UaHVyc2RheSwgSmFudWFyeSAyOCwgMjAyMSBhdCAx
MDozNCBBTTxicj4NCjxiPlRvOiA8L2I+RGF2aWQgU2NoaW5hemkgJmx0O2RzY2hpbmF6aS5pZXRm
QGdtYWlsLmNvbSZndDs8YnI+DQo8Yj5DYzogPC9iPldlYlRyYW5zcG9ydCAmbHQ7d2VidHJhbnNw
b3J0QGlldGYub3JnJmd0OywgTHVjYXMgUGFyZHVlICZsdDtsdWNhc3BhcmR1ZS4yNC43QGdtYWls
LmNvbSZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UmU6IFtXZWJ0cmFuc3BvcnRdIENvbmZpcm1p
bmcgQ29uc2Vuc3VzIG9uIFdlYlRyYW5zcG9ydCBwcm90b2NvbHM8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkndmUgcmVhZCB0aGUg
bGF0ZXN0IHZlcnNpb24gYW5kIHN1cHBvcnQgYWRvcHRpb24uPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBXZWQsIEphbiAyNywgMjAyMSBhdCA3OjMzIFBN
IERhdmlkIFNjaGluYXppICZsdDs8YSBocmVmPSJtYWlsdG86ZHNjaGluYXppLmlldGZAZ21haWwu
Y29tIj5kc2NoaW5hemkuaWV0ZkBnbWFpbC5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNv
bGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0
LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IaSBM
dWNhcyw8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGUgYWRvcHRpb24g
Y2FsbCBjb3ZlcnMgdGhlIGxhdGVzdCB2ZXJzaW9uIGFzIG9mIHRvZGF5LCB3aGljaCBpcyAtMDM6
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YSBo
cmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtdnZ2LXdlYnRyYW5zcG9ydC1o
dHRwMy0wMyIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC12dnYtd2VidHJhbnNwb3J0LWh0dHAzLTAzPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5EYXZpZDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIFdlZCwgSmFuIDI3LCAy
MDIxIGF0IDQ6MjUgUE0gTHVjYXMgUGFyZHVlICZsdDs8YSBocmVmPSJtYWlsdG86bHVjYXNwYXJk
dWUuMjQuN0BnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5sdWNhc3BhcmR1ZS4yNC43QGdtYWls
LmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5n
OjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0K
PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbTox
Mi4wcHQiPkhpIERhdmlkJm5ic3A7PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPk9uIFRodSwgMjggSmFuIDIwMjEsIDAwOjE3IERhdmlkIFNjaGluYXpp
LCAmbHQ7PGEgaHJlZj0ibWFpbHRvOmRzY2hpbmF6aS5pZXRmQGdtYWlsLmNvbSIgdGFyZ2V0PSJf
YmxhbmsiPmRzY2hpbmF6aS5pZXRmQGdtYWlsLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6
c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0
OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhp
IFdlYlRyYW5zcG9ydCBlbnRodXNpYXN0cyw8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPlRoaXMgY29uc2Vuc3VzIGlzIG5vdyBjb25maXJtZWQ6IGZvciB0aGUg
Zm9yZXNlZWFibGUmbmJzcDtmdXR1cmUsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj50aGUgV0VCVFJBTlMgd29ya2luZyBncm91cCB3aWxsIGZvY3Vz
IG9uIGJ1aWxkaW5nIGEgc2luZ2xlPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5VRFAtYmFzZWQgcHJvdG9jb2wgZm9yIFdlYlRyYW5zcG9ydCwgYW5k
IHRoYXQgcHJvdG9jb2wgd2lsbDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+cnVuIGF0b3AgSFRUUC8zLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PdXIgbmV4dCBzdGVwIGlzIHRvIGFkb3B0IGEg
ZG9jdW1lbnQgdGhhdCBtYXRjaGVzIHRoaXM8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPmRlc2NyaXB0aW9uLiBUaGUgb25seSBtYXRjaGluZyBwcm9w
b3NhbCB0aGF0IGhhcyBiZWVuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5kaXNjdXNzZWQgb24gdGhpcyBsaXN0IHNvIGZhciBpcyBWaWN0b3Inczxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+JnF1b3Q7
V2ViVHJhbnNwb3J0IG92ZXIgSFRUUC8zJnF1b3Q7IGluZGl2aWR1YWwgZHJhZnQ6PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YSBocmVmPSJodHRw
czovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtdnZ2LXdlYnRyYW5zcG9ydC1odHRwMyIgdGFy
Z2V0PSJfYmxhbmsiPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC12dnYtd2VidHJh
bnNwb3J0LWh0dHAzPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5XZSBhcmUgdGhlcmVmb3JlJm5ic3A7cGxhY2luZyB0aGlzIGRvY3VtZW50
IGluIGEgY2FsbCBmb3IgYWRvcHRpb24uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPkNhbiB5b3UgcGxlYXNlIGNvbmZpcm0gdGhlIGRyYWZ0IHZlcnNpb24gdGhhdCB5b3UgYXJl
IGlzc3VpbmcgYW4gYWRvcHRpb24gY2FsbCBmb3I/PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoZSByZWFzb24gSSBhc2sgaXMgdGhhdCBhIG5l
dyBkcmFmdCB3YXMgcHVibGlzaGVkIG9uIEphbnVhcnkgMjcgKGp1c3QgeWVzdGVyZGF5KSwgd2hp
bGUgdGhlIGdyb3VwIGRpc2N1c3NlZCBhbiBvbGRlciBkcmFmdCAoYW5kIGV2ZW4gYSBiaXQgb2Yg
YW4gZWRpdG9ycyBjb3B5KSBkdXJpbmcgdGhlIGludGVyaW0gbWVldGluZy4mbmJzcDs8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+UGVyc29uYWxs
eSwgSSBkb24ndCB0aGluayB0aGVyZSBpcyBtYXRlcmlhbCBkaWZmZXJlbmNlIGJ1dCBJIHRoaW5r
IGl0IGJlbmVmaXRzIHRoZSBncm91cCB0byBiZSBwcmVjaXNlIGhlcmUuPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkNoZWVyczxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+THVjYXM8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPi0tIDxicj4NCldlYnRyYW5zcG9ydCBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVm
PSJtYWlsdG86V2VidHJhbnNwb3J0QGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+V2VidHJhbnNw
b3J0QGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vd2VidHJhbnNwb3J0IiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby93ZWJ0cmFuc3BvcnQ8L2E+PG86cD48L286cD48L3A+DQo8
L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_5F32D122C9FF41C5957A1B94DB9926A7fbcom_--


From nobody Thu Jan 28 18:32:04 2021
Return-Path: <bernard.aboba@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 E7DFC3A0A8E for <webtransport@ietfa.amsl.com>; Thu, 28 Jan 2021 18:32:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 JHoerwrgwL0g for <webtransport@ietfa.amsl.com>; Thu, 28 Jan 2021 18:32:01 -0800 (PST)
Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) (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 2209B3A0A73 for <webtransport@ietf.org>; Thu, 28 Jan 2021 18:32:00 -0800 (PST)
Received: by mail-pj1-x1029.google.com with SMTP id s24so4987032pjp.5 for <webtransport@ietf.org>; Thu, 28 Jan 2021 18:32:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:content-transfer-encoding:mime-version:subject:date:message-id :references:in-reply-to:to; bh=9NLO5km5fkWe0G0dkfx2WA7SwRUmaohYbWXIJ1RzbTc=; b=bZDjCa6zeSete7gv9AXvUNDRO17zs4Pdaaee4zxQ/rU1Y33O9yFQYcIIffIAmDmrL9 X/IVwe7hayRnODt9LC5Ikb3cvjleIE9eewhMBFJrNmfPuznpvqHbSC8adlg71bctyvCk Rzb7Abh8dqbjJDx+piV9KFRINlsb30JO1io7DeDj41Rw3JvY/nV7JFH6ByOs7X3ELeun LaPINhMwWol6wYepP/OIQJu7emRmUoFfncd4Af+DjgP04OIM4BAe7TnRG1mhxZKx3oTc lGaB2gBcRibW53DXcinsN5AJB+vtpqE6qng9tHJWo/S9KbCtvHawZsJGPN4euqMrUauU YWzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:message-id:references:in-reply-to:to; bh=9NLO5km5fkWe0G0dkfx2WA7SwRUmaohYbWXIJ1RzbTc=; b=jbV7rOBJ4GSyBF55Af30CdzxHoQ9FViiihsfz9wGCFH3DenYydjxwuaOvjdYzfYCqs 9Eflu1n29IGk9l+gaa8VYlsyn2V2J7LOsy8/WV+t7GQxya2FgEsvSb/Vfqh0pcPTrQ8i o550Ue3or5GffDMZy9f89PxT2hPYvjyuKLlnMR32grIUiK1sal0SywNGlMpj62NBodLu QsKlg0Wa+9akFGu/mvDv1fw2EocOTTtpfxyxi1bAHvzx0J7WGTCPJveYueF6HZTL/HXh UC4OkAd3GOKS8494vyzLGsfSxjsx0oZdRGdnQbdAZ3gOdLh4CNZ1XsmTKv1nUdN+C+vP EgFA==
X-Gm-Message-State: AOAM531Wharra5DIZWeuIoNej3YKUTqxoU2JoDMd1WRs+/I5wcaRUbLv msiwCsK0RvvslZefnVue+CXT/HJatb43/A==
X-Google-Smtp-Source: ABdhPJwFnupVdaFp3ufZZSSB3VjRDds8RZu9/E6v+9mULQkpTe5JJ28jnNAzcgpO1HXFX4LOxCAcuw==
X-Received: by 2002:a17:902:7804:b029:e1:de3:4ae6 with SMTP id p4-20020a1709027804b02900e10de34ae6mr2103159pll.22.1611887518878;  Thu, 28 Jan 2021 18:31:58 -0800 (PST)
Received: from [192.168.1.116] (c-73-83-125-67.hsd1.wa.comcast.net. [73.83.125.67]) by smtp.gmail.com with ESMTPSA id p128sm4203980pfp.210.2021.01.28.18.31.57 for <webtransport@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 28 Jan 2021 18:31:58 -0800 (PST)
From: Bernard Aboba <bernard.aboba@gmail.com>
X-Google-Original-From: Bernard Aboba <Bernard.Aboba@gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-F1173D2B-2A0A-4B43-88DD-212B5E4D4B6E
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Thu, 28 Jan 2021 18:31:57 -0800
Message-Id: <76A1A84F-965E-4B59-A74A-CC6ACBF1C8DE@gmail.com>
References: <CAKcm_gPOS_yjM9P_eRMdkuEB8dZumSHwkkxBkdD6Pi3-AdZ_WQ@mail.gmail.com>
In-Reply-To: <CAKcm_gPOS_yjM9P_eRMdkuEB8dZumSHwkkxBkdD6Pi3-AdZ_WQ@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
X-Mailer: iPhone Mail (18D52)
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/m0CMUyd_26wiHR1YAdiU55tnEFU>
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: Fri, 29 Jan 2021 02:32:03 -0000

--Apple-Mail-F1173D2B-2A0A-4B43-88DD-212B5E4D4B6E
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

I support adoption.

>>>> 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
>>>>=20
>>>> We are therefore placing this document in a call for adoption.
>>>=20
>>>=20
>>> Can you please confirm the draft version that you are issuing an adoptio=
n call for?
>>>=20
>>> The reason I ask is that a new draft was published on January 27 (just y=
esterday), while the group discussed an older draft (and even a bit of an ed=
itors copy) during the interim meeting.=20
>>>=20
>>> Personally, I don't think there is material difference but I think it be=
nefits the group to be precise here.
>>>=20
>>> Cheers
>>> Lucas
>> --=20
>> Webtransport mailing list
>> Webtransport@ietf.org
>> https://www.ietf.org/mailman/listinfo/webtransport
> --=20
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport

--Apple-Mail-F1173D2B-2A0A-4B43-88DD-212B5E4D4B6E
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div dir=3D"ltr">I support adoption.</div><=
div dir=3D"ltr"><br></div><blockquote type=3D"cite"><div dir=3D"ltr"><div cl=
ass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div cl=
ass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div di=
r=3D"auto"><div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"ltr"><div>Our next step is to adopt a document t=
hat matches this</div><div>description. The only matching proposal that has b=
een</div><div>discussed on this list so far is Victor's</div><div>"WebTransp=
ort over HTTP/3" individual draft:</div><div><a href=3D"https://tools.ietf.o=
rg/html/draft-vvv-webtransport-http3" rel=3D"noreferrer" target=3D"_blank">h=
ttps://tools.ietf.org/html/draft-vvv-webtransport-http3</a></div><div><br></=
div><div>We are therefore&nbsp;placing this document in a call for adoption.=
</div></div></blockquote></div></div><div dir=3D"auto"><br></div><div dir=3D=
"auto">Can you please confirm the draft version that you are issuing an adop=
tion call for?</div><div dir=3D"auto"><br></div><div dir=3D"auto">The reason=
 I ask is that a new draft was published on January 27 (just yesterday), whi=
le the group discussed an older draft (and even a bit of an editors copy) du=
ring the interim meeting.&nbsp;</div><div dir=3D"auto"><br></div><div dir=3D=
"auto">Personally, I don't think there is material difference but I think it=
 benefits the group to be precise here.</div><div dir=3D"auto"><br></div><di=
v dir=3D"auto">Cheers</div><div dir=3D"auto">Lucas</div></div>
</blockquote></div>
-- <br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@ietf=
.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"norefe=
rrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport</=
a><br>
</blockquote></div>
<span>-- </span><br><span>Webtransport mailing list</span><br><span>Webtrans=
port@ietf.org</span><br><span>https://www.ietf.org/mailman/listinfo/webtrans=
port</span><br></div></blockquote></body></html>=

--Apple-Mail-F1173D2B-2A0A-4B43-88DD-212B5E4D4B6E--

