Re: [quicwg/base-drafts] Allow not creating QPACK codec streams (#2529)

[Lucas Pardue <[e-mail]>]

LPardue commented on this pull request.



>  HTTP_WRONG_STREAM_COUNT. These streams MUST NOT be closed. Closure of either
 unidirectional stream type MUST be treated as a connection error of type
 HTTP_CLOSED_CRITICAL_STREAM.
 
+An endpoint MAY avoid creating its own encoder stream if the maximum size of
+the dynamic table permitted by the peer is zero.
+
+An endpoint MAY avoid creating its own decoder stream if the maximum size of
+its own dynamic table is zero.
+
+An endpoint MUST allow its peer to create both encoder and decoder streams

The trap here is that a peer sets initial uni directional streams. And then may increase this value. 

Uni directional stream accounting needs to factor in qpack, push promise and whatever other extension mechanisms might come to pass.
The explicit signal that's missing is for QPACK off. If you dont tell the peer you wont use QPACK, and it advertised a size > 0. It will have to entertain that this could happen at any point in the connection. 

In a pathological case, you give me 3 credits and I use them to send control and 2 grease streams. What happens next?

I think these sorts of issues will come to light, the specs are not so helpful in guidance right now.

-- 
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/pull/2529#discussion_r267535756