Re: Stream State and PRIORITY Frames

On Tue, Jan 17, 2017 at 7:37 AM, Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
wrote:
>
> ​
> ​I think Option 1 is the expected result.
>
>
>> [1] https://tools.ietf.org/html/rfc7540#section-5.1.1
>> > The first use of a new stream identifier implicitly closes all
>> streams in the "idle" state that might have been initiated by that
>> peer with a lower-valued stream identifier.
>>
>>
> ​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.
>
>
> I believe that is correct.
>
>
>
>