- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Tue, 10 May 2016 01:00:59 -0700 (PDT)
- To: fielding@gbiv.com, julian.reschke@greenbytes.de, ben@nostrum.com, alissa@cooperw.in, aamelnikov@fastmail.fm, mnot@mnot.net
- Cc: quae@daurnimator.com, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
The following errata report has been submitted for RFC7231,
"Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content".
--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=7231&eid=4689
--------------------------------------
Type: Technical
Reported by: Daurnimator <quae@daurnimator.com>
Section: 3.1.1.2
Original Text
-------------
3.1.1.2. Charset
HTTP uses charset names to indicate or negotiate the character
encoding scheme of a textual representation [RFC6365]. A charset is
identified by a case-insensitive token.
charset = token
Charset names ought to be registered in the IANA "Character Sets"
registry (<http://www.iana.org/assignments/character-sets>) according
to the procedures defined in [RFC2978].
Corrected Text
--------------
3.1.1.2. Charset
HTTP uses charset names to indicate or negotiate the character
encoding scheme of a textual representation [RFC6365].
charset = <mime-charset, see [RFC5987], Section 3.2.1>
Charset names ought to be registered in the IANA "Character Sets"
registry (<http://www.iana.org/assignments/character-sets>) according
to the procedures defined in [RFC2978].
Notes
-----
The definition of charset from RFC 5987 is more strict and more correct.
Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary.
--------------------------------------
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 Tuesday, 10 May 2016 08:02:22 UTC