IETF Logo Mail Archive

[Technical Errata Reported] RFC7231 (4689)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 10 May 2016 08:06 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EF0312B012 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 10 May 2016 01:06:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.917
X-Spam-Level:
X-Spam-Status: No, score=-7.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nIB0oa4KQodM for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 10 May 2016 01:06:45 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EC86128B44 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 10 May 2016 01:06:45 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1b02ce-0003yb-Im for ietf-http-wg-dist@listhub.w3.org; Tue, 10 May 2016 08:02:28 +0000
Resent-Date: Tue, 10 May 2016 08:02:28 +0000
Resent-Message-Id: <E1b02ce-0003yb-Im@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <wwwrun@rfc-editor.org>) id 1b02cY-0003wY-FR for ietf-http-wg@listhub.w3.org; Tue, 10 May 2016 08:02:22 +0000
Received: from rfc-editor.org ([4.31.198.49]) by maggie.w3.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from <wwwrun@rfc-editor.org>) id 1b02cU-0004PZ-VY for ietf-http-wg@w3.org; Tue, 10 May 2016 08:02:21 +0000
Received: by rfc-editor.org (Postfix, from userid 30) id 99725180003; 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
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: quae@daurnimator.com, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
Message-Id: <20160510080059.99725180003@rfc-editor.org>
Date: Tue, 10 May 2016 01:00:59 -0700
Received-SPF: pass client-ip=4.31.198.49; envelope-from=wwwrun@rfc-editor.org; helo=rfc-editor.org
X-W3C-Hub-Spam-Status: No, score=-10.5
X-W3C-Hub-Spam-Report: AWL=4.498, BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-2.079, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1b02cU-0004PZ-VY 02c8aaddd545a3e343bf88f4a903e913
X-Original-To: ietf-http-wg@w3.org
Subject: [Technical Errata Reported] RFC7231 (4689)
Archived-At: <http://www.w3.org/mid/20160510080059.99725180003@rfc-editor.org>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31625
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

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

v2.23.0 | Report a Bug | By Email