Subject: [quicwg/base-drafts] Do not require clients to reset initial streams (#425)

From: Igor Lubashev <[email-masked]>
Date: Wed, 29 Mar 2017 22:47:52 -0700

The draft currently requires clients to reset initial streams beyond the value declared by the server.
> Similarly, a client might exceed the initial stream limit declared by the server.  A client MUST reset any streams that exceed this limit.

This can be problematic for applications where stream IDs are meaningful, since the client will never be able to reopen a previously-reset stream ID. It is also wasteful of bandwidth, in case the server is willing to accept the extra data.

Also, the paragraph in its entirety is either unclear or self-contradictory:
>A client MUST reset any streams that exceed this limit. A server SHOULD reset any streams it cannot handle [...]

If the client MUST reset extra streams, whether server can or cannot handle the extra streams becomes irrelevant -- they are being reset!

Instead, we should require that the client stops sending any additional STREAM frames for the extra streams (even retransmissions) until the server indicates that it is ready for those streams via LIMIT_UPDATE (#419).  The server should be free to reset what it cannot handle (but for an application with meaningful stream IDs this would render the connection useless).

-- 
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/issues/425