Re: [quicwg/base-drafts] Mandate allowing peer to create enough unidirectional streams for HTTP and QPACK (#2762)

[afrind <[e-mail]>]

afrind commented on this pull request.



> @@ -912,10 +912,20 @@ Endpoints that set low values for the QUIC transport parameters
 chance that the remote peer reaches the limit early and becomes blocked. In
 particular, the value chosen for `initial_max_uni_streams` should consider that
 remote peers may wish to exercise reserved stream behaviour ({{stream-grease}}).
-To reduce the likelihood of blocking, both clients and servers SHOULD send a
-value of three or greater for the QUIC transport parameter
-`initial_max_uni_streams`, and a value of 1,024 or greater for the QUIC
-transport parameter `initial_max_stream_data_uni`.
+To reduce the likelihood of blocking, both clients and servers MUST allow
+the peer to create one unidirectional stream for the HTTP control stream plus
+the number of unidirectional streams required by mandatory extensions (such as
+QPACK), by setting an appropriate value for the QUIC transport parameter

I'd say you have to put it in the TP.  What is the possible reason an implementation would have for setting inital_max_uni_streams to less than 3 and making up for it with MAX_STREAMS?  What if the packet containing MAX_STREAMS is lost?

-- 
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/2762#discussion_r291342259