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

> Hmmm, I think I was reading #2100 (comment) wrong.
> 
> But yeah, the **intention there was to disallow setting the uni streams limit to less than 3** in order to allow the other side to open all of their streams.

(Emphasis added)

I see how you get that from that comment by @MikeBishop:

> Discussed in Tokyo; do not require creating the streams, but creating them is not forbidden even if the setting prevents their use

But the "setting" refers to the QPACK settings -- namely, the size of the dynamic table -- and not to the stream limits.  Otherwise, how could it not be forbidden to create streams over the stream number limits specified by the peer?

I agree that more clarity is required.  My preference would be to allow the unidirectional stream limit to be set to 1 to allow just the HTTP Control Stream.

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