Re: Call for Adoption: Extensible Prioritization Scheme for HTTP

I strongly support adoption. We don't want to end up with a gap in client
priority due to the h3 transition so timeliness matters. The broad input it
has already received makes it the right candidate for the WG to begin work
on - the core tension around e2e vs hop-2-hop is one we have in a number of
places and is something we might just have to focus on how we can put as
much of it into upgradable pieces that we can replace later. In any event,
that's something for the WG to deal with after adoption.

-Patrick


On Thu, Nov 21, 2019 at 3:31 PM Tommy Pauly <tpauly@apple.com> wrote:

> Hello HTTPbis,
>
> During our IETF 106 meetings, we received updates from the design team for
> updating HTTP's priority hinting mechanism, with the goals of defining
> priorities for HTTP/3 and allowing this scheme to be backported to HTTP/2.
>
> The output of the design team is documented in this draft:
> https://tools.ietf.org/html/draft-kazuho-httpbis-priority-04
>
> This draft defines:
> - A SETTINGS parameter to disable the HTTP/2 priority mechanism
> - Two priority values, urgency (0-7), and incremental (boolean)
> - Mechanisms to communicate these priority values using headers and frames
>
> This email begins a call for Working Group adoption of this draft. Note
> that adoption indicates that we, as a working group, want to
> use draft-kazuho-httpbis-priority as a basis for the definition of
> priorities for HTTP/3. There is still ongoing discussion that will
> continue, specifically around the mechanism for end-to-end and hop-by-hop
> signaling.
>
> This call will end on *Friday, December 6*. Please reply to this email
> and indicate whether or not you believe we should adopt this document!
>
> Best,
> Tommy & Mark
>