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

I think this is telling that the current definition of signalling around QPACK is all a bit wrong. The receiver tells the sender if it is willing to support dynamic compression but there is no explicit signal it will happen until a stream is opened, are we happy with that?

For @ianswett's issue, an additional clause to this sentence could help e.g. 

"An endpoint MAY avoid creating its own encoder stream if the maximum size of the dynamic table permitted by the peer is zero, or if the endpoint doesn't want to use the dynamic table."

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