- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Tue, 10 Mar 2026 06:49:28 -0700 (PDT)
- To: ricardo.perezper@gmail.com, mt@lowentropy.net, caw@heapingbits.net
- Cc: mbishop@evequefou.be, iesg@ietf.org, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
The following errata report has been held for document update for RFC9292, "Binary Representation of HTTP Messages". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8559 -------------------------------------- Status: Held for Document Update Type: Technical Reported by: Ricardo Perez <ricardo.perezper@gmail.com> Date Reported: 2025-08-29 Held by: Mike Bishop (IESG) Section: 3.6 Original Text ------------- invalid messages. A recipient MUST treat a message that contains field values that would cause an HTTP/2 message to be malformed according to Section 8.2.1 of [HTTP/2] as invalid; see Section 4. Corrected Text -------------- invalid messages. A recipient MUST treat a message that contains field names or values that would cause an HTTP/2 message to be malformed according to Section 8.2.1 of [HTTP/2] as invalid; see Section 4. Notes ----- Calling out field name handling explicitly since encoding and decoding entities might be using different versions of HTTP. An additional section explaining encoder and decoder expectations might be useful as well, something like the following: "To ensure interoperability where communicating entities use different HTTP versions, encoders MUST convert field names to lowercase upon encoding. Decoders MUST treat any uppercase field names as an error." -------------------------------------- RFC9292 (draft-ietf-httpbis-binary-message-06) -------------------------------------- Title : Binary Representation of HTTP Messages Publication Date : August 2022 Author(s) : M. Thomson, C. A. Wood Category : PROPOSED STANDARD Source : HTTP Stream : IETF Verifying Party : IESG
Received on Tuesday, 10 March 2026 13:50:07 UTC