- From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
- Date: Thu, 25 Jul 2019 15:17:47 -0400
- To: Brad Lassey <lassey@chromium.org>
- Cc: ietf-http-wg@w3.org
From the draft: " 3. The SETTINGS_ENABLE_HTTP2_PRIORITIES SETTINGS Parameter " " This document adds a new SETTINGS parameter to those defined by " [RFC7540], Section 6.5.2. " " The new parameter name is SETTINGS_ENABLE_HTTP2_PRIORITIES. Including "HTTP2" in the name is superfluous: Since this is an HTTP/2 setting, it deals with HTTP/2 priorities. Or was "HTTP2" added to the name to differentiate it from possible future priority mechanisms? In that case, I suggest s/HTTP2/RFC7540/ - Dmitri. On Thu, Jul 25, 2019 at 02:49:52PM -0400, Brad Lassey wrote: > Hi all, > Lucas and I put together a draft to capture at least one of the ways > forward that were identified at the priorities side meeting yesterday > morning. Please have a look. > > https://datatracker.ietf.org/doc/draft-lassey-priority-setting/ > https://github.com/bslassey/priority-setting > > -Brad
Received on Thursday, 25 July 2019 19:18:12 UTC