[Json] [Technical Errata Reported] RFC8259 (5853)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 05 September 2019 14:20 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 371331200CD for <json@ietfa.amsl.com>; Thu, 5 Sep 2019 07:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 IFmb0MzF2z_5 for <json@ietfa.amsl.com>; Thu, 5 Sep 2019 07:20:08 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D4FD120026 for <json@ietf.org>; Thu, 5 Sep 2019 07:20:08 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4217CB8181D; Thu, 5 Sep 2019 07:19:46 -0700 (PDT)
To: tbray@textuality.com, barryleiba@computer.org, aamelnikov@fastmail.fm, adam@nostrum.com, linuxwolf+ietf@outer-planes.net
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: lucab@lucabruno.net, json@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20190905141946.4217CB8181D@rfc-editor.org>
Date: Thu, 5 Sep 2019 07:19:46 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/r53biO1Ht0QIosmzOh2OXdIHe54>
Subject: [Json] [Technical Errata Reported] RFC8259 (5853)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Sep 2019 14:20:10 -0000

The following errata report has been submitted for RFC8259,
"The JavaScript Object Notation (JSON) Data Interchange Format".

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

--------------------------------------
Type: Technical
Reported by: Luca BRUNO <lucab@lucabruno.net>

Section: 11

Original Text
-------------
Note:  No "charset" parameter is defined for this registration.
    Adding one really has no effect on compliant recipients.

Corrected Text
--------------
Note:  No "charset" parameter is defined for this registration.
    JSON text is encoded as described in RFC 8259, Section 8.1.


Notes
-----
Last sentence of last note of section 11 should be amended, as it introduces confusion by going against other explicit statements, like the followings:
 * RFC8259 sect. 8.1 defines that inner encoding is UTF-8
 * RFC8259 sect. 11 defines no formal (optional/required) parameters for this registered type
 * RFC6838 sect. 4.2.1 defines the common usage of a "charset" parameter as a "required" one (which isn't the case here)
 * RFC6838 sect. 4.2.1 defines that "charset" should not be used if the inner payload already transports charset information (e.g. mandatory UTF-8, which is the case here)
 * RFC6838 sect. 4.2.1 defines a "charset" parameter only for subtypes of the "text/*" hierarchy (which isn't the case here)

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  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC8259 (draft-ietf-jsonbis-rfc7159bis-04)
--------------------------------------
Title               : The JavaScript Object Notation (JSON) Data Interchange Format
Publication Date    : December 2017
Author(s)           : T. Bray, Ed.
Category            : INTERNET STANDARD
Source              : Javascript Object Notation Update
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG