RFC 7540, "Hypertext Transfer Protocol Version 2 (HTTP/2)", May 2015Source of RFC: httpbis (app)
Errata ID: 4925
Status: Held for Document Update
Reported By: Martin Thomson
Date Reported: 2017-02-07
Held for Document Update by: Alexey Melnikov
Date Held: 2017-02-23
Throughout the document, when it says:
It's unclear from the text whether PRIORITY frames affect stream states (as shown in the state machine in Section 5.1). The original intent was that prioritization of streams was independent of the mechanics of opening and closing streams, but this was not consistently captured.
Two small additions to the document would help considerably.
In Section 5.3 (Stream Priority) add a new paragraph:
> The information that an endpoint maintains for stream priority is separate from other state. Importantly, this includes stream states (Section 5.1). A stream in any state can have its priority changed with a PRIORITY frame. The state of a stream is not changed as a result of changing its priority. The number of streams for which state is remembered is at the discretion of an endpoint, see Section 5.3.4 for details.
In Section 6.4 (PRIORITY) a new sentence at the end of the first paragraph:
> Sending or receiving a PRIORITY frame does not affect the state of any stream (Section 5.1), only the priority of streams is altered.