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

[Dmitri Tikhonov <[e-mail]>]

dtikhonov 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

> I think the current consensus regarding QPACK streams is that you cannot prevent their creation

What does that mean -- "[one] cannot prevent their creation?"  Surely, setting the limit low does just that.

The general MO of this WG has been to assume that the implementers are capable of making sensible choices.  Creating an unnecessary QPACK stream instead of the HTTP Control Stream when the allowance is just one stream is far from a subtle "gotcha."

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