Re: [Technical Errata Reported] RFC9651 (8869)

[Poul-Henning Kamp <[e-mail]>]

--------
Mark Nottingham writes:

> The errata.

Agree.

Poul-Henning

>
> Cheers,
>
> > On 6 Apr 2026, at 6:44=E2=80=AFpm, Poul-Henning Kamp =
> <[e-mail]> 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
> >> <[e-mail]> 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 <[e-mail]>
> >>> =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
> > [e-mail]         | 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/
>

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
[e-mail]         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.