[Json] [Errata Verified] RFC8259 (7600)
rfc-editor@rfc-editor.org Thu, 28 May 2026 18:36 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 A79AFF6D4B1A; Thu, 28 May 2026 11:36:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1779993369; bh=wW/uss8YJzmRCYtx38BIqoJbXFqkNrUQ1SX0unPPJlc=; h=Subject:From:To:Cc:Date; b=SYe9XiMId7M9/EMKHJTwXxQFVRJK7CRbcsoqi72uzYwiN7fzQ2ZzF4snFXbD5N4CM bdr+oRi4BIRSv4d00hvqXMa5WO9mbk+sSvD8nDCAWgfkKCFPNeZQ3dLOHUx/QzAQmu hgg4TbVTp1ci9NbR7Xa8EoJw1/UYYsNXLeIUKwvk=
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:36:09 -0000
message-id: <177999336936.16.15158618995271881999@rfc-editor.org>
Message-ID-Hash: N4DC2RP65DOFR7LMTXVQX5IGAKW3QILZ
X-Message-ID-Hash: N4DC2RP65DOFR7LMTXVQX5IGAKW3QILZ
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 (7600)
List-Id: "JavaScript Object Notation (JSON) WG mailing list" <json.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/Ar4kIT4XpI79llS22rHHYzgHS3g>
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/eid7600/ -------------------------------------- Status: Verified Type: Technical Reported by: Guillaume Fortin-Debigaré <guillaume.fortin@debigare.com> Date Reported: Aug. 11, 2023, 7 p.m. Verified by: Andy Newton (IESG) Section 6 says: Original Text ------------- The representation of numbers is similar to that used in most programming languages. A number is represented in base 10 using decimal digits. It contains an integer component that may be prefixed with an optional minus sign, which may be followed by a fraction part and/or an exponent part. Leading zeros are not allowed. Corrected Text -------------- The representation of numbers is similar to that used in most programming languages. A number is represented in base 10 using decimal digits. It contains an integer component that may be prefixed with an optional minus sign, which may be followed by a fraction part and/or an exponent part. Leading zeros in the integer component beyond the units digit are not allowed. Notes ----- The original wording about leading zeros contradicts the documented ABNF grammar for JSON numbers in the following cases: - If the integer component is equal to 0 and the fractional component exists. (Examples: 0.1, 0.001) - In the exponent part, after the letter E or e or the optional sign. (Example: 1E01) -------------------------------------- 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 (7600) rfc-editor