Re: [Json] Limitations on number size?

Nico Williams <nico@cryptonector.com> Wed, 05 June 2013 04:05 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 E2B2521F9AF7 for <json@ietfa.amsl.com>; Tue, 4 Jun 2013 21:05:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.852
X-Spam-Level:
X-Spam-Status: No, score=-1.852 tagged_above=-999 required=5 tests=[AWL=0.125, 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 qoLJfLrTVKuY for <json@ietfa.amsl.com>; Tue, 4 Jun 2013 21:05:45 -0700 (PDT)
Received: from homiemail-a63.g.dreamhost.com (caiajhbdcaib.dreamhost.com [208.97.132.81]) by ietfa.amsl.com (Postfix) with ESMTP id 2DE8221F9AFD for <json@ietf.org>; Tue, 4 Jun 2013 21:05:43 -0700 (PDT)
Received: from homiemail-a63.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a63.g.dreamhost.com (Postfix) with ESMTP id 8643B2F406A for <json@ietf.org>; Tue, 4 Jun 2013 21:05: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; s=cryptonector.com; bh=LiiFPoAXZTuF/gZUGOEd arm4et8=; b=TmBQPGY/NR0Ypd+JSMFpnSHpgWlwZPP+SwVyFG3bcZQINvcGzOLs bkCrJaGBlhSXPd7RcewStj4lfyBwGRH6Ao+pcgH6y97JGX4eonKORjftg+j1Yhyr PAVw/TBRAK2RMbSQH3SHXcSmMorL6oscQ298cCfp6E+jRqLeUHstE3k=
Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a63.g.dreamhost.com (Postfix) with ESMTPSA id 312972F4059 for <json@ietf.org>; Tue, 4 Jun 2013 21:05:42 -0700 (PDT)
Received: by mail-wi0-f177.google.com with SMTP id hr14so859817wib.10 for <json@ietf.org>; Tue, 04 Jun 2013 21:05:40 -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; bh=5yDEpww80qnfBGwu9LgzjWjYgUQ4R90bJ0LEs1hrVJM=; b=UYRo3Rk0rzHpCtPJWj0+SH3wAnHjaUDNwRtN8SN98SKMaofp+OxygtHbOtRPAyyWHe UD5AUIIO8FhSzQq7Euy24I+WEO6+47wFHCtrcjoYGzuzxOvcOXnmxWaL66X8Af0yxxSu 6jHBQSYFZYPi5xjapSqet3BWAbdUT8g+SMlOUrIjrn4Izku2s0ZQGb3o7ohCmJy5f3Ar KcZz3dmiqBFvoSnSYo+hhBUd2K60t78FbPx9E9TWn2TEJGuRulI8J7oVFNdkLoG+bHtD D2zBeMcXowVRjqZIi3FE8mboKZ4qVdPQtkP41+4sftXpnm48G1lIKfSCZfN14Kupbha+ NBkQ==
MIME-Version: 1.0
X-Received: by 10.180.183.139 with SMTP id em11mr4457208wic.16.1370405140818; Tue, 04 Jun 2013 21:05:40 -0700 (PDT)
Received: by 10.216.63.136 with HTTP; Tue, 4 Jun 2013 21:05:40 -0700 (PDT)
In-Reply-To: <CAChr6SxzAQ+MFG60foM915Za+nroo6yy=JL1N40dZsx84u6rMg@mail.gmail.com>
References: <CAK3OfOgPGi4PKxKAGEG=PCv-xaszMqWpUUUH2B9f0UaeMMO1gQ@mail.gmail.com> <C42654A3-E218-45A8-B368-4A60CB89619D@vpnc.org> <C4D8E604-E4F8-408B-B7DD-97226300C212@tzi.org> <CAK3OfOjDp=S=HZ5LTP3L+rqq1VjhSShakmBOJD9aPiN8fSULKw@mail.gmail.com> <C30B2D0D-75A7-49A5-A190-5AD5DC1FCDCC@vpnc.org> <CAK3OfOi6uNcXLCcStg90j2LqqdyVWQeoBAd0Mad-EjFEDyixpw@mail.gmail.com> <51AE63B1.80800@crockford.com> <CAChr6Szu11Qtbc9JGrG-bNvq=SCN-f81dZ1GoH_sz+KvddE0nw@mail.gmail.com> <BF7E36B9C495A6468E8EC573603ED9411527BC7D@xmb-aln-x11.cisco.com> <CAChr6SxzAQ+MFG60foM915Za+nroo6yy=JL1N40dZsx84u6rMg@mail.gmail.com>
Date: Tue, 4 Jun 2013 23:05:40 -0500
Message-ID: <CAK3OfOgO_DgP=O-hpMRJNYicnWs9S00zY=B2xZ5tM6++RqXYig@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: R S <sayrer@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: "json@ietf.org" <json@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, Douglas Crockford <douglas@crockford.com>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
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, 05 Jun 2013 04:05:50 -0000

On Tue, Jun 4, 2013 at 9:06 PM, R S <sayrer@gmail.com> wrote:
> On the issue at hand, it might be good to rewrite the beginning of the
> "Number" section along these lines:
>
> - The representation of numbers is similar to that used in most programming
> languages.
> + JSON numbers are arbitrary precision, and represented in a manner similar
> to that used in most programming languages.

It might be nice to be able to specify some ranges that MUST be
supported by decoders, but in practice I think we can't (and probably
shouldn't try to) even do that.

Nico
--