Original text:
-1, so the largest legal value of Quarter Stream ID is 2 -1.  Receipt of a frame that includes a larger value MUST be <del> treated as a connection error of type FRAME_ENCODING_ERROR. </del>  The payload of the datagram, whose semantics are defined by individual applications.  Note that this field can be empty. Receipt of a QUIC DATAGRAM frame whose payload is too short to allow parsing the Quarter Stream ID field MUST be treated as an HTTP/3 <del> connection error of type H3_GENERAL_PROTOCOL_ERROR. </del>  Endpoints MUST NOT send HTTP/3 datagrams unless the corresponding stream's send side is open.  On a given endpoint, once the receive 4.2.  Definitions of new HTTP Upgrade Tokens that use the Capsule Protocol MAY use the Capsule-Protocol header field to simplify intermediary processing. Protocol header field value, but future documents MAY define parameters.  Receivers MUST ignore unknown parameters. <del> 4.3. </del>  This document defines the DATAGRAM capsule type (see iana-types for the value of the capsule type).  This capsule allows an endpoint to 8.2. This document will request IANA to register the following entry in  the "HTTP Field Name" registry: Capsule-Protocol None <del> 8.3. </del>  This document establishes a registry for HTTP capsule type codes. The "HTTP Capsule Types" registry governs a 62-bit space.

Reviewer comments:
Borrowing text from H3. Also I don't think there is a 'FRAMEENCODINGERROR' defined anywhere.
Thanks! Approved pending some minor tweaks

Revised text:
-1, so the largest legal value of Quarter Stream ID is 2 -1.  Receipt of a frame that includes a larger value MUST be  <ins> treated as a connection error of type H3_DATAGRAM_ERROR. </ins> The payload of the datagram, whose semantics are defined by individual applications.  Note that this field can be empty. Receipt of a QUIC DATAGRAM frame whose payload is too short to allow parsing the Quarter Stream ID field MUST be treated as an HTTP/3  <ins> connection error of type H3_DATAGRAM_ERROR. </ins> Endpoints MUST NOT send HTTP/3 datagrams unless the corresponding stream's send side is open.  On a given endpoint, once the receive 4.2. <ins> When an error occurs processing the capsule protocol, the receiver MUST treat the message as malformed or incomplete, according to the underlying transport protocol.  For HTTP/3, the handling of malformed messages is described in section 4.1.3 of H3.  For HTTP/2, the handling of malformed messages is described in section 8.1.2.6 of H2. For HTTP/1.1, the handling of incomplete messages is described in section 8 of CORE-MESSAGING. Each capsule's payload MUST contain exactly the fields identified in its description.  A capsule payload that contains additional bytes after the identified fields or a capsule payload that terminates before the end of the identified fields MUST be treated as a malformed or incomplete message.  In particular, redundant length encodings MUST be verified to be self-consistent. When a stream carrying capsules terminates cleanly, if the last capsule on the stream was truncated, this MUST be treated as a malformed or incomplete message. 4.3. </ins> Definitions of new HTTP Upgrade Tokens that use the Capsule Protocol MAY use the Capsule-Protocol header field to simplify intermediary processing. Protocol header field value, but future documents MAY define parameters.  Receivers MUST ignore unknown parameters.  <ins> 4.4. </ins> This document defines the DATAGRAM capsule type (see iana-types for the value of the capsule type).  This capsule allows an endpoint to 8.2. This document will request IANA to register the following entry in <ins> the "HTTP/3 Error Code" registry: 8.3. This document will request IANA to register the following entry in </ins> the "HTTP Field Name" registry: Capsule-Protocol None  <ins> 8.4. </ins> This document establishes a registry for HTTP capsule type codes. The "HTTP Capsule Types" registry governs a 62-bit space.