[Json] Limitations on number size?

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 03 June 2013 22:19 UTC

Return-Path: <paul.hoffman@vpnc.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 66A3621F861F for <json@ietfa.amsl.com>; Mon, 3 Jun 2013 15:19:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id O+bv-GawXeaJ for <json@ietfa.amsl.com>; Mon, 3 Jun 2013 15:19:21 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id EB7F711E8121 for <json@ietf.org>; Mon, 3 Jun 2013 15:10:38 -0700 (PDT)
Received: from [] (50-0-66-165.dsl.dynamic.sonic.net []) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r53MAa8N039867 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <json@ietf.org>; Mon, 3 Jun 2013 15:10:37 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 3 Jun 2013 15:10:36 -0700
References: <CAK3OfOgPGi4PKxKAGEG=PCv-xaszMqWpUUUH2B9f0UaeMMO1gQ@mail.gmail.com>
To: "json@ietf.org" <json@ietf.org>
Message-Id: <C42654A3-E218-45A8-B368-4A60CB89619D@vpnc.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Subject: [Json] Limitations on number size?
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 03 Jun 2013 22:19:31 -0000

Greetings. I'm forwarding this fragment with permission from the AppsAWG mailing list. It might warrant clarification in -bis document.

Begin forwarded message:

> From: Nico Williams <nico@cryptonector.com>
> On Mon, Jun 3, 2013 at 10:21 AM, Manger, James H
> <James.H.Manger@team.telstra.com> wrote:
>>> Imagine JSON had bignums (doesn't, but imagine).
>> JavaScript might not, but JSON actually does have indefinite length bignums. A JSON number can have any number of decimal digits.
> Yeah, but it is constrained to IEEE 754 64-bit floating point values, no?

I don't see any limitation in RFC 4627, but it would be interesting if other folks here believe there is a limitation as Nico does.

--Paul Hoffman