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

[afrind <[e-mail]>]

afrind 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

@dtikhonov : I mean to say, that an implementation that prevents the creation of QPACK streams is not conformant, in the same way it would not be conformant to set it to 0 and block the creation of the control stream.  This is my understanding of the consensus based on the last discussion in Toyko.

@LPardue : I'm not sure that's such a big deal.  If you planned to use the dynamic table, but wasted your stream on grease instead of an encoder stream, then you can't use the table.  If you disabled the dynamic table for your peer, then you don't need to create the decoder stream anyways.  If you allowed the peer to use the dynamic table but can't create a decoder stream, then your compression will eventually degrade to ~static only but I think the connection will still work. 

-- 
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_r267578761