IETF Logo Mail Archive

Re: [Json] Limitations on number size?

Carsten Bormann <cabo@tzi.org> Wed, 10 July 2013 03:16 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6806211E80FF for <json@ietfa.amsl.com>; Tue, 9 Jul 2013 20:16:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.206
X-Spam-Level:
X-Spam-Status: No, score=-106.206 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AWDoGrB8kvvG for <json@ietfa.amsl.com>; Tue, 9 Jul 2013 20:16:19 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 460FB11E80E8 for <json@ietf.org>; Tue, 9 Jul 2013 20:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r6A3GGlA005935; Wed, 10 Jul 2013 05:16:16 +0200 (CEST)
Received: from [192.168.217.105] (p548949D5.dip0.t-ipconnect.de [84.137.73.213]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3CC7D37C0; Wed, 10 Jul 2013 05:16:16 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20130710024215.GO9153@mercury.ccil.org>
Date: Wed, 10 Jul 2013 05:16:15 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <60109A8A-548F-4C60-8865-1C0AF5D09064@tzi.org>
References: <51DC0F95.7010407@gmail.com> <hf8ot8hnpa93pi3t54c4d5qcc3p5tnb3ca@hive.bjoern.hoehrmann.de> <CAK3OfOgTNaLpRthrRcU4Bo+3z1aXUOOn0Ord7RBPN8z6TtiiWw@mail.gmail.com> <51DC7F87.6060503@gmail.com> <CAGrxA24v5L7oCGxEOwecJSLCNiLrSWSt=jFJMA0M9E8fztNLag@mail.gmail.com> <20130710024215.GO9153@mercury.ccil.org>
To: John Cowan <cowan@mercury.ccil.org>
X-Mailer: Apple Mail (2.1508)
Cc: "json@ietf.org WG" <json@ietf.org>
Subject: Re: [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: Wed, 10 Jul 2013 03:16:25 -0000

On Jul 10, 2013, at 04:42, John Cowan <cowan@mercury.ccil.org> wrote:

> google for [json large numbers bugs]

Next up: google for »number overflow bugs«.

Somehow, it seems that handling large numbers is not entirely a problem specific to JSON.

Any interchange format that exchanges numbers between ecosystems with different number formats will run into this.  That is not a valid argument for saying JSON should be a single-ecosystem format.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email