[quicwg/base-drafts] Need to clarify QUIC stream usage in HTTP/2 mapping (#1882)

[Magnus Westerlund <[e-mail]>]

I tried reading the HTTP/2 mapping draft (-15) to answer a question regarding the QUIC stream usage by HTTP/2 over QUIC. And that failed misserably until I looked at the slides from Montreal IETF meeting. 

Where I think there are need for clarification are:

Section 3.: Here a general overview of the how the four streams per HTTP request are used and assigned. Currently it says that client bi-directional will be every fourth 0,4, 8 etc. Nothing more aobut which streams are which of the remaining three, not even which names are used for them. 

In Section 3.3.3 the first mention of the word "push stream" occurs. That appears to indicate that a unidirectional stream that starts with a 0x43 stream type is then barred from use by any other stream type. I think 3.3 has to be clearer that the usages of unidirectional streams are not necessarily connected to the HTTP request response happening on the bi-directional stream. And that implementations needing a new unidirectional stream simple takes the next free (X+2/3) mod 4 depending on direction. 

I think it would be good to exemplify in the HTTP draft that a connection for HTTP/2 will have a number of unidirectional streams that are used long term or some short term and then closed and that one can't rely on stream ID being in the group related to a particular request. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/1882