Technical Summary
This document defines a new mechanism for communicating per-stream priorities in HTTP/2 and HTTP/3. Priority here communicates a level of urgency and information about if the data can be loaded incrementally, and can be communicated at the start of a request and updated later. This mechanism can be used instead of the unsuccessful priority mechanism originally defined in HTTP/2.
Working Group Summary
This work item came to HTTPbis as a requirement for HTTP/3 (developed in QUIC), which on its own didn't define any priorities. The working group ran a design team for the topic early on, and has seen good engagement in development of the solution.
Document Quality
There are a few implementations of the protocol in HTTP/3 to validate the effectiveness of the protocol, and implementations in general do intend to deploy this solution going forward (favored over the previous priority scheme). The document is well-structured and clear, and received extensive review from the WG.
Personnel
Tommy Pauly is the Document Shepherd.
Francesca Palombini is the Responsible Area Director.