Re: Stream State and PRIORITY Frames

On 18 January 2017 at 09:27, Martin Thomson <> wrote:
> On 18 January 2017 at 01:37, Tatsuhiro Tsujikawa <> wrote:
>> If my understanding is correct, this only refers to the new stream ID used
>> by HEADERS, and PUSH_PROMISE frames which open or reserve streams.  The
>> example text following that statement uses HEADERS which opens new stream.
>> PRIORITY frame does not change stream state, and there is no reason to close
>> all unused streams lower than bearing stream ID.  That said, I agree that
>> this is not crystal clear in the document.  In practice, this is probably
>> rather rare case.
> This is, I think, the expectation.
> I think that we probably want to clarify the point by explicitly
> saying that PRIORITY doesn't affect stream states.  We say that it can
> be sent in any state, but we don't also mention that important point.
> Do people here agree that an erratum on this point is appropriate
> here?

Yes. I recently ran into this issue myself

Received on Wednesday, 18 January 2017 00:34:53 UTC