
From nobody Thu Apr  1 10:01:54 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 8F2323A1BAF for <webtransport@ietfa.amsl.com>; Thu,  1 Apr 2021 10:01:53 -0700 (PDT)
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 w8wwmvDQn1x0 for <webtransport@ietfa.amsl.com>; Thu,  1 Apr 2021 10:01:49 -0700 (PDT)
Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (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 E99E53A1BB1 for <webtransport@ietf.org>; Thu,  1 Apr 2021 10:01:48 -0700 (PDT)
Received: by mail-wm1-x330.google.com with SMTP id b2-20020a7bc2420000b029010be1081172so1250759wmj.1 for <webtransport@ietf.org>; Thu, 01 Apr 2021 10:01:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=OE8BaBwS8QnNovqVz8p4FQCkghYT+hN/C9psivx5cVo=; b=Fvnag01cvHhTJQmmLQCeLeVgZTPgK2ZuB8hU3GwvkZkJdFgD71pssfqDZx8wT6xdOw bQl3Ql6HiwWQSP8M6K2U3/+HBcsMPGj2CWUd3g5a6QypL1CPi17t9QCxKG4jNJ4ziZ8l xJ9lRF5zzReQ4H5MfvPquIh1ewUI2kTyujkKoJ1hpxK/ehmO/S14b5r6Sx6zGuHmm0yO AFimtpOsiopE9jtg/JMKrYyBwiKPdWDz99ol7O8qMiiszB1/GzgjUPV6xN1UKv5gYRJm vb3pRdHrsii0Lm9zM0cgHotM3Y+Er6yjIaguDbIifYvopP8GK5XJGD/p+ilTUu6SrQhg 3thQ==
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=OE8BaBwS8QnNovqVz8p4FQCkghYT+hN/C9psivx5cVo=; b=WLZYEBd5dCqnRd4SQfW8eMnTsnSyaTACbAvyXhllXiMVs/8hxVnzNBLnbuVg33NMSx h96NS1SVwxVNsSQ9p5Nhq539TP+YAmUScswhnrT3lGNWF7YaHxQlzuyKw+t8nBSB6Jb2 QEqSkeaBnhsiFbz6MJ6t5q3NkKaFUz1FQ5b44dZ2gUAtE4fwP3zGMXPSLhyKw87uUISS 2i5vs5PuyVudL4zXJI7O6yNE13CEUE3Ih1b/94oO26m3j3hgaP2DCB1nDwYGBlGQDzWX mTknQIy1rrn7doMK6x5IuhyCudjPS6B+HVJJzpbcgfdaY+iQOtjRGU+PpirMvn53F4nl MDTA==
X-Gm-Message-State: AOAM533XS5qTxLrluwDGdy/0ZoB6HgdYIBXYTat7dg2xOMy3IQrbrxhM ss3iYKU/5MyUBouuGbbY0UaYgerFmx8GXkBLQuplm3u8LIZA4g==
X-Google-Smtp-Source: ABdhPJzTHZ1+daIvzdvGtwFzUIsNqREGPL13vFpu32dFJz9TlkPHyyF7XB07/4bEwLPdU4g2OTTDI0I2Ky4G91v4SFQ=
X-Received: by 2002:a7b:ce91:: with SMTP id q17mr9287406wmj.28.1617296505044;  Thu, 01 Apr 2021 10:01:45 -0700 (PDT)
MIME-Version: 1.0
From: Ian Swett <ianswett@google.com>
Date: Thu, 1 Apr 2021 13:00:00 -0400
Message-ID: <CAKcm_gOMcFYF2YROhsbVW15Q+tnWfwGsHhrjxQwq1jJAyvLvVQ@mail.gmail.com>
To: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000aec81b05beec2fb5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/QyzmrD37GhwiPadSZu5FJhKTFIQ>
Subject: [Webtransport] Use of HTTP priorities in WebTransport
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, 01 Apr 2021 17:01:54 -0000

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

Now that WebTransport is targeted at HTTP/3 and not QUIC, it seems logical
to build on the prioritization work in the HTTP priorities draft(
draft-ietf-httpbis-priority
<https://tools.ietf.org/html/draft-ietf-httpbis-priority-03>).  This could
be particularly important when pooling HTTP/3 with WebTransport, but I
think that priority model is a good one for WebTransport by itself as well.

Except for bidi streams, most of this priority information wouldn't need to
be sent on the wire, but it could be used by local schedulers.

Thoughts?

Ian

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

<div dir=3D"ltr">Now that WebTransport is targeted at HTTP/3 and not QUIC, =
it seems logical to build on the prioritization work in the HTTP priorities=
 draft(<a href=3D"https://tools.ietf.org/html/draft-ietf-httpbis-priority-0=
3">draft-ietf-httpbis-priority</a>).=C2=A0 This could be particularly impor=
tant when pooling HTTP/3 with WebTransport, but I think that priority model=
 is a good one for WebTransport by itself as well.<div><br></div><div>Excep=
t for bidi streams, most of this priority information wouldn&#39;t need to =
be sent on the wire, but it could be used by local schedulers.</div><div><b=
r></div><div>Thoughts?</div><div><br></div><div>Ian</div></div>

--000000000000aec81b05beec2fb5--


From nobody Thu Apr  1 16:40:29 2021
Return-Path: <lucaspardue.24.7@gmail.com>
X-Original-To: webtransport@ietfa.amsl.com
Delivered-To: webtransport@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FCD63A2801 for <webtransport@ietfa.amsl.com>; Thu,  1 Apr 2021 16:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (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 T-khPz8OevDq for <webtransport@ietfa.amsl.com>; Thu,  1 Apr 2021 16:40:22 -0700 (PDT)
Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) (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 40D883A2802 for <webtransport@ietf.org>; Thu,  1 Apr 2021 16:40:22 -0700 (PDT)
Received: by mail-ej1-x634.google.com with SMTP id u9so5254819ejj.7 for <webtransport@ietf.org>; Thu, 01 Apr 2021 16:40:21 -0700 (PDT)
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=bIL42/tPD840VIcCji/aqOmvJf3GYU2klh59DT+PbaI=; b=Nb1EYTCUehLB9Tkb/i/Uj0r7OVuU/Axx18GlK4utCKQr/e6FOZ6l35tHLUqD1rwTxo AZTiI5wTLBEiE/wKNYDRJ5/uOS6oG6SVIslHhgDh2FafvyBlhhH0P0xhwfijjM01iUnj xc5xqFpdapMro400+EkBaPtSJaEcFpzt+8c3NvpqRQACDbVI7xAjnfFXiaIp3AovizFS CdpsF585xOp8qwXCDSSMmyEz5/cX7sP2zciYfs4pXIXUjHKtUuoZbp9ztvDAT0MzePFA 81ZUK9vNdEyKrlPvfVUqBhG80AmDyKbK60phG1jYaudZiFmFt16bmRRxq7WYnr8bsSu5 GP0Q==
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=bIL42/tPD840VIcCji/aqOmvJf3GYU2klh59DT+PbaI=; b=Tmykl0qSS5xUsXy6T9qDp5NKJQT/cGOISGPXcfq2dQdLtsWArxYpPw1mvnI5c7dAaV r79b0AuyDGY+WlJgoUX7jThz4obXa9hDTYw2NxRdVNXE43HXqz0NUXwhfge5BffSJXsE PGjI3xyMlAF7hq382vTsgxDWepQXIyhhrF45O4spgt5qiHK4gsYzNK5k+Nny9G3umimi h6HVv5z7x39hX/QPs9bB4vMgkYMoL96n6VRp+iazv8skKQyvHEKOFkLDq4cSVI8dZYFh 59P8ObJ/i0wl4vJQQOPbDWZz5wENJb0W+14vh9K6DSBAZjtKvZTozSoz9+UPN7wLwael NXLg==
X-Gm-Message-State: AOAM5331haBU42uk3WvgGjxy626L325X7o62d7ObvELi5l+rq7FuPueN ByU5h84Hnply5jBKOpb4NTpdv7DQvNtUHT/NIIII7r69
X-Google-Smtp-Source: ABdhPJy/hHbaNSCUC9w0lFxTLJo9aMmnSZCBgxV/PRFybWDFW+217OlDrazALmmeORfmtR71BH+3tMOod5t2k/Iki1M=
X-Received: by 2002:a17:907:2955:: with SMTP id et21mr11554128ejc.448.1617320419075;  Thu, 01 Apr 2021 16:40:19 -0700 (PDT)
MIME-Version: 1.0
References: <CAKcm_gOMcFYF2YROhsbVW15Q+tnWfwGsHhrjxQwq1jJAyvLvVQ@mail.gmail.com>
In-Reply-To: <CAKcm_gOMcFYF2YROhsbVW15Q+tnWfwGsHhrjxQwq1jJAyvLvVQ@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Fri, 2 Apr 2021 00:40:08 +0100
Message-ID: <CALGR9obOXRk=ZxL8Sj9zhsP-wQyv_09doZuzfCSRzquw4CZFYw@mail.gmail.com>
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000112d8605bef1c1ef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/NKB-z2qM0MtcL82vCGtoNA1YxMI>
Subject: Re: [Webtransport] Use of HTTP priorities in WebTransport
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, 01 Apr 2021 23:40:28 -0000

--000000000000112d8605bef1c1ef
Content-Type: text/plain; charset="UTF-8"

Hey Ian,


On Thu, Apr 1, 2021 at 6:01 PM Ian Swett <ianswett=
40google.com@dmarc.ietf.org> wrote:

> Now that WebTransport is targeted at HTTP/3 and not QUIC, it seems logical
> to build on the prioritization work in the HTTP priorities draft(
> draft-ietf-httpbis-priority
> <https://tools.ietf.org/html/draft-ietf-httpbis-priority-03>).  This
> could be particularly important when pooling HTTP/3 with WebTransport, but
> I think that priority model is a good one for WebTransport by itself as
> well.
>
> Except for bidi streams, most of this priority information wouldn't need
> to be sent on the wire, but it could be used by local schedulers.
>
> Thoughts?
>

The HTTP priorities draft is very specific in that it defines an asymmetric
signal from client to server. So I'm curious how you picture it applying to
WebTransport. You're right, the general prioritization scheme might be a
good fit but I'd like to understand the requirements better. Is it only a
local priority configuration from the send side? In which case, this seems
like a W3C API issue. Or is the requirement to support sending priority
signals that instruct the peer to do something too? The hardest case to
solve is a server-initiated bidi stream that wants to signal a priority to
the client. Since WebTransport over HTTP/3 is an extension, you might get
away with changing the rules for PRIORITY_UPDATE. You could define a new
frame that carries the same information, or include it in the WebTransport
stream itself somehow.

Cheers,
Lucas

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

<div dir=3D"ltr"><div dir=3D"ltr"><div>Hey Ian,</div><div><br></div><div></=
div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_at=
tr">On Thu, Apr 1, 2021 at 6:01 PM Ian Swett &lt;ianswett=3D<a href=3D"mail=
to:40google.com@dmarc.ietf.org">40google.com@dmarc.ietf.org</a>&gt; wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"=
>Now that WebTransport is targeted at HTTP/3 and not QUIC, it seems logical=
 to build on the prioritization work in the HTTP priorities draft(<a href=
=3D"https://tools.ietf.org/html/draft-ietf-httpbis-priority-03" target=3D"_=
blank">draft-ietf-httpbis-priority</a>).=C2=A0 This could be particularly i=
mportant when pooling HTTP/3 with WebTransport, but I think that priority m=
odel is a good one for WebTransport by itself as well.<div><br></div><div>E=
xcept for bidi streams, most of this priority information wouldn&#39;t need=
 to be sent on the wire, but it could be used by local schedulers.</div><di=
v><br></div><div>Thoughts?</div></div></blockquote><div><br></div><div>The =
HTTP priorities draft is very specific in that it defines an asymmetric sig=
nal from client to server. So I&#39;m curious how you picture it applying t=
o WebTransport. You&#39;re right, the general prioritization scheme might b=
e a good fit but I&#39;d like to understand the requirements better. Is it =
only a local priority configuration from the send side? In which case, this=
 seems like a W3C API issue. Or is the requirement to support sending prior=
ity signals that instruct the peer to do something too? The hardest case to=
 solve is a server-initiated bidi stream that wants to signal a priority to=
 the client. Since WebTransport over HTTP/3 is an extension, you might get =
away with changing the rules for PRIORITY_UPDATE. You could define a new fr=
ame that carries the same information, or include it in the WebTransport st=
ream itself somehow.</div><div><br></div><div>Cheers,</div><div>Lucas<br></=
div></div></div>

--000000000000112d8605bef1c1ef--


From nobody Mon Apr  5 12:47:47 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 E52173A2534 for <webtransport@ietfa.amsl.com>; Mon,  5 Apr 2021 12:47:44 -0700 (PDT)
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=unavailable 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 GnSp-OG69Ezp for <webtransport@ietfa.amsl.com>; Mon,  5 Apr 2021 12:47:40 -0700 (PDT)
Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (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 A7AB73A2532 for <webtransport@ietf.org>; Mon,  5 Apr 2021 12:47:40 -0700 (PDT)
Received: by mail-wm1-x336.google.com with SMTP id w203-20020a1c49d40000b029010c706d0642so95351wma.0 for <webtransport@ietf.org>; Mon, 05 Apr 2021 12:47:40 -0700 (PDT)
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=pQhOvcGUpTIsF7E795RBxvlpV89Wl/Al109dXezT5vg=; b=HLsSdkn5VZ4YJ9+ilXq15D6E1AR0c4hm4gsqlvZB9YqGMvJF9RRCaYgYBhT82vEDfQ Jpgd/cWbhgSNqoU8y+2Iup/Xy1lL7HNY14heJjwEeISaAf1J/JCLe08jqx/J/bEVK/Zw slzS9mgqUdAA9383W/0w82lR4KjofDQGDag8vcWzJ9UF/ncPO9du2h+Cl/3X6eb2MpeL Qw0AZ59YgRk+PShN/B9bXaO3B0VHcirumVxtX+m916UjxZlrkUTHp+jQYu0cq11vCVzO BLJHBbqireqlsEhlMq6+cPzJUVqVs4n3992NJsEsY4Yj5c6+1J87aeinDAP419yIn8rR L3Vg==
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=pQhOvcGUpTIsF7E795RBxvlpV89Wl/Al109dXezT5vg=; b=jqOaMJk4AgrNn4BRohF1mGyO+8/hy8yDL2cnAntEIm9JoXof8ZI3yTbpKwLre2wzii OtfDwIVBx9X8/lpSFuqG2cgHk+ynl+KD02j7Cp7tsS8AQ3vDSqsw4mgVhO8QBYcePtWY 3oc27mwp3JrweRN15+f3jrJj0yorcjoSM6OGzX6uZSsYEHnBmWEcwiruDGASoPbfDkyz IZzYLIlHBNx5L1puFRZG6lj7bW3mlMXFcq1CSVdTv3x3srxhVdCC/T7XRGYFJ3FuBdrZ mMLpDR8yKZ/47+h03X3gur1Y3ueXkgVPWUG4nWSpfakJVUEwNJ22GFovszFTWVJKkoe+ VX6w==
X-Gm-Message-State: AOAM533OSVrEG4hbuR4+k7it2jIEfkUQTh3mmIeIOB79+VA/RD+Nnq5a BKM88FtwMAwCDHd34B7lg8k28ehsmDpIwx5xh9c=
X-Google-Smtp-Source: ABdhPJwlDGURNqCAJNGkbU7jy1yak8FmPZ4un5pD+2q5WfynwlNwWJt5DnpouYFEy9E0EjKYIYiVqqvS95UwhOAhm0E=
X-Received: by 2002:a1c:b002:: with SMTP id z2mr599010wme.121.1617652057527; Mon, 05 Apr 2021 12:47:37 -0700 (PDT)
MIME-Version: 1.0
References: <CAKcm_gOMcFYF2YROhsbVW15Q+tnWfwGsHhrjxQwq1jJAyvLvVQ@mail.gmail.com> <CALGR9obOXRk=ZxL8Sj9zhsP-wQyv_09doZuzfCSRzquw4CZFYw@mail.gmail.com>
In-Reply-To: <CALGR9obOXRk=ZxL8Sj9zhsP-wQyv_09doZuzfCSRzquw4CZFYw@mail.gmail.com>
From: Luke Curley <kixelated@gmail.com>
Date: Mon, 5 Apr 2021 12:47:26 -0700
Message-ID: <CAHVo=Zmo0Nta92_Ub0m8v6+=hjQ1iR6R9Aa==fe_-VXkhJEJYQ@mail.gmail.com>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>,  WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000425a2805bf3ef88b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/45iOgG3Gkt0XH5wCsmp9dwFOiI8>
Subject: Re: [Webtransport] Use of HTTP priorities in WebTransport
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, 05 Apr 2021 19:47:45 -0000

--000000000000425a2805bf3ef88b
Content-Type: text/plain; charset="UTF-8"

I think stream prioritization is an important next phase for WebTransport.
But like Lucas mentioned, I'm not sure it needs to be handled at the
transport layer.

Currently, the server can prioritize sending stream data based on any
scheme it wants. The browser could inform the server which prioritization
scheme to use for a given stream, but I think that use-case can be
negotiated at the application level instead.

The browser definitely needs an API for prioritizing sending stream data
though and a simple scheme like the priorities draft would be a good
starting point.

On Thu, Apr 1, 2021 at 4:40 PM Lucas Pardue <lucaspardue.24.7@gmail.com>
wrote:

> Hey Ian,
>
>
> On Thu, Apr 1, 2021 at 6:01 PM Ian Swett <ianswett=
> 40google.com@dmarc.ietf.org> wrote:
>
>> Now that WebTransport is targeted at HTTP/3 and not QUIC, it seems
>> logical to build on the prioritization work in the HTTP priorities draft(
>> draft-ietf-httpbis-priority
>> <https://tools.ietf.org/html/draft-ietf-httpbis-priority-03>).  This
>> could be particularly important when pooling HTTP/3 with WebTransport, but
>> I think that priority model is a good one for WebTransport by itself as
>> well.
>>
>> Except for bidi streams, most of this priority information wouldn't need
>> to be sent on the wire, but it could be used by local schedulers.
>>
>> Thoughts?
>>
>
> The HTTP priorities draft is very specific in that it defines an
> asymmetric signal from client to server. So I'm curious how you picture it
> applying to WebTransport. You're right, the general prioritization scheme
> might be a good fit but I'd like to understand the requirements better. Is
> it only a local priority configuration from the send side? In which case,
> this seems like a W3C API issue. Or is the requirement to support sending
> priority signals that instruct the peer to do something too? The hardest
> case to solve is a server-initiated bidi stream that wants to signal a
> priority to the client. Since WebTransport over HTTP/3 is an extension, you
> might get away with changing the rules for PRIORITY_UPDATE. You could
> define a new frame that carries the same information, or include it in the
> WebTransport stream itself somehow.
>
> Cheers,
> Lucas
> --
> Webtransport mailing list
> Webtransport@ietf.org
> https://www.ietf.org/mailman/listinfo/webtransport
>

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

<div dir=3D"ltr">I think stream prioritization is an important next phase f=
or WebTransport. But like Lucas mentioned, I&#39;m not sure it needs to be =
handled at the transport layer.<div><br></div><div>Currently, the=C2=A0serv=
er can prioritize sending stream=C2=A0data based on any scheme it wants. Th=
e browser could inform the server which prioritization scheme to use for a =
given stream, but I think that use-case can=C2=A0be negotiated at the appli=
cation level instead.</div><div><br></div><div>The browser definitely needs=
 an API for prioritizing sending stream data though and a=C2=A0simple schem=
e like the priorities draft would be a good starting point.</div></div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Ap=
r 1, 2021 at 4:40 PM Lucas Pardue &lt;<a href=3D"mailto:lucaspardue.24.7@gm=
ail.com">lucaspardue.24.7@gmail.com</a>&gt; wrote:<br></div><blockquote cla=
ss=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 dir=3D"ltr"><div>H=
ey Ian,</div><div><br></div><div></div></div><br><div class=3D"gmail_quote"=
><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Apr 1, 2021 at 6:01 PM Ian S=
wett &lt;ianswett=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=
=3D"_blank">40google.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Now that WebTranspo=
rt is targeted at HTTP/3 and not QUIC, it seems logical to build on the pri=
oritization work in the HTTP priorities draft(<a href=3D"https://tools.ietf=
.org/html/draft-ietf-httpbis-priority-03" target=3D"_blank">draft-ietf-http=
bis-priority</a>).=C2=A0 This could be particularly important when pooling =
HTTP/3 with WebTransport, but I think that priority model is a good one for=
 WebTransport by itself as well.<div><br></div><div>Except for bidi streams=
, most of this priority information wouldn&#39;t need to be sent on the wir=
e, but it could be used by local schedulers.</div><div><br></div><div>Thoug=
hts?</div></div></blockquote><div><br></div><div>The HTTP priorities draft =
is very specific in that it defines an asymmetric signal from client to ser=
ver. So I&#39;m curious how you picture it applying to WebTransport. You&#3=
9;re right, the general prioritization scheme might be a good fit but I&#39=
;d like to understand the requirements better. Is it only a local priority =
configuration from the send side? In which case, this seems like a W3C API =
issue. Or is the requirement to support sending priority signals that instr=
uct the peer to do something too? The hardest case to solve is a server-ini=
tiated bidi stream that wants to signal a priority to the client. Since Web=
Transport over HTTP/3 is an extension, you might get away with changing the=
 rules for PRIORITY_UPDATE. You could define a new frame that carries the s=
ame information, or include it in the WebTransport stream itself somehow.</=
div><div><br></div><div>Cheers,</div><div>Lucas<br></div></div></div>
-- <br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport=
</a><br>
</blockquote></div>

--000000000000425a2805bf3ef88b--


From nobody Fri Apr 23 14:02:58 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 193903A0C3A for <webtransport@ietfa.amsl.com>; Fri, 23 Apr 2021 14:02:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.6
X-Spam-Level: 
X-Spam-Status: No, score=-17.6 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, 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 H4zW9q_c2IWb for <webtransport@ietfa.amsl.com>; Fri, 23 Apr 2021 14:02:52 -0700 (PDT)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (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 7D92B3A0C38 for <webtransport@ietf.org>; Fri, 23 Apr 2021 14:02:52 -0700 (PDT)
Received: by mail-wr1-x436.google.com with SMTP id h4so40575734wrt.12 for <webtransport@ietf.org>; Fri, 23 Apr 2021 14:02:52 -0700 (PDT)
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=3lweM+RoOLI7mDCIo29sBbFLQJdpDfKXGbcJzqKHxvQ=; b=wNE2PvGgFB3WKrZsAMfJZ5f4UQISeHUUTBHySMWddnOqz49Jdlbgu5FL1w13IogOXR 9BemQuL2tB0gWSFh7eRaJpaYFNpeLyF5Oks37MUMeZSBt5tp2jkYaBXrSU21SFf8wegW r2bx9lP3NTTT8PAtBQ3LjqAukxdM9Le9jv3OJPEOyK+VhYyzHVaYsVHfb2aP3ohS83c+ ZVLPJ/uRvOROPMMwXdRsuie+0ASCzXTbfsElINoiTKKF12A6+X03nJ0n7PwnMW35zsMQ FbzwHzdegeKxCYOWATN1jBmmZuwfWEwuusjqH8P7BvkPL/nsNTtnpF5qc+rogVNWm85G AZGA==
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=3lweM+RoOLI7mDCIo29sBbFLQJdpDfKXGbcJzqKHxvQ=; b=QSpAfDOvegiTewgYO621j5UOUEIZZbrbqT4R8iEA3mprkv6OcGOvwQhkUz5kYmch0b XL/zpkx/G8CfOkQfCVGL+nsJ84NZUBKBqhFte0BF3zJ9A3deLYwAajcin8pT/QOnFTg8 PvF6mzn8EJGwuyIRk3/AHfxeCwsjpOGTOo56tvYbv7kZmBHo2bVsw7HpbjWaDK/JIdLM kM++64NUEAfQPln/fJeDjNw0x2SAq1lx1e37Xoq62c+AmJ4Am9pKb4c126EN937KkXeF D+KjoJqf5rjXy3p6a+XJvuyrTHBYPCLR2sA1Ms1Xwd/Z2nbaakKwC4UCrQRMwqGCMlJC 9n7w==
X-Gm-Message-State: AOAM530z1Pv+vhGSmAbEGAPyx7l2EcdH5SxYOOc4ZVdLCtpo+i82O3+9 2zHWQ5+VSpJ+4tsKmE3bhzrQQLbxSNSFsIVhy06UwQ==
X-Google-Smtp-Source: ABdhPJxfr0tdLZjvEbEfrTnIbkD2e7dxc2cYWhQ3+xVkQsWNIdF3G9fbcCdvCUN1DaF/4uRVhzhjgQR/9X1Jlajb+oE=
X-Received: by 2002:a5d:524d:: with SMTP id k13mr7195048wrc.113.1619211765619;  Fri, 23 Apr 2021 14:02:45 -0700 (PDT)
MIME-Version: 1.0
References: <CAKcm_gOMcFYF2YROhsbVW15Q+tnWfwGsHhrjxQwq1jJAyvLvVQ@mail.gmail.com> <CALGR9obOXRk=ZxL8Sj9zhsP-wQyv_09doZuzfCSRzquw4CZFYw@mail.gmail.com> <CAHVo=Zmo0Nta92_Ub0m8v6+=hjQ1iR6R9Aa==fe_-VXkhJEJYQ@mail.gmail.com>
In-Reply-To: <CAHVo=Zmo0Nta92_Ub0m8v6+=hjQ1iR6R9Aa==fe_-VXkhJEJYQ@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Fri, 23 Apr 2021 17:02:32 -0400
Message-ID: <CAKcm_gN9Ro1+ceNd_Q80oLF6Su6LiqV7UV4zN_g6Fz1K_6e4jg@mail.gmail.com>
To: Luke Curley <kixelated@gmail.com>
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, WebTransport <webtransport@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001b786305c0aa1ef7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/s1QXOuqFbdnbEZDtI97bddflmsY>
Subject: Re: [Webtransport] Use of HTTP priorities in WebTransport
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, 23 Apr 2021 21:02:57 -0000

--0000000000001b786305c0aa1ef7
Content-Type: text/plain; charset="UTF-8"

(sorry for the delay, now caught up from leave)

I agree this is potentially more of a W3C issue to standardize an API than
an IETF issue.

I agree that most of this information would not be sent on the wire, but as
we add functionality to HTTP(ie: WebTransport and MASQUE), it becomes
increasingly important to understand how prioritization might work.
Ideally no explicit signals are necessary and each endpoint knows what to
do, and we can fit WebTransport(and MASQUE) into the existing scheduler so
when multiplexed, there's no ambiguity about what implementations should
send first?

My concern is if there are no rules or APIs for prioritization, different
implementations may make different choices, and the more things which are
multiplexed on a single connection, the more important it becomes.

Ian

On Mon, Apr 5, 2021 at 3:47 PM Luke Curley <kixelated@gmail.com> wrote:

> I think stream prioritization is an important next phase for WebTransport.
> But like Lucas mentioned, I'm not sure it needs to be handled at the
> transport layer.
>
> Currently, the server can prioritize sending stream data based on any
> scheme it wants. The browser could inform the server which prioritization
> scheme to use for a given stream, but I think that use-case can be
> negotiated at the application level instead.
>
> The browser definitely needs an API for prioritizing sending stream data
> though and a simple scheme like the priorities draft would be a good
> starting point.
>
> On Thu, Apr 1, 2021 at 4:40 PM Lucas Pardue <lucaspardue.24.7@gmail.com>
> wrote:
>
>> Hey Ian,
>>
>>
>> On Thu, Apr 1, 2021 at 6:01 PM Ian Swett <ianswett=
>> 40google.com@dmarc.ietf.org> wrote:
>>
>>> Now that WebTransport is targeted at HTTP/3 and not QUIC, it seems
>>> logical to build on the prioritization work in the HTTP priorities draft(
>>> draft-ietf-httpbis-priority
>>> <https://tools.ietf.org/html/draft-ietf-httpbis-priority-03>).  This
>>> could be particularly important when pooling HTTP/3 with WebTransport, but
>>> I think that priority model is a good one for WebTransport by itself as
>>> well.
>>>
>>> Except for bidi streams, most of this priority information wouldn't need
>>> to be sent on the wire, but it could be used by local schedulers.
>>>
>>> Thoughts?
>>>
>>
>> The HTTP priorities draft is very specific in that it defines an
>> asymmetric signal from client to server. So I'm curious how you picture it
>> applying to WebTransport. You're right, the general prioritization scheme
>> might be a good fit but I'd like to understand the requirements better. Is
>> it only a local priority configuration from the send side? In which case,
>> this seems like a W3C API issue. Or is the requirement to support sending
>> priority signals that instruct the peer to do something too? The hardest
>> case to solve is a server-initiated bidi stream that wants to signal a
>> priority to the client. Since WebTransport over HTTP/3 is an extension, you
>> might get away with changing the rules for PRIORITY_UPDATE. You could
>> define a new frame that carries the same information, or include it in the
>> WebTransport stream itself somehow.
>>
>> Cheers,
>> Lucas
>> --
>> Webtransport mailing list
>> Webtransport@ietf.org
>> https://www.ietf.org/mailman/listinfo/webtransport
>>
>

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

<div dir=3D"ltr"><div>(sorry for the delay, now caught up from leave)</div>=
<div><br></div>I agree this=C2=A0is potentially more of a W3C issue to stan=
dardize an API than an IETF issue.<div><br></div><div>I agree that most of =
this information would not be sent on the wire, but as we add functionality=
 to HTTP(ie: WebTransport and MASQUE), it becomes increasingly important to=
 understand=C2=A0how prioritization might work.=C2=A0 Ideally no explicit s=
ignals are necessary and each endpoint knows=C2=A0what to do, and we can fi=
t WebTransport(and MASQUE) into the existing scheduler so when multiplexed,=
 there&#39;s no ambiguity about what implementations should send first?</di=
v><div><br></div><div>My concern is if there are no rules or APIs for prior=
itization, different implementations may make different choices, and the mo=
re things which=C2=A0are multiplexed on a single connection, the more impor=
tant it becomes.</div><div><br></div><div>Ian</div></div><br><div class=3D"=
gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Apr 5, 2021 at 3=
:47 PM Luke Curley &lt;<a href=3D"mailto:kixelated@gmail.com">kixelated@gma=
il.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex"><div dir=3D"ltr">I think stream prioritization is an important next p=
hase for WebTransport. But like Lucas mentioned, I&#39;m not sure it needs =
to be handled at the transport layer.<div><br></div><div>Currently, the=C2=
=A0server can prioritize sending stream=C2=A0data based on any scheme it wa=
nts. The browser could inform the server which prioritization scheme to use=
 for a given stream, but I think that use-case can=C2=A0be negotiated at th=
e application level instead.</div><div><br></div><div>The browser definitel=
y needs an API for prioritizing sending stream data though and a=C2=A0simpl=
e scheme like the priorities draft would be a good starting point.</div></d=
iv><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On =
Thu, Apr 1, 2021 at 4:40 PM Lucas Pardue &lt;<a href=3D"mailto:lucaspardue.=
24.7@gmail.com" target=3D"_blank">lucaspardue.24.7@gmail.com</a>&gt; wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr=
"><div dir=3D"ltr"><div>Hey Ian,</div><div><br></div><div></div></div><br><=
div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Apr=
 1, 2021 at 6:01 PM Ian Swett &lt;ianswett=3D<a href=3D"mailto:40google.com=
@dmarc.ietf.org" target=3D"_blank">40google.com@dmarc.ietf.org</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">Now that WebTransport is targeted at HTTP/3 and not QUIC, it seems logi=
cal to build on the prioritization work in the HTTP priorities draft(<a hre=
f=3D"https://tools.ietf.org/html/draft-ietf-httpbis-priority-03" target=3D"=
_blank">draft-ietf-httpbis-priority</a>).=C2=A0 This could be particularly =
important when pooling HTTP/3 with WebTransport, but I think that priority =
model is a good one for WebTransport by itself as well.<div><br></div><div>=
Except for bidi streams, most of this priority information wouldn&#39;t nee=
d to be sent on the wire, but it could be used by local schedulers.</div><d=
iv><br></div><div>Thoughts?</div></div></blockquote><div><br></div><div>The=
 HTTP priorities draft is very specific in that it defines an asymmetric si=
gnal from client to server. So I&#39;m curious how you picture it applying =
to WebTransport. You&#39;re right, the general prioritization scheme might =
be a good fit but I&#39;d like to understand the requirements better. Is it=
 only a local priority configuration from the send side? In which case, thi=
s seems like a W3C API issue. Or is the requirement to support sending prio=
rity signals that instruct the peer to do something too? The hardest case t=
o solve is a server-initiated bidi stream that wants to signal a priority t=
o the client. Since WebTransport over HTTP/3 is an extension, you might get=
 away with changing the rules for PRIORITY_UPDATE. You could define a new f=
rame that carries the same information, or include it in the WebTransport s=
tream itself somehow.</div><div><br></div><div>Cheers,</div><div>Lucas<br><=
/div></div></div>
-- <br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport=
</a><br>
</blockquote></div>
</blockquote></div>

--0000000000001b786305c0aa1ef7--


From nobody Fri Apr 23 18:31:28 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 30EA73A1939 for <webtransport@ietfa.amsl.com>; Fri, 23 Apr 2021 18:31:27 -0700 (PDT)
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 LRuVUQw7XoDi for <webtransport@ietfa.amsl.com>; Fri, 23 Apr 2021 18:31:25 -0700 (PDT)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (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 071903A1933 for <webtransport@ietf.org>; Fri, 23 Apr 2021 18:31:24 -0700 (PDT)
Received: by mail-lf1-x131.google.com with SMTP id x19so49737402lfa.2 for <webtransport@ietf.org>; Fri, 23 Apr 2021 18:31:24 -0700 (PDT)
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=jutd4ke2QLLYFOee6kEE6pX2ceP4mw8ZfTQaXPn7g5Q=; b=Rr6oD41KHgrgRMnZ5cbJOhW9HpjkQ9NdneO76u8K7WSJfIbcsPcEi8cRd0gEv9BitO aM3EfFiHSi9UpoP0POfL65ilaUpYuoM1IdQXFQqRzu005TaH9zdQAWiT8g/VbbmjPZlX 5LbSbiKqV5jj7msWf3aWkZki8tBciHqN5To0NRskRBAbFio/MLKkVmMbUNwCPzslnbJC vMGvyK6RczbBS9sEXOitjC9vxqAz+p+W72uTDxA43yLC2R6l6OAYYYsEzdAsinVerP+i /GdbYEkMy58ti7Dsti/a8+SxSkQeuEFEnX2Wyt5gSEgizNILwEqi0fduV+qgrwYR2PW3 D7Ug==
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=jutd4ke2QLLYFOee6kEE6pX2ceP4mw8ZfTQaXPn7g5Q=; b=PwGTB35MIrk5XkvwuW0YfsYLgP8Zqq5FISzkpV9js5ycAAbYTfz6IHiKyEEfZf7O+P QOJllfWMhle+A7cj8uiXIHQggFVTJwRYPgYwbTHsxKobM/2LcLdxoFI2Xp22srpYtzEp OKvfwiYuL5UVy7FxV7RsmnbMT5L7fpvWCCvjjaWsicYtFTDCqc+E0qMTRRWLT5uzfGYB EVdsHMf80v3MPdLVibaQSQVj+jJbHpugm5GXxKVFmMPsY6ycw57N5JpnuywXKnG/JaEq u0O9pbVh2MY7KDLy1mUvH5FCr+CC3ZIVz7kMCw6IUfEebo5+0hTiCLpWJLS05EEVXqXa Gz5A==
X-Gm-Message-State: AOAM531vmklQQEUEM+/TSlCj695dOfpy5of6+AfdhwMpK82kCzaX+QAP VQH3A+aKGuCy3aJRHjp9cszD3ElD6OlEtR6o3W0=
X-Google-Smtp-Source: ABdhPJz5EmIBL8AcuBKaeh1fEUCjULuAH5H3wNLbXyGz5P8S5v5oZQmZOoIFxIVjIi/jIsXmXS2UIe37TWfyw80t/jE=
X-Received: by 2002:a05:6512:3ca9:: with SMTP id h41mr4910185lfv.145.1619227882329;  Fri, 23 Apr 2021 18:31:22 -0700 (PDT)
MIME-Version: 1.0
References: <CAKcm_gOMcFYF2YROhsbVW15Q+tnWfwGsHhrjxQwq1jJAyvLvVQ@mail.gmail.com> <CALGR9obOXRk=ZxL8Sj9zhsP-wQyv_09doZuzfCSRzquw4CZFYw@mail.gmail.com> <CAHVo=Zmo0Nta92_Ub0m8v6+=hjQ1iR6R9Aa==fe_-VXkhJEJYQ@mail.gmail.com> <CAKcm_gN9Ro1+ceNd_Q80oLF6Su6LiqV7UV4zN_g6Fz1K_6e4jg@mail.gmail.com>
In-Reply-To: <CAKcm_gN9Ro1+ceNd_Q80oLF6Su6LiqV7UV4zN_g6Fz1K_6e4jg@mail.gmail.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Fri, 23 Apr 2021 18:31:11 -0700
Message-ID: <CAOW+2ds2yn5Cr-VjqB51WmB=d++TXKxscb5zX7BsAFuNGeXzvQ@mail.gmail.com>
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: Luke Curley <kixelated@gmail.com>, WebTransport <webtransport@ietf.org>,  Lucas Pardue <lucaspardue.24.7@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000bc9b2205c0adde24"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/JudZRpArpr8tjTmVdgmdFoRzXrs>
Subject: Re: [Webtransport] Use of HTTP priorities in WebTransport
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, 24 Apr 2021 01:31:27 -0000

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

Ian said:

"I agree this is potentially more of a W3C issue to standardize an API than
an IETF issue."

[BA ]I'm aware of an example of a priority API
<https://www.w3.org/blog/news/archives/8969>.  But implementations seem to
be scarce.  Is there an example of a successful W3C API
supporting priority?

On Fri, Apr 23, 2021 at 2:03 PM Ian Swett <ianswett=
40google.com@dmarc.ietf.org> wrote:

> (sorry for the delay, now caught up from leave)
>
> I agree this is potentially more of a W3C issue to standardize an API than
> an IETF issue.
>
> I agree that most of this information would not be sent on the wire, but
> as we add functionality to HTTP(ie: WebTransport and MASQUE), it becomes
> increasingly important to understand how prioritization might work.
> Ideally no explicit signals are necessary and each endpoint knows what to
> do, and we can fit WebTransport(and MASQUE) into the existing scheduler so
> when multiplexed, there's no ambiguity about what implementations should
> send first?
>
> My concern is if there are no rules or APIs for prioritization, different
> implementations may make different choices, and the more things which are
> multiplexed on a single connection, the more important it becomes.
>
> Ian
>
> On Mon, Apr 5, 2021 at 3:47 PM Luke Curley <kixelated@gmail.com> wrote:
>
>> I think stream prioritization is an important next phase for
>> WebTransport. But like Lucas mentioned, I'm not sure it needs to be handled
>> at the transport layer.
>>
>> Currently, the server can prioritize sending stream data based on any
>> scheme it wants. The browser could inform the server which prioritization
>> scheme to use for a given stream, but I think that use-case can be
>> negotiated at the application level instead.
>>
>> The browser definitely needs an API for prioritizing sending stream data
>> though and a simple scheme like the priorities draft would be a good
>> starting point.
>>
>> On Thu, Apr 1, 2021 at 4:40 PM Lucas Pardue <lucaspardue.24.7@gmail.com>
>> wrote:
>>
>>> Hey Ian,
>>>
>>>
>>> On Thu, Apr 1, 2021 at 6:01 PM Ian Swett <ianswett=
>>> 40google.com@dmarc.ietf.org> wrote:
>>>
>>>> Now that WebTransport is targeted at HTTP/3 and not QUIC, it seems
>>>> logical to build on the prioritization work in the HTTP priorities draft(
>>>> draft-ietf-httpbis-priority
>>>> <https://tools.ietf.org/html/draft-ietf-httpbis-priority-03>).  This
>>>> could be particularly important when pooling HTTP/3 with WebTransport, but
>>>> I think that priority model is a good one for WebTransport by itself as
>>>> well.
>>>>
>>>> Except for bidi streams, most of this priority information wouldn't
>>>> need to be sent on the wire, but it could be used by local schedulers.
>>>>
>>>> Thoughts?
>>>>
>>>
>>> The HTTP priorities draft is very specific in that it defines an
>>> asymmetric signal from client to server. So I'm curious how you picture it
>>> applying to WebTransport. You're right, the general prioritization scheme
>>> might be a good fit but I'd like to understand the requirements better. Is
>>> it only a local priority configuration from the send side? In which case,
>>> this seems like a W3C API issue. Or is the requirement to support sending
>>> priority signals that instruct the peer to do something too? The hardest
>>> case to solve is a server-initiated bidi stream that wants to signal a
>>> priority to the client. Since WebTransport over HTTP/3 is an extension, you
>>> might get away with changing the rules for PRIORITY_UPDATE. You could
>>> define a new frame that carries the same information, or include it in the
>>> WebTransport stream itself somehow.
>>>
>>> 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
>

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

<div dir=3D"ltr"><div dir=3D"ltr">Ian said:=C2=A0<div><br></div><div>&quot;=
I agree this=C2=A0is potentially more of a W3C issue to standardize an API =
than an IETF issue.&quot;</div><div><br></div><div>[BA ]I&#39;m aware of an=
 example of a=C2=A0<a href=3D"https://www.w3.org/blog/news/archives/8969">p=
riority API</a>.=C2=A0 But implementations seem to be scarce.=C2=A0 Is ther=
e an example of a successful W3C API supporting=C2=A0priority?=C2=A0</div><=
/div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_a=
ttr">On Fri, Apr 23, 2021 at 2:03 PM Ian Swett &lt;ianswett=3D<a href=3D"ma=
ilto:40google.com@dmarc.ietf.org">40google.com@dmarc.ietf.org</a>&gt; wrote=
:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"lt=
r"><div>(sorry for the delay, now caught up from leave)</div><div><br></div=
>I agree this=C2=A0is potentially more of a W3C issue to standardize an API=
 than an IETF issue.<div><br></div><div>I agree that most of this informati=
on would not be sent on the wire, but as we add functionality to HTTP(ie: W=
ebTransport and MASQUE), it becomes increasingly important to understand=C2=
=A0how prioritization might work.=C2=A0 Ideally no explicit signals are nec=
essary and each endpoint knows=C2=A0what to do, and we can fit WebTransport=
(and MASQUE) into the existing scheduler so when multiplexed, there&#39;s n=
o ambiguity about what implementations should send first?</div><div><br></d=
iv><div>My concern is if there are no rules or APIs for prioritization, dif=
ferent implementations may make different choices, and the more things whic=
h=C2=A0are multiplexed on a single connection, the more important it become=
s.</div><div><br></div><div>Ian</div></div><br><div class=3D"gmail_quote"><=
div dir=3D"ltr" class=3D"gmail_attr">On Mon, Apr 5, 2021 at 3:47 PM Luke Cu=
rley &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">I think stream prioritization is an important n=
ext phase for WebTransport. But like Lucas mentioned, I&#39;m not sure it n=
eeds to be handled at the transport layer.<div><br></div><div>Currently, th=
e=C2=A0server can prioritize sending stream=C2=A0data based on any scheme i=
t wants. The browser could inform the server which prioritization scheme to=
 use for a given stream, but I think that use-case can=C2=A0be negotiated a=
t the application level instead.</div><div><br></div><div>The browser defin=
itely needs an API for prioritizing sending stream data though and a=C2=A0s=
imple scheme like the priorities draft would be a good starting point.</div=
></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr"=
>On Thu, Apr 1, 2021 at 4:40 PM Lucas Pardue &lt;<a href=3D"mailto:lucaspar=
due.24.7@gmail.com" target=3D"_blank">lucaspardue.24.7@gmail.com</a>&gt; wr=
ote:<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 dir=3D"ltr"><div>Hey Ian,</div><div><br></div><div></div></div><=
br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu,=
 Apr 1, 2021 at 6:01 PM Ian Swett &lt;ianswett=3D<a href=3D"mailto:40google=
.com@dmarc.ietf.org" target=3D"_blank">40google.com@dmarc.ietf.org</a>&gt; =
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr">Now that WebTransport is targeted at HTTP/3 and not QUIC, it seems=
 logical to build on the prioritization work in the HTTP priorities draft(<=
a href=3D"https://tools.ietf.org/html/draft-ietf-httpbis-priority-03" targe=
t=3D"_blank">draft-ietf-httpbis-priority</a>).=C2=A0 This could be particul=
arly important when pooling HTTP/3 with WebTransport, but I think that prio=
rity model is a good one for WebTransport by itself as well.<div><br></div>=
<div>Except for bidi streams, most of this priority information wouldn&#39;=
t need to be sent on the wire, but it could be used by local schedulers.</d=
iv><div><br></div><div>Thoughts?</div></div></blockquote><div><br></div><di=
v>The HTTP priorities draft is very specific in that it defines an asymmetr=
ic signal from client to server. So I&#39;m curious how you picture it appl=
ying to WebTransport. You&#39;re right, the general prioritization scheme m=
ight be a good fit but I&#39;d like to understand the requirements better. =
Is it only a local priority configuration from the send side? In which case=
, this seems like a W3C API issue. Or is the requirement to support sending=
 priority signals that instruct the peer to do something too? The hardest c=
ase to solve is a server-initiated bidi stream that wants to signal a prior=
ity to the client. Since WebTransport over HTTP/3 is an extension, you migh=
t get away with changing the rules for PRIORITY_UPDATE. You could define a =
new frame that carries the same information, or include it in the WebTransp=
ort stream itself somehow.</div><div><br></div><div>Cheers,</div><div>Lucas=
<br></div></div></div>
-- <br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport=
</a><br>
</blockquote></div>
</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>

--000000000000bc9b2205c0adde24--


From nobody Sun Apr 25 19:49:14 2021
Return-Path: <kinuko@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 9AA0D3A1255 for <webtransport@ietfa.amsl.com>; Sun, 25 Apr 2021 19:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.25
X-Spam-Level: 
X-Spam-Status: No, score=-9.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=chromium.org
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 M1a_VFSlcMfh for <webtransport@ietfa.amsl.com>; Sun, 25 Apr 2021 19:49:09 -0700 (PDT)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 8E8293A1250 for <webtransport@ietf.org>; Sun, 25 Apr 2021 19:49:09 -0700 (PDT)
Received: by mail-wm1-x332.google.com with SMTP id l189-20020a1cbbc60000b0290140319ad207so1890014wmf.2 for <webtransport@ietf.org>; Sun, 25 Apr 2021 19:49:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hkEb9CV18IGjBKB8C45Jzn2yuJFcCsVb0RfRrTyJmrQ=; b=htUm/sgPWQ7krJ4dlPAOd0lAl3ejmCou/IizpDSQUKugu34td+ykWeYKtjvLeJNJSv KKTYOvMzzTWpNIlazJeMV7bv+tKCYJNVP3Gj1g2h/AY6X1vjwuakZeXlWoK81XtQ9CwZ SJv6fiLZjbhIrkgVb6U6eB4V0zJ8ol1c4d6o4=
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=hkEb9CV18IGjBKB8C45Jzn2yuJFcCsVb0RfRrTyJmrQ=; b=eb3Iswohfg/PIs0zLdXChmA1kem8mWR8rS3kLiroV5Y+kFW2O8NOB27VnLAO1u7t6X b3Ut4OB/+PoM3GTqLm/NzUWFt2yxNwGJPdxvxoCHLWb37jVyGOgIa0eHvIQ5H7tYVNrP ehiqpRKwxTSImAIihvcU4J2voNZyuyil5XVeGMy1u/sirOpKdOy0sj2Qj7UK3h0Gh1ot gjcHGunIrjwTYSVtZPwvtpZOG8GUpMO69h8ZW6kNiKtaDg8WzdTcPDnuPOnt8mKKMBYw v9QKLuNsAjh27BGHn5GJX2Hya0U752oEIds/1jN4Drv7cUeqLhDlzZct3Gw/f4gzc7hb y6ig==
X-Gm-Message-State: AOAM531oyBxvCVKOKGMxjZFjIYJn6gdpQODa5Ly1gECNU9FpdVsiPkby OaEavdNVjxs64PNVzOl1dvvv4MpUEqoFDALj/ALiEA==
X-Google-Smtp-Source: ABdhPJxguFLrxF+O33PfRGwVEwN6B9iD4+4Ah1PpSWmOI304yp+SuT2PVJOaSQ94OcaYwObv8ltr0dWD8t23yKWd87o=
X-Received: by 2002:a1c:4d0d:: with SMTP id o13mr5700520wmh.26.1619405346826;  Sun, 25 Apr 2021 19:49:06 -0700 (PDT)
MIME-Version: 1.0
References: <CAKcm_gOMcFYF2YROhsbVW15Q+tnWfwGsHhrjxQwq1jJAyvLvVQ@mail.gmail.com> <CALGR9obOXRk=ZxL8Sj9zhsP-wQyv_09doZuzfCSRzquw4CZFYw@mail.gmail.com> <CAHVo=Zmo0Nta92_Ub0m8v6+=hjQ1iR6R9Aa==fe_-VXkhJEJYQ@mail.gmail.com> <CAKcm_gN9Ro1+ceNd_Q80oLF6Su6LiqV7UV4zN_g6Fz1K_6e4jg@mail.gmail.com> <CAOW+2ds2yn5Cr-VjqB51WmB=d++TXKxscb5zX7BsAFuNGeXzvQ@mail.gmail.com>
In-Reply-To: <CAOW+2ds2yn5Cr-VjqB51WmB=d++TXKxscb5zX7BsAFuNGeXzvQ@mail.gmail.com>
From: Kinuko Yasuda <kinuko@chromium.org>
Date: Mon, 26 Apr 2021 11:48:55 +0900
Message-ID: <CAMWgRNawrEYasohE5qk_NY+6tzA3A-6tqZJbiLJ0g7J5BvuXMA@mail.gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>,  WebTransport <webtransport@ietf.org>, Luke Curley <kixelated@gmail.com>,  Lucas Pardue <lucaspardue.24.7@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000007249dc05c0d7301b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/52Xtklzg3ADCWOOGUktv4H8Fhjo>
Subject: Re: [Webtransport] Use of HTTP priorities in WebTransport
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, 26 Apr 2021 02:49:13 -0000

--0000000000007249dc05c0d7301b
Content-Type: text/plain; charset="UTF-8"

Fyi, reg: priority API at web layer, there's an API proposal for resource
loading prioritization that tries to give the priority info as a
"importance hint" (of low, medium, high) rather than concrete priority
value.  This approach has some benefits as UA could still affect and take
care of relative priorities, and got positive buy-ins from developers.
(This hasn't shipped yet though...) I suspect the same/similar attribute
might work here.

https://wicg.github.io/priority-hints/


On Sat, Apr 24, 2021 at 10:31 AM Bernard Aboba <bernard.aboba@gmail.com>
wrote:

> Ian said:
>
> "I agree this is potentially more of a W3C issue to standardize an API
> than an IETF issue."
>
> [BA ]I'm aware of an example of a priority API
> <https://www.w3.org/blog/news/archives/8969>.  But implementations seem
> to be scarce.  Is there an example of a successful W3C API
> supporting priority?
>
> On Fri, Apr 23, 2021 at 2:03 PM Ian Swett <ianswett=
> 40google.com@dmarc.ietf.org> wrote:
>
>> (sorry for the delay, now caught up from leave)
>>
>> I agree this is potentially more of a W3C issue to standardize an API
>> than an IETF issue.
>>
>> I agree that most of this information would not be sent on the wire, but
>> as we add functionality to HTTP(ie: WebTransport and MASQUE), it becomes
>> increasingly important to understand how prioritization might work.
>> Ideally no explicit signals are necessary and each endpoint knows what to
>> do, and we can fit WebTransport(and MASQUE) into the existing scheduler so
>> when multiplexed, there's no ambiguity about what implementations should
>> send first?
>>
>> My concern is if there are no rules or APIs for prioritization, different
>> implementations may make different choices, and the more things which are
>> multiplexed on a single connection, the more important it becomes.
>>
>> Ian
>>
>> On Mon, Apr 5, 2021 at 3:47 PM Luke Curley <kixelated@gmail.com> wrote:
>>
>>> I think stream prioritization is an important next phase for
>>> WebTransport. But like Lucas mentioned, I'm not sure it needs to be handled
>>> at the transport layer.
>>>
>>> Currently, the server can prioritize sending stream data based on any
>>> scheme it wants. The browser could inform the server which prioritization
>>> scheme to use for a given stream, but I think that use-case can be
>>> negotiated at the application level instead.
>>>
>>> The browser definitely needs an API for prioritizing sending stream data
>>> though and a simple scheme like the priorities draft would be a good
>>> starting point.
>>>
>>> On Thu, Apr 1, 2021 at 4:40 PM Lucas Pardue <lucaspardue.24.7@gmail.com>
>>> wrote:
>>>
>>>> Hey Ian,
>>>>
>>>>
>>>> On Thu, Apr 1, 2021 at 6:01 PM Ian Swett <ianswett=
>>>> 40google.com@dmarc.ietf.org> wrote:
>>>>
>>>>> Now that WebTransport is targeted at HTTP/3 and not QUIC, it seems
>>>>> logical to build on the prioritization work in the HTTP priorities draft(
>>>>> draft-ietf-httpbis-priority
>>>>> <https://tools.ietf.org/html/draft-ietf-httpbis-priority-03>).  This
>>>>> could be particularly important when pooling HTTP/3 with WebTransport, but
>>>>> I think that priority model is a good one for WebTransport by itself as
>>>>> well.
>>>>>
>>>>> Except for bidi streams, most of this priority information wouldn't
>>>>> need to be sent on the wire, but it could be used by local schedulers.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>
>>>> The HTTP priorities draft is very specific in that it defines an
>>>> asymmetric signal from client to server. So I'm curious how you picture it
>>>> applying to WebTransport. You're right, the general prioritization scheme
>>>> might be a good fit but I'd like to understand the requirements better. Is
>>>> it only a local priority configuration from the send side? In which case,
>>>> this seems like a W3C API issue. Or is the requirement to support sending
>>>> priority signals that instruct the peer to do something too? The hardest
>>>> case to solve is a server-initiated bidi stream that wants to signal a
>>>> priority to the client. Since WebTransport over HTTP/3 is an extension, you
>>>> might get away with changing the rules for PRIORITY_UPDATE. You could
>>>> define a new frame that carries the same information, or include it in the
>>>> WebTransport stream itself somehow.
>>>>
>>>> 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
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small;color:#000000">Fyi, reg: priority API at=
 web layer, there&#39;s an API proposal for resource loading prioritization=
 that tries to give the priority info as a &quot;importance hint&quot; (of =
low, medium, high) rather than concrete priority value.=C2=A0 This approach=
 has some benefits as UA could still affect and take care of relative prior=
ities, and got=C2=A0positive=C2=A0buy-ins from developers.=C2=A0 (This hasn=
&#39;t shipped yet though...) I suspect the same/similar attribute might wo=
rk here.</div><div class=3D"gmail_default" style=3D"font-family:arial,helve=
tica,sans-serif;font-size:small;color:#000000"><br></div><div class=3D"gmai=
l_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;=
color:#000000"><a href=3D"https://wicg.github.io/priority-hints/">https://w=
icg.github.io/priority-hints/</a><br></div><div class=3D"gmail_default" sty=
le=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#000000"=
><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Sat, Apr 24, 2021 at 10:31 AM Bernard Aboba &lt;<a href=3D"ma=
ilto:bernard.aboba@gmail.com">bernard.aboba@gmail.com</a>&gt; wrote:<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div =
dir=3D"ltr">Ian said:=C2=A0<div><br></div><div>&quot;I agree this=C2=A0is p=
otentially more of a W3C issue to standardize an API than an IETF issue.&qu=
ot;</div><div><br></div><div>[BA ]I&#39;m aware of an example of a=C2=A0<a =
href=3D"https://www.w3.org/blog/news/archives/8969" target=3D"_blank">prior=
ity API</a>.=C2=A0 But implementations seem to be scarce.=C2=A0 Is there an=
 example of a successful W3C API supporting=C2=A0priority?=C2=A0</div></div=
></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr"=
>On Fri, Apr 23, 2021 at 2:03 PM Ian Swett &lt;ianswett=3D<a href=3D"mailto=
:40google.com@dmarc.ietf.org" target=3D"_blank">40google.com@dmarc.ietf.org=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
<div dir=3D"ltr"><div>(sorry for the delay, now caught up from leave)</div>=
<div><br></div>I agree this=C2=A0is potentially more of a W3C issue to stan=
dardize an API than an IETF issue.<div><br></div><div>I agree that most of =
this information would not be sent on the wire, but as we add functionality=
 to HTTP(ie: WebTransport and MASQUE), it becomes increasingly important to=
 understand=C2=A0how prioritization might work.=C2=A0 Ideally no explicit s=
ignals are necessary and each endpoint knows=C2=A0what to do, and we can fi=
t WebTransport(and MASQUE) into the existing scheduler so when multiplexed,=
 there&#39;s no ambiguity about what implementations should send first?</di=
v><div><br></div><div>My concern is if there are no rules or APIs for prior=
itization, different implementations may make different choices, and the mo=
re things which=C2=A0are multiplexed on a single connection, the more impor=
tant it becomes.</div><div><br></div><div>Ian</div></div><br><div class=3D"=
gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Apr 5, 2021 at 3=
:47 PM Luke Curley &lt;<a href=3D"mailto:kixelated@gmail.com" target=3D"_bl=
ank">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">I think stream prioritization is a=
n important next phase for WebTransport. But like Lucas mentioned, I&#39;m =
not sure it needs to be handled at the transport layer.<div><br></div><div>=
Currently, the=C2=A0server can prioritize sending stream=C2=A0data based on=
 any scheme it wants. The browser could inform the server which prioritizat=
ion scheme to use for a given stream, but I think that use-case can=C2=A0be=
 negotiated at the application level instead.</div><div><br></div><div>The =
browser definitely needs an API for prioritizing sending stream data though=
 and a=C2=A0simple scheme like the priorities draft would be a good startin=
g point.</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Thu, Apr 1, 2021 at 4:40 PM Lucas Pardue &lt;<a href=3D"=
mailto:lucaspardue.24.7@gmail.com" target=3D"_blank">lucaspardue.24.7@gmail=
.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hey Ian,</div><div><br></div><di=
v></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmai=
l_attr">On Thu, Apr 1, 2021 at 6:01 PM Ian Swett &lt;ianswett=3D<a href=3D"=
mailto:40google.com@dmarc.ietf.org" target=3D"_blank">40google.com@dmarc.ie=
tf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex"><div dir=3D"ltr">Now that WebTransport is targeted at HTTP/3 and not =
QUIC, it seems logical to build on the prioritization work in the HTTP prio=
rities draft(<a href=3D"https://tools.ietf.org/html/draft-ietf-httpbis-prio=
rity-03" target=3D"_blank">draft-ietf-httpbis-priority</a>).=C2=A0 This cou=
ld be particularly important when pooling HTTP/3 with WebTransport, but I t=
hink that priority model is a good one for WebTransport by itself as well.<=
div><br></div><div>Except for bidi streams, most of this priority informati=
on wouldn&#39;t need to be sent on the wire, but it could be used by local =
schedulers.</div><div><br></div><div>Thoughts?</div></div></blockquote><div=
><br></div><div>The HTTP priorities draft is very specific in that it defin=
es an asymmetric signal from client to server. So I&#39;m curious how you p=
icture it applying to WebTransport. You&#39;re right, the general prioritiz=
ation scheme might be a good fit but I&#39;d like to understand the require=
ments better. Is it only a local priority configuration from the send side?=
 In which case, this seems like a W3C API issue. Or is the requirement to s=
upport sending priority signals that instruct the peer to do something too?=
 The hardest case to solve is a server-initiated bidi stream that wants to =
signal a priority to the client. Since WebTransport over HTTP/3 is an exten=
sion, you might get away with changing the rules for PRIORITY_UPDATE. You c=
ould define a new frame that carries the same information, or include it in=
 the WebTransport stream itself somehow.</div><div><br></div><div>Cheers,</=
div><div>Lucas<br></div></div></div>
-- <br>
Webtransport mailing list<br>
<a href=3D"mailto:Webtransport@ietf.org" target=3D"_blank">Webtransport@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webtransport" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/webtransport=
</a><br>
</blockquote></div>
</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>
-- <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>

--0000000000007249dc05c0d7301b--


From nobody Tue Apr 27 16:40:26 2021
Return-Path: <session-request@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 A2A153A2530; Tue, 27 Apr 2021 16:40:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: bernard.aboba@gmail.com, francesca.palombini@ericsson.com, webtrans-chairs@ietf.org, webtransport@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.28.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161956682453.12580.9182746490028929074@ietfa.amsl.com>
Date: Tue, 27 Apr 2021 16:40:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/ipwozTYN7J7JJfnMVoYeMxpYj1o>
Subject: [Webtransport] webtrans - New Meeting Session Request for IETF 111
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: Tue, 27 Apr 2021 23:40:25 -0000

A new meeting session request has just been submitted by Bernard Aboba, a Chair of the webtrans working group.


---------------------------------------------------------
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: 100
Conflicts to Avoid: 
 Chair Conflict:  avtcore masque sframe
 Technology Overlap:  quic httpbis artarea






People who must be present:
  Bernard Aboba
  David Schinazi
  Francesca Palombini

Resources Requested:

Special Requests:
  
---------------------------------------------------------


