
From nobody Mon Feb  1 16:11:43 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 5EE663A15E0 for <webtransport@ietfa.amsl.com>; Mon,  1 Feb 2021 16:11:39 -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 uvKGD3ba5L5S for <webtransport@ietfa.amsl.com>; Mon,  1 Feb 2021 16:11:37 -0800 (PST)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (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 1911C3A15D9 for <webtransport@ietf.org>; Mon,  1 Feb 2021 16:11:37 -0800 (PST)
Received: by mail-pg1-x531.google.com with SMTP id t25so13586958pga.2 for <webtransport@ietf.org>; Mon, 01 Feb 2021 16:11:37 -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=xPWMo4TvCIPEXxupHrbwb9Sd0nnceJATzsmlnly3VXo=; b=uGXadbyZsmMOClIuz3SyrDyCB4bTaxh3ZHiAtwifGY0y9RgVcWUrZ2fcjgl659Mztl 9gsMY4AJMLlgodOv4rckqiP6viGoS0m3K1fdVPzNuftP5VHFRBBf86lmBaKT72n70u1i 0rspmLlmU54gezyewdpsBT2jjhjC6Y0ari+jC2XROb58Zb78AdASx6AwvSSGzDgyDuSf aUcT/SGqsAYVWTe8dFCYjW+vgw9rGrLWqSGmg6COnw9v0/DqK8t6ylg3A6omaCQVVstx UYpqs0OO9Dgnfyx5yyzqiwB+l6w9vDUnzSR3Ck9vSeMcqdc0HvrefG7mWo5nOuleBghu ZaWA==
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=xPWMo4TvCIPEXxupHrbwb9Sd0nnceJATzsmlnly3VXo=; b=JIvf2ozeBaTJ5X9ilRqouJO3a4uxk0BAvsdpuX8O3b51bF4I4/xpojVPeU4aNUDY0t uggoCCuNKRE85pgxAcHlRgy23oVZG7qsWT4L3IZ+oqeIZ80E/IcMAi3Rmzf4kAwiI7Xa YLhJwhx6Jm7DIlHx9NxengttVQl578BrGs4+ZPhUNIf5iXQleOauWgi0xrAcn9TUHXEA p2l8lYjW+KJazMl2BuQ05JiOKGqGSw1DO6v9c8omVH/cyez8AdlJgPdnYV7Z1lofEfNx zeW2inaoeuOi69Y6zZ8X3ua8lLNk0nDuHTr4+3G1McFL1On4glcv9x7+nwfkm113egES lUIg==
X-Gm-Message-State: AOAM530slXpziIjOF+Vj4D1eKWa6Lm6p1JuGuX1bu+WLEZ6s+RiLnRaY wQVqUUOKmg3RI2M6l4ycHDNffoISSAHM6q3fJx4gk5jE0JQ=
X-Google-Smtp-Source: ABdhPJwGupUrpZkt4Sy2yyBkdgolg9dC577076BveNYS5wWFucRJsftZ78W+GJovzX9Ezi1n2hIH7WVDhu0K3nWjnK0=
X-Received: by 2002:a63:705c:: with SMTP id a28mr19733533pgn.402.1612224696336;  Mon, 01 Feb 2021 16:11:36 -0800 (PST)
MIME-Version: 1.0
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Mon, 1 Feb 2021 16:11:25 -0800
Message-ID: <CAPDSy+7AE_xfWXs3zcXROJSVK_ira22Nr_w-UrkGOmTmOkHTjg@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000052c39805ba4f5070"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/_dkkxEpT7DEoMPmdV4VzRlpZXT4>
Subject: [Webtransport] Reminder: adoption call for draft-vvv-webtransport-http3-03
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, 02 Feb 2021 00:11:40 -0000

--00000000000052c39805ba4f5070
Content-Type: text/plain; charset="UTF-8"

Hi WebTransport enthusiasts,

I realized that some of you may have muted the
previous consensus thread, so I'm creating a
new one here to make sure everyone sees it.

TLDR: we are in an adoption call until 2021-02-10
for draft-vvv-webtransport-http3-03.

Full details in previous thread:
https://mailarchive.ietf.org/arch/msg/webtransport/kOKkn7qTSCQW3ug0Lbud0ApETQI/

David

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

<div dir=3D"ltr">Hi WebTransport enthusiasts,<br><div><br></div><div>I real=
ized that some of you may have muted the</div><div>previous consensus threa=
d, so I&#39;m creating a</div><div>new one here to make sure everyone sees =
it.</div><div><br></div><div>TLDR: we are in an adoption call until=C2=A020=
21-02-10</div><div>for draft-vvv-webtransport-http3-03.</div><div><br></div=
><div>Full details in previous thread:</div><div><a href=3D"https://mailarc=
hive.ietf.org/arch/msg/webtransport/kOKkn7qTSCQW3ug0Lbud0ApETQI/">https://m=
ailarchive.ietf.org/arch/msg/webtransport/kOKkn7qTSCQW3ug0Lbud0ApETQI/</a><=
/div><div><br></div><div>David</div></div>

--00000000000052c39805ba4f5070--


From nobody Thu Feb  4 11:00:11 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 75B593A1724 for <webtransport@ietfa.amsl.com>; Thu,  4 Feb 2021 11:00:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.35
X-Spam-Level: 
X-Spam-Status: No, score=-2.35 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_H2=-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=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 JAaJcKkZzPgS for <webtransport@ietfa.amsl.com>; Thu,  4 Feb 2021 11:00:07 -0800 (PST)
Received: from nwk-aaemail-lapp01.apple.com (nwk-aaemail-lapp01.apple.com [17.151.62.66]) (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 9C4EB3A1723 for <webtransport@ietf.org>; Thu,  4 Feb 2021 11:00:07 -0800 (PST)
Received: from pps.filterd (nwk-aaemail-lapp01.apple.com [127.0.0.1]) by nwk-aaemail-lapp01.apple.com (8.16.0.43/8.16.0.42) with SMTP id 114It2lh008664 for <webtransport@ietf.org>; Thu, 4 Feb 2021 11:00:07 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : content-type : mime-version : subject : date : references : to : in-reply-to : message-id; s=20180706; bh=mSFCKa+GLK80uXaIN0L7Aj+NfaDxlDXdx/isuGq0+oY=; b=Uf8fxhNJv9iJmgLW8XmCCwr6cIKrh0n4GOve3nnnUsVgZcSiXka27uBVPPlg0D+9383V nW+1AKDoD22zO+1Z+VjJFhtxySVwiZ+Z77pAsAuAtl7TT1S8GMcj34M4m7a0KIHZ9Hxa vhoA9o1RlduZ9FlIf5VJ7h7QuzFehETRQErMVohHvHozpAd/qKUhEZ7RPMbkO9X6rOVT 7PCn7JVxid1Gqw+phEHzBm1eO+yVIro4ICGjZ/N2fktLq2fFYSf00D53ZrHV8fHCn2uJ odNVMgyEd+bIwtBd/GvlFIUNQLbhCqJFS10GecvqFhc+UJvHRjTgTwHuCjO0SsnCfPng LA== 
Received: from rn-mailsvcp-mta-lapp02.rno.apple.com (rn-mailsvcp-mta-lapp02.rno.apple.com [10.225.203.150]) by nwk-aaemail-lapp01.apple.com with ESMTP id 36d794vcgc-4 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <webtransport@ietf.org>; Thu, 04 Feb 2021 11:00:07 -0800
Received: from rn-mailsvcp-mmp-lapp01.rno.apple.com (rn-mailsvcp-mmp-lapp01.rno.apple.com [17.179.253.14]) by rn-mailsvcp-mta-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec  3 2020)) with ESMTPS id <0QO000AJEQ452790@rn-mailsvcp-mta-lapp02.rno.apple.com> for webtransport@ietf.org; Thu, 04 Feb 2021 11:00:05 -0800 (PST)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp01.rno.apple.com by rn-mailsvcp-mmp-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec  3 2020)) id <0QO000P00Q3TJ900@rn-mailsvcp-mmp-lapp01.rno.apple.com> for webtransport@ietf.org; Thu, 04 Feb 2021 11:00:05 -0800 (PST)
X-Va-A: 
X-Va-T-CD: 70a0b9fe8493d6f3346f871a1b530886
X-Va-E-CD: 4ed4f33e0687dabe1b06172a3ab84b82
X-Va-R-CD: 4c92cd742ca1261c688b326f07bb1224
X-Va-CD: 0
X-Va-ID: d9667063-7e35-4cc9-8d66-c8918ee14c02
X-V-A: 
X-V-T-CD: 70a0b9fe8493d6f3346f871a1b530886
X-V-E-CD: 4ed4f33e0687dabe1b06172a3ab84b82
X-V-R-CD: 4c92cd742ca1261c688b326f07bb1224
X-V-CD: 0
X-V-ID: b6473903-2f2e-43b4-82e0-f096ddd74287
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.737 definitions=2021-02-04_09:2021-02-04, 2021-02-04 signatures=0
Received: from [17.234.20.27] (unknown [17.234.20.27]) by rn-mailsvcp-mmp-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec  3 2020)) with ESMTPSA id <0QO000TLPQ42A100@rn-mailsvcp-mmp-lapp01.rno.apple.com> for webtransport@ietf.org; Thu, 04 Feb 2021 11:00:03 -0800 (PST)
From: Eric Kinnear <ekinnear@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_91408BB4-23EA-47A0-B836-EA592673E38C"
MIME-version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Thu, 04 Feb 2021 11:00:02 -0800
References: <CAKcm_gPOS_yjM9P_eRMdkuEB8dZumSHwkkxBkdD6Pi3-AdZ_WQ@mail.gmail.com> <76A1A84F-965E-4B59-A74A-CC6ACBF1C8DE@gmail.com>
To: WebTransport <webtransport@ietf.org>
In-reply-to: <76A1A84F-965E-4B59-A74A-CC6ACBF1C8DE@gmail.com>
Message-id: <286E2251-DE83-41C7-995F-9B63079F3722@apple.com>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.737 definitions=2021-02-04_09:2021-02-04, 2021-02-04 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/AYQ6LpL2XPCFskfH59hLRIJce1s>
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, 04 Feb 2021 19:00:10 -0000

--Apple-Mail=_91408BB4-23EA-47A0-B836-EA592673E38C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I=E2=80=99ve read -03 and I support adoption.

Thanks,
Eric


> On Jan 28, 2021, at 6:31 PM, Bernard Aboba <bernard.aboba@gmail.com> =
wrote:
>=20
> I support adoption.
>=20
>> 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 =
<https://tools.ietf.org/html/draft-vvv-webtransport-http3>
>>=20
>> We are therefore placing this document in a call for adoption.
>>=20
>> Can you please confirm the draft version that you are issuing an =
adoption call for?
>>=20
>> 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.=20
>>=20
>> Personally, I don't think there is material difference but I think it =
benefits the group to be precise here.
>>=20
>> Cheers
>> Lucas
>> --=20
>> Webtransport mailing list
>> Webtransport@ietf.org <mailto:Webtransport@ietf.org>
>> https://www.ietf.org/mailman/listinfo/webtransport =
<https://www.ietf.org/mailman/listinfo/webtransport>
>> --=20
>> Webtransport mailing list
>> Webtransport@ietf.org
>> https://www.ietf.org/mailman/listinfo/webtransport
> --=20
> Webtransport mailing list
> Webtransport@ietf.org <mailto:Webtransport@ietf.org>
> https://www.ietf.org/mailman/listinfo/webtransport =
<https://www.ietf.org/mailman/listinfo/webtransport>

--Apple-Mail=_91408BB4-23EA-47A0-B836-EA592673E38C
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=E2=80=99ve read -03 and I support adoption.<div =
class=3D""><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 28, 2021, at 6:31 PM, Bernard Aboba &lt;<a =
href=3D"mailto:bernard.aboba@gmail.com" =
class=3D"">bernard.aboba@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" class=3D""><div dir=3D"ltr" 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"">I support adoption.</div><div =
dir=3D"ltr" 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""><br class=3D""></div><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin: =
0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; =
border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin: =
0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; =
border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div =
dir=3D"auto" class=3D""><div class=3D""><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin: =
0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; =
border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div =
dir=3D"ltr" class=3D""><div class=3D"">Our next step is to adopt a =
document that matches this</div><div class=3D"">description. The only =
matching proposal that has been</div><div class=3D"">discussed on this =
list so far is Victor's</div><div class=3D"">"WebTransport over HTTP/3" =
individual draft:</div><div class=3D""><a =
href=3D"https://tools.ietf.org/html/draft-vvv-webtransport-http3" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://tools.ietf.org/html/draft-vvv-webtransport-http3</a></d=
iv><div class=3D""><br class=3D""></div><div class=3D"">We are =
therefore&nbsp;placing this document in a call for =
adoption.</div></div></blockquote></div></div><div dir=3D"auto" =
class=3D""><br class=3D""></div><div dir=3D"auto" class=3D"">Can you =
please confirm the draft version that you are issuing an adoption call =
for?</div><div dir=3D"auto" class=3D""><br class=3D""></div><div =
dir=3D"auto" class=3D"">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.&nbsp;</div><div dir=3D"auto" class=3D""><br class=3D""></div><div=
 dir=3D"auto" class=3D"">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" class=3D""><br class=3D""></div><div =
dir=3D"auto" class=3D"">Cheers</div><div dir=3D"auto" =
class=3D"">Lucas</div></div></blockquote></div>--<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D"">Webtransport =
mailing list<br class=3D""><a href=3D"mailto:Webtransport@ietf.org" =
target=3D"_blank" class=3D"">Webtransport@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/webtransport" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/webtransport</a><br =
class=3D""></blockquote></div><span class=3D"">--<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br class=3D""><span =
class=3D"">Webtransport mailing list</span><br class=3D""><span =
class=3D""><a href=3D"mailto:Webtransport@ietf.org" =
class=3D"">Webtransport@ietf.org</a></span><br class=3D""><span =
class=3D""><a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" =
class=3D"">https://www.ietf.org/mailman/listinfo/webtransport</a></span><b=
r class=3D""></div></blockquote><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""><a href=3D"mailto:Webtransport@ietf.org" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">Webtransport@ietf.org</a><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""><a =
href=3D"https://www.ietf.org/mailman/listinfo/webtransport" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/webtransport</a></div></b=
lockquote></div><br class=3D""></div></div></body></html>=

--Apple-Mail=_91408BB4-23EA-47A0-B836-EA592673E38C--


