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

Going back over some of the discussion thread on this topic, was the preference to do lazy loading of streams in response to SETTINGS? In which case, when an endpoint receives a SETTINGS_QPACK_MAX_TABLE_CAPACITY it should send a QUIC MAX_STREAMS to allow the peer to open the encoder stream, and hope that the peer has also given enough streams to open the decoder stream.

Its hard to tell from the different threads what the consensus was.

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