- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Fri, 29 Aug 2025 12:32:56 -0700 (PDT)
- To: mt@lowentropy.net, caw@heapingbits.net, httpbis-ads@ietf.org, mnot@mnot.net, tpauly@apple.com
- Cc: ricardo.perezper@gmail.com, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
The following errata report has been submitted for RFC9292, "Binary Representation of HTTP Messages". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8559 -------------------------------------- Type: Technical Reported by: Ricardo Perez <ricardo.perezper@gmail.com> 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 and 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." Instructions: ------------- This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- 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 Friday, 29 August 2025 19:33:52 UTC