From nobody Sun Feb  7 09:27:48 2021
Return-Path: <alex.gouaillard@cosmosoftware.io>
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 6DAAD3A1171 for <webtransport@ietfa.amsl.com>; Sun,  7 Feb 2021 09:27:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=cosmosoftware-io.20150623.gappssmtp.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 pM604FHvKG-R for <webtransport@ietfa.amsl.com>; Sun,  7 Feb 2021 09:27:45 -0800 (PST)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (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 43CCE3A116F for <webtransport@ietf.org>; Sun,  7 Feb 2021 09:27:45 -0800 (PST)
Received: by mail-pg1-x530.google.com with SMTP id r38so8711955pgk.13 for <webtransport@ietf.org>; Sun, 07 Feb 2021 09:27:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cosmosoftware-io.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nkKQ0rP6mE3d7bZ88HHbdlpU5O83UDhht2SYE+5xJzI=; b=f8G3kQ3dFN93Chdi4bmbSJ6CN0m3rUPPhzOuSyIWOzQV3Mhu9waAYfVpGadQ4LPgVP li89jrR0HjlPRu2POU6BMNvF08iWSmROGkWiml2fPa+Na/a0NQey3PkjX9q7eD7zgsUK 2P2255GWfaUF/rmaRPj68QPLtMa091CvBmmIgt798nStktYDELzHR1JbCaeC0/CYIVpt gX13KXqkv71cOUHPRHjjZbEhTU4b8xurp/vF+jQ5U22Vgqoxc1YxT9VhcLvLA5PYba70 N86GTYPJWsvFh9AfapzkDBB9MML/OBsXexA8gaZU4bqt7AHzDXeMfIBU5Lcbg85oGk1U x/+w==
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=nkKQ0rP6mE3d7bZ88HHbdlpU5O83UDhht2SYE+5xJzI=; b=HGdXUdPNgy1IbpotGnM3Nker4jMZFSifXlypdzHCBF1zyyQlYiNRQn82bIaPjwqQVC DyQqkvebC/lbQ4uYZZ39y1DunviN1lbvhlJ5FUatK4e3zyAWsNX4N5LJfZpdslUEgISv F0JWIPBuv98Ni0nIyS1PRqT7suvmZlwPwOgNqsPbF6QXuOT4k14QyiiQ+7jptoJuV4Ai Ay6uPIaAV9k/3xFaH3bb+zpMaFSMTy7LpOpm66Y0eFOIldjo6ACah2vjS4LsdPp7KldA ENRrhnBxwJdKIh5D3FFBwz6B+MVrYIKcEJK2iU1WlQ/fFZE0ZonZvbY8gbjl2xNEAFg4 UYYA==
X-Gm-Message-State: AOAM533yHwTWkSRQY/fg6AWjG8Bb919HX1w6J0tk9hHyv2rDEznTyejs 5sCt/cafdpJyDDbdZKAWX5Ai6Z5F2rxpgeL7KWRhoDkaStI=
X-Google-Smtp-Source: ABdhPJy1btfzVzAG4/rya78GCiDFcQPCb1NXS/7WuhfxS5j+bNMrlBkx8bJ0cG5HqjNeIAJnzCbHmST9MgS0fGxB/GY=
X-Received: by 2002:a65:6715:: with SMTP id u21mr13642074pgf.312.1612718864514;  Sun, 07 Feb 2021 09:27:44 -0800 (PST)
MIME-Version: 1.0
References: <CAKcm_gPOS_yjM9P_eRMdkuEB8dZumSHwkkxBkdD6Pi3-AdZ_WQ@mail.gmail.com> <76A1A84F-965E-4B59-A74A-CC6ACBF1C8DE@gmail.com> <286E2251-DE83-41C7-995F-9B63079F3722@apple.com>
In-Reply-To: <286E2251-DE83-41C7-995F-9B63079F3722@apple.com>
From: Alexandre GOUAILLARD <Alex.GOUAILLARD@cosmosoftware.io>
Date: Mon, 8 Feb 2021 01:27:33 +0800
Message-ID: <CACtMSQXncYCPUDzMnE-10=4KWh4hTyOm8Gh1shZdWxJB61mYGQ@mail.gmail.com>
To: Eric Kinnear <ekinnear=40apple.com@dmarc.ietf.org>
Cc: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000ad5b505bac25fe8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/ZvommDjHYeltPwx1alLG2Jn8Lg4>
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: Sun, 07 Feb 2021 17:27:48 -0000

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

I support adoption.

On Fri, Feb 5, 2021 at 3:00 AM Eric Kinnear <ekinnear=3D
40apple.com@dmarc.ietf.org> wrote:

> I=E2=80=99ve read -03 and I support adoption.
>
> Thanks,
> Eric
>
>
> On Jan 28, 2021, at 6:31 PM, Bernard Aboba <bernard.aboba@gmail.com>
> wrote:
>
> 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
>>>>
>>>> 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
>>
> --
> 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
>

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

<div dir=3D"ltr">I support adoption.</div><br><div class=3D"gmail_quote"><d=
iv dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 5, 2021 at 3:00 AM Eric Kin=
near &lt;ekinnear=3D<a href=3D"mailto:40apple.com@dmarc.ietf.org">40apple.c=
om@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:=
solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div style=3D"wo=
rd-wrap:break-word;line-break:after-white-space">I=E2=80=99ve read -03 and =
I support adoption.<div><div><br></div><div>Thanks,</div><div>Eric</div><di=
v><br><div><br><blockquote type=3D"cite"><div>On Jan 28, 2021, at 6:31 PM, =
Bernard Aboba &lt;<a href=3D"mailto:bernard.aboba@gmail.com" target=3D"_bla=
nk">bernard.aboba@gmail.com</a>&gt; wrote:</div><br><div><div dir=3D"ltr" s=
tyle=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-de=
coration:none">I support adoption.</div><div dir=3D"ltr" style=3D"font-fami=
ly: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"><b=
r></div><blockquote type=3D"cite" style=3D"font-family:Helvetica;font-size:=
12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-s=
pacing:normal;text-align:start;text-indent:0px;text-transform:none;white-sp=
ace:normal;word-spacing:0px;text-decoration:none"><div dir=3D"ltr"><div cla=
ss=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color=
:rgb(204,204,204);padding-left:1ex"><div class=3D"gmail_quote"><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1=
px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:=
1ex"><div dir=3D"auto"><div><div class=3D"gmail_quote"><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;borde=
r-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><di=
v dir=3D"ltr"><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>--<span>=C2=A0</span><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"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo=
/webtransport</a><br></blockquote></div><span>--<span>=C2=A0</span></span><=
br><span>Webtransport mailing list</span><br><span><a href=3D"mailto:Webtra=
nsport@ietf.org" target=3D"_blank">Webtransport@ietf.org</a></span><br><spa=
n><a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" target=3D"=
_blank">https://www.ietf.org/mailman/listinfo/webtransport</a></span><br></=
div></blockquote><span style=3D"font-family:Helvetica;font-size:12px;font-s=
tyle:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:norm=
al;text-align:start;text-indent:0px;text-transform:none;white-space:normal;=
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:nor=
mal;text-align:start;text-indent:0px;text-transform:none;white-space:normal=
;word-spacing:0px;text-decoration:none"><span style=3D"font-family:Helvetic=
a;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:nor=
mal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:n=
one;white-space:normal;word-spacing:0px;text-decoration:none;float:none;dis=
play:inline">Webtransport mailing list</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"><a href=3D=
"mailto:Webtransport@ietf.org" style=3D"font-family:Helvetica;font-size:12p=
x;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spac=
ing:normal;text-align:start;text-indent:0px;text-transform:none;white-space=
:normal;word-spacing:0px" target=3D"_blank">Webtransport@ietf.org</a><br st=
yle=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-dec=
oration:none"><a href=3D"https://www.ietf.org/mailman/listinfo/webtransport=
" style=3D"font-family:Helvetica;font-size:12px;font-style:normal;font-vari=
ant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;t=
ext-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport</a></div>=
</blockquote></div><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>

--0000000000000ad5b505bac25fe8--


From nobody Fri Feb 12 16:36:46 2021
Return-Path: <agenda@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 90F9C3A115D; Fri, 12 Feb 2021 16:33:28 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <bernard.aboba@gmail.com>, <webtrans-chairs@ietf.org>
Cc: barryleiba@computer.org, webtransport@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161317640857.31337.2148215778685096512@ietfa.amsl.com>
Date: Fri, 12 Feb 2021 16:33:28 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/2jOw2lRHddRXJjDpOKFe1bCTV_0>
Subject: [Webtransport] webtrans - Requested session has been scheduled for IETF 110
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: Sat, 13 Feb 2021 00:33:37 -0000

Dear Bernard Aboba,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 


    webtrans Session 1 (2:00 requested)
    Monday, 8 March 2021, Session III 1700-1900
    Room Name: Room 3 size: 503
    ---------------------------------------------


iCalendar: https://datatracker.ietf.org/meeting/110/sessions/webtrans.ics

Request Information:


---------------------------------------------------------
Working Group Name: WebTransport
Area Name: Applications and Real-Time Area
Session Requester: Bernard Aboba


Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 120
Conflicts to Avoid: 
 Chair Conflict: masque quic avtcore







People who must be present:
  Barry Leiba
  David Schinazi
  Bernard Aboba

Resources Requested:

Special Requests:
  Time between 8 AM and 8 PM Pacific desirable.
---------------------------------------------------------



From nobody Fri Feb 12 23:01:10 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 D99D53A0FB5 for <webtransport@ietfa.amsl.com>; Fri, 12 Feb 2021 23:01: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 NQKfo5yMJOTA for <webtransport@ietfa.amsl.com>; Fri, 12 Feb 2021 23:01:06 -0800 (PST)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 6843E3A0FAD for <webtransport@ietf.org>; Fri, 12 Feb 2021 23:01:06 -0800 (PST)
Received: by mail-lf1-x12b.google.com with SMTP id w36so2691758lfu.4 for <webtransport@ietf.org>; Fri, 12 Feb 2021 23:01:06 -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=xm7HGto4TkWQZSkogtidReKrrZEKZb/VXItiF80nLRw=; b=IOPqm1FnFQhJr8LooVYQmVLGVWLIJZY/0/mTHsDjn7wgnICjjAMB43VFa6y0cch0ip XRoh1kq828y3XlACYoadJAxXztAHVOnfzTsE3hw/HzsvDRTcp/M5zCEq63PySegoxolI DxTtTf1hbS3O9CQHSA5r52PIEyAJ3Xyl66Sxo3sH+9V6ci62AdeXMoqe+ynxS5pH8OYr H8PJ9lzpCeZU47Ye+yPWxfoRw5Ep1NVBqwBXk/CKZik7SVm/SnTUotx99mSDAgQj+Nq7 y/SemBOoEeM8wepM2bK4XhAXsb6qjolU7dQjZ8xy6uwj+TsgOUxXBGvOCHT7NsaOCQ/L yCWg==
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=xm7HGto4TkWQZSkogtidReKrrZEKZb/VXItiF80nLRw=; b=AVT2pe1fn4fCCrnJNEZIVtX2BDjZPVHIL+1lfExVAfMy+mOwnNYsAHsy/GDlXX9flK 5W3+SkCYmPRG4xhaXdoAV3DBw0/XfzC/vKJ+bN1W5h1ePilsWwkf6wc8nw735I5MBI4n ecaAzBj/VOoGlgWBV6h0GT5YisstF4vINojFLDMFNCRtrux1tGHXALkj8Up778m9q+8z wJiFDzZqDMRCBEoljpRlyECjfZV1G2gVaa9I5BII1AEPgIZ5UE8YTwUyA5gU6kxjyQ55 rdZV6xxVomxUz3pKqfjFFatiTNlbp3dq66HRkCiV8YQVUVwyuGlYMssW+V7alOl306xe NeTw==
X-Gm-Message-State: AOAM531Z1o4a2gdu9aVUvHMs+uMnnrJ+wVbvYTnVi2eEQqHkoRtN4m1K jYDrUNxGxBs7GBk57nQzyYFd7bRK738WW9Hs+JVPcteF8adzSw==
X-Google-Smtp-Source: ABdhPJy4tx6051xusv3foAUJGFN1VdMJ64uVSkktH7tMlQjPdTei5bv7qL5SDp9YP0DW1jEk8/efpdMAS3iOJMR1yto=
X-Received: by 2002:ac2:5086:: with SMTP id f6mr3335827lfm.16.1613199662944; Fri, 12 Feb 2021 23:01:02 -0800 (PST)
MIME-Version: 1.0
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Fri, 12 Feb 2021 23:00:54 -0800
Message-ID: <CAOW+2dtsnGAarH9rXVSYfcin08-GXXzpmJoG-s_F2+z6=u3xeg@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dc93b605bb3250eb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/Vj2_pX_7jNhFBMSph0Ku7ckEhoQ>
Subject: [Webtransport] WEBTRANS WG meeting at IETF 110
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: Sat, 13 Feb 2021 07:01:09 -0000

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

The IETF WEBTRANS WG will meet on Monday March 8, 2021 during Session III,
in "Room 3".  Time is 8 - 10 AM Pacific.  To see the full schedule or
translate this into your preferred timezone, see the link below:
https://datatracker.ietf.org/meeting/110/agenda.html

We are also soliciting agenda requests at this time.

---------- Forwarded message ---------
From: IETF Agenda <agenda@ietf.org>
Date: Fri, Feb 12, 2021 at 4:56 PM
Subject: IETF 110 Final Agenda
To: Working Group Chairs <wgchairs@ietf.org>


IETF 110
Online
March 8-12, 2021
Hosted By: Google

The IETF 110 Final Agenda is now available. At this point, only Area
Directors may submit changes by suggesting a swap to agenda@ietf.org.

https://datatracker.ietf.org/meeting/110/agenda.html
https://datatracker.ietf.org/meeting/110/agenda.txt


While this is considered the final agenda, changes may be made to the
agenda up to and during the meeting. Updates will be reflected on the web
versions of the agenda.

Please note the agenda times are listed in CET (UTC +1) by default. You may
select which time zone is displayed on the HTML version of the agenda with
a menu on the right side of the page. Choose =E2=80=9CMeeting Timezone=E2=
=80=9D for CET,
=E2=80=9CLocal Timezone=E2=80=9D for your own current time zone, =E2=80=9CU=
TC=E2=80=9D for UTC, or choose
any other time zone from the drop down list.



Side Meetings

At IETF 110 Online, we=E2=80=99ve created a space on the wiki where individ=
uals can
post details of their side meetings. Since there are many freely available
conferencing services, the IESG will not provide conferencing support for
side meetings. Please see the wiki page for more details.

        - For more information about side meetings:
https://trac.ietf.org/trac/ietf/meeting/wiki/110sidemeetings


Gather

We will continue to use Gather for side events, help desks, hallway
conversations, and a scavenger hunt. We=E2=80=99ll be making more details a=
vailable
in the coming weeks, so please look out for further announcements.

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

<div dir=3D"ltr">The IETF WEBTRANS WG will meet on Monday March 8, 2021 dur=
ing Session III, in &quot;Room 3&quot;.=C2=A0 Time is 8 - 10 AM Pacific.=C2=
=A0 To see the full schedule or translate this into your preferred timezone=
, see the link below:=C2=A0<div><a href=3D"https://datatracker.ietf.org/mee=
ting/110/agenda.html">https://datatracker.ietf.org/meeting/110/agenda.html<=
/a></div><div><br></div><div>We are also soliciting agenda requests at this=
 time.=C2=A0<br><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gm=
ail_attr">---------- Forwarded message ---------<br>From: <strong class=3D"=
gmail_sendername" dir=3D"auto">IETF Agenda</strong> <span dir=3D"auto">&lt;=
<a href=3D"mailto:agenda@ietf.org">agenda@ietf.org</a>&gt;</span><br>Date: =
Fri, Feb 12, 2021 at 4:56 PM<br>Subject: IETF 110 Final Agenda<br>To: Worki=
ng Group Chairs &lt;<a href=3D"mailto:wgchairs@ietf.org">wgchairs@ietf.org<=
/a>&gt;<br></div><br><br>IETF 110<br>
Online<br>
March 8-12, 2021<br>
Hosted By: Google<br>
<br>
The IETF 110 Final Agenda is now available. At this point, only Area Direct=
ors may submit changes by suggesting a swap to <a href=3D"mailto:agenda@iet=
f.org" target=3D"_blank">agenda@ietf.org</a>.<br>
<br>
<a href=3D"https://datatracker.ietf.org/meeting/110/agenda.html" rel=3D"nor=
eferrer" target=3D"_blank">https://datatracker.ietf.org/meeting/110/agenda.=
html</a><br>
<a href=3D"https://datatracker.ietf.org/meeting/110/agenda.txt" rel=3D"nore=
ferrer" target=3D"_blank">https://datatracker.ietf.org/meeting/110/agenda.t=
xt</a><br>
<br>
<br>
While this is considered the final agenda, changes may be made to the agend=
a up to and during the meeting. Updates will be reflected on the web versio=
ns of the agenda. <br>
<br>
Please note the agenda times are listed in CET (UTC +1) by default. You may=
 select which time zone is displayed on the HTML version of the agenda with=
 a menu on the right side of the page. Choose =E2=80=9CMeeting Timezone=E2=
=80=9D for CET, =E2=80=9CLocal Timezone=E2=80=9D for your own current time =
zone, =E2=80=9CUTC=E2=80=9D for UTC, or choose any other time zone from the=
 drop down list. <br>
<br>
<br>
<br>
Side Meetings <br>
<br>
At IETF 110 Online, we=E2=80=99ve created a space on the wiki where individ=
uals can post details of their side meetings. Since there are many freely a=
vailable conferencing services, the IESG will not provide conferencing supp=
ort for side meetings. Please see the wiki page for more details.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 - For more information about side meetings: <a =
href=3D"https://trac.ietf.org/trac/ietf/meeting/wiki/110sidemeetings" rel=
=3D"noreferrer" target=3D"_blank">https://trac.ietf.org/trac/ietf/meeting/w=
iki/110sidemeetings</a><br>
<br>
<br>
Gather<br>
<br>
We will continue to use Gather for side events, help desks, hallway convers=
ations, and a scavenger hunt. We=E2=80=99ll be making more details availabl=
e in the coming weeks, so please look out for further announcements.<br></d=
iv></div></div>

--000000000000dc93b605bb3250eb--


From nobody Mon Feb 15 13:35:01 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 C97953A11A6 for <webtransport@ietfa.amsl.com>; Mon, 15 Feb 2021 13:34:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 82nvzAgmQ-ME for <webtransport@ietfa.amsl.com>; Mon, 15 Feb 2021 13:34:55 -0800 (PST)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FA783A11A7 for <webtransport@ietf.org>; Mon, 15 Feb 2021 13:34:55 -0800 (PST)
Received: by mail-pf1-x430.google.com with SMTP id y25so1629741pfp.5 for <webtransport@ietf.org>; Mon, 15 Feb 2021 13:34:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=7RHweS/5eZXeGf3LgH3Ve4PXKpYQ83oJvsppUi1+t/Y=; b=Lzw6nwpvVcgCc3B5a7Ja4rORFsZt5/0NbKUzuaJjbCAQJ5hlJNOGQ6HIbN+UZk8A4P aeBNSBig0GArKjqaEsQX9a5sNb8FsE6XAzL0NFyQIN2fwf8opBkQH3X730AHTxjoPMN9 73FKKNqwFZpb9CaNJAZjFmpVvJVM6j+OO5BayhuK8utalf7NBbDIraH63n77BMrNDKGH 0oVHEkz2XZvJ8DjLbzh5/8N20uzRWMnPEuDIjCSY8TWa0R4O2TFW6D0Dx1VecdDoxGmt yo+yi84SHCWLSXTjoi2TnzsNXTCVCb7vOwDw9Ffrl8rPEniLgHp3RAsKJbyyI8nLQL+z eUHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=7RHweS/5eZXeGf3LgH3Ve4PXKpYQ83oJvsppUi1+t/Y=; b=lCRTxPif1GkpiWERwiksWWVjm1Z9k9VfHpo2sMxK4XHuMTBUb5hSfHboSjGyIlxY2j +dzt1yM6B2v9WFyw3fPCJeksLixKPjqVawtAtALTfeDf2VXYc6OYs9Y8zgDSuOpUZMq2 s1LlA0ER2tEO3GMCwT4qxFesYOdXvLJl0NKqXwM00RIyZ/qy8+IiVtyLTsaCvbjdFtt1 URVoDWoOFGaZ2OeOe8kcb0MsINu/ipquYGbVxZQ3s15t622pcWqp61Kz2hKhK67pPpQ1 MUOGLz/7S3WBmDWjvBQSVNPQ74UpVdVOim5NknJJDk1Qenc1i6xRRmzDmpzgaegTQh/V VsXQ==
X-Gm-Message-State: AOAM531ttm4IbfJwToqFokwijluTH3NCvzSASRq4FPw1cNSexkoRVEQt Lfeoq4rrC5bw+R9O7ibwf6gTzuww80hACHXVVNA5PX/TfEI=
X-Google-Smtp-Source: ABdhPJw6d4U9xWHsDMpDli3ny0IAiy1Mh5lg7nfDs72HydDnTz0O8dfxgyErOABHqoBVSQ+yDsu0j4lBeHOGSNAKt/k=
X-Received: by 2002:aa7:9e82:0:b029:1ec:c566:50b2 with SMTP id p2-20020aa79e820000b02901ecc56650b2mr585237pfq.22.1613424894572; Mon, 15 Feb 2021 13:34:54 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <CAPDSy+4REQypGw2=_R0OGWPdUL20ZB4gnS2jqnsyU+D1pCscCQ@mail.gmail.com>
In-Reply-To: <CAPDSy+4REQypGw2=_R0OGWPdUL20ZB4gnS2jqnsyU+D1pCscCQ@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Mon, 15 Feb 2021 13:34:43 -0800
Message-ID: <CAPDSy+70YVUHSd_cmhzCAZz-UgDku2sC2OX3fhjaDyNosJm=0g@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b67c1805bb66c1bd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/Aj7jvjDdJ3iAW_L0zgFv7jzLwxk>
Subject: Re: [Webtransport] Confirming Consensus on WebTransport protocols
X-BeenThere: webtransport@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <webtransport.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webtransport>, <mailto:webtransport-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/webtransport/>
List-Post: <mailto:webtransport@ietf.org>
List-Help: <mailto:webtransport-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webtransport>, <mailto:webtransport-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2021 21:35:00 -0000

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

Hi everyone,

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

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

Thanks,
David

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

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

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

<div dir=3D"ltr">Hi everyone,<br><div><br></div><div>In the last 2.5 weeks =
of the adoption call, the chairs received</div><div>multiple indications of=
 support, and no objections. We therefore</div><div>declare consensus:=C2=
=A0draft-vvv-webtransport-http3=C2=A0has now been</div><div>adopted by the =
WEBTRANS WG.</div><div><br></div><div>The chairs will work with the author =
to move the GitHub</div><div>repository under our WG organization.</div><di=
v><br></div><div>Thanks,</div><div>David</div></div><br><div class=3D"gmail=
_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 27, 2021 at 4:16 =
PM 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" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-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>r=
un atop HTTP/3.</div><div><br></div><div>Our next step is to adopt a docume=
nt 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;WebTransport over HTTP/3&quot; individual draft:</div><div><a href=
=3D"https://tools.ietf.org/html/draft-vvv-webtransport-http3" target=3D"_bl=
ank">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 a=
doption.</div><div><br></div><div>Please reply to this email stating whethe=
r you support adoption</div><div>of draft-vvv-webtransport-http3=C2=A0by th=
e WEBTRANS WG. Note</div><div>that WG adoption does not indicate consensus =
on the contents</div><div>of the document, 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 e=
mail thread - please</div><div>create a separate email thread on=C2=A0&lt;<=
a href=3D"mailto:webtransport@ietf.org" target=3D"_blank">webtransport@ietf=
.org</a>&gt; or open</div><div>a GitHub issue at &lt;<a href=3D"https://git=
hub.com/vasilvv/webtransport/issues" target=3D"_blank">https://github.com/v=
asilvv/webtransport/issues</a>&gt;.</div><div><br></div><div>As usual, if y=
ou believe that we should not adopt this document,</div><div>please state w=
hy. In our last meeting we&#39;ve noted some concerns</div><div>around pool=
ing for example, and we plan on discussing those as</div><div>a working gro=
up once the document is adopted.</div><div><br></div><div>This adoption cal=
l will last for two weeks until 2021-02-10.</div><div><br></div><div>Thanks=
,</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" 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"><div>Hi WebTransport enthusiasts,<br></div><div=
><br></div><div>Today we had an interim of the IETF WEBTRANS WG,</div><div>=
where we reached consensus in the (virtual) room on</div><div>the following=
 questions:</div><div><br></div><div>Question 1: number of protocols<br></d=
iv><div>=C2=A0 =C2=A0 Should the working group adopt only one UDP-based tra=
nsport?<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><d=
iv>The consensus was option 1A.</div><div><br></div><div>Additionally, we n=
oted that this does not preclude=C2=A0us from</div><div>building a second p=
rotocol 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 Whi=
ch UDP-based option should we adopt as a starting</div><div>=C2=A0 =C2=A0 p=
oint for WebTransport 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><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><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 imperative. Please also provide as much</div><div>detail as possible to =
explain your position. Please also respond</div><div>if you support this co=
nsensus - 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 th=
is 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>
</blockquote></div>
</blockquote></div>

--000000000000b67c1805bb66c1bd--


From nobody Wed Feb 17 14:50:28 2021
Return-Path: <internet-drafts@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 B399D3A1E06; Wed, 17 Feb 2021 14:50:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: webtransport@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: webtransport@ietf.org
Message-ID: <161360222368.19296.12839747663762605057@ietfa.amsl.com>
Date: Wed, 17 Feb 2021 14:50:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/_cqtBsts_82Lyp4I6IDsupSt3CE>
Subject: [Webtransport] I-D Action: draft-ietf-webtrans-http3-00.txt
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: Wed, 17 Feb 2021 22:50:24 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the WebTransport WG of the IETF.

        Title           : WebTransport over HTTP/3
        Author          : Victor Vasiliev
	Filename        : draft-ietf-webtrans-http3-00.txt
	Pages           : 12
	Date            : 2021-02-17

Abstract:
   WebTransport [OVERVIEW] is a protocol framework that enables clients
   constrained by the Web security model to communicate with a remote
   server using a secure multiplexed transport.  This document describes
   a WebTransport protocol that is based on HTTP/3 [HTTP3] and provides
   support for unidirectional streams, bidirectional streams and
   datagrams, all multiplexed within the same HTTP/3 connection.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-webtrans-http3/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-webtrans-http3-00.html


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Wed Feb 17 15:23:38 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 B85133A1E24 for <webtransport@ietfa.amsl.com>; Wed, 17 Feb 2021 15:23:36 -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 zAmWXxiwmq1u for <webtransport@ietfa.amsl.com>; Wed, 17 Feb 2021 15:23:34 -0800 (PST)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (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 F1ADC3A1E21 for <webtransport@ietf.org>; Wed, 17 Feb 2021 15:23:33 -0800 (PST)
Received: by mail-pl1-x62e.google.com with SMTP id g20so194790plo.2 for <webtransport@ietf.org>; Wed, 17 Feb 2021 15:23:33 -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=QNa0ENaNlkfak0Ck59OOjY/SSAgDA3hIKAZtjYrDXRo=; b=l9EIgJYuOpYx+0L9RjaKXRRKIZdy3j9fbA/fA4v6JeXHX5pTDuCITSp+6vb/qI2h1h NhiT99IgcC3MmLKEsT0RlV0AB3UngQ12ZQgUmWIiWAJh04piADUAqXEih/q4RW6N8tbm gdYFXzKk7tZEDzP08tGB0vOWAvA4rd429NLdfAG6vcg53sG71GSIfexTMODcoZW48cha wZazb/uXiaFmTwuKmrcYXjh8p7gaADZdTnTMsqTZuvlhMY+QKH+ewSRsX6HaUF04vfOA ShbOzgKQCIDM0YMb7YKmEyFMCnO+5DtOPvrs/rXPh6kjv/piG4XzBVrKvQ1eCjZb0c0c Ua1A==
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=QNa0ENaNlkfak0Ck59OOjY/SSAgDA3hIKAZtjYrDXRo=; b=AcSRNHfNty3TY/ZIeiIOAt+jdt0Renbgd4biPyXxV5dCAjZDh90lPBGYs6ibWXnTvH YL8IJhRiULmxRBsFwINWQOInL7qym8/0a0wCrXnQWyEZXvdOGumvj6KYlNE9jiZrpVgB cFMuLZzZ7XaIT3gipRLz1VCW1qe6dTMIzdadFBvEHMV7MuemhW9bz2U0tcAFZaiXaEeD 0htfFBOoBVEf/GNSH0ZeYdprnukan5ZElg+lJEDbgv+dTzOs6xviq70TS5jqvm1NHljm mfcL4UK+dnG97qfVhTRzUt0obqfRjmHuHTuZELizfC+PHgpVtrdjjVh+XnqzCwh6Xwig pHxw==
X-Gm-Message-State: AOAM531pkC6sI6H0ebM7zGLbd0QPn3qLGN0UcZbly9jfTaDvMfE7Oe+f 0aqpuaZ3FlJwvJ1eEXpEctYwunVpcXiS/8SSh/EPriwZvBk=
X-Google-Smtp-Source: ABdhPJydG3A5SyHWShRgV7v8Lsw4LGQI5Pgh72dl/QAGDAPUXX9IdLjM/hDNr/ToXaguaujnJVW482QN4dRy5DKiqCM=
X-Received: by 2002:a17:90b:2382:: with SMTP id mr2mr1153484pjb.190.1613604213148;  Wed, 17 Feb 2021 15:23:33 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+5R=v2GjyJU1o=+Ai0X0iOqJSX787GfLBSUkd9odR++Rw@mail.gmail.com> <CAPDSy+4REQypGw2=_R0OGWPdUL20ZB4gnS2jqnsyU+D1pCscCQ@mail.gmail.com> <CAPDSy+70YVUHSd_cmhzCAZz-UgDku2sC2OX3fhjaDyNosJm=0g@mail.gmail.com>
In-Reply-To: <CAPDSy+70YVUHSd_cmhzCAZz-UgDku2sC2OX3fhjaDyNosJm=0g@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Wed, 17 Feb 2021 15:23:22 -0800
Message-ID: <CAPDSy+7pcD24NaoQurW_1NwMdwjztKE02VWpxfPYKPrbibfvRw@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000eeceee05bb908149"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/1WLe2uaXgVWWd3GPd8RzXpF6DY8>
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, 17 Feb 2021 23:23:37 -0000

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

Adoption is now complete. Victor has uploaded the WG document:
https://tools.ietf.org/html/draft-ietf-webtrans-http3-00
Please give it a read and file issues on the official WG GitHub repo:
https://github.com/ietf-wg-webtrans/draft-ietf-webtrans-http3/issues

Cheers,
David

On Mon, Feb 15, 2021 at 1:34 PM David Schinazi <dschinazi.ietf@gmail.com>
wrote:

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

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

<div dir=3D"ltr"><div dir=3D"ltr">Adoption is now complete. Victor has uplo=
aded the WG document:<br><div><a href=3D"https://tools.ietf.org/html/draft-=
ietf-webtrans-http3-00">https://tools.ietf.org/html/draft-ietf-webtrans-htt=
p3-00</a><br></div><div>Please give it a read and file issues on the offici=
al WG GitHub repo:</div><div><a href=3D"https://github.com/ietf-wg-webtrans=
/draft-ietf-webtrans-http3/issues">https://github.com/ietf-wg-webtrans/draf=
t-ietf-webtrans-http3/issues</a><br></div><div><br></div><div>Cheers,</div>=
<div>David</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Mon, Feb 15, 2021 at 1:34 PM 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"lt=
r">Hi everyone,<br><div><br></div><div>In the last 2.5 weeks of the adoptio=
n call, the chairs received</div><div>multiple indications of support, and =
no objections. We therefore</div><div>declare consensus:=C2=A0draft-vvv-web=
transport-http3=C2=A0has now been</div><div>adopted by the WEBTRANS WG.</di=
v><div><br></div><div>The chairs will work with the author to move the GitH=
ub</div><div>repository under our WG organization.</div><div><br></div><div=
>Thanks,</div><div>David</div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Wed, Jan 27, 2021 at 4:16 PM David Schinaz=
i &lt;<a href=3D"mailto:dschinazi.ietf@gmail.com" target=3D"_blank">dschina=
zi.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);p=
adding-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><div><br></div><div>Our next step is to adopt a docu=
ment that matches this</div><div>description. The only matching proposal th=
at has been</div><div>discussed on this list so far is Victor&#39;s</div><d=
iv>&quot;WebTransport over HTTP/3&quot; individual draft:</div><div><a href=
=3D"https://tools.ietf.org/html/draft-vvv-webtransport-http3" target=3D"_bl=
ank">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 a=
doption.</div><div><br></div><div>Please reply to this email stating whethe=
r you support adoption</div><div>of draft-vvv-webtransport-http3=C2=A0by th=
e WEBTRANS WG. Note</div><div>that WG adoption does not indicate consensus =
on the contents</div><div>of the document, 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 e=
mail thread - please</div><div>create a separate email thread on=C2=A0&lt;<=
a href=3D"mailto:webtransport@ietf.org" target=3D"_blank">webtransport@ietf=
.org</a>&gt; or open</div><div>a GitHub issue at &lt;<a href=3D"https://git=
hub.com/vasilvv/webtransport/issues" target=3D"_blank">https://github.com/v=
asilvv/webtransport/issues</a>&gt;.</div><div><br></div><div>As usual, if y=
ou believe that we should not adopt this document,</div><div>please state w=
hy. In our last meeting we&#39;ve noted some concerns</div><div>around pool=
ing for example, and we plan on discussing those as</div><div>a working gro=
up once the document is adopted.</div><div><br></div><div>This adoption cal=
l will last for two weeks until 2021-02-10.</div><div><br></div><div>Thanks=
,</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" 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"><div>Hi WebTransport enthusiasts,<br></div><div=
><br></div><div>Today we had an interim of the IETF WEBTRANS WG,</div><div>=
where we reached consensus in the (virtual) room on</div><div>the following=
 questions:</div><div><br></div><div>Question 1: number of protocols<br></d=
iv><div>=C2=A0 =C2=A0 Should the working group adopt only one UDP-based tra=
nsport?<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><d=
iv>The consensus was option 1A.</div><div><br></div><div>Additionally, we n=
oted that this does not preclude=C2=A0us from</div><div>building a second p=
rotocol 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 Whi=
ch UDP-based option should we adopt as a starting</div><div>=C2=A0 =C2=A0 p=
oint for WebTransport 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><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><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 imperative. Please also provide as much</div><div>detail as possible to =
explain your position. Please also respond</div><div>if you support this co=
nsensus - 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 th=
is 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>
</blockquote></div>
</blockquote></div>
</blockquote></div></div>

--000000000000eeceee05bb908149--


From nobody Fri Feb 19 12:49:45 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 468743A150A for <webtransport@ietfa.amsl.com>; Fri, 19 Feb 2021 12:49:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level: 
X-Spam-Status: No, score=-7.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, RCVD_IN_DNSWL_HI=-5, 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 jMDTT-iFM9Y9 for <webtransport@ietfa.amsl.com>; Fri, 19 Feb 2021 12:49:41 -0800 (PST)
Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (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 968503A1509 for <webtransport@ietf.org>; Fri, 19 Feb 2021 12:49:41 -0800 (PST)
Received: by mail-wm1-x333.google.com with SMTP id o15so8090328wmq.5 for <webtransport@ietf.org>; Fri, 19 Feb 2021 12:49:41 -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=ROq3muAIosElgX/i9UKmksh19C/ygo6sr3xJa1Y9GRI=; b=PeWTNMCzY5ODtiPCEw/FE7RtIuPuxPLeS7Q189NePlcDS32cr4LcNnqsFislAu5yUB lTUEPQnk7KJK0l5n/87JtlOJWc3HxnRswQyomss4FjI0WT3i+jipMvZWHU6hl6mwm4O1 NzFiXCJWSrhDilTkSLMBaigyJFg3WW+KW+AY0FRZGz2aHPMB9xMfDs+HqBzukxncwrkH yPNabNw/g2PGXx2TIQBS1o4+gz4T+Be0YSIdUwclLOfSr+pnk7DlJWUztBpx6f8gCZEO wtJY+No4bkKzDdAyIJ/wc7BrRtGnhUXtLXlRUpeirXEq8WOIozMTyaPkVob+kK5LXaUy tl+Q==
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=ROq3muAIosElgX/i9UKmksh19C/ygo6sr3xJa1Y9GRI=; b=UGDCcznFWV1JcKQ5zeIx0s5pvhbqPx/IxXvWf4ykEZlIpCXR2vK51ejBIAgtM4ohzb o3aX4gSlZzgXuEc5+0mjFnADkYww3ZsjkkxMtybr1aBfPqahy8htTlz0SRdTT2aKrWzF qQBFHzJLn3V24x5yuNJvx4DdCKeF0Xf7sWFDm0U0cPe94J+pspKfa9VCkmcCjSHOJ6EC ff6E4+asYwJqBa4+SNhGYr4LXr59/q3KicS4jySiXtMu0kCOxEduQ1yWMl/OmZIHWXF6 R/In8C5c+vfbHeSCvyN2hhN6Pmm2OjxsFnGN0qi6RdyATXsZzeQFQ5YJdVMgDMU8wTIW 2THw==
X-Gm-Message-State: AOAM530wbnR2Yyp9Rw3IkPsos9OjM1fxaDhnDTvTvO1FCDzfulTDgRYb OFE9Y1HMWsASBqCJrnaHSgH8nnrTlANK8aBxGD1CQaWgyzu8Zw==
X-Google-Smtp-Source: ABdhPJyiS6hw/VjpX1EAyLdP5+sEcjrBdUqQi21L8h4Ymm2moZUV8UsewHPvyIhwDRhIGdEx4ukx9hqDcwx6SREpPTI=
X-Received: by 2002:a1c:4386:: with SMTP id q128mr9706777wma.184.1613767779607;  Fri, 19 Feb 2021 12:49:39 -0800 (PST)
MIME-Version: 1.0
From: Luke Curley <kixelated@gmail.com>
Date: Fri, 19 Feb 2021 12:49:28 -0800
Message-ID: <CAHVo=ZmRketpx02KeYPSHSB2gQNvYi6RSs3HrXA1isYTgYorLg@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000040e78c05bbb697fe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/-m9ha6QZXARIk2FbXI_FJ_ui8hg>
Subject: [Webtransport] Http3Transport: Connection-basd Functionality
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, 19 Feb 2021 20:49:43 -0000

--00000000000040e78c05bbb697fe
Content-Type: text/plain; charset="UTF-8"

Hey everybody, I wanted to start the discussion now that Victor's document
has been adopted!

I filed some issues
<https://github.com/ietf-wg-webtrans/draft-ietf-webtrans-http3> earlier on
Github over a few small things. Overall, the draft is clean and it's nice
that we've converged on a single WebTransport protocol. One bigger topic I
wanted to discuss is the ramifications of connection pooling.

Broadly speaking, any QUIC parameters or frames that operate on the
connection as a whole can no longer be exposed to the application.
Specifically: MAX_DATA, MAX_STREAMS, CONNECTION_CLOSE*, connection ID, and
any transport parameters.

The WebTransport specification specifically mentions MAX_STREAMS, as HTTP/3
servers can no longer use this to limit the number of simultaneous
requests. Returning an error code instead of utilizing the built-in flow
control is not a problem, but it's not ideal either.

I believe this is a one-way door in general. Any protocols or applications
built on top of QUIC will no longer be able to use connection-based QUIC
features without breaking WebTransport compatibility. This primarily means
HTTP/3, but it also includes any new protocols that utilize QUIC and desire
browser support.

What does the group think? Is this something worth caring about?

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

<div dir=3D"ltr">Hey everybody, I wanted to start the discussion now that V=
ictor&#39;s document has been adopted!<div><br></div><div>I filed some <a h=
ref=3D"https://github.com/ietf-wg-webtrans/draft-ietf-webtrans-http3" targe=
t=3D"_blank">issues</a>=C2=A0earlier on Github over a few small things. Ove=
rall, the draft is clean and it&#39;s nice that we&#39;ve converged on a si=
ngle WebTransport protocol. One bigger topic I wanted to discuss is the ram=
ifications of connection pooling.</div><div><br></div><div>Broadly speaking=
, any QUIC parameters or frames that operate on the connection as a whole c=
an no longer be exposed to the application. Specifically: MAX_DATA, MAX_STR=
EAMS, CONNECTION_CLOSE*, connection ID, and any transport parameters.</div>=
<div><br></div><div>The WebTransport specification specifically mentions MA=
X_STREAMS, as HTTP/3 servers can no longer use this to limit the number of =
simultaneous requests. Returning an error code instead of utilizing the bui=
lt-in flow control is not a problem, but it&#39;s not ideal either.</div><d=
iv><br></div><div>I believe this is a one-way door in general. Any protocol=
s or applications built on top of QUIC will no longer be able to use connec=
tion-based QUIC features without breaking WebTransport compatibility. This =
primarily means HTTP/3, but it also includes any new protocols that utilize=
 QUIC and desire browser support.</div><div><br></div><div>What does the gr=
oup think? Is this something worth caring about?</div></div>

--00000000000040e78c05bbb697fe--


From nobody Fri Feb 19 13:32:31 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 817853A096C for <webtransport@ietfa.amsl.com>; Fri, 19 Feb 2021 13:32:29 -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 RKIP-rxvTTqf for <webtransport@ietfa.amsl.com>; Fri, 19 Feb 2021 13:32:27 -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 4FA613A0958 for <webtransport@ietf.org>; Fri, 19 Feb 2021 13:32:27 -0800 (PST)
Received: by mail-lj1-x22c.google.com with SMTP id v6so28698575ljh.9 for <webtransport@ietf.org>; Fri, 19 Feb 2021 13:32: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 :cc; bh=B0NDyuyIzGlpwFa0fOuQ3o3tAPuJx1mDxx3Wom5IoUQ=; b=fkIQ9EVNPl8zTs9pRjxnGVMym7C2z3PW+yItZCaJUDLMIZ0G//v0wvb8j+E/XoL6a1 3cqiy/xLVeCOcHxxgeH+aaIf7lqwuhjS6Qp4d/BDx9R5+8Q+lEZHBu7QdXuzmlIb25Pr /QL7mtL6/7OOf6UWlpHaIwKkrIEzSYdx/2DWYqjePv8SPQAi4CoOyAVzK8OFnvo3qlGk HiRuTQj6Rcpavp4vPgjy/Cnxy/0FAyayxVpT0L/K5kfsygpN7kpzbR/FK7wM0qhZMWnS Q4chU9dQx9WK8DiqUHgakO4Y/HOz+vnPqdjMYvvks2v1vTVFuMLlJ9lYmm0xLSznTjgo YgxA==
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=B0NDyuyIzGlpwFa0fOuQ3o3tAPuJx1mDxx3Wom5IoUQ=; b=Jm8zlC2Bq+xtbEg5Kh3+czzsJR67ukinhAkBrrkr68T4JCUY3yR6fKpCck6cIXVroz aEdxWaWMgxcRDePVtbkkitGwBvMWUM+vGniP28Lfle8tJPJRnBmYFY0ILulKFLYzQfqL 4W+0jfMXVrQfXOx5BqEzNBKiQPx1llt5v29Y7dCrylIoiQ/Q3HLL6DJpGz7rPFCgvIuy 33dt8RWglnHsd8IGBqIllm1m4UbCIeMVyCIyMaLSTktjn8IBXDZRrtBrhB3U6LpKybQk cuStQ2wG8Mb69Ioh4edJf0sMCQjhm2pUQaMNpxCpZfwfvP0N1Fb7FpVEzgoX6SlNicU7 mVfA==
X-Gm-Message-State: AOAM531HqmTevF8i183wkKhZRtJGF7T0aYtnQZ30M19egoIGH9+ASwJc UGcv5ZyHhzbAtjviZdy+nG2ejuFJOxR8vza+9X8=
X-Google-Smtp-Source: ABdhPJw58aAHXGc9baTkw76PVOYnb33hVUR0bguGizzTof/ayQ7ncdj9LBp8g4fK3k5M/CF6YlGvQsb/AfqLvpKtdC4=
X-Received: by 2002:a2e:9a52:: with SMTP id k18mr1260425ljj.413.1613770345468;  Fri, 19 Feb 2021 13:32:25 -0800 (PST)
MIME-Version: 1.0
References: <CAHVo=ZmRketpx02KeYPSHSB2gQNvYi6RSs3HrXA1isYTgYorLg@mail.gmail.com>
In-Reply-To: <CAHVo=ZmRketpx02KeYPSHSB2gQNvYi6RSs3HrXA1isYTgYorLg@mail.gmail.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Fri, 19 Feb 2021 13:32:14 -0800
Message-ID: <CAOW+2duU6Xg98Tpec6NbEL5pyxAShp76rPMyZV07Wpmx3pJX2Q@mail.gmail.com>
To: Luke Curley <kixelated@gmail.com>
Cc: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000030d51405bbb73086"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/OXGp_xqSeVCbTcw_26WgUKOoP9k>
Subject: Re: [Webtransport] Http3Transport: Connection-basd Functionality
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, 19 Feb 2021 21:32:30 -0000

--00000000000030d51405bbb73086
Content-Type: text/plain; charset="UTF-8"

Luke --

Thanks for bringing this up!

At the Interim meeting, we talked about having the API provide some control
over pooling (e.g. allowing an appiication to specify that a WebTransport
connection not be pooled), as well as allowing a server to specify that it
doesn't support pooling.

In W3C WebTransport WG we are now in the process of developing PRs to deal
with pooling, and are running into some of the same questions, such as:

1. Under what circumstances can WebTransport connections be pooled, and
what kinds of pooling are allowed?
PR: https://github.com/whatwg/fetch/pull/1171

2.  What are the differences in API behavior between Http3Transport and
quic-transport?
PR: https://github.com/w3c/webtransport/pull/205

3.  For Http3Transport, are there differences in API behavior between
non-sharable connections and sharable ones (e.g. behavior of
webtransport.close())?
Also coming up in PR: https://github.com/w3c/webtransport/pull/205

4. For a non-sharable WebTransport connection, is it possible to obtain
some of the stats that were supported for quic-transport, but would not be
appropriate for a sharable transport?
Issue: https://github.com/w3c/webtransport/issues/206



On Fri, Feb 19, 2021 at 12:49 PM Luke Curley <kixelated@gmail.com> wrote:

> Hey everybody, I wanted to start the discussion now that Victor's document
> has been adopted!
>
> I filed some issues
> <https://github.com/ietf-wg-webtrans/draft-ietf-webtrans-http3> earlier
> on Github over a few small things. Overall, the draft is clean and it's
> nice that we've converged on a single WebTransport protocol. One bigger
> topic I wanted to discuss is the ramifications of connection pooling.
>
> Broadly speaking, any QUIC parameters or frames that operate on the
> connection as a whole can no longer be exposed to the application.
> Specifically: MAX_DATA, MAX_STREAMS, CONNECTION_CLOSE*, connection ID, and
> any transport parameters.
>
> The WebTransport specification specifically mentions MAX_STREAMS, as
> HTTP/3 servers can no longer use this to limit the number of simultaneous
> requests. Returning an error code instead of utilizing the built-in flow
> control is not a problem, but it's not ideal either.
>
> I believe this is a one-way door in general. Any protocols or applications
> built on top of QUIC will no longer be able to use connection-based QUIC
> features without breaking WebTransport compatibility. This primarily means
> HTTP/3, but it also includes any new protocols that utilize QUIC and desire
> browser support.
>
> What does the group think? Is this something worth caring about?
> --
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport
>

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

<div dir=3D"ltr">Luke --<div><br></div><div>Thanks for bringing this up!=C2=
=A0</div><div><br></div><div>At the Interim meeting, we talked about having=
 the API provide some control over pooling (e.g. allowing an appiication to=
 specify that a WebTransport connection not be pooled), as well as allowing=
 a server to specify that it doesn&#39;t support pooling.=C2=A0=C2=A0</div>=
<div><br></div><div>In W3C WebTransport WG we are now in the process of dev=
eloping PRs to deal with pooling, and are running into some of the same que=
stions, such as:=C2=A0</div><div><br></div><div>1. Under what circumstances=
 can WebTransport connections be pooled, and what kinds of pooling are allo=
wed?=C2=A0</div><div>PR: <a href=3D"https://github.com/whatwg/fetch/pull/11=
71">https://github.com/whatwg/fetch/pull/1171</a>=C2=A0</div><div><br></div=
><div>2.=C2=A0 What are the differences in API behavior between Http3Transp=
ort and quic-transport?=C2=A0</div><div>PR:=C2=A0<a href=3D"https://github.=
com/w3c/webtransport/pull/205">https://github.com/w3c/webtransport/pull/205=
</a></div><div><br></div><div>3.=C2=A0 For Http3Transport, are there differ=
ences in API behavior between non-sharable connections and sharable=C2=A0on=
es (e.g. behavior of webtransport.close())?=C2=A0</div><div>Also coming up =
in=C2=A0PR:=C2=A0<a href=3D"https://github.com/w3c/webtransport/pull/205">h=
ttps://github.com/w3c/webtransport/pull/205</a></div><div><br></div><div>4.=
 For a non-sharable WebTransport connection, is it possible to obtain some =
of the stats that were supported for quic-transport, but would not be appro=
priate for a sharable transport?=C2=A0</div><div>Issue:=C2=A0<a href=3D"htt=
ps://github.com/w3c/webtransport/issues/206">https://github.com/w3c/webtran=
sport/issues/206</a><br></div><div><br></div><div><br></div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 19,=
 2021 at 12:49 PM Luke Curley &lt;<a href=3D"mailto:kixelated@gmail.com">ki=
xelated@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);p=
adding-left:1ex"><div dir=3D"ltr">Hey everybody, I wanted to start the disc=
ussion now that Victor&#39;s document has been adopted!<div><br></div><div>=
I filed some <a href=3D"https://github.com/ietf-wg-webtrans/draft-ietf-webt=
rans-http3" target=3D"_blank">issues</a>=C2=A0earlier on Github over a few =
small things. Overall, the draft is clean and it&#39;s nice that we&#39;ve =
converged on a single WebTransport protocol. One bigger topic I wanted to d=
iscuss is the ramifications of connection pooling.</div><div><br></div><div=
>Broadly speaking, any QUIC parameters or frames that operate on the connec=
tion as a whole can no longer be exposed to the application. Specifically: =
MAX_DATA, MAX_STREAMS, CONNECTION_CLOSE*, connection ID, and any transport =
parameters.</div><div><br></div><div>The WebTransport specification specifi=
cally mentions MAX_STREAMS, as HTTP/3 servers can no longer use this to lim=
it the number of simultaneous requests. Returning an error code instead of =
utilizing the built-in flow control is not a problem, but it&#39;s not idea=
l either.</div><div><br></div><div>I believe this is a one-way door in gene=
ral. Any protocols or applications built on top of QUIC will no longer be a=
ble to use connection-based QUIC features without breaking WebTransport com=
patibility. This primarily means HTTP/3, but it also includes any new proto=
cols that utilize QUIC and desire browser support.</div><div><br></div><div=
>What does the group think? Is this something worth caring about?</div></di=
v>
-- <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>

--00000000000030d51405bbb73086--


From nobody Fri Feb 19 13:56:28 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 E86BA3A0B12 for <webtransport@ietfa.amsl.com>; Fri, 19 Feb 2021 13:56:19 -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 X0jdE3LbAa5S for <webtransport@ietfa.amsl.com>; Fri, 19 Feb 2021 13:56:18 -0800 (PST)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (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 BE9DD3A0ADE for <webtransport@ietf.org>; Fri, 19 Feb 2021 13:56:17 -0800 (PST)
Received: by mail-wr1-x42f.google.com with SMTP id v1so10510499wrd.6 for <webtransport@ietf.org>; Fri, 19 Feb 2021 13:56: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=nlqj6QxivBC8pUId2KLhrJRNgXlG45KGjFRj86gPV/I=; b=q10daiR6tKRuyKo9C3iV6b/B+70y50GFX12maJXfks98LU5BqDsZwSgTPgg2Qfp3C7 evpH3epeJGWZDhffPcIdSImChGYoem/Lto6eG1R5xZzBFCTyxVdOHRFuo68jRCDDuIgW 03RJ5BmZIcwrckgShtitUyF++HV2Nt3ORx0r9W4ezTHhd9dz6WF7f3cqJwhDAfMXGkAt Vr9+kEFYTQjITyRW5oGs+Hzntxyiv3+gOrkr8Jy3cOMPi/7Xfx+jRjkIMr5x7wG4md17 70TcK7iQe0a3sL7bInAr5WtcLBSxOnZVBXI4PFS5sHDQHJHiH/g/fHG3CrbrxcPER04v IFIw==
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=nlqj6QxivBC8pUId2KLhrJRNgXlG45KGjFRj86gPV/I=; b=cba2RYuuoUmGBonDZcVOtxrofuZ1ml8PUm3OqKO2mZWhPqUcW4c8pZlGOMx5jjHse4 RRKSP1nRCgWsHEYiH5/ur5StmhAR8Cc2xtTDsv7+PW3t5UnTXwBf1z3rjC7euPbAd/pv isPIDK5okm1LFjuH5VS+WwJC9+dW5PGIBlYk7r3m0iUyZHKNqkpddiqilQ0n5l0PSREu mtwd+70hYWH6hJQYli6tUtcejPQyN+gYRofl4w8JN8bvgcuj30OfSRZX1WmklnbwLrZp 3m7+nknBdWjR2Qbp3Tbwc200R0za+Crj2+0stIDrsECy1OL3WP+utApvCBBCdqJbEYKz wmmg==
X-Gm-Message-State: AOAM530edSoWXLq3zEQcAkOdJp3cLmfZ6kctotm9Cepu8SAMqw8rjnRr mdmQj/roU/O3pXu/EaFzHcHhXRupKRCa/avZ5Oo=
X-Google-Smtp-Source: ABdhPJx2Mjl6E4bsKpNEgBopqBuiHQCQfF2MO+KJTQjz0JBUMe7/2dAhbzvxNVql7zDs9QrOoGogyjJT2xlxZVL1HQ8=
X-Received: by 2002:adf:a31b:: with SMTP id c27mr10631856wrb.188.1613771776103;  Fri, 19 Feb 2021 13:56:16 -0800 (PST)
MIME-Version: 1.0
References: <CAHVo=ZmRketpx02KeYPSHSB2gQNvYi6RSs3HrXA1isYTgYorLg@mail.gmail.com> <CAOW+2duU6Xg98Tpec6NbEL5pyxAShp76rPMyZV07Wpmx3pJX2Q@mail.gmail.com>
In-Reply-To: <CAOW+2duU6Xg98Tpec6NbEL5pyxAShp76rPMyZV07Wpmx3pJX2Q@mail.gmail.com>
From: Luke Curley <kixelated@gmail.com>
Date: Fri, 19 Feb 2021 13:56:05 -0800
Message-ID: <CAHVo=Z=o-oMfWaOUMxjtgaTNVvo28ot5EhinE+uio19-c2S0Gg@mail.gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Cc: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000076c13e05bbb78507"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/7T4t_UgYUcNibItTrcMzqNbvlnU>
Subject: Re: [Webtransport] Http3Transport: Connection-basd Functionality
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, 19 Feb 2021 21:56:26 -0000

--00000000000076c13e05bbb78507
Content-Type: text/plain; charset="UTF-8"

Oh man I just noticed the typo in the email subject... that's embarrassing.

I mentioned this earlier, but I think pooling is a potential future
optimization. The benefit is that pooling can avoid additional TLS
handshakes iff a client has multiple WebTransport or HTTP/3 connections to
the same host (rare?). The cost of pooling is that connection-level QUIC
functionality is no longer available, and must be avoided or worked around.

I liked how QuicTransport was connection oriented and I think something
similar could be done for Http3Transport without precluding pooling support
in the future.

On Fri, Feb 19, 2021 at 1:32 PM Bernard Aboba <bernard.aboba@gmail.com>
wrote:

> Luke --
>
> Thanks for bringing this up!
>
> At the Interim meeting, we talked about having the API provide some
> control over pooling (e.g. allowing an appiication to specify that a
> WebTransport connection not be pooled), as well as allowing a server to
> specify that it doesn't support pooling.
>
> In W3C WebTransport WG we are now in the process of developing PRs to deal
> with pooling, and are running into some of the same questions, such as:
>
> 1. Under what circumstances can WebTransport connections be pooled, and
> what kinds of pooling are allowed?
> PR: https://github.com/whatwg/fetch/pull/1171
>
> 2.  What are the differences in API behavior between Http3Transport and
> quic-transport?
> PR: https://github.com/w3c/webtransport/pull/205
>
> 3.  For Http3Transport, are there differences in API behavior between
> non-sharable connections and sharable ones (e.g. behavior of
> webtransport.close())?
> Also coming up in PR: https://github.com/w3c/webtransport/pull/205
>
> 4. For a non-sharable WebTransport connection, is it possible to obtain
> some of the stats that were supported for quic-transport, but would not be
> appropriate for a sharable transport?
> Issue: https://github.com/w3c/webtransport/issues/206
>
>
>
> On Fri, Feb 19, 2021 at 12:49 PM Luke Curley <kixelated@gmail.com> wrote:
>
>> Hey everybody, I wanted to start the discussion now that Victor's
>> document has been adopted!
>>
>> I filed some issues
>> <https://github.com/ietf-wg-webtrans/draft-ietf-webtrans-http3> earlier
>> on Github over a few small things. Overall, the draft is clean and it's
>> nice that we've converged on a single WebTransport protocol. One bigger
>> topic I wanted to discuss is the ramifications of connection pooling.
>>
>> Broadly speaking, any QUIC parameters or frames that operate on the
>> connection as a whole can no longer be exposed to the application.
>> Specifically: MAX_DATA, MAX_STREAMS, CONNECTION_CLOSE*, connection ID, and
>> any transport parameters.
>>
>> The WebTransport specification specifically mentions MAX_STREAMS, as
>> HTTP/3 servers can no longer use this to limit the number of simultaneous
>> requests. Returning an error code instead of utilizing the built-in flow
>> control is not a problem, but it's not ideal either.
>>
>> I believe this is a one-way door in general. Any protocols or
>> applications built on top of QUIC will no longer be able to use
>> connection-based QUIC features without breaking WebTransport compatibility.
>> This primarily means HTTP/3, but it also includes any new protocols that
>> utilize QUIC and desire browser support.
>>
>> What does the group think? Is this something worth caring about?
>> --
>> Webtransport mailing list
>> Webtransport@ietf.org
>> https://www.ietf.org/mailman/listinfo/webtransport
>>
>

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

<div dir=3D"ltr">Oh man I just noticed the typo in the email subject... tha=
t&#39;s embarrassing.<div><br></div><div>I mentioned this earlier, but I th=
ink pooling is a potential future optimization. The benefit is that pooling=
 can avoid additional TLS handshakes=C2=A0iff a client has multiple WebTran=
sport or HTTP/3 connections to the same host (rare?). The cost of pooling i=
s that connection-level QUIC functionality is no longer available, and must=
 be avoided or worked around.</div><div><br></div><div>I liked how QuicTran=
sport was connection oriented and I think something similar could be done f=
or Http3Transport without precluding pooling support in the future.</div></=
div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On=
 Fri, Feb 19, 2021 at 1:32 PM Bernard Aboba &lt;<a href=3D"mailto:bernard.a=
boba@gmail.com">bernard.aboba@gmail.com</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Luke --<div><br></d=
iv><div>Thanks for bringing this up!=C2=A0</div><div><br></div><div>At the =
Interim meeting, we talked about having the API provide some control over p=
ooling (e.g. allowing an appiication to specify that a WebTransport connect=
ion not be pooled), as well as allowing a server to specify that it doesn&#=
39;t support pooling.=C2=A0=C2=A0</div><div><br></div><div>In W3C WebTransp=
ort WG we are now in the process of developing PRs to deal with pooling, an=
d are running into some of the same questions, such as:=C2=A0</div><div><br=
></div><div>1. Under what circumstances can WebTransport connections be poo=
led, and what kinds of pooling are allowed?=C2=A0</div><div>PR: <a href=3D"=
https://github.com/whatwg/fetch/pull/1171" target=3D"_blank">https://github=
.com/whatwg/fetch/pull/1171</a>=C2=A0</div><div><br></div><div>2.=C2=A0 Wha=
t are the differences in API behavior between Http3Transport and quic-trans=
port?=C2=A0</div><div>PR:=C2=A0<a href=3D"https://github.com/w3c/webtranspo=
rt/pull/205" target=3D"_blank">https://github.com/w3c/webtransport/pull/205=
</a></div><div><br></div><div>3.=C2=A0 For Http3Transport, are there differ=
ences in API behavior between non-sharable connections and sharable=C2=A0on=
es (e.g. behavior of webtransport.close())?=C2=A0</div><div>Also coming up =
in=C2=A0PR:=C2=A0<a href=3D"https://github.com/w3c/webtransport/pull/205" t=
arget=3D"_blank">https://github.com/w3c/webtransport/pull/205</a></div><div=
><br></div><div>4. For a non-sharable WebTransport connection, is it possib=
le to obtain some of the stats that were supported for quic-transport, but =
would not be appropriate for a sharable transport?=C2=A0</div><div>Issue:=
=C2=A0<a href=3D"https://github.com/w3c/webtransport/issues/206" target=3D"=
_blank">https://github.com/w3c/webtransport/issues/206</a><br></div><div><b=
r></div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr=
" class=3D"gmail_attr">On Fri, Feb 19, 2021 at 12:49 PM Luke Curley &lt;<a =
href=3D"mailto:kixelated@gmail.com" target=3D"_blank">kixelated@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">Hey everybody, I wanted to start the discussion now that Vic=
tor&#39;s document has been adopted!<div><br></div><div>I filed some <a hre=
f=3D"https://github.com/ietf-wg-webtrans/draft-ietf-webtrans-http3" target=
=3D"_blank">issues</a>=C2=A0earlier on Github over a few small things. Over=
all, the draft is clean and it&#39;s nice that we&#39;ve converged on a sin=
gle WebTransport protocol. One bigger topic I wanted to discuss is the rami=
fications of connection pooling.</div><div><br></div><div>Broadly speaking,=
 any QUIC parameters or frames that operate on the connection as a whole ca=
n no longer be exposed to the application. Specifically: MAX_DATA, MAX_STRE=
AMS, CONNECTION_CLOSE*, connection ID, and any transport parameters.</div><=
div><br></div><div>The WebTransport specification specifically mentions MAX=
_STREAMS, as HTTP/3 servers can no longer use this to limit the number of s=
imultaneous requests. Returning an error code instead of utilizing the buil=
t-in flow control is not a problem, but it&#39;s not ideal either.</div><di=
v><br></div><div>I believe this is a one-way door in general. Any protocols=
 or applications built on top of QUIC will no longer be able to use connect=
ion-based QUIC features without breaking WebTransport compatibility. This p=
rimarily means HTTP/3, but it also includes any new protocols that utilize =
QUIC and desire browser support.</div><div><br></div><div>What does the gro=
up think? Is this something worth caring about?</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>
</blockquote></div>

--00000000000076c13e05bbb78507--


From nobody Fri Feb 19 14:27:36 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 938C43A0BEB for <webtransport@ietfa.amsl.com>; Fri, 19 Feb 2021 14:27:35 -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 M3dg8vDkCp8F for <webtransport@ietfa.amsl.com>; Fri, 19 Feb 2021 14:27:33 -0800 (PST)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (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 BA2983A0BE9 for <webtransport@ietf.org>; Fri, 19 Feb 2021 14:27:33 -0800 (PST)
Received: by mail-pj1-x102e.google.com with SMTP id fa16so4534965pjb.1 for <webtransport@ietf.org>; Fri, 19 Feb 2021 14:27:33 -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=Qcmvn46+OBDQoqdno7pW63PoPz0kl++/Dit1wJzPvTw=; b=Q4A2TwZ7EBvpk9t9G4P0yb4HWouad8T1UUzSogj7u4spGJxhsxdqtXdkqgL6UNXCem KIuRsdHRxXvVIgw3k0TT8PYBJzFAr/l9NAMaisFS1fYYjwXVtHguFUxhNL0S1kQ227Ts om4nZCVxluI/vAzvxvZfaHZ/CrJ6IlKLNJ/VTqjz3BjWBC178BbUKgCL6yJ0X4xaG0dI mCeZP0TDGyhvYbV9Exy0qSRzoD54/2vE56ZxKaZ6wsSIQcqeeK6w9eP1Z8X5olY+aDme +iqub9oTFEv75oulMWxWjdU85Dm4Ljvo4HRTJVYqzhqs3FeWDinzUy3pzBuY8umW+OCp zY6g==
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=Qcmvn46+OBDQoqdno7pW63PoPz0kl++/Dit1wJzPvTw=; b=hCSTa6PZTLJ8aG6IY+X7G/zjSTwdlMLmolt5N8517unnhwZTrg9mG7/uuVe20cW7YV bBSix3LFzylMFYRdRTHCO5aaV6t+vAplMwHlSQmwFEhbc13Fh42Q+rEPGP/5nz4Z/yYk FroMfy/LMyxQinb8oyM1mCriOLFQncfmvit+sAMzQ4D6Uwl3ZP+Fd2cygbSo4cimWn9W D8ecs38cMF+Znw4PYTdXL1oThnUoVHHD6rnfIAz4NcbZ9+/Pr5H2mIyCeLwnu6wjtLIR Cclqn7sQ1MNyKs578m4fAGhWQ9fQ9zhQrxYgJ0LVtRVQSpNq5EtIyS799HDhuI1NUYom w2kQ==
X-Gm-Message-State: AOAM533UQx5NEY6jKXYQ2Lso5jVkAYb0cp53JNXDrUtvIAf2DjFeMugT R9PNtvMEY7liKMRQboYZhpScVLFVwj3/HyJm45Hkt2R/
X-Google-Smtp-Source: ABdhPJxGvBNyf+QAQDA/jQkrEKC18fCvQFLA+1nsUrMg2DHzgh8px9cIo8sdbogZLAQ8iMMF/ApteONvhr7d8YanVmo=
X-Received: by 2002:a17:902:7b89:b029:e1:1b46:bcec with SMTP id w9-20020a1709027b89b02900e11b46bcecmr11083041pll.5.1613773653045; Fri, 19 Feb 2021 14:27:33 -0800 (PST)
MIME-Version: 1.0
References: <CAHVo=ZmRketpx02KeYPSHSB2gQNvYi6RSs3HrXA1isYTgYorLg@mail.gmail.com> <CAOW+2duU6Xg98Tpec6NbEL5pyxAShp76rPMyZV07Wpmx3pJX2Q@mail.gmail.com> <CAHVo=Z=o-oMfWaOUMxjtgaTNVvo28ot5EhinE+uio19-c2S0Gg@mail.gmail.com>
In-Reply-To: <CAHVo=Z=o-oMfWaOUMxjtgaTNVvo28ot5EhinE+uio19-c2S0Gg@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Fri, 19 Feb 2021 14:27:21 -0800
Message-ID: <CAPDSy+6tWTWyL6KHZTGJ3z3L6ZGJmTrVyiPiq0zRo-SGUb39tg@mail.gmail.com>
To: Luke Curley <kixelated@gmail.com>
Cc: Bernard Aboba <bernard.aboba@gmail.com>, WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000056793f05bbb7f521"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/EgFNJi5VW7L_itFAAU9Dth4sGPQ>
Subject: Re: [Webtransport] Http3Transport: Connection-basd Functionality
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, 19 Feb 2021 22:27:36 -0000

--00000000000056793f05bbb7f521
Content-Type: text/plain; charset="UTF-8"

Hi Luke,

Can you elaborate on what benefits you see in exposing
QUIC-connection-level information to a WebTransport application?
In particular, which information would benefit WebTransport applications?
Because for example I don't see how knowing the connection ID or transport
parameters would be useful, but I could just be missing something.

David

On Fri, Feb 19, 2021 at 1:56 PM Luke Curley <kixelated@gmail.com> wrote:

> Oh man I just noticed the typo in the email subject... that's embarrassing.
>
> I mentioned this earlier, but I think pooling is a potential future
> optimization. The benefit is that pooling can avoid additional TLS
> handshakes iff a client has multiple WebTransport or HTTP/3 connections to
> the same host (rare?). The cost of pooling is that connection-level QUIC
> functionality is no longer available, and must be avoided or worked around.
>
> I liked how QuicTransport was connection oriented and I think something
> similar could be done for Http3Transport without precluding pooling support
> in the future.
>
> On Fri, Feb 19, 2021 at 1:32 PM Bernard Aboba <bernard.aboba@gmail.com>
> wrote:
>
>> Luke --
>>
>> Thanks for bringing this up!
>>
>> At the Interim meeting, we talked about having the API provide some
>> control over pooling (e.g. allowing an appiication to specify that a
>> WebTransport connection not be pooled), as well as allowing a server to
>> specify that it doesn't support pooling.
>>
>> In W3C WebTransport WG we are now in the process of developing PRs to
>> deal with pooling, and are running into some of the same questions, such
>> as:
>>
>> 1. Under what circumstances can WebTransport connections be pooled, and
>> what kinds of pooling are allowed?
>> PR: https://github.com/whatwg/fetch/pull/1171
>>
>> 2.  What are the differences in API behavior between Http3Transport and
>> quic-transport?
>> PR: https://github.com/w3c/webtransport/pull/205
>>
>> 3.  For Http3Transport, are there differences in API behavior between
>> non-sharable connections and sharable ones (e.g. behavior of
>> webtransport.close())?
>> Also coming up in PR: https://github.com/w3c/webtransport/pull/205
>>
>> 4. For a non-sharable WebTransport connection, is it possible to obtain
>> some of the stats that were supported for quic-transport, but would not be
>> appropriate for a sharable transport?
>> Issue: https://github.com/w3c/webtransport/issues/206
>>
>>
>>
>> On Fri, Feb 19, 2021 at 12:49 PM Luke Curley <kixelated@gmail.com> wrote:
>>
>>> Hey everybody, I wanted to start the discussion now that Victor's
>>> document has been adopted!
>>>
>>> I filed some issues
>>> <https://github.com/ietf-wg-webtrans/draft-ietf-webtrans-http3> earlier
>>> on Github over a few small things. Overall, the draft is clean and it's
>>> nice that we've converged on a single WebTransport protocol. One bigger
>>> topic I wanted to discuss is the ramifications of connection pooling.
>>>
>>> Broadly speaking, any QUIC parameters or frames that operate on the
>>> connection as a whole can no longer be exposed to the application.
>>> Specifically: MAX_DATA, MAX_STREAMS, CONNECTION_CLOSE*, connection ID, and
>>> any transport parameters.
>>>
>>> The WebTransport specification specifically mentions MAX_STREAMS, as
>>> HTTP/3 servers can no longer use this to limit the number of simultaneous
>>> requests. Returning an error code instead of utilizing the built-in flow
>>> control is not a problem, but it's not ideal either.
>>>
>>> I believe this is a one-way door in general. Any protocols or
>>> applications built on top of QUIC will no longer be able to use
>>> connection-based QUIC features without breaking WebTransport compatibility.
>>> This primarily means HTTP/3, but it also includes any new protocols that
>>> utilize QUIC and desire browser support.
>>>
>>> What does the group think? Is this something worth caring about?
>>> --
>>> 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
>

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

<div dir=3D"ltr">Hi Luke,<div><br></div><div>Can you elaborate on what bene=
fits you see in exposing QUIC-connection-level information to a WebTranspor=
t application?</div><div>In particular, which information would benefit Web=
Transport applications? Because for example I don&#39;t see how knowing the=
 connection ID or transport parameters would be useful,=C2=A0but I could ju=
st be missing something.</div><div><br></div><div>David</div></div><br><div=
 class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 19=
, 2021 at 1:56 PM Luke Curley &lt;<a href=3D"mailto:kixelated@gmail.com">ki=
xelated@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);p=
adding-left:1ex"><div dir=3D"ltr">Oh man I just noticed the typo in the ema=
il subject... that&#39;s embarrassing.<div><br></div><div>I mentioned this =
earlier, but I think pooling is a potential future optimization. The benefi=
t is that pooling can avoid additional TLS handshakes=C2=A0iff a client has=
 multiple WebTransport or HTTP/3 connections to the same host (rare?). The =
cost of pooling is that connection-level QUIC functionality is no longer av=
ailable, and must be avoided or worked around.</div><div><br></div><div>I l=
iked how QuicTransport was connection oriented and I think something simila=
r could be done for Http3Transport without precluding pooling support in th=
e future.</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Fri, Feb 19, 2021 at 1:32 PM Bernard Aboba &lt;<a href=
=3D"mailto:bernard.aboba@gmail.com" target=3D"_blank">bernard.aboba@gmail.c=
om</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
"><div dir=3D"ltr">Luke --<div><br></div><div>Thanks for bringing this up!=
=C2=A0</div><div><br></div><div>At the Interim meeting, we talked about hav=
ing the API provide some control over pooling (e.g. allowing an appiication=
 to specify that a WebTransport connection not be pooled), as well as allow=
ing a server to specify that it doesn&#39;t support pooling.=C2=A0=C2=A0</d=
iv><div><br></div><div>In W3C WebTransport WG we are now in the process of =
developing PRs to deal with pooling, and are running into some of the same =
questions, such as:=C2=A0</div><div><br></div><div>1. Under what circumstan=
ces can WebTransport connections be pooled, and what kinds of pooling are a=
llowed?=C2=A0</div><div>PR: <a href=3D"https://github.com/whatwg/fetch/pull=
/1171" target=3D"_blank">https://github.com/whatwg/fetch/pull/1171</a>=C2=
=A0</div><div><br></div><div>2.=C2=A0 What are the differences in API behav=
ior between Http3Transport and quic-transport?=C2=A0</div><div>PR:=C2=A0<a =
href=3D"https://github.com/w3c/webtransport/pull/205" target=3D"_blank">htt=
ps://github.com/w3c/webtransport/pull/205</a></div><div><br></div><div>3.=
=C2=A0 For Http3Transport, are there differences in API behavior between no=
n-sharable connections and sharable=C2=A0ones (e.g. behavior of webtranspor=
t.close())?=C2=A0</div><div>Also coming up in=C2=A0PR:=C2=A0<a href=3D"http=
s://github.com/w3c/webtransport/pull/205" target=3D"_blank">https://github.=
com/w3c/webtransport/pull/205</a></div><div><br></div><div>4. For a non-sha=
rable WebTransport connection, is it possible to obtain some of the stats t=
hat were supported for quic-transport, but would not be appropriate for a s=
harable transport?=C2=A0</div><div>Issue:=C2=A0<a href=3D"https://github.co=
m/w3c/webtransport/issues/206" target=3D"_blank">https://github.com/w3c/web=
transport/issues/206</a><br></div><div><br></div><div><br></div></div><br><=
div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb=
 19, 2021 at 12:49 PM Luke Curley &lt;<a href=3D"mailto:kixelated@gmail.com=
" target=3D"_blank">kixelated@gmail.com</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hey everybody, I wa=
nted to start the discussion now that Victor&#39;s document has been adopte=
d!<div><br></div><div>I filed some <a href=3D"https://github.com/ietf-wg-we=
btrans/draft-ietf-webtrans-http3" target=3D"_blank">issues</a>=C2=A0earlier=
 on Github over a few small things. Overall, the draft is clean and it&#39;=
s nice that we&#39;ve converged on a single WebTransport protocol. One bigg=
er topic I wanted to discuss is the ramifications of connection pooling.</d=
iv><div><br></div><div>Broadly speaking, any QUIC parameters or frames that=
 operate on the connection as a whole can no longer be exposed to the appli=
cation. Specifically: MAX_DATA, MAX_STREAMS, CONNECTION_CLOSE*, connection =
ID, and any transport parameters.</div><div><br></div><div>The WebTransport=
 specification specifically mentions MAX_STREAMS, as HTTP/3 servers can no =
longer use this to limit the number of simultaneous requests. Returning an =
error code instead of utilizing the built-in flow control is not a problem,=
 but it&#39;s not ideal either.</div><div><br></div><div>I believe this is =
a one-way door in general. Any protocols or applications built on top of QU=
IC will no longer be able to use connection-based QUIC features without bre=
aking WebTransport compatibility. This primarily means HTTP/3, but it also =
includes any new protocols that utilize QUIC and desire browser support.</d=
iv><div><br></div><div>What does the group think? Is this something worth c=
aring about?</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>
</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>

--00000000000056793f05bbb7f521--


From nobody Fri Feb 19 14:59:27 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 5F4043A0D9D for <webtransport@ietfa.amsl.com>; Fri, 19 Feb 2021 14:59:22 -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, 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 8PGJsxImJD33 for <webtransport@ietfa.amsl.com>; Fri, 19 Feb 2021 14:59:20 -0800 (PST)
Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (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 AA6843A0D48 for <webtransport@ietf.org>; Fri, 19 Feb 2021 14:59:19 -0800 (PST)
Received: by mail-wr1-x42c.google.com with SMTP id h98so5889680wrh.11 for <webtransport@ietf.org>; Fri, 19 Feb 2021 14:59:19 -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=Sbbh+Qm5qvbbOD9w3zO4yFB1xKxWpfpm5LZFr2IEMPk=; b=gI9rxdVBG4ZVyhq9KutfSpAAoaH+BL5E1dqUyiSEGrJbO6v9sH2XN/QH3c1g3pMKP2 hlVyj3m6m/7nhSpChFUy3ZZ0gZ5E1Y4zAXKjjnAuLPJs0+vqgQY3RMliy7nz4ENymwsW mA7mlcUE/HrEUO5219B98jZYc+L2WNFNLkP65KkChPpY+i/bFRnvdJCJBvxv2XpdJMbB n6mTv8tJkYdfDOAuUrrbNw8GiWnQ6rhXBywK1PlVMmQH+rE8k8Rsxr38TCxzupRORmf5 aoZcLwkY7Zl/dsIxHDmAAH6Nu9vlFYF8gKG1p/WZ+1fiG5iyNh6Z6EkUA8RNUHVxIAKT iBfA==
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=Sbbh+Qm5qvbbOD9w3zO4yFB1xKxWpfpm5LZFr2IEMPk=; b=VDUzq/LxaapWM5DwncC3C6dRuekEwyrmPc1tFR60yL4uEymmEWK3UV7962VMFvy9GJ Zjj4zH24fMTh0AcL4/UOAae3WY/A08ZEiD582GGUW3AuVFZw3Lgjnr/mMEuNfwdsRSoL QHgd7AMWMEdYZvdHccvUWRX/fmogykQpn+6KslQLAp+OYYKUUFmHaWQAgjuNJZS3MMuK C74zrnaWixU41x5A2fIto880q7HfWWlbgnsJ9NhUHVPkwQgjQCJIQfeHzoOdZfRY0QdI PT4v18bFyBfcuLQt5OfjCfWhnF3nmvRLK1zIQUB7oeAo1RcGhIcLMkXK+s/ntbqenHjM FbUg==
X-Gm-Message-State: AOAM5320Zs0ECW0mFzyDyri4VwbDbOnildI7nr4J5/HUttlht8w70IgF jtHp2MmuVboVwYaSo7TVyQvlEDC9lOvV0hHHOZg=
X-Google-Smtp-Source: ABdhPJxW01aXAHe94Zle7IpGWwn0cesOzDgZvGcXroYmFIqZVSyFwUMH1P+1iK7u+33OaUnb/WLmJD+yNeCBegoXFO0=
X-Received: by 2002:adf:f5ce:: with SMTP id k14mr8016942wrp.194.1613775557925;  Fri, 19 Feb 2021 14:59:17 -0800 (PST)
MIME-Version: 1.0
References: <CAHVo=ZmRketpx02KeYPSHSB2gQNvYi6RSs3HrXA1isYTgYorLg@mail.gmail.com> <CAOW+2duU6Xg98Tpec6NbEL5pyxAShp76rPMyZV07Wpmx3pJX2Q@mail.gmail.com> <CAHVo=Z=o-oMfWaOUMxjtgaTNVvo28ot5EhinE+uio19-c2S0Gg@mail.gmail.com> <CAPDSy+6tWTWyL6KHZTGJ3z3L6ZGJmTrVyiPiq0zRo-SGUb39tg@mail.gmail.com>
In-Reply-To: <CAPDSy+6tWTWyL6KHZTGJ3z3L6ZGJmTrVyiPiq0zRo-SGUb39tg@mail.gmail.com>
From: Luke Curley <kixelated@gmail.com>
Date: Fri, 19 Feb 2021 14:59:07 -0800
Message-ID: <CAHVo=Z=gsLRuFFuYiXo73HwPiThgGH5n_scw7Bn8aNrAjQ2Dig@mail.gmail.com>
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: Bernard Aboba <bernard.aboba@gmail.com>, WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e09e8705bbb866bc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/ST2cKWGZnGbUhxX-ORm8Tr-okfc>
Subject: Re: [Webtransport] Http3Transport: Connection-basd Functionality
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, 19 Feb 2021 22:59:26 -0000

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

Good examples, because HTTP/3 is currently the only QUIC application and it
doesn't utilize both of those. But QUIC doesn't prohibit an
application/protocol from utilizing the connection ID or TLS extensions. It
could be useful for some future purpose, like the client using a
pre-arranged connection ID (encoded with routing info?) or new TLS
extensions/parameters (remove a round trip for a handshake?).

WebTransport does prohibit using these connection-level functionalities for
the sake of pooling. None of this is critical functionality, but it might
hamper future efforts which is why I wanted to bring up the one-way door.

It's on my mind because I'm designing a video protocol over QUIC. It would
be nice if I could use MAX_STREAMS, MAX_DATA, etc, but as it stands now,
I'll need to implement my own flow control mechanisms for WebTransport
(browser) support.

On Fri, Feb 19, 2021 at 2:27 PM David Schinazi <dschinazi.ietf@gmail.com>
wrote:

> Hi Luke,
>
> Can you elaborate on what benefits you see in exposing
> QUIC-connection-level information to a WebTransport application?
> In particular, which information would benefit WebTransport applications?
> Because for example I don't see how knowing the connection ID or transport
> parameters would be useful, but I could just be missing something.
>
> David
>
> On Fri, Feb 19, 2021 at 1:56 PM Luke Curley <kixelated@gmail.com> wrote:
>
>> Oh man I just noticed the typo in the email subject... that's
>> embarrassing.
>>
>> I mentioned this earlier, but I think pooling is a potential future
>> optimization. The benefit is that pooling can avoid additional TLS
>> handshakes iff a client has multiple WebTransport or HTTP/3 connections to
>> the same host (rare?). The cost of pooling is that connection-level QUIC
>> functionality is no longer available, and must be avoided or worked around.
>>
>> I liked how QuicTransport was connection oriented and I think something
>> similar could be done for Http3Transport without precluding pooling support
>> in the future.
>>
>> On Fri, Feb 19, 2021 at 1:32 PM Bernard Aboba <bernard.aboba@gmail.com>
>> wrote:
>>
>>> Luke --
>>>
>>> Thanks for bringing this up!
>>>
>>> At the Interim meeting, we talked about having the API provide some
>>> control over pooling (e.g. allowing an appiication to specify that a
>>> WebTransport connection not be pooled), as well as allowing a server to
>>> specify that it doesn't support pooling.
>>>
>>> In W3C WebTransport WG we are now in the process of developing PRs to
>>> deal with pooling, and are running into some of the same questions, such
>>> as:
>>>
>>> 1. Under what circumstances can WebTransport connections be pooled, and
>>> what kinds of pooling are allowed?
>>> PR: https://github.com/whatwg/fetch/pull/1171
>>>
>>> 2.  What are the differences in API behavior between Http3Transport and
>>> quic-transport?
>>> PR: https://github.com/w3c/webtransport/pull/205
>>>
>>> 3.  For Http3Transport, are there differences in API behavior between
>>> non-sharable connections and sharable ones (e.g. behavior of
>>> webtransport.close())?
>>> Also coming up in PR: https://github.com/w3c/webtransport/pull/205
>>>
>>> 4. For a non-sharable WebTransport connection, is it possible to obtain
>>> some of the stats that were supported for quic-transport, but would not be
>>> appropriate for a sharable transport?
>>> Issue: https://github.com/w3c/webtransport/issues/206
>>>
>>>
>>>
>>> On Fri, Feb 19, 2021 at 12:49 PM Luke Curley <kixelated@gmail.com>
>>> wrote:
>>>
>>>> Hey everybody, I wanted to start the discussion now that Victor's
>>>> document has been adopted!
>>>>
>>>> I filed some issues
>>>> <https://github.com/ietf-wg-webtrans/draft-ietf-webtrans-http3> earlier
>>>> on Github over a few small things. Overall, the draft is clean and it's
>>>> nice that we've converged on a single WebTransport protocol. One bigger
>>>> topic I wanted to discuss is the ramifications of connection pooling.
>>>>
>>>> Broadly speaking, any QUIC parameters or frames that operate on the
>>>> connection as a whole can no longer be exposed to the application.
>>>> Specifically: MAX_DATA, MAX_STREAMS, CONNECTION_CLOSE*, connection ID, and
>>>> any transport parameters.
>>>>
>>>> The WebTransport specification specifically mentions MAX_STREAMS, as
>>>> HTTP/3 servers can no longer use this to limit the number of simultaneous
>>>> requests. Returning an error code instead of utilizing the built-in flow
>>>> control is not a problem, but it's not ideal either.
>>>>
>>>> I believe this is a one-way door in general. Any protocols or
>>>> applications built on top of QUIC will no longer be able to use
>>>> connection-based QUIC features without breaking WebTransport compatibility.
>>>> This primarily means HTTP/3, but it also includes any new protocols that
>>>> utilize QUIC and desire browser support.
>>>>
>>>> What does the group think? Is this something worth caring about?
>>>> --
>>>> 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
>>
>

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

<div dir=3D"ltr"><div>Good examples, because HTTP/3 is currently the only Q=
UIC application and it doesn&#39;t utilize both of those. But QUIC doesn&#3=
9;t prohibit an application/protocol from utilizing the connection ID or TL=
S extensions. It could be useful for some future purpose, like the client u=
sing a pre-arranged connection ID (encoded with routing info?) or new TLS e=
xtensions/parameters (remove a round trip for a handshake?).</div><div><br>=
</div><div>WebTransport does prohibit using these connection-level function=
alities for the sake of pooling. None of this is critical functionality, bu=
t it might hamper future efforts which is why I wanted to bring up the one-=
way door.</div><div><br></div><div>It&#39;s on my mind because I&#39;m desi=
gning a video protocol over QUIC. It would be nice if I could use MAX_STREA=
MS, MAX_DATA, etc, but as it stands now, I&#39;ll need to implement my own =
flow control mechanisms for WebTransport (browser) support.</div></div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Fe=
b 19, 2021 at 2:27 PM David Schinazi &lt;<a href=3D"mailto:dschinazi.ietf@g=
mail.com">dschinazi.ietf@gmail.com</a>&gt; wrote:<br></div><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"><div dir=3D"ltr">Hi Luke,<div><br></div><=
div>Can you elaborate on what benefits you see in exposing QUIC-connection-=
level information to a WebTransport application?</div><div>In particular, w=
hich information would benefit WebTransport applications? Because for examp=
le I don&#39;t see how knowing the connection ID or transport parameters wo=
uld be useful,=C2=A0but I could just be missing something.</div><div><br></=
div><div>David</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c=
lass=3D"gmail_attr">On Fri, Feb 19, 2021 at 1:56 PM Luke Curley &lt;<a href=
=3D"mailto:kixelated@gmail.com" target=3D"_blank">kixelated@gmail.com</a>&g=
t; wrote:<br></div><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 d=
ir=3D"ltr">Oh man I just noticed the typo in the email subject... that&#39;=
s embarrassing.<div><br></div><div>I mentioned this earlier, but I think po=
oling is a potential future optimization. The benefit is that pooling can a=
void additional TLS handshakes=C2=A0iff a client has multiple WebTransport =
or HTTP/3 connections to the same host (rare?). The cost of pooling is that=
 connection-level QUIC functionality is no longer available, and must be av=
oided or worked around.</div><div><br></div><div>I liked how QuicTransport =
was connection oriented and I think something similar could be done for Htt=
p3Transport without precluding pooling support in the future.</div></div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, =
Feb 19, 2021 at 1:32 PM Bernard Aboba &lt;<a href=3D"mailto:bernard.aboba@g=
mail.com" target=3D"_blank">bernard.aboba@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">Luke --=
<div><br></div><div>Thanks for bringing this up!=C2=A0</div><div><br></div>=
<div>At the Interim meeting, we talked about having the API provide some co=
ntrol over pooling (e.g. allowing an appiication to specify that a WebTrans=
port connection not be pooled), as well as allowing a server to specify tha=
t it doesn&#39;t support pooling.=C2=A0=C2=A0</div><div><br></div><div>In W=
3C WebTransport WG we are now in the process of developing PRs to deal with=
 pooling, and are running into some of the same questions, such as:=C2=A0</=
div><div><br></div><div>1. Under what circumstances can WebTransport connec=
tions be pooled, and what kinds of pooling are allowed?=C2=A0</div><div>PR:=
 <a href=3D"https://github.com/whatwg/fetch/pull/1171" target=3D"_blank">ht=
tps://github.com/whatwg/fetch/pull/1171</a>=C2=A0</div><div><br></div><div>=
2.=C2=A0 What are the differences in API behavior between Http3Transport an=
d quic-transport?=C2=A0</div><div>PR:=C2=A0<a href=3D"https://github.com/w3=
c/webtransport/pull/205" target=3D"_blank">https://github.com/w3c/webtransp=
ort/pull/205</a></div><div><br></div><div>3.=C2=A0 For Http3Transport, are =
there differences in API behavior between non-sharable connections and shar=
able=C2=A0ones (e.g. behavior of webtransport.close())?=C2=A0</div><div>Als=
o coming up in=C2=A0PR:=C2=A0<a href=3D"https://github.com/w3c/webtransport=
/pull/205" target=3D"_blank">https://github.com/w3c/webtransport/pull/205</=
a></div><div><br></div><div>4. For a non-sharable WebTransport connection, =
is it possible to obtain some of the stats that were supported for quic-tra=
nsport, but would not be appropriate for a sharable transport?=C2=A0</div><=
div>Issue:=C2=A0<a href=3D"https://github.com/w3c/webtransport/issues/206" =
target=3D"_blank">https://github.com/w3c/webtransport/issues/206</a><br></d=
iv><div><br></div><div><br></div></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 19, 2021 at 12:49 PM Luke Curl=
ey &lt;<a href=3D"mailto:kixelated@gmail.com" target=3D"_blank">kixelated@g=
mail.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-le=
ft:1ex"><div dir=3D"ltr">Hey everybody, I wanted to start the discussion no=
w that Victor&#39;s document has been adopted!<div><br></div><div>I filed s=
ome <a href=3D"https://github.com/ietf-wg-webtrans/draft-ietf-webtrans-http=
3" target=3D"_blank">issues</a>=C2=A0earlier on Github over a few small thi=
ngs. Overall, the draft is clean and it&#39;s nice that we&#39;ve converged=
 on a single WebTransport protocol. One bigger topic I wanted to discuss is=
 the ramifications of connection pooling.</div><div><br></div><div>Broadly =
speaking, any QUIC parameters or frames that operate on the connection as a=
 whole can no longer be exposed to the application. Specifically: MAX_DATA,=
 MAX_STREAMS, CONNECTION_CLOSE*, connection ID, and any transport parameter=
s.</div><div><br></div><div>The WebTransport specification specifically men=
tions MAX_STREAMS, as HTTP/3 servers can no longer use this to limit the nu=
mber of simultaneous requests. Returning an error code instead of utilizing=
 the built-in flow control is not a problem, but it&#39;s not ideal either.=
</div><div><br></div><div>I believe this is a one-way door in general. Any =
protocols or applications built on top of QUIC will no longer be able to us=
e connection-based QUIC features without breaking WebTransport compatibilit=
y. This primarily means HTTP/3, but it also includes any new protocols that=
 utilize QUIC and desire browser support.</div><div><br></div><div>What doe=
s the group think? Is this something worth caring about?</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>
</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>
</blockquote></div>

--000000000000e09e8705bbb866bc--


From nobody Fri Feb 19 16:12:00 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 7C0823A091B for <webtransport@ietfa.amsl.com>; Fri, 19 Feb 2021 16:11:58 -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, RCVD_IN_DNSWL_BLOCKED=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 8U6JmzhHw0Fx for <webtransport@ietfa.amsl.com>; Fri, 19 Feb 2021 16:11:55 -0800 (PST)
Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) (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 A0D6F3A091C for <webtransport@ietf.org>; Fri, 19 Feb 2021 16:11:55 -0800 (PST)
Received: by mail-pl1-x62c.google.com with SMTP id z7so4250688plk.7 for <webtransport@ietf.org>; Fri, 19 Feb 2021 16:11:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=U97XYN8kr/Eu5J6Qeax02suefjGhKQI26UFHEnNfiRA=; b=Ompyzp2z8n+j2zIS9q1YV2TpJEXa1f4pCDqO+nEFOXYKm5HzreWEyaFZGaqNtsYKvN OcNXK5djTvIvbmCIeijXR7yu31CiwlBJmJP+wgrrAZGG5hv7fFhy7i1pZDwoU4WS3cRQ krGmUAsqDNSq10WVWeusenQe9ojcuDP7ESAoB49l4sa1WjrPYZfb3VrA02sEPvt6c++9 Yo0Alc7zzvWgxmpqwq6X96hqkL0ayaQoRbR+y18lLn/+W2wyJ9yDSoOu3l+wki5VVL7U swkvpNDYNxl7JPo99g4zgUXNSe9AnCEhZEQjHnkTn10G7GyOXvuh9TpcNTu9CEDzzT7f Y4Aw==
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=U97XYN8kr/Eu5J6Qeax02suefjGhKQI26UFHEnNfiRA=; b=Ja9B8EGPpiZbmOyzt4jQQal/bGDlYgq18FwlIV1hAGez1B3jLMEDGGJA2W1MfjWNo5 5y8WcE/2PsB7O9ltXLZWBo0W7VTj74NQYQ/fWHhrMeftLI0uzxrwJkBXCdKjf1BJafe5 m534SWcip9r0a6n3EY6KOVABAnpw5kAUAROiqBHOEklNOzl+eN5VGrJyN1W27mKcmAHu TZgX027gMj6hjgp9JfoPeczGVlvEJJmhGPqd09YgOGJqLhaPqwaPQAPIEircLhbo9idm GOGRUd5M4aJhrkXE8HEHwqGC7t2Wozkvg1OffW3AKZq3Vs9iuqqbzBuvW+lVUDt1fBSr UpvA==
X-Gm-Message-State: AOAM531jDnVelLFzH51Z+QO3bSErezveHZmaaOm9DIiPatB5EyzefwIw VqXJi86ICpe9cc6cLOHK4w0XjKsPC0cFzp3TgjIjfO5w
X-Google-Smtp-Source: ABdhPJxKskzo73etDSZPnh+rlEF020HTbTXm3M8ECXwFCfL7B3BfgcScSU4Au6YVSCTRMnKFR8STIDFVIlPvCzt6LFM=
X-Received: by 2002:a17:902:ce83:b029:de:6b3c:fcd2 with SMTP id f3-20020a170902ce83b02900de6b3cfcd2mr11212040plg.67.1613779913592; Fri, 19 Feb 2021 16:11:53 -0800 (PST)
MIME-Version: 1.0
References: <CAHVo=ZmRketpx02KeYPSHSB2gQNvYi6RSs3HrXA1isYTgYorLg@mail.gmail.com> <CAOW+2duU6Xg98Tpec6NbEL5pyxAShp76rPMyZV07Wpmx3pJX2Q@mail.gmail.com> <CAHVo=Z=o-oMfWaOUMxjtgaTNVvo28ot5EhinE+uio19-c2S0Gg@mail.gmail.com> <CAPDSy+6tWTWyL6KHZTGJ3z3L6ZGJmTrVyiPiq0zRo-SGUb39tg@mail.gmail.com> <CAHVo=Z=gsLRuFFuYiXo73HwPiThgGH5n_scw7Bn8aNrAjQ2Dig@mail.gmail.com>
In-Reply-To: <CAHVo=Z=gsLRuFFuYiXo73HwPiThgGH5n_scw7Bn8aNrAjQ2Dig@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Fri, 19 Feb 2021 16:11:42 -0800
Message-ID: <CAPDSy+6LT9dMS6RofRzdqL6R5VFDRfv21qV+Xd9jx22w2yyuZA@mail.gmail.com>
To: Luke Curley <kixelated@gmail.com>
Cc: Bernard Aboba <bernard.aboba@gmail.com>, WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007ed4d005bbb96a37"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/W_wEM9-qHAIVO2BUeUpujatrq6w>
Subject: Re: [Webtransport] Http3Transport: Connection-basd Functionality
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: Sat, 20 Feb 2021 00:11:58 -0000

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

Thanks!

WebTransport is intentionally designed to be limited because we don't want
to expose too much to JavaScript.
Similarly, when JavaScript is using WebSocket, we don't let it access TLS
extensions or TCP flow control information, as doing that could cause
security issues.

To your MAX_STREAMS/MAX_DATA example, I think there's value in having
WebTransport-specific flow control, but I don't think that should rely on
the underlying transport and connection, we can easily build that inside
WebTransport itself.
In other words, if there are QUIC-connection-level features that we think
might benefit WebTransport applications, we should analyze their security
implications and add those specifically to WebTransport instead of giving
JavaScript blanket control over connection properties.

David

On Fri, Feb 19, 2021 at 2:59 PM Luke Curley <kixelated@gmail.com> wrote:

> Good examples, because HTTP/3 is currently the only QUIC application and
> it doesn't utilize both of those. But QUIC doesn't prohibit an
> application/protocol from utilizing the connection ID or TLS extensions. It
> could be useful for some future purpose, like the client using a
> pre-arranged connection ID (encoded with routing info?) or new TLS
> extensions/parameters (remove a round trip for a handshake?).
>
> WebTransport does prohibit using these connection-level functionalities
> for the sake of pooling. None of this is critical functionality, but it
> might hamper future efforts which is why I wanted to bring up the one-way
> door.
>
> It's on my mind because I'm designing a video protocol over QUIC. It would
> be nice if I could use MAX_STREAMS, MAX_DATA, etc, but as it stands now,
> I'll need to implement my own flow control mechanisms for WebTransport
> (browser) support.
>
> On Fri, Feb 19, 2021 at 2:27 PM David Schinazi <dschinazi.ietf@gmail.com>
> wrote:
>
>> Hi Luke,
>>
>> Can you elaborate on what benefits you see in exposing
>> QUIC-connection-level information to a WebTransport application?
>> In particular, which information would benefit WebTransport applications?
>> Because for example I don't see how knowing the connection ID or transport
>> parameters would be useful, but I could just be missing something.
>>
>> David
>>
>> On Fri, Feb 19, 2021 at 1:56 PM Luke Curley <kixelated@gmail.com> wrote:
>>
>>> Oh man I just noticed the typo in the email subject... that's
>>> embarrassing.
>>>
>>> I mentioned this earlier, but I think pooling is a potential future
>>> optimization. The benefit is that pooling can avoid additional TLS
>>> handshakes iff a client has multiple WebTransport or HTTP/3 connections to
>>> the same host (rare?). The cost of pooling is that connection-level QUIC
>>> functionality is no longer available, and must be avoided or worked around.
>>>
>>> I liked how QuicTransport was connection oriented and I think something
>>> similar could be done for Http3Transport without precluding pooling support
>>> in the future.
>>>
>>> On Fri, Feb 19, 2021 at 1:32 PM Bernard Aboba <bernard.aboba@gmail.com>
>>> wrote:
>>>
>>>> Luke --
>>>>
>>>> Thanks for bringing this up!
>>>>
>>>> At the Interim meeting, we talked about having the API provide some
>>>> control over pooling (e.g. allowing an appiication to specify that a
>>>> WebTransport connection not be pooled), as well as allowing a server to
>>>> specify that it doesn't support pooling.
>>>>
>>>> In W3C WebTransport WG we are now in the process of developing PRs to
>>>> deal with pooling, and are running into some of the same questions, such
>>>> as:
>>>>
>>>> 1. Under what circumstances can WebTransport connections be pooled, and
>>>> what kinds of pooling are allowed?
>>>> PR: https://github.com/whatwg/fetch/pull/1171
>>>>
>>>> 2.  What are the differences in API behavior between Http3Transport and
>>>> quic-transport?
>>>> PR: https://github.com/w3c/webtransport/pull/205
>>>>
>>>> 3.  For Http3Transport, are there differences in API behavior between
>>>> non-sharable connections and sharable ones (e.g. behavior of
>>>> webtransport.close())?
>>>> Also coming up in PR: https://github.com/w3c/webtransport/pull/205
>>>>
>>>> 4. For a non-sharable WebTransport connection, is it possible to obtain
>>>> some of the stats that were supported for quic-transport, but would not be
>>>> appropriate for a sharable transport?
>>>> Issue: https://github.com/w3c/webtransport/issues/206
>>>>
>>>>
>>>>
>>>> On Fri, Feb 19, 2021 at 12:49 PM Luke Curley <kixelated@gmail.com>
>>>> wrote:
>>>>
>>>>> Hey everybody, I wanted to start the discussion now that Victor's
>>>>> document has been adopted!
>>>>>
>>>>> I filed some issues
>>>>> <https://github.com/ietf-wg-webtrans/draft-ietf-webtrans-http3> earlier
>>>>> on Github over a few small things. Overall, the draft is clean and it's
>>>>> nice that we've converged on a single WebTransport protocol. One bigger
>>>>> topic I wanted to discuss is the ramifications of connection pooling.
>>>>>
>>>>> Broadly speaking, any QUIC parameters or frames that operate on the
>>>>> connection as a whole can no longer be exposed to the application.
>>>>> Specifically: MAX_DATA, MAX_STREAMS, CONNECTION_CLOSE*, connection ID, and
>>>>> any transport parameters.
>>>>>
>>>>> The WebTransport specification specifically mentions MAX_STREAMS, as
>>>>> HTTP/3 servers can no longer use this to limit the number of simultaneous
>>>>> requests. Returning an error code instead of utilizing the built-in flow
>>>>> control is not a problem, but it's not ideal either.
>>>>>
>>>>> I believe this is a one-way door in general. Any protocols or
>>>>> applications built on top of QUIC will no longer be able to use
>>>>> connection-based QUIC features without breaking WebTransport compatibility.
>>>>> This primarily means HTTP/3, but it also includes any new protocols that
>>>>> utilize QUIC and desire browser support.
>>>>>
>>>>> What does the group think? Is this something worth caring about?
>>>>> --
>>>>> 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
>>>
>>

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

<div dir=3D"ltr"><div>Thanks!</div><div><br></div>WebTransport is intention=
ally designed to be limited because we don&#39;t want to expose too much to=
 JavaScript.<div>Similarly, when JavaScript is using WebSocket, we don&#39;=
t let it access TLS extensions or TCP flow control information, as doing th=
at could cause security issues.</div><div><br></div><div>To your=C2=A0MAX_S=
TREAMS/MAX_DATA example, I think there&#39;s value in having WebTransport-s=
pecific flow control, but I don&#39;t think that should rely on the underly=
ing transport and connection, we can easily build that inside WebTransport =
itself.</div><div>In other words, if there are QUIC-connection-level featur=
es that we think might benefit WebTransport applications, we should analyze=
 their security implications and add those specifically to WebTransport ins=
tead of giving JavaScript blanket control over connection properties.</div>=
<div><br></div><div>David</div></div><br><div class=3D"gmail_quote"><div di=
r=3D"ltr" class=3D"gmail_attr">On Fri, Feb 19, 2021 at 2:59 PM Luke Curley =
&lt;<a href=3D"mailto:kixelated@gmail.com">kixelated@gmail.com</a>&gt; wrot=
e:<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"l=
tr"><div>Good examples, because HTTP/3 is currently the only QUIC applicati=
on and it doesn&#39;t utilize both of those. But QUIC doesn&#39;t prohibit =
an application/protocol from utilizing the connection ID or TLS extensions.=
 It could be useful for some future purpose, like the client using a pre-ar=
ranged connection ID (encoded with routing info?) or new TLS extensions/par=
ameters (remove a round trip for a handshake?).</div><div><br></div><div>We=
bTransport does prohibit using these connection-level functionalities for t=
he sake of pooling. None of this is critical functionality, but it might ha=
mper future efforts which is why I wanted to bring up the one-way door.</di=
v><div><br></div><div>It&#39;s on my mind because I&#39;m designing a video=
 protocol over QUIC. It would be nice if I could use MAX_STREAMS, MAX_DATA,=
 etc, but as it stands now, I&#39;ll need to implement my own flow control =
mechanisms for WebTransport (browser) support.</div></div><br><div class=3D=
"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 19, 2021 at=
 2:27 PM David Schinazi &lt;<a href=3D"mailto:dschinazi.ietf@gmail.com" tar=
get=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 so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hi Luke,<div><br></=
div><div>Can you elaborate on what benefits you see in exposing QUIC-connec=
tion-level information to a WebTransport application?</div><div>In particul=
ar, which information would benefit WebTransport applications? Because for =
example I don&#39;t see how knowing the connection ID or transport paramete=
rs would be useful,=C2=A0but I could just be missing something.</div><div><=
br></div><div>David</div></div><br><div class=3D"gmail_quote"><div dir=3D"l=
tr" class=3D"gmail_attr">On Fri, Feb 19, 2021 at 1:56 PM Luke Curley &lt;<a=
 href=3D"mailto:kixelated@gmail.com" target=3D"_blank">kixelated@gmail.com<=
/a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><=
div dir=3D"ltr">Oh man I just noticed the typo in the email subject... that=
&#39;s embarrassing.<div><br></div><div>I mentioned this earlier, but I thi=
nk pooling is a potential future optimization. The benefit is that pooling =
can avoid additional TLS handshakes=C2=A0iff a client has multiple WebTrans=
port or HTTP/3 connections to the same host (rare?). The cost of pooling is=
 that connection-level QUIC functionality is no longer available, and must =
be avoided or worked around.</div><div><br></div><div>I liked how QuicTrans=
port was connection oriented and I think something similar could be done fo=
r Http3Transport without precluding pooling support in the future.</div></d=
iv><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On =
Fri, Feb 19, 2021 at 1:32 PM Bernard Aboba &lt;<a href=3D"mailto:bernard.ab=
oba@gmail.com" target=3D"_blank">bernard.aboba@gmail.com</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Lu=
ke --<div><br></div><div>Thanks for bringing this up!=C2=A0</div><div><br><=
/div><div>At the Interim meeting, we talked about having the API provide so=
me control over pooling (e.g. allowing an appiication to specify that a Web=
Transport connection not be pooled), as well as allowing a server to specif=
y that it doesn&#39;t support pooling.=C2=A0=C2=A0</div><div><br></div><div=
>In W3C WebTransport WG we are now in the process of developing PRs to deal=
 with pooling, and are running into some of the same questions, such as:=C2=
=A0</div><div><br></div><div>1. Under what circumstances can WebTransport c=
onnections be pooled, and what kinds of pooling are allowed?=C2=A0</div><di=
v>PR: <a href=3D"https://github.com/whatwg/fetch/pull/1171" target=3D"_blan=
k">https://github.com/whatwg/fetch/pull/1171</a>=C2=A0</div><div><br></div>=
<div>2.=C2=A0 What are the differences in API behavior between Http3Transpo=
rt and quic-transport?=C2=A0</div><div>PR:=C2=A0<a href=3D"https://github.c=
om/w3c/webtransport/pull/205" target=3D"_blank">https://github.com/w3c/webt=
ransport/pull/205</a></div><div><br></div><div>3.=C2=A0 For Http3Transport,=
 are there differences in API behavior between non-sharable connections and=
 sharable=C2=A0ones (e.g. behavior of webtransport.close())?=C2=A0</div><di=
v>Also coming up in=C2=A0PR:=C2=A0<a href=3D"https://github.com/w3c/webtran=
sport/pull/205" target=3D"_blank">https://github.com/w3c/webtransport/pull/=
205</a></div><div><br></div><div>4. For a non-sharable WebTransport connect=
ion, is it possible to obtain some of the stats that were supported for qui=
c-transport, but would not be appropriate for a sharable transport?=C2=A0</=
div><div>Issue:=C2=A0<a href=3D"https://github.com/w3c/webtransport/issues/=
206" target=3D"_blank">https://github.com/w3c/webtransport/issues/206</a><b=
r></div><div><br></div><div><br></div></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 19, 2021 at 12:49 PM Luke=
 Curley &lt;<a href=3D"mailto:kixelated@gmail.com" target=3D"_blank">kixela=
ted@gmail.com</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">Hey everybody, I wanted to start the discussi=
on now that Victor&#39;s document has been adopted!<div><br></div><div>I fi=
led some <a href=3D"https://github.com/ietf-wg-webtrans/draft-ietf-webtrans=
-http3" target=3D"_blank">issues</a>=C2=A0earlier on Github over a few smal=
l things. Overall, the draft is clean and it&#39;s nice that we&#39;ve conv=
erged on a single WebTransport protocol. One bigger topic I wanted to discu=
ss is the ramifications of connection pooling.</div><div><br></div><div>Bro=
adly speaking, any QUIC parameters or frames that operate on the connection=
 as a whole can no longer be exposed to the application. Specifically: MAX_=
DATA, MAX_STREAMS, CONNECTION_CLOSE*, connection ID, and any transport para=
meters.</div><div><br></div><div>The WebTransport specification specificall=
y mentions MAX_STREAMS, as HTTP/3 servers can no longer use this to limit t=
he number of simultaneous requests. Returning an error code instead of util=
izing the built-in flow control is not a problem, but it&#39;s not ideal ei=
ther.</div><div><br></div><div>I believe this is a one-way door in general.=
 Any protocols or applications built on top of QUIC will no longer be able =
to use connection-based QUIC features without breaking WebTransport compati=
bility. This primarily means HTTP/3, but it also includes any new protocols=
 that utilize QUIC and desire browser support.</div><div><br></div><div>Wha=
t does the group think? Is this something worth caring about?</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>
</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>
</blockquote></div>
</blockquote></div>

--0000000000007ed4d005bbb96a37--


From nobody Sun Feb 21 09:57: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 16DE93A0DD3 for <webtransport@ietfa.amsl.com>; Sun, 21 Feb 2021 09:57:28 -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 PUn8uTXfB_a3 for <webtransport@ietfa.amsl.com>; Sun, 21 Feb 2021 09:57:25 -0800 (PST)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (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 1B6033A0DD4 for <webtransport@ietf.org>; Sun, 21 Feb 2021 09:57:25 -0800 (PST)
Received: by mail-wr1-x42a.google.com with SMTP id v15so16721941wrx.4 for <webtransport@ietf.org>; Sun, 21 Feb 2021 09:57:24 -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=/b/86pxYVFhRy0xDtLFjm0KfePGNZL0LLL3mP08O8pY=; b=fNngrQKS+XgVHMG70UBhPS+R2wRoC0O1yLiiHUq9KEKaWhxcfW5fPpXLdVcUIdD9L0 NmiRahc+DJl/Oa8RNQjCdNLim/QA78DG4sWm1bs7whg5nw/J99/2THkT7i/wJT55xLi5 zsTK8zU0sNiDcRvwGqZRLeC33XF6jGhIspse3V1dTVzAauvG1dFfLWscdiYlU3XywgYa 0YIJvkHXGoo04HUuxKCdgL1GHq9U9TIksWgpai6gmWQUKlawVWLQj8CpsW7cTd62DhTs 7wN1es1nudRgminoKNBTaSkh/0sfWeMmlQmZEiiRlp/XznJXNij/hoPcc57cw5eawFC4 o6gg==
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=/b/86pxYVFhRy0xDtLFjm0KfePGNZL0LLL3mP08O8pY=; b=ZCRN695/+iSucffpv2ae/fa2Mc4PB/iU6N6YRQ5FnVIt7ZHu1x4u2FsbjWmuKrQNMT eboozrKN3JCACaoc3Zgj4E3Q7ZzAG61BolAKQY3DTmcEEKaOhvgptgDu7GTFCKUiIS+m vC9DVXFd3/GHHxbYuwPYiRQzoN+k9+5cVGNlxbdgp4euKHrZUFFB8qTL77ycHQjrppJz 1m8O6O6W9dR4aytHKMgmm1VJDiDVD0G0m0ppazvnG1ChI4DIK1qPwlQSItyE91JBFoOJ sePwZ+UuwDdhuXtYrOHjsc4l+2labuXxyjqo1NrslQGCbYe8OkBJleCcaUpMoRIXevVx hiPQ==
X-Gm-Message-State: AOAM530K6ql7hHY2jv3pn4x7Aazu05gX/jfsBxXLV90qXesjIUxolGNu UpLz8FERNFcn0m2+/Tcxx5S0Ot/1qsTBdt3NcceLTg==
X-Google-Smtp-Source: ABdhPJzbP68hoYob7UVTmcNWo/CIeeSSzKCv0cQKK6rns3BpSFSemsTwZoQyGcytewjqB4ZeZh2HEbRxXW9fSGUdE2U=
X-Received: by 2002:adf:f484:: with SMTP id l4mr7019646wro.409.1613930243264;  Sun, 21 Feb 2021 09:57:23 -0800 (PST)
MIME-Version: 1.0
References: <CAHVo=ZmRketpx02KeYPSHSB2gQNvYi6RSs3HrXA1isYTgYorLg@mail.gmail.com> <CAOW+2duU6Xg98Tpec6NbEL5pyxAShp76rPMyZV07Wpmx3pJX2Q@mail.gmail.com> <CAHVo=Z=o-oMfWaOUMxjtgaTNVvo28ot5EhinE+uio19-c2S0Gg@mail.gmail.com> <CAPDSy+6tWTWyL6KHZTGJ3z3L6ZGJmTrVyiPiq0zRo-SGUb39tg@mail.gmail.com> <CAHVo=Z=gsLRuFFuYiXo73HwPiThgGH5n_scw7Bn8aNrAjQ2Dig@mail.gmail.com> <CAPDSy+6LT9dMS6RofRzdqL6R5VFDRfv21qV+Xd9jx22w2yyuZA@mail.gmail.com>
In-Reply-To: <CAPDSy+6LT9dMS6RofRzdqL6R5VFDRfv21qV+Xd9jx22w2yyuZA@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Sun, 21 Feb 2021 12:57:11 -0500
Message-ID: <CAKcm_gO4GQ9uSOFQjw6W-CXkOexcKiuswUZyaTfc5KykAH2Lyg@mail.gmail.com>
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: Luke Curley <kixelated@gmail.com>, WebTransport <webtransport@ietf.org>,  Bernard Aboba <bernard.aboba@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000d7e2eb05bbdc6ad3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/ql6aD3gv-XTeuQVuy8g_7nkPbWs>
Subject: Re: [Webtransport] Http3Transport: Connection-basd Functionality
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, 21 Feb 2021 17:57:28 -0000

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

The MAX_STREAMS/MAX_DATA example does seem like a tricky point I hadn't
fully appreciated earlier.

In H3, we took the attitude that using those transport connection level
features was the right thing to do, which I think makes sense because
HTTP/2 had too much transport(non-HTTP) functionality in it.

But if we allow pooling of H3 with WebTransport or other applications which
need to use MAX_STREAMS/MAX_DATA, then each other application needs to add
transport-style mechanisms and the H3 implementation probably needs to be
aware that MAX_STREAMS needs to be adjusted by the other applications
MAX_STREAMS in order to have the intended effect.

I think I'm leaning towards one of two options: We don't care about
isolating the pooled H3 session from the WebTransport session when pooling
occurs, or we need to spend more time thinking about this
'session-layer'(to use Roberto's phrasing) problem in general now or we're
going to create some problems down the road.

Ian



On Fri, Feb 19, 2021 at 7:12 PM David Schinazi <dschinazi.ietf@gmail.com>
wrote:

> Thanks!
>
> WebTransport is intentionally designed to be limited because we don't want
> to expose too much to JavaScript.
> Similarly, when JavaScript is using WebSocket, we don't let it access TLS
> extensions or TCP flow control information, as doing that could cause
> security issues.
>
> To your MAX_STREAMS/MAX_DATA example, I think there's value in having
> WebTransport-specific flow control, but I don't think that should rely on
> the underlying transport and connection, we can easily build that inside
> WebTransport itself.
> In other words, if there are QUIC-connection-level features that we think
> might benefit WebTransport applications, we should analyze their security
> implications and add those specifically to WebTransport instead of giving
> JavaScript blanket control over connection properties.
>
> David
>
> On Fri, Feb 19, 2021 at 2:59 PM Luke Curley <kixelated@gmail.com> wrote:
>
>> Good examples, because HTTP/3 is currently the only QUIC application and
>> it doesn't utilize both of those. But QUIC doesn't prohibit an
>> application/protocol from utilizing the connection ID or TLS extensions. It
>> could be useful for some future purpose, like the client using a
>> pre-arranged connection ID (encoded with routing info?) or new TLS
>> extensions/parameters (remove a round trip for a handshake?).
>>
>> WebTransport does prohibit using these connection-level functionalities
>> for the sake of pooling. None of this is critical functionality, but it
>> might hamper future efforts which is why I wanted to bring up the one-way
>> door.
>>
>> It's on my mind because I'm designing a video protocol over QUIC. It
>> would be nice if I could use MAX_STREAMS, MAX_DATA, etc, but as it stands
>> now, I'll need to implement my own flow control mechanisms for WebTransport
>> (browser) support.
>>
>> On Fri, Feb 19, 2021 at 2:27 PM David Schinazi <dschinazi.ietf@gmail.com>
>> wrote:
>>
>>> Hi Luke,
>>>
>>> Can you elaborate on what benefits you see in exposing
>>> QUIC-connection-level information to a WebTransport application?
>>> In particular, which information would benefit WebTransport
>>> applications? Because for example I don't see how knowing the connection ID
>>> or transport parameters would be useful, but I could just be missing
>>> something.
>>>
>>> David
>>>
>>> On Fri, Feb 19, 2021 at 1:56 PM Luke Curley <kixelated@gmail.com> wrote:
>>>
>>>> Oh man I just noticed the typo in the email subject... that's
>>>> embarrassing.
>>>>
>>>> I mentioned this earlier, but I think pooling is a potential future
>>>> optimization. The benefit is that pooling can avoid additional TLS
>>>> handshakes iff a client has multiple WebTransport or HTTP/3 connections to
>>>> the same host (rare?). The cost of pooling is that connection-level QUIC
>>>> functionality is no longer available, and must be avoided or worked around.
>>>>
>>>> I liked how QuicTransport was connection oriented and I think something
>>>> similar could be done for Http3Transport without precluding pooling support
>>>> in the future.
>>>>
>>>> On Fri, Feb 19, 2021 at 1:32 PM Bernard Aboba <bernard.aboba@gmail.com>
>>>> wrote:
>>>>
>>>>> Luke --
>>>>>
>>>>> Thanks for bringing this up!
>>>>>
>>>>> At the Interim meeting, we talked about having the API provide some
>>>>> control over pooling (e.g. allowing an appiication to specify that a
>>>>> WebTransport connection not be pooled), as well as allowing a server to
>>>>> specify that it doesn't support pooling.
>>>>>
>>>>> In W3C WebTransport WG we are now in the process of developing PRs to
>>>>> deal with pooling, and are running into some of the same questions, such
>>>>> as:
>>>>>
>>>>> 1. Under what circumstances can WebTransport connections be pooled,
>>>>> and what kinds of pooling are allowed?
>>>>> PR: https://github.com/whatwg/fetch/pull/1171
>>>>>
>>>>> 2.  What are the differences in API behavior between Http3Transport
>>>>> and quic-transport?
>>>>> PR: https://github.com/w3c/webtransport/pull/205
>>>>>
>>>>> 3.  For Http3Transport, are there differences in API behavior between
>>>>> non-sharable connections and sharable ones (e.g. behavior of
>>>>> webtransport.close())?
>>>>> Also coming up in PR: https://github.com/w3c/webtransport/pull/205
>>>>>
>>>>> 4. For a non-sharable WebTransport connection, is it possible to
>>>>> obtain some of the stats that were supported for quic-transport, but would
>>>>> not be appropriate for a sharable transport?
>>>>> Issue: https://github.com/w3c/webtransport/issues/206
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Feb 19, 2021 at 12:49 PM Luke Curley <kixelated@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hey everybody, I wanted to start the discussion now that Victor's
>>>>>> document has been adopted!
>>>>>>
>>>>>> I filed some issues
>>>>>> <https://github.com/ietf-wg-webtrans/draft-ietf-webtrans-http3> earlier
>>>>>> on Github over a few small things. Overall, the draft is clean and it's
>>>>>> nice that we've converged on a single WebTransport protocol. One bigger
>>>>>> topic I wanted to discuss is the ramifications of connection pooling.
>>>>>>
>>>>>> Broadly speaking, any QUIC parameters or frames that operate on the
>>>>>> connection as a whole can no longer be exposed to the application.
>>>>>> Specifically: MAX_DATA, MAX_STREAMS, CONNECTION_CLOSE*, connection ID, and
>>>>>> any transport parameters.
>>>>>>
>>>>>> The WebTransport specification specifically mentions MAX_STREAMS, as
>>>>>> HTTP/3 servers can no longer use this to limit the number of simultaneous
>>>>>> requests. Returning an error code instead of utilizing the built-in flow
>>>>>> control is not a problem, but it's not ideal either.
>>>>>>
>>>>>> I believe this is a one-way door in general. Any protocols or
>>>>>> applications built on top of QUIC will no longer be able to use
>>>>>> connection-based QUIC features without breaking WebTransport compatibility.
>>>>>> This primarily means HTTP/3, but it also includes any new protocols that
>>>>>> utilize QUIC and desire browser support.
>>>>>>
>>>>>> What does the group think? Is this something worth caring about?
>>>>>> --
>>>>>> 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
>

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

<div dir=3D"ltr">The MAX_STREAMS/MAX_DATA example does seem like a tricky p=
oint I hadn&#39;t fully appreciated earlier.<div><br></div><div>In H3, we t=
ook the attitude that using those transport connection level features was t=
he right thing to do, which I think makes sense because HTTP/2 had too much=
 transport(non-HTTP) functionality in it.</div><div><br></div><div>But if w=
e allow pooling of H3 with WebTransport or other applications which need to=
 use MAX_STREAMS/MAX_DATA, then each other application needs to add transpo=
rt-style mechanisms and the H3 implementation=C2=A0probably needs to be awa=
re that MAX_STREAMS needs to be adjusted by the other applications MAX_STRE=
AMS in order to have the intended effect.</div><div><br></div><div>I think =
I&#39;m leaning towards one of two options: We don&#39;t care about isolati=
ng the pooled H3 session from the WebTransport session when pooling occurs,=
 or we need to spend more time thinking about this &#39;session-layer&#39;(=
to use Roberto&#39;s phrasing) problem in general now or we&#39;re going to=
 create some problems down the road.</div><div><br></div><div>Ian</div><div=
><br></div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr" class=3D"gmail_attr">On Fri, Feb 19, 2021 at 7:12 PM David Schinazi &l=
t;<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 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div =
dir=3D"ltr"><div>Thanks!</div><div><br></div>WebTransport is intentionally =
designed to be limited because we don&#39;t want to expose too much to Java=
Script.<div>Similarly, when JavaScript is using WebSocket, we don&#39;t let=
 it access TLS extensions or TCP flow control information, as doing that co=
uld cause security issues.</div><div><br></div><div>To your=C2=A0MAX_STREAM=
S/MAX_DATA example, I think there&#39;s value in having WebTransport-specif=
ic flow control, but I don&#39;t think that should rely on the underlying t=
ransport and connection, we can easily build that inside WebTransport itsel=
f.</div><div>In other words, if there are QUIC-connection-level features th=
at we think might benefit WebTransport applications, we should analyze thei=
r security implications and add those specifically to WebTransport instead =
of giving JavaScript blanket control over connection properties.</div><div>=
<br></div><div>David</div></div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr" class=3D"gmail_attr">On Fri, Feb 19, 2021 at 2:59 PM Luke Curley &lt;<=
a href=3D"mailto:kixelated@gmail.com" target=3D"_blank">kixelated@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>Good examples, because HTTP/3 is currently the only Q=
UIC application and it doesn&#39;t utilize both of those. But QUIC doesn&#3=
9;t prohibit an application/protocol from utilizing the connection ID or TL=
S extensions. It could be useful for some future purpose, like the client u=
sing a pre-arranged connection ID (encoded with routing info?) or new TLS e=
xtensions/parameters (remove a round trip for a handshake?).</div><div><br>=
</div><div>WebTransport does prohibit using these connection-level function=
alities for the sake of pooling. None of this is critical functionality, bu=
t it might hamper future efforts which is why I wanted to bring up the one-=
way door.</div><div><br></div><div>It&#39;s on my mind because I&#39;m desi=
gning a video protocol over QUIC. It would be nice if I could use MAX_STREA=
MS, MAX_DATA, etc, but as it stands now, I&#39;ll need to implement my own =
flow control mechanisms for WebTransport (browser) support.</div></div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Fe=
b 19, 2021 at 2:27 PM David Schinazi &lt;<a href=3D"mailto:dschinazi.ietf@g=
mail.com" target=3D"_blank">dschinazi.ietf@gmail.com</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hi Luk=
e,<div><br></div><div>Can you elaborate on what benefits you see in exposin=
g QUIC-connection-level information to a WebTransport application?</div><di=
v>In particular, which information would benefit WebTransport applications?=
 Because for example I don&#39;t see how knowing the connection ID or trans=
port parameters would be useful,=C2=A0but I could just be missing something=
.</div><div><br></div><div>David</div></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 19, 2021 at 1:56 PM Luke =
Curley &lt;<a href=3D"mailto:kixelated@gmail.com" target=3D"_blank">kixelat=
ed@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><div dir=3D"ltr">Oh man I just noticed the typo in the email su=
bject... that&#39;s embarrassing.<div><br></div><div>I mentioned this earli=
er, but I think pooling is a potential future optimization. The benefit is =
that pooling can avoid additional TLS handshakes=C2=A0iff a client has mult=
iple WebTransport or HTTP/3 connections to the same host (rare?). The cost =
of pooling is that connection-level QUIC functionality is no longer availab=
le, and must be avoided or worked around.</div><div><br></div><div>I liked =
how QuicTransport was connection oriented and I think something similar cou=
ld be done for Http3Transport without precluding pooling support in the fut=
ure.</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gm=
ail_attr">On Fri, Feb 19, 2021 at 1:32 PM Bernard Aboba &lt;<a href=3D"mail=
to:bernard.aboba@gmail.com" target=3D"_blank">bernard.aboba@gmail.com</a>&g=
t; wrote:<br></div><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 d=
ir=3D"ltr">Luke --<div><br></div><div>Thanks for bringing this up!=C2=A0</d=
iv><div><br></div><div>At the Interim meeting, we talked about having the A=
PI provide some control over pooling (e.g. allowing an appiication to speci=
fy that a WebTransport connection not be pooled), as well as allowing a ser=
ver to specify that it doesn&#39;t support pooling.=C2=A0=C2=A0</div><div><=
br></div><div>In W3C WebTransport WG we are now in the process of developin=
g PRs to deal with pooling, and are running into some of the same questions=
, such as:=C2=A0</div><div><br></div><div>1. Under what circumstances can W=
ebTransport connections be pooled, and what kinds of pooling are allowed?=
=C2=A0</div><div>PR: <a href=3D"https://github.com/whatwg/fetch/pull/1171" =
target=3D"_blank">https://github.com/whatwg/fetch/pull/1171</a>=C2=A0</div>=
<div><br></div><div>2.=C2=A0 What are the differences in API behavior betwe=
en Http3Transport and quic-transport?=C2=A0</div><div>PR:=C2=A0<a href=3D"h=
ttps://github.com/w3c/webtransport/pull/205" target=3D"_blank">https://gith=
ub.com/w3c/webtransport/pull/205</a></div><div><br></div><div>3.=C2=A0 For =
Http3Transport, are there differences in API behavior between non-sharable =
connections and sharable=C2=A0ones (e.g. behavior of webtransport.close())?=
=C2=A0</div><div>Also coming up in=C2=A0PR:=C2=A0<a href=3D"https://github.=
com/w3c/webtransport/pull/205" target=3D"_blank">https://github.com/w3c/web=
transport/pull/205</a></div><div><br></div><div>4. For a non-sharable WebTr=
ansport connection, is it possible to obtain some of the stats that were su=
pported for quic-transport, but would not be appropriate for a sharable tra=
nsport?=C2=A0</div><div>Issue:=C2=A0<a href=3D"https://github.com/w3c/webtr=
ansport/issues/206" target=3D"_blank">https://github.com/w3c/webtransport/i=
ssues/206</a><br></div><div><br></div><div><br></div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 19, 2021=
 at 12:49 PM Luke Curley &lt;<a href=3D"mailto:kixelated@gmail.com" target=
=3D"_blank">kixelated@gmail.com</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 dir=3D"ltr">Hey everybody, I wanted t=
o start the discussion now that Victor&#39;s document has been adopted!<div=
><br></div><div>I filed some <a href=3D"https://github.com/ietf-wg-webtrans=
/draft-ietf-webtrans-http3" target=3D"_blank">issues</a>=C2=A0earlier on Gi=
thub over a few small things. Overall, the draft is clean and it&#39;s nice=
 that we&#39;ve converged on a single WebTransport protocol. One bigger top=
ic I wanted to discuss is the ramifications of connection pooling.</div><di=
v><br></div><div>Broadly speaking, any QUIC parameters or frames that opera=
te on the connection as a whole can no longer be exposed to the application=
. Specifically: MAX_DATA, MAX_STREAMS, CONNECTION_CLOSE*, connection ID, an=
d any transport parameters.</div><div><br></div><div>The WebTransport speci=
fication specifically mentions MAX_STREAMS, as HTTP/3 servers can no longer=
 use this to limit the number of simultaneous requests. Returning an error =
code instead of utilizing the built-in flow control is not a problem, but i=
t&#39;s not ideal either.</div><div><br></div><div>I believe this is a one-=
way door in general. Any protocols or applications built on top of QUIC wil=
l no longer be able to use connection-based QUIC features without breaking =
WebTransport compatibility. This primarily means HTTP/3, but it also includ=
es any new protocols that utilize QUIC and desire browser support.</div><di=
v><br></div><div>What does the group think? Is this something worth caring =
about?</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>
</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>
</blockquote></div>
</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>

--000000000000d7e2eb05bbdc6ad3--


From nobody Thu Feb 25 11:47:42 2021
Return-Path: <prvs=1690807433=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 76C6E3A1F1F for <webtransport@ietfa.amsl.com>; Thu, 25 Feb 2021 11:47:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.666
X-Spam-Level: 
X-Spam-Status: No, score=-2.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.57, 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.001, RCVD_IN_MSPIKE_WL=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 (1024-bit key) header.d=fb.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 XLkNEWQZfSfE for <webtransport@ietfa.amsl.com>; Thu, 25 Feb 2021 11:47:39 -0800 (PST)
Received: from mx0b-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 050D53A1F1E for <webtransport@ietf.org>; Thu, 25 Feb 2021 11:47:38 -0800 (PST)
Received: from pps.filterd (m0148460.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 11PJdwDJ010336 for <webtransport@ietf.org>; Thu, 25 Feb 2021 11:47:38 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : subject : date : message-id : content-type : mime-version; s=facebook; bh=Qz1Y9MjdEjmHajs13ex9if/bLEZL6USmj0w4IBXz7vA=; b=hyqR/SLMiThGh/083sWd0jbclFFXSjcLOh3K90uaJDhEXSejuR5RaPUtEUKaE+O2XdrV Vq6zGS4qVNb7zJbyV18u9TlRSUV7Nvparha+gNMmrCbYLxzKfxGsNLp6Mw5RUJML++oY yqRwpOV3y4FAJe0bUwCN3opakyYljAnWxOE= 
Received: from maileast.thefacebook.com ([163.114.130.16]) by mx0a-00082601.pphosted.com with ESMTP id 36x9caua3d-3 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for <webtransport@ietf.org>; Thu, 25 Feb 2021 11:47:38 -0800
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (100.104.31.183) by o365-in.thefacebook.com (100.104.36.101) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Thu, 25 Feb 2021 11:47:36 -0800
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=LtmrvbBUzaeu+G2UUAwXGOz64KS6uhsjt74k2pGiiMHyAvW2xOVWk9ZmqgD3O9cWQsKeqPNYWej2vxPLfiVMu8D9U6CuDs+0iFibUbwkwxs9iRw/CjzkEZqvwKuE06yNAZbfAXIC7wI2wAsp0nGVoXEy6lHij0dxf826oZe9guxbRdD+RcJtZcDBYMyN0uqf+bHedw/ZNXym/+7N1HQX3h840Tfr0B2I9jaBE1oeWO/c02i2HfkoKf+7MD0q8CLGSMc0sk3jCE1TnEN2fJUjuifXcU6ZLyoGJxxBX/AKliY6tdZRb9eu1itZP7lbdbtPoOBx7n3dY/OFsu4LWZjQkg==
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=Qz1Y9MjdEjmHajs13ex9if/bLEZL6USmj0w4IBXz7vA=; b=cmRxdujOvgnOwGmNix8vXMDKVlac8cJ7EUgEEkL/B6GgSKuWPekfvnIqaSK3RPVlQLceB+wGq4JUgh0EV6MifOpeUbjHDrKJ71vp9n556Zt7ZofLjZdO6KHQVo4XjxnRCPIm53fsm/VmM1XX7zAWGy+VFuyCL5NQql8hKBg73Ga+8JmPJ7/SAPjsRKi4pSVNAKw1duyRufjvMigPY/ZJuCbQaUUETucS5vr3HnMi6OTvIngTclOspcSceAuW0GheebHNlhlMkc5kZHdXxZKqyr84xfqeZkxRjHwMqCsY1+/unmKwxOn5LsnOEryAIMqXubCs4pUPXGGlTFsx1yfq9g==
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
Received: from MW3PR15MB3772.namprd15.prod.outlook.com (2603:10b6:303:4c::14) by MW4PR15MB4362.namprd15.prod.outlook.com (2603:10b6:303:bb::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3868.32; Thu, 25 Feb 2021 19:47:35 +0000
Received: from MW3PR15MB3772.namprd15.prod.outlook.com ([fe80::b8db:7d56:d1bd:668d]) by MW3PR15MB3772.namprd15.prod.outlook.com ([fe80::b8db:7d56:d1bd:668d%4]) with mapi id 15.20.3890.020; Thu, 25 Feb 2021 19:47:35 +0000
From: Alan Frindell <afrind@fb.com>
To: "webtransport@ietf.org" <webtransport@ietf.org>
Thread-Topic: Anyone up for hackathon?
Thread-Index: AQHXC68Qx4P1nT12+0G7oAR6HpUc5g==
Date: Thu, 25 Feb 2021 19:47:35 +0000
Message-ID: <5FD74782-4CCD-4623-8D7F-5C5D2EADB57E@fb.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: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=fb.com;
x-originating-ip: [2620:10d:c090:400::5:9ca7]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c78b5882-3ae5-42c2-5391-08d8d9c632f9
x-ms-traffictypediagnostic: MW4PR15MB4362:
x-microsoft-antispam-prvs: <MW4PR15MB4362AF3EAF43CD878003E6C1A79E9@MW4PR15MB4362.namprd15.prod.outlook.com>
x-fb-source: Internal
x-ms-oob-tlc-oobclassifiers: OLM:5516;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: aH5ANpl3tgTaBYMKucRVzzULY5o2uulPz85cxa/wXgjOUHbsJKK3RlX2ch9hRsfeJQ/KBUhGJ7HKopHuGFuFHK6mZVcBlbILsHcVj0rS2gOjT7KCRwBzh95/01SpQVAnoOptdN8Ozr9aQQoKfrU2x2leNd2XPZ+P4jkK0kfh3GyN0oEsMKHdyR+nmxhF2EGYEWu4z7YTNx/8uXmu3U94sbwyi9HcZ2a4AiKuuMIg2S3GsFc5WrZ4JO8xyEHbm0asPaXHNOxCSG/5cL0PPnsOqYB6ZerEHZ3xCm7C1DeEnkJfbzMNKj5niptUv/KUXdHtRB6cBRefNiXV9ChhroLhBP0bcrQ7A2l5GtVKe12oCiqd04LdAj/EIzWz4MbL0dmTJrDeiS36Hi4la0N9BqmjV+FOgnb49HNV/TlrV39hdNVTVfvv1Cel5z5y+DR6QyafnRZdS8Sb2L0QPutnE4b2iLSpTj2Q/2uH1DRkUOqODEZq5ZNvxXVVaG5fBihpM7Cllg/N7YjgO05s+1vHe34czHy/e6IcSLF3UGwOLRjIXr24uBjcWG+PkFFuhjY+HVSM4ll1xPyXAfHl1L9Rdx6BJA==
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:(396003)(39860400002)(366004)(376002)(136003)(346002)(8676002)(71200400001)(5660300002)(6916009)(2616005)(2906002)(36756003)(86362001)(6512007)(8936002)(33656002)(66476007)(66446008)(316002)(66556008)(91956017)(558084003)(6506007)(66946007)(76116006)(64756008)(478600001)(6486002)(186003)(3480700007)(45980500001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?YjQ5aStpejh6VUMva0lpRmhPU0RKY3NxV1JEOXVGdG5DemNPMXdNT2R2eTRM?= =?utf-8?B?VzdnS1BobGhqZ2FMR3BxZUJDdFQrQU5wVEZDME1zK0h5STNpVVVZWnc3Vmpt?= =?utf-8?B?YVkzZ042aFd5SUgwTFpmZHY3ZGRaVUJHTTR6TlJqY1dDOTNvQnFqNzlDdGhr?= =?utf-8?B?a1UwR2VWN2lOamw4ZEZOU29OZy9lNGo0OTNzbU1LWG5kbjVBVE5YTGo0RW5j?= =?utf-8?B?cTh2aktCaW9URmNRd2dCVDB0NHRuMlJOVXA4a0lRVGtYbDl1YjcvRFVSdk5q?= =?utf-8?B?VUo3QjdjVWVnK0dsdHljQ3psYlNpWFNzQy9LNkttVDNjRko0djY3M1JkZTBJ?= =?utf-8?B?b0FaQ012RHUyditUc25Ic3kzZTBJaW40NmlzWnlMRlFPR3VDanBEZkM2Um9E?= =?utf-8?B?R0ZXRXg3NlZhN3AxSitmSUpYWDlFQ2xVMkFiSWVvaCtBZHVVN2VsaWp2M1Bp?= =?utf-8?B?V3ZHRG5SbTFGL3hWamYwSWlFbktCNG43c1pCNjBVc2pnbER6V0wxWjVFYkpi?= =?utf-8?B?Rk12R1BJaHJrM2JiS2l4bUZ0OXkvYUViUTNLc0pWRW9LSldUa0ptS0ZnUURP?= =?utf-8?B?b1BSa3pYQU5UMjJUdkNKckgvZ1gxSlAraklnODJvczJaQjNuS01XNVlWVzMv?= =?utf-8?B?SndpYVJxamVKR2lvYW9vZ3VjVXQxRmR4b1ZVcXlsQXFaRHpHTmFUeVFwMXpu?= =?utf-8?B?TjA2RjV4TENXMnpVK2pSYlE4RjN6Tmd4QXFHV05uYjFFTFo2WVJvOGYzSVpO?= =?utf-8?B?U2VsMGQ0RGRIaDFZVVFsYWFocm4vYU5hczYzRW9rRWtXamRyaDhPVjJnQ3pm?= =?utf-8?B?dDBzQ04xcUFMcmdsY3RtY2dIRWI1aHRheVBRZUtUanJnNkxRMVJ1K0VUeVky?= =?utf-8?B?UStwNGdMVEl1OGhLY0x6T0VxMVh3OVBoSDZaSU1NaGNRTzFkLzVwU0toV3lo?= =?utf-8?B?dUVjVVkwa2FtRittQlQ1ZjVibHkzcHFaczhrNnZWRTNkVU56aHIrUlNaOXpM?= =?utf-8?B?eTVGb3VIQU80K3hGSUw1KzY5UFhSdzlrb2dNbzFGLzdJa0w3STdIV0VmSUNW?= =?utf-8?B?ZHE2akdyQ0FEdkJyaXZGVklGYVVDbEJDbURFTkszc3JSL3FUTEJ1dDhkdEFM?= =?utf-8?B?ZXlSbDZ4ejkzUU9GUkt5cFppRzExMVhsOHB2dHk3ZnRCV1E4Mm1zK1pFL21S?= =?utf-8?B?NE5iOURCUjZCNFF1TlQ0QUpvU21vNVNaL2RpZE9rcGNVS0VGZ3RnRW1MZWNt?= =?utf-8?B?L2tyQ1BlTTJRelZrN0MzREdtTjl6cXE5SXAxV3hSOXR4ZkNVK1lrQmJWTGoz?= =?utf-8?B?Q3B2aDRsczIyRzdxaGozZ0JyMnZWaDUzTCtyVEhpU2VHWmgyT2hUS1owVDU4?= =?utf-8?B?dk1CR212MEc0blNlbTVRanFKaXhUYXQ2L1R2MndKb3hZV055Q2hUbHR0bXRS?= =?utf-8?B?TjhPRXd4NmpCTmQzZ1V6OWJaelBFTDloNG40SjVva0FsakxHWFFBaE4rblha?= =?utf-8?B?MFlIZzJOMW9ZUnU0cTFvdjZwYythb1NycXpMNDZPdG9XNm81VFFkM0kzZm5D?= =?utf-8?B?SDI3dHJ4c0RyVmQzNnBIZmpFYjludTUyTzBxQit0TFZGVlplV0NRY2Y5ZCtL?= =?utf-8?B?RFdEM0JvNjN3YmRYL0ovb0cvN0FhblhseHovd1hNak5LYno5RlpsWFdFNmZu?= =?utf-8?B?bUZEOWcwM21SNFI5UkV2MkJ3MXpYNzBpbGh2WjN2MUd1WFRmTzRyMjFEUlh4?= =?utf-8?B?ejFEVzh3YXdXb1RIaWorSytic0xHVmRCNlJoSkpGdFJPOVhtNGhBMjFQQ1pK?= =?utf-8?Q?+MeQay/bhDzAzx2jiBiglJjVqbGhqXl6ixYag=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_5FD747824CCD46238D7F5C5D2EADB57Efbcom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MW3PR15MB3772.namprd15.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c78b5882-3ae5-42c2-5391-08d8d9c632f9
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Feb 2021 19:47:35.3483 (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: I1FJnyDst0cqGezP01cpWu+F+ym2wTZ13k0nGb5uwlz/NIF/B0BzXJeHaCj0PRTC
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW4PR15MB4362
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-02-25_11:2021-02-24, 2021-02-25 signatures=0
X-Proofpoint-Spam-Details: rule=fb_default_notspam policy=fb_default score=0 mlxlogscore=454 malwarescore=0 mlxscore=0 priorityscore=1501 impostorscore=0 clxscore=1011 adultscore=0 suspectscore=0 spamscore=0 lowpriorityscore=0 phishscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2102250149
X-FB-Internal: deliver
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/Hj4WYImEtiq8nO4j5rlC2xFswHs>
Subject: [Webtransport] Anyone up for hackathon?
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, 25 Feb 2021 19:47:40 -0000

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

SSBhbSBwbGFubmluZyB0byB3b3JrIG9uIGFuIGltcGxlbWVudGF0aW9uIG9mIHRoZSBXVCBvdmVy
IEgzIGRyYWZ0IG5leHQgd2Vlay4gIElmIGFueW9uZSBlbHNlIGlzIGludGVyZXN0ZWQgd2UgY2Fu
IHNldCB1cCBhIHRhYmxlLg0KDQotQWxhbg0K

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

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCWZvbnQtc2l6
ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5FbWFp
bFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCi5Nc29DaHBEZWZh
dWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJ
e3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpk
aXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+DQo8L2hl
YWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iIzA1NjNDMSIgdmxpbms9IiM5NTRGNzIiIHN0
eWxlPSJ3b3JkLXdyYXA6YnJlYWstd29yZCI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPkkgYW0g
cGxhbm5pbmcgdG8gd29yayBvbiBhbiBpbXBsZW1lbnRhdGlvbiBvZiB0aGUgV1Qgb3ZlciBIMyBk
cmFmdCBuZXh0IHdlZWsuJm5ic3A7IElmIGFueW9uZSBlbHNlIGlzIGludGVyZXN0ZWQgd2UgY2Fu
IHNldCB1cCBhIHRhYmxlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dCI+LUFsYW48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4N
Cg==

--_000_5FD747824CCD46238D7F5C5D2EADB57Efbcom_--


From nobody Sun Feb 28 16:47:58 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 825703A10A9 for <webtransport@ietfa.amsl.com>; Sun, 28 Feb 2021 16:47:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 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] 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 92Zf9gKhX8SD for <webtransport@ietfa.amsl.com>; Sun, 28 Feb 2021 16:47:55 -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 A386C3A10D4 for <webtransport@ietf.org>; Sun, 28 Feb 2021 16:47:51 -0800 (PST)
Received: by mail-lj1-x231.google.com with SMTP id u18so3812533ljd.3 for <webtransport@ietf.org>; Sun, 28 Feb 2021 16:47: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=PXohnOIz6R6magdX7i4qfLQPCsDhn2KpQ6cza5PFr/Y=; b=L+xA4i/Hqhvge9rk2PTuyoJTtFSSaiepQxxsnSoe7TCr2mfu7zgARe3oFyuMdkpE4J Yrd9DG6NroJjzqujzaSsVg+koS3xpFnr6I5455iWPf0rDcA+f4+cx86fyueWupRQFV1I rbtf/01WmUZvJ1sofBxX2gARgKxVUGnoJLAnaAXNKwybg911eTF2DgAh4shatWrPs3oy EnKszNV6bNAwJq7yrRyt91uhLpxlsqEYemiY21CpAepTuXCuAbKLR4JP/5cpyA+3LK78 XUmvsPDDWNw5dEibUPp5lokKObSj5l2dgAswx+LEb0mPd1m4Kfe+fWK4SJjpu0WC0PQS tL1g==
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=PXohnOIz6R6magdX7i4qfLQPCsDhn2KpQ6cza5PFr/Y=; b=P7u/NILagk4xUP16eDRAMjh3Sak9HZHAYO3aE9OMLIEn1xGuSiJfF/QaZLKtGi8s+J X4TcwN1vpvSqwiGD2u8kgGZSSCU+w/YU9Mzi22fdHD5AHAw1+PEs5J46cFKuAjONomrW 8mAZCZ7MUOEq/A3kEvA00s6it+TNzMyHipvIpyhjETkZHGsmtB1M2L8bf2aCfyfXY9n3 cKqMWbwZ6QBaYK8AReyz/0Sp89lqtFbrJiCsbHOKBVHJoYnZR1GveqdcOkKihBnP5+3I TcbEveu6rsc+uzJLdgEVcRAsFPyKdVI7VKFG3TZ0CwF8wXaFvsSh1gbty4kP46eNruQ7 bXRw==
X-Gm-Message-State: AOAM530U10o7my+M136iCpn8ObqhYrhOCpir4cl0sqf3RQ+mnOP4rHZw OpRe5tMaVTrgklgwp1WGMWxsdFNa0Z9YxgNc0khV0tUHSlU=
X-Google-Smtp-Source: ABdhPJy8fLiJLlbOPox9AoqGcctEYE39ZjSsscIvbpRIZejZnF1dlpQiq+0UwQAgZ+kWNkVrbqPhp+09JF7w4FgqHfc=
X-Received: by 2002:a2e:904b:: with SMTP id n11mr7567328ljg.85.1614559664506;  Sun, 28 Feb 2021 16:47:44 -0800 (PST)
MIME-Version: 1.0
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Sun, 28 Feb 2021 16:47:33 -0800
Message-ID: <CAOW+2dtAvdhaMz1JeA01mpyff_zFK7LKr_cuzBrjKHR-H5To_w@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000458bdf05bc6ef78a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/FfBir4ciyBjw-zeHhF3VA5U7wdc>
Subject: [Webtransport] Call for Agenda items: IETF 110 Meeting of the WEBTRANS WG
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, 01 Mar 2021 00:47:57 -0000

--000000000000458bdf05bc6ef78a
Content-Type: text/plain; charset="UTF-8"

This is a call for agenda items at the IETF 110 meeting of the WEBTRANS WG.

If you have an item you'd like to add to the agenda, please contact the
Chairs.

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

<div dir=3D"ltr">This is a call for agenda items at the IETF 110 meeting of=
 the WEBTRANS WG.=C2=A0<div><br></div><div>If you have an item you&#39;d li=
ke to add to the agenda, please=C2=A0contact the Chairs.</div></div>

--000000000000458bdf05bc6ef78a--

