Re: [quicwg/base-drafts] Consider making h3 frame types varint (#2253)

[Kazuho Oku <[e-mail]>]

> That's not really relevant. If the intent is to enable pushing of stuff in 0.5RTT, then the design wouldn't necessarily use push IDs. It doesn't need to associate the push with a request, so it doesn't need them, it could just use a new stream type.

The point is that how such a context-free push in 0.5 RTT would look like to a client that only implements H3. H3 requires every push stream to carry a Push ID (immediately following the stream type). Every non-negotiated extension including context-free push need to obey the requirements.

> Point is that there *might* be valid uses for sending extension frames before receiving SETTINGS.

Yeah. My point is that there would be not a single case for that, because my understanding is that a server cannot start sending frames on an unidirectional stream due to the restriction I point out.

-- 
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/2253#issuecomment-450609959