Re: [quicwg/base-drafts] Grease HTTP error codes (#3360)

[Lucas Pardue <[e-mail]>]

LPardue commented on this pull request.



> @@ -925,7 +925,9 @@ transferred. Endpoints MUST NOT consider these streams to have any meaning upon
 receipt.
 
 The payload and length of the stream are selected in any manner the
-implementation chooses.
+implementation chooses.  Implementations MAY terminate these streams cleanly,
+or MAY abruptly terminate them with an error code of the implementation's
+choice, including reserved error codes ({{http-error-codes}}).

We already say https://quicwg.org/base-drafts/draft-ietf-quic-http.html#section-8

> Because new error codes can be defined without negotiation (see Section 9), use of an error code in an unexpected context or receipt of an unknown error code MUST be treated as equivalent to H3_NO_ERROR. However, closing a stream can have other effects regardless of the error code

Closing a stream with the error code H3_CLOSED_CRITICAL_STREAM seems like an unexpected context to me. Martin makes the suggestion above to also treat reserved error values as H3_NO_ERROR.

By defining and exercising grease of error codes, we can help surface naiive implementations that react in the unfortunate way of your example. 


-- 
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/3360#discussion_r368989867