- From: Ryan Hamilton <rch@google.com>
- Date: Thu, 21 Nov 2019 09:42:50 -0800
- To: Tommy Pauly <tpauly@apple.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
- Message-ID: <CAJ_4DfTgcQFU5jNDBKCjC3vF-nWA5y_gZXBOvc_B5zQzNsSMSw@mail.gmail.com>
I strongly support the adoption of this work. (I'm skeptical of the header-based mechanism for conveying this information, but as you said, this discussion can continue in the WG). On Wed, Nov 20, 2019 at 11: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 >
Received on Thursday, 21 November 2019 17:43:06 UTC