Resent-Date: Mon, 06 Apr 2026 21:23:09 +0000
Resent-Message-Id: <E1w9rPZ-0058BD-1Q@mab.w3.org>
Received-SPF: pass (puck.w3.org: domain of mnot.net designates 103.168.172.149 as permitted sender) client-ip=103.168.172.149; envelope-from=mnot@mnot.net; helo=fout-a6-smtp.messagingengine.com;
Feedback-ID: ie6694242:Fastmail
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.500.181\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <202604060844.6368iMxj041435@critter.freebsd.dk>
Date: Tue, 7 Apr 2026 07:22:59 +1000
Cc: RFC Errata System <rfc-editor@rfc-editor.org>,
 phk@varnish-cache.org,
 httpbis-ads@ietf.org,
 tpauly@apple.com,
 "Julian F. Reschke" <julian.reschke@gmx.de>,
 ietf-http-wg@w3.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F3FCD25-D3F2-4297-8D84-C87A7CD2527D@mnot.net>
References: <20260406065246.2FCBA2B9F32@rfcpa.rfc-editor.org>
 <8FDAE1AE-18D1-441B-8EBE-841874115D38@mnot.net>
 <202604060844.6368iMxj041435@critter.freebsd.dk>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Subject: Re: [Technical Errata Reported] RFC9651 (8869)
Archived-At: <https://www.w3.org/mid/2F3FCD25-D3F2-4297-8D84-C87A7CD2527D@mnot.net>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

The errata.

Cheers,

> On 6 Apr 2026, at 6:44=E2=80=AFpm, Poul-Henning Kamp =
<phk@phk.freebsd.dk> wrote:
>=20
> --------
> Mark Nottingham writes:
>=20
>> This is correct.
>=20
> Just to make sure I dont misunderstand you:
>=20
> "This" =3D the errata
>=20
> or
>=20
> "This" =3D the original text=20
>=20
> ?
>=20
>>=20
>>> On 6 Apr 2026, at 4:52=3DE2=3D80=3DAFpm, RFC Errata System =3D
>> <rfc-editor@rfc-editor.org> wrote:
>>> =3D20
>>> The following errata report has been submitted for RFC9651,
>>> "Structured Field Values for HTTP".
>>> =3D20
>>> --------------------------------------
>>> You may review the report below and at:
>>> https://www.rfc-editor.org/errata/eid8869
>>> =3D20
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Julian Reschke <julian.reschke@gmx.de>
>>> =3D20
>>> Section: 3.3
>>> =3D20
>>> Original Text
>>> -------------
>>>  An Item can be an Integer (Section 3.3.1), a Decimal (Section =3D
>> 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).
>>> =3D20
>>> Corrected Text
>>> --------------
>>>  An Item can be an Integer (Section 3.3.1), a Decimal (Section =3D
>> 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).
>>> =3D20
>>> Notes
>>> -----
>>> Display String missing.
>>> =3D20
>>> Instructions:
>>> -------------
>>> This erratum is currently posted as "Reported". (If it is spam, =
it=3D20
>>> 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 =3D20
>>> will log in to change the status and edit the report, if necessary.
>>> =3D20
>>> --------------------------------------
>>> RFC9651 (draft-ietf-httpbis-sfbis-06)
>>> --------------------------------------
>>> Title               : Structured Field Values for HTTP
>>> Publication Date    : September 2024
>>> Author(s)           : M. Nottingham, P-H. Kamp
>>> Category            : PROPOSED STANDARD
>>> Source              : HTTP
>>> Stream              : IETF
>>> Verifying Party     : IESG
>>=20
>> --
>> Mark Nottingham   https://www.mnot.net/
>>=20
>=20
> --=20
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk@FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe   =20
> Never attribute to malice what can adequately be explained by =
incompetence.

--
Mark Nottingham   https://www.mnot.net/