W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2020

[Errata Rejected] RFC7231 (6019)

From: RFC Errata System <rfc-editor@rfc-editor.org>
Date: Fri, 10 Jul 2020 05:48:51 -0700 (PDT)
To: 1983-01-06@gmx.net, fielding@gbiv.com, julian.reschke@greenbytes.de
Cc: barryleiba@computer.org, iesg@ietf.org, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
Message-Id: <20200710124851.7C0F7F40720@rfc-editor.org>
The following errata report has been rejected for RFC7231,
"Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6019

--------------------------------------
Status: Rejected
Type: Editorial

Reported by: Michael Osipov <1983-01-06@gmx.net>
Date Reported: 2020-03-16
Rejected by: Barry Leiba (IESG)

Section: 3.1.1.1

Original Text
-------------
 A parameter value that matches the token production can be
   transmitted either as a token or within a quoted-string.  The quoted
   and unquoted values are equivalent.  For example, the following
   examples are all equivalent, but the first is preferred for
   consistency:

     text/html;charset=utf-8
     text/html;charset=UTF-8
     Text/HTML;Charset="utf-8"
     text/html; charset="utf-8"


Corrected Text
--------------
 A parameter value that matches the token production can be
   transmitted either as a token or within a quoted-string.  The quoted
   and unquoted values are equivalent.  For example, the following
   examples are all equivalent, but the first is preferred for
   consistency:

     text/html;charset=utf-8
     text/html;charset=UTF-8


Notes
-----
Section 3.1.1.2 defines charset value to be a token. I consider this to be a bad example which might cause confusion. Why should I quote the value if it is defined as token?! You make want to use some other example.
 --VERIFIER NOTES-- 
   What's relevant is the ABNF for *parameter*, and that allows both token and quoted-string.  So the example is correct.

--------------------------------------
RFC7231 (draft-ietf-httpbis-p2-semantics-26)
--------------------------------------
Title               : Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Publication Date    : June 2014
Author(s)           : R. Fielding, Ed., J. Reschke, Ed.
Category            : PROPOSED STANDARD
Source              : Hypertext Transfer Protocol Bis APP
Area                : Applications
Stream              : IETF
Verifying Party     : IESG
Received on Friday, 10 July 2020 12:49:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 10 July 2020 12:49:36 UTC