[Json] [Errata Rejected] RFC8259 (7617)
rfc-editor@rfc-editor.org Thu, 28 May 2026 18:38 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 17D18F6D5347; Thu, 28 May 2026 11:38:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1779993490; bh=XClkscETgyiXlSqWnx42He3bEzywnWVgLVbvQVKBTVA=; h=Subject:From:To:Cc:Date; b=N7Nf/Gst7TRhgzbh+iwjjHIH8eYVXU3eVAwZc2rJonb60Fj7DghvU9UyMfx6VbSPp 4wW7bjXy7R13+uq2UrWvrtlX6U3WsuopFR87OOzP/sLQzilxLNxwuE2Mkh3fidY7vk qrurU09oolXNWsFDXlro6ObdcDC1atFnK0+1Ay44=
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:38:10 -0000
message-id: <177999348995.13.17883254671295948903@rfc-editor.org>
Message-ID-Hash: ITKK4TQ4KTCEDLRXWX4LBKZOE6Q7SKGY
X-Message-ID-Hash: ITKK4TQ4KTCEDLRXWX4LBKZOE6Q7SKGY
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 (7617)
List-Id: "JavaScript Object Notation (JSON) WG mailing list" <json.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/6ONx6RodCTPiI4vLFxWp4nUuYf0>
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/eid7617/ -------------------------------------- Status: Rejected Type: Technical Reported by: Guillaume Fortin-Debigaré <guillaume.fortin@debigare.com> Date Reported: Aug. 25, 2023, 7 p.m. Rejected by: Andy Newton (IESG) Section 6 says: Original Text ------------- Note that when such software is used, numbers that are integers and are in the range [-(2**53)+1, (2**53)-1] are interoperable in the sense that implementations will agree exactly on their numeric values. Corrected Text -------------- Note that when such software parses numbers as rational numbers in decimal or scientific notation, they are interoperable in the sense that implementations will agree exactly on their numeric values. In particular, when such software is used, numbers that are integers and are in the range [-(2**53)+1, (2**53)-1] are interoperable in that sense. Notes ----- IEEE 754 does not consider negative zero and positive zero to be the same numeric value, even though it considers them equal. Despite this, JavaScript serializes negative zero as the JSON text "0", which contradicts the original text. My suggested correction mentions "rational numbers in decimal or scientific notation" since it's never explicitly mentioned in the document how a number should be interpreted when parsed to maximize interoperability. This version addresses that concern at the same time. -------------------------------------- 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 (7617) rfc-editor