- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Tue, 24 Oct 2023 11:07:59 -0700
- To: iana-matrix@iana.org
- Cc: RFC Errata System <rfc-editor@rfc-editor.org>, Mark Nottingham <mnot@mnot.net>, Julian Reschke <julian.reschke@greenbytes.de>, HTTP Working Group <ietf-http-wg@w3.org>, Francesca Palombini <francesca.palombini@ericsson.com>, daveshawley@gmail.com
> On Oct 24, 2023, at 10:58 AM, Amanda Baber via RT <iana-matrix@iana.org> wrote: > > Hi all, > > Does this errata report need to be listed as an additional reference for the "Accept-Encoding" or "Accept-Charset" HTTP Field Name registrations? > > thanks, > > Amanda Baber > IANA Operations Manager I don't believe so -- it is just the wrong name being referred to informationally. The error would not be reused or referred to by other specs. ....Roy > On Mon Oct 23 09:42:55 2023, rfc-editor@rfc-editor.org wrote: >> The following errata report has been verified for RFC9110, >> "HTTP Semantics". >> >> -------------------------------------- >> You may review the report below and at: >> https://www.rfc-editor.org/errata/eid7419 >> >> -------------------------------------- >> Status: Verified >> Type: Technical >> >> Reported by: Dave Shawley <daveshawley@gmail.com> >> Date Reported: 2023-04-11 >> Verified by: Francesca Palombini (IESG) >> >> Section: 8.3.2 >> >> Original Text >> ------------- >> In the fields defined by this document, charset names appear either >> in parameters (Content-Type), or, for Accept-Encoding, in the form of >> a plain token. >> >> Corrected Text >> -------------- >> In the fields defined by this document, charset names appear either >> in parameters (Content-Type), or, for Accept-Charset, in the form of >> a plain token. >> >> Notes >> ----- >> Accept-Encoding is the preferred list of response content codings. >> Accept-Charset is the preferred list of response charsets. >> >> -------------------------------------- >> RFC9110 (draft-ietf-httpbis-semantics-19) >> -------------------------------------- >> Title : HTTP Semantics >> Publication Date : June 2022 >> Author(s) : R. Fielding, Ed., M. Nottingham, Ed., J. >> Reschke, Ed. >> Category : INTERNET STANDARD >> Source : HTTP >> Area : Applications and Real-Time >> Stream : IETF >> Verifying Party : IESG >
Received on Tuesday, 24 October 2023 18:08:19 UTC