[Json] [Technical Errata Reported] RFC7493 (5354)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 10 May 2018 05:02 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 4A04C12EA53 for <json@ietfa.amsl.com>; Wed, 9 May 2018 22:02:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id oH7TDZ67jOyH for <json@ietfa.amsl.com>; Wed, 9 May 2018 22:02:15 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8E1012EA42 for <json@ietf.org>; Wed, 9 May 2018 22:02:15 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 916C4B81EA7; Wed, 9 May 2018 22:02:05 -0700 (PDT)
To: tbray@textuality.com, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, mamille2@cisco.com, paul.hoffman@vpnc.org
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: anders.rundgren.net@gmail.com, json@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20180510050214.916C4B81EA7@rfc-editor.org>
Date: Wed, 09 May 2018 22:02:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/ldojFA4eUi78AyON5L8QjzG2-vU>
Subject: [Json] [Technical Errata Reported] RFC7493 (5354)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
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, 10 May 2018 05:02:17 -0000

The following errata report has been submitted for RFC7493,
"The I-JSON Message Format".

You may review the report below and at:

Type: Technical
Reported by: Anders Rundgren <anders.rundgren.net@gmail.com>

Section: 2.2

Original Text
An I-JSON sender cannot expect a receiver to treat an integer whose
absolute value is greater than 9007199254740991 (i.e., that is
outside the range [-(2**53)+1, (2**53)-1]) as an exact value.

Corrected Text
An I-JSON sender cannot expect a receiver to treat an integer whose
absolute value is greater than 9007199254740992 (i.e., that is
outside the range [-(2**53), (2**53)]) as an exact value.

The limit is presumably derived from ECMAScript which says:

"The value of Number.MAX_SAFE_INTEGER is the largest integer n such that n and n + 1 are both exactly representable as a Number value"

However, Number.MAX_SAFE_INTEGER is 9007199254740991.

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. 

RFC7493 (draft-ietf-json-i-json-06)
Title               : The I-JSON Message Format
Publication Date    : March 2015
Author(s)           : T. Bray, Ed.
Category            : PROPOSED STANDARD
Source              : JavaScript Object Notation
Area                : Applications
Stream              : IETF
Verifying Party     : IESG