Re: [Json] Limitations on number size?

"John Levine" <johnl@taugh.com> Tue, 09 July 2013 22:26 UTC

Return-Path: <johnl@iecc.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 EA6BA11E817A for <json@ietfa.amsl.com>; Tue, 9 Jul 2013 15:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.656
X-Spam-Level:
X-Spam-Status: No, score=-110.656 tagged_above=-999 required=5 tests=[AWL=0.543, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, 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 fmftterBlNq9 for <json@ietfa.amsl.com>; Tue, 9 Jul 2013 15:26:29 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 38A9421F9CDC for <json@ietf.org>; Tue, 9 Jul 2013 15:26:25 -0700 (PDT)
Received: (qmail 14553 invoked from network); 9 Jul 2013 22:26:25 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 9 Jul 2013 22:26:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51dc8e11.xn--30v786c.k1307; i=johnl@user.iecc.com; bh=jIyL/0poCAGrGwHzHhgLKUYe7HLK+0CdEM2NM5/gIOA=; b=MeVJbJG5qciVw7IOY1jvsXwKbFO+O9bBFed6BjK8GTd8Uectn1WBG/OSQOykKzhNMuVNKM/mQwaSvdPSR2Deh4RtcIiL/WIL07IRSAv3N9UfMeUxtKLzIAH+1uknYjx4uy1PscLmUNZFOlbkkzfD3BD5IrLLsh5ydtBjPXS3Sdt2UEKJkG54nv8RfSRut8mvtiOgYFNiptMid8b3AkLzPzH0PHLGs9YBAaQwf070PUBt9ppxC0aO/F6DExDc5Rkv
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51dc8e11.xn--30v786c.k1307; olt=johnl@user.iecc.com; bh=jIyL/0poCAGrGwHzHhgLKUYe7HLK+0CdEM2NM5/gIOA=; b=X4MZsbpGFeUCE/GO10E4MUzyXR6JbNvrRep+vxmVvoDBqszO3WOb3MMERuK+oqrdJWjLL+XERK0GFphZo9ypSQv2fj2rAPXPEn9WcmWupsSXcEo7IxNQLkHoSB31aV4oqAd/3B0EvtHzUy6lHLwUw0XfaJe6G3ZngPRqJMLVMLVhUkaYElpBdLJOSf1iyvgzeHMxKviJZRKmPfeV42BC/7HnVnx+Bi6T/e6+wNYgI9CFNaPOAYrkCZWYCvkppnAt
Date: 9 Jul 2013 22:26:01 -0000
Message-ID: <20130709222601.32831.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: json@ietf.org
In-Reply-To: <CAK3OfOi_q8KTQd-RW7PPhS5ZXXYSMEJ57uKTKL-ck6ocd6Nbeg@mail.gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: nico@cryptonector.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: Tue, 09 Jul 2013 22:26:46 -0000

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

Do we actually know?  Or is it just whatever number format a library's
underlying language happens to provide?