- From: Amos Jeffries <squid3@treenet.co.nz>
- Date: Sat, 23 Nov 2019 18:33:15 +1300
- To: ietf-http-wg@w3.org
Another vote for adoption. IMO we had too many compromises aggregated in the h2 scheme that complicated it in the end. It may be nice to try a selection of use-case targeted prioritization schemes. AYJ On 21/11/19 8:28 pm, Tommy Pauly 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
Received on Saturday, 23 November 2019 05:33:56 UTC