- From: <rfc-editor@rfc-editor.org>
- Date: Wed, 27 May 2026 03:58:47 -0000
- To: phk@varnish-cache.org, julian.reschke@gmx.de, mnot@mnot.net
- Cc: iesg@ietf.org, mbishop@evequefou.be, rfc-editor@rfc-editor.org, ietf-http-wg@w3.org, iana@iana.org
The following errata report has been verified for RFC9651, "Structured Field Values for HTTP" -------------------------------------- You may review the report below and at: https://errata.rfc-editor.org/eid8869/ -------------------------------------- Status: Verified Type: Technical Reported by: Julian Reschke <julian.reschke@gmx.de> Date Reported: April 6, 2026, 7 p.m. Verified by: Mike Bishop (IESG) Section 3.3 says: Original Text ------------- An Item can be an Integer (Section 3.3.1), a Decimal (Section 3.3.2), a String (Section 3.3.3), a Token (Section 3.3.4), a Byte Sequence (Section 3.3.5), a Boolean (Section 3.3.6), or a Date (Section 3.3.7). It can have associated parameters (Section 3.1.2). Corrected Text -------------- An Item can be an Integer (Section 3.3.1), a Decimal (Section 3.3.2), a String (Section 3.3.3), a Token (Section 3.3.4), a Byte Sequence (Section 3.3.5), a Boolean (Section 3.3.6), a Date (Section 3.3.7), or a Display String (Section 3.3.8). It can have associated parameters (Section 3.1.2). Notes ----- Display String missing. -------------------------------------- RFC9651 (draft-ietf-httpbis-sfbis) -------------------------------------- Title : Structured Field Values for HTTP Publication Date : September 2024 Author(s) : M. Nottingham, P-H. Kamp Category : Proposed Standard Source : httpbis (wit) Stream : IETF
Received on Wednesday, 27 May 2026 03:58:51 UTC