Re: [Json] Limitations on number size?

Nico Williams <nico@cryptonector.com> Tue, 09 July 2013 19:55 UTC

Return-Path: <nico@cryptonector.com>
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 64A0B21F9CA7 for <json@ietfa.amsl.com>; Tue, 9 Jul 2013 12:55:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.153
X-Spam-Level:
X-Spam-Status: No, score=-2.153 tagged_above=-999 required=5 tests=[AWL=-0.176, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 UfXw0yDSxU7j for <json@ietfa.amsl.com>; Tue, 9 Jul 2013 12:55:42 -0700 (PDT)
Received: from homiemail-a29.g.dreamhost.com (caiajhbdcaib.dreamhost.com [208.97.132.81]) by ietfa.amsl.com (Postfix) with ESMTP id 8433D21F9964 for <json@ietf.org>; Tue, 9 Jul 2013 12:55:42 -0700 (PDT)
Received: from homiemail-a29.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a29.g.dreamhost.com (Postfix) with ESMTP id 0D34D67432C for <json@ietf.org>; Tue, 9 Jul 2013 12:55:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type:content-transfer-encoding; s= cryptonector.com; bh=q/8MVpSyb9vzlMUALC0FJh54Bms=; b=rqO3udRG4BR BpW7SQ/7n0BdBZ6x4LVBrpERRzoo5sMp+drEtdg0RgdMhmNQtIqqyz9+38fpRH+k juWb9zvJfAOG3i93u4FltjQrCJWr+wTTCtbiKhtbAGFjVx7ftgXmP5OLl5JM9iQP 3DRB/f3NJzzfR1hT9BRx0653k8voxrvI=
Received: from mail-we0-f177.google.com (mail-we0-f177.google.com [74.125.82.177]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a29.g.dreamhost.com (Postfix) with ESMTPSA id 39204674546 for <json@ietf.org>; Tue, 9 Jul 2013 08:38:03 -0700 (PDT)
Received: by mail-we0-f177.google.com with SMTP id m19so4705836wev.8 for <json@ietf.org>; Tue, 09 Jul 2013 08:38:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Z3a0CfT3Itj/Dq5tqketsBoFeWf/boYmzjVblqpxawQ=; b=WYCvZBEn9pxC//cLNKYFiiYsNtsZ0yXYXugfx1oe3Gz5Mw2jaUe+gAhOMcD6kz13Rh 2JB3WdaIstBOIkKA8n0BAFXEyOQy8GsNJ/Uq1zoxtGnlzonTeiJimLEICTqKbBGRYOPu 1in/cDRDXQPN/B/73tDcnv4CbBBCpedR/1pCo+GYUn3cBDG4oT9IoAIOAGbh9yLqeRkh vRJ00WzIFsU48U233npDYd0zWEVeTsfeiMEtMYk6VcKlAgMeT9KIFMgPJgmdLeFvCuZ+ s8e00nK4ha7EIAoecG6PrMnLb+DCB9jksBs03w6Sm26RDhmdCRIhYiZNPDdoEZebbwDf knHg==
MIME-Version: 1.0
X-Received: by 10.180.74.197 with SMTP id w5mr32351937wiv.20.1373384282263; Tue, 09 Jul 2013 08:38:02 -0700 (PDT)
Received: by 10.217.38.138 with HTTP; Tue, 9 Jul 2013 08:38:02 -0700 (PDT)
In-Reply-To: <CAHBU6isckD0JCNT66BiS7sWXV3qyUXfseJ1kJk0bSL62QNFkQw@mail.gmail.com>
References: <51DC0F95.7010407@gmail.com> <F142B117-37C4-4936-AE81-D3571AB118C8@tzi.org> <CAHBU6isckD0JCNT66BiS7sWXV3qyUXfseJ1kJk0bSL62QNFkQw@mail.gmail.com>
Date: Tue, 9 Jul 2013 10:38:02 -0500
Message-ID: <CAK3OfOi_q8KTQd-RW7PPhS5ZXXYSMEJ57uKTKL-ck6ocd6Nbeg@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Tim Bray <tbray@textuality.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Carsten Bormann <cabo@tzi.org>, "Peter F. Patel-Schneider" <pfpschneider@gmail.com>, "json@ietf.org" <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: Tue, 09 Jul 2013 19:55:47 -0000

On Tue, Jul 9, 2013 at 10:27 AM, Tim Bray <tbray@textuality.com> wrote:
> Yeah, we can’t retroactively change the 4627 production for number, nor, in
> the -bis, say very much useful aside from a caution that implementations are
> all over the map.  When we move on to the BCP or Internet JSON or whatever,
> I think the single most interesting discussion will be how to constrain
> numeric values for maximum interoperability.

I would like to do two things here though:

1) give advice as to what numeric ranges and precisions are generally
supported (e.g., 32-bit signed integers);

2) what a parser SHOULD do when it parsers a number that it cannot represent.

Nico
--