[Json] [Errata Verified] RFC8259 (7603)
rfc-editor@rfc-editor.org Thu, 28 May 2026 18:37 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 4C313F6D4DD1; Thu, 28 May 2026 11:37:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1779993441; bh=U/VG+vdzyO5quH1TF3O1K0mcAuSADtSzcI45N8FuCkA=; h=Subject:From:To:Cc:Date; b=H3GgCnvlm8x+5Bxs7kMLZGsfvKcYakOgnZvbxEItv785kjAizMxy2UgZhk90mXJbr c2gGYc+duZAc3bcnULJxnDxtIQC4Jbo4eaXsHOcWZ8kiNQsooWOFM0vdjCCjnk+akO B5ff8ZUCYQ6GLT+DND7TeQJavZ6qwq8qBVHQVtJw=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
From: rfc-editor@rfc-editor.org
To: tbray@textuality.com, guillaume.fortin@debigare.com
Date: Thu, 28 May 2026 18:37:21 -0000
message-id: <177999344120.19.9084297026054305875@rfc-editor.org>
Message-ID-Hash: H72WIHMIN4VMT42DOLINQO2EECJ3P3YT
X-Message-ID-Hash: H72WIHMIN4VMT42DOLINQO2EECJ3P3YT
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 Verified] RFC8259 (7603)
List-Id: "JavaScript Object Notation (JSON) WG mailing list" <json.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/p40Qf_xZ3c93kCijdRkQp2vnw3o>
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 verified for RFC8259, "The JavaScript Object Notation (JSON) Data Interchange Format" -------------------------------------- You may review the report below and at: https://errata.rfc-editor.org/eid7603/ -------------------------------------- Status: Verified Type: Technical Reported by: Guillaume Fortin-Debigaré <guillaume.fortin@debigare.com> Date Reported: Aug. 13, 2023, 7 p.m. Verified by: Andy Newton (IESG) Section 1 says: Original Text ------------- A string is a sequence of zero or more Unicode characters [UNICODE]. Corrected Text -------------- A string is a sequence of zero or more Unicode code points [UNICODE]. Notes ----- Surrogate code points are not Unicode characters, as explained here: https://www.unicode.org/glossary/#surrogate_character However, a surrogate code point outside of a surrogate pair is allowed in JSON strings both in escaped and unescaped forms according to the ABNF grammar in section 7 and the warning in section 8.2, despite an UTF-8 incompatibility for the unescaped form. In addition, the original text contradicts ECMA-404 section 9, which states: "A string is a sequence of Unicode code points wrapped with quotation marks (U+0022). All code points may be placed within the quotation marks except for the code points that must be escaped: quotation mark (U+0022), reverse solidus (U+005C), and the control characters U+0000 to U+001F. " -------------------------------------- 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 Verified] RFC8259 (7603) rfc-editor