RFC 9297 defines H3_DATAGRAM_ERROR as "Datagram or Capsule Protocol parse error". Then it started being used to convey errors during the parsing of data inside capsules by connect-ip:
If any of the capsule fields are malformed upon reception, the receiver of the capsule MUST follow the error-handling procedure defined in Section 3.3 of [HTTP-DGRAM].
RFC 9297 defines H3_DATAGRAM_ERROR as "Datagram or Capsule Protocol parse error". Then it started being used to convey errors during the parsing of data inside capsules by connect-ip:
This has caused confusion for readers, both in QUIC Proxying and in WRAP_UP.
So we should define more generic capsule parsing errors for h2 and h3.