[Json] [Errata Rejected] RFC8259 (5853)
rfc-editor@rfc-editor.org Thu, 28 May 2026 18:34 UTC
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: json@ietf.org
Delivered-To: json@mail2.ietf.org
Received: from errata-celery-557d7d6cc7-t9blw (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 9D53AF6D4336; Thu, 28 May 2026 11:34:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1779993266; bh=9Sbljth1fw12Wa1Oe6SnSswveHPDvs0nJY0Cy90vcXc=; h=Subject:From:To:Cc:Date; b=QS1BiENxOukCu91oqjGTHiPrXQTEIsWSfTk1tMIqZqKOgxbaFl3ClZQOv/1k0x4S0 wrKEjz9EyHAGbWV/wjB39k3OlXPZXmdzs4A6ZNnxYUnmj1fmZw26di/IYUoTH5VYVP KjWnSP9dBZuJqdYLuhd5IxAqQdE2Hc4iIEus6vrQ=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: rfc-editor@rfc-editor.org
To: lucab@lucabruno.net, tbray@textuality.com
Date: Thu, 28 May 2026 18:34:26 -0000
message-id: <177999326648.19.6292498303423129414@rfc-editor.org>
Message-ID-Hash: OV7KTEHWON4FQEORZE2IFMHVBXPWOD3K
X-Message-ID-Hash: OV7KTEHWON4FQEORZE2IFMHVBXPWOD3K
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-json.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: andy@hxr.us, iesg@ietf.org, json@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Json] [Errata Rejected] RFC8259 (5853)
List-Id: "JavaScript Object Notation (JSON) WG mailing list" <json.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/43exfPMt3Hy73Z7xXg7l85VsNDs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Owner: <mailto:json-owner@ietf.org>
List-Post: <mailto:json@ietf.org>
List-Subscribe: <mailto:json-join@ietf.org>
List-Unsubscribe: <mailto:json-leave@ietf.org>
The following errata report has been rejected for RFC8259, "The JavaScript Object Notation (JSON) Data Interchange Format" -------------------------------------- You may review the report below and at: https://errata.rfc-editor.org/eid5853/ -------------------------------------- Status: Rejected Type: Technical Reported by: Luca BRUNO <lucab@lucabruno.net> Date Reported: Sept. 5, 2019, 7 p.m. Rejected by: Andy Newton (IESG) Section 11 says: 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) -------------------------------------- RFC8259 (draft-ietf-jsonbis-rfc7159bis) -------------------------------------- Title : The JavaScript Object Notation (JSON) Data Interchange Format Publication Date : December 2017 Author(s) : T. Bray, Ed. Category : Internet Standard Source : jsonbis (art) Stream : IETF
- [Json] [Errata Rejected] RFC8259 (5853) rfc-editor