Change:
to treat a stream error as a connection error. Because new error codes can be defined without negotiation (see <del> extensions), receipt of an unknown error code or use of an error code in an unexpected context MUST NOT be treated as an error.  However, closing a stream can constitute an error regardless of the error code (see request-response). </del> <ins> extensions), 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 (see request-response). </ins> This section describes HTTP/3-specific error codes which can be used to express the cause of a connection or stream error.

Discussion:
This is not quite editorial. We previously cautioned implementations not to freak out about unexpected uses of error codes; this text requires them to treat unknown/unexpected codes as equivalent to H3NOERROR.
Because this changes a MUST, this might deserve the full process, even if it's borderline.
Creating an issue on behalf of NAME that reflects . On that PR they quote a section of the document: Section 9), receipt of an unknown error code or use of an error code in an unexpected context MUST NOT be treated as an error. However, closing a stream can constitute an error regardless of the error code (see Section 4.1). and say: Maybe [replacing "an error" with "a further error"] is what's meant? (If not, please explain it better.)
I don't think the suggested change is aligned with the intent but there might be something we can do to improve the readability. "error codes" are used for normal operations when it comes to closing streams. So one interpretation of the current text is to say that if you get an unknown error code in a RESET_STREAM, don't treat it as any kind of error. The suggested text "further error" confuses this interpretation.
Maybe something like "MUST NOT be interpreted as an indication of a problem"?
The paragraph in question (see ) talks about different things: Let's break it up to make it easier to talk about: Treating an unexpected error code as an error is not allowed, in particular: a. Receiving unknown error is not an error in itself (a "further" error); and b. Receiving an unexpected error code (known or unknown) is not an error. A stream close may be an error independent of error code. Item 1(a) follows from Section 9. This does not need to be stated here. Item 1(b) seems to suggest that error codes are not to be used to make decisions, for they could be anything, notwithstanding all the "MUST treat as error type" admonitions elsewhere in the code. (This is what the text implies, which may not be what was intended.) Item 2 says that some error occur due to changes in stream state and are not communicated via an error code from peer.

I would drop Items 1(a) and 1(b); Item 2 can be rephrased. P.S. Given the loose treatment given to error codes by their recipient, it is logical to allow their sender to keep on treating specified errors as errors ("MUST treat as error..."), but allow setting the error codes to anything. Stating that "MUST treat as error of type X and SHOULD set error code to X" sounds awkward; perhaps this guidance could be added to Section 8 as a new item.
1a/1b are two sides of the same coin. Because error codes are extensible, a future document might define a new error code, or might prescribe the use of an existing error code in a new circumstance. Therefore, the takeaway should be: An error code the recipient knows in an situation where they expect it has understood semantics that the recipient might be able to act on. An unknown error code, or an error code in an unexpected situation, has semantics which the recipient does not understand and cannot act on. The statement here is that the second case is not a violation of the protocol by the peer; you know the stream (or connection) is closing even if you don't understand why. The admonition is to respond to the closure itself, not the unknown semantics of why it was closed. While I agree that both versions of the second case follow from Section 9, I think it's useful to mention them in the context of error handling as well. We've seen recently with HTTP/2 what happens when the possibility of extension values isn't mentioned/considered in the description of how the base-protocol pieces are to be handled.
NAME points out that promotion from stream to connection error is something you shouldn't do absent an understanding of the error semantics.
The only case where this matters is for stream errors (RESETSTREAM / STOPSENDING). The scenario we want to avoid is closing the connection in response to an unexpected error code in a stream closure. So the right guidance here might be to say that you MUST NOT close the connection based on the unexpected error code.
Correction: We also care about closing one side of bidirectional streams. You shouldn't close the other direction because the first direction closed. One possibility is to treat unknown error codes as equivalent to NO_ERROR.

If you receive a STOPSENDING, aren't you supposed to RESETSTREAM if you haven't sent a FIN yet? I guess the other direction is weirder (abrupt termination of response, should you terminate the request too. etc?) but probably tearing everything down is the right move most of the time? At least it's not totally unexpected or catastrophic. Preventing connection closure still seems like the main objective. I think the general guidance of 'treat unknown error codes as you would treat NO_ERROR' is good, though.
Right, but if you receive a RESET_STREAM, that doesn't tell you anything about what to do with the other direction.
NAME / NAME this is borderline, but the PR does touch the specifics of the "MUST." Shall we run the process on this?
I don't think it changes the intent; let's keep it editorial unless someone explicitly objects to that.
SOLD, as editorial, to the chairs.
LGTM. I like the new text. It's super clear!