[quicwg/base-drafts] Recommended behavior for reserved streams (#3933)

[Mike Bishop <[e-mail]>]

In Section 6.2.3, we recommend the following about the reserved unidirectional stream types:
> When terminating abruptly, the error code H3_NO_ERROR or a reserved error code (Section 8.1) SHOULD be used.

However, this has a fatal flaw -- it recommends special handling for the grease types, which is *precisely* the behavior we're trying to disincent with grease.

Instead, I think we should move the recommendation to use reserved error codes to the guidance on what to do with unknown stream types, which is currently:
> Recipients of unknown stream types MAY abort reading of the stream with an error code of H3_STREAM_CREATION_ERROR, but MUST NOT consider such streams to be a connection error of any kind.

This has the same net effect on the grease streams.  The change in behavior is on actual unknown-but-real stream types, which will now get grease error codes in response.

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