Stream 0 DT proposal conflicts with PRIORITY

[MikeBishop]

After the design team output, all client-initiated bidirectional streams are used for requests, including Stream 0. Since Stream 0 will be a valid, actual client request, this creates a conflict with the use of Stream ID 0 in PRIORITY to indicate the root of the priority tree.

[martinthomson]

Yep, placeholders FTW.

[ianswett]

Or/And we can start stream IDs at 1.

[mikkelfj]

if SID >= 1 at http level, that would be require handling stream 0 actually being used.

If enforced at transport layer then max stream ID = 0 as default suddenly enables not allowing any streams without resorting to stream counts in TP. That could be a good thing.