[quicwg/base-drafts] Rationalize HTTP/3 stream creation errors (#2821)

[Lucas Pardue <[e-mail]>]

There are presently several kinds of very similar error when creating streams:

1. HTTP_UNKNOWN_STREAM_TYPE MAY be used to tell a peer to STOP_SENDING on a stream type that is unknown by the local peer. It is **not** a connection error.
2. HTTP_WRONG_STREAM_COUNT MUST be used if a peer tries to open more than one critical stream (control, QPACK). Connection error.
3. HTTP_WRONG_STREAM_DIRECTION MUST be used if a client tries to open a push stream. More generally this could be used if a peer attempts to open a stream type that is not allowed to, but push is the only example today. Connection error.
4. HTTP_DUPLICATE_PUSH MUST be used if you open multiple push streams. 

The suggestion is to rationalize these into a single error code - HTTP_STREAM_CREATION_ERROR - that can be used in STOP_SENDING or CLOSE_CONNECTION.

The impact of merging _COUNT and _DIRECTION is minimal because implementations fundamentally have to open streams correctly in order to interop.

PS. The eagle eyes will notice I omitted the HTTP_DUPLICATE_PUSH creation error. This is on the chopping block in #2818. I class it differently because it is about parsing information **after** the stream type.

-- 
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/2821