Re: [quicwg/base-drafts] HTTP/3 references QUIC Stream IDs directly, allowing illegal references (#3273)

[Mike Bishop <[e-mail]>]

> This seems a bit at odd with our design principles, since it requires the HTTP/3 implementation to understand the QUIC Stream ID numbering scheme.

While the issue is closed, I wanted to point out that it does not imply this requirement.  I've held very strictly to this mental model:

- HTTP/3 can ask QUIC for a stream of a given type
- HTTP/3 can query the newly-received stream for its ID
- HTTP/3 can thereafter use the ID to refer to the stream
- HTTP/3 can query QUIC for the type of a given Stream ID and/or retrieve a stream by ID and then query its type

If QUIC were to change how Stream IDs are allocated, the changes could be entirely within the transport.  Now, it's a fair critique to say that this model is not explicitly stated in the draft, and so it's not guaranteed that any given implementation would actually preserve this flexibility.

-- 
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/3273#issuecomment-561763014