Re: [Json] I-JSON Topic #5: Numbers

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 29 April 2014 17:33 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A3DE1A093C for <json@ietfa.amsl.com>; Tue, 29 Apr 2014 10:33:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6sfP7Q-_6cDA for <json@ietfa.amsl.com>; Tue, 29 Apr 2014 10:33:53 -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 D8DA41A092A for <json@ietf.org>; Tue, 29 Apr 2014 10:33:53 -0700 (PDT)
Received: from [10.20.30.90] (142-254-17-198.dsl.dynamic.fusionbroadband.com [142.254.17.198]) (authenticated bits=0) by hoffman.proper.com (8.14.8/8.14.7) with ESMTP id s3THXpqE062705 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <json@ietf.org>; Tue, 29 Apr 2014 10:33:52 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 142-254-17-198.dsl.dynamic.fusionbroadband.com [142.254.17.198] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <535EB3BF.8080606@cisco.com>
Date: Tue, 29 Apr 2014 10:33:50 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <295B22FF-2677-4FC8-B9B8-B59D9F4B78D2@vpnc.org>
References: <535EB3BF.8080606@cisco.com>
To: IETF JSON WG <json@ietf.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/json/DPhO20i0A30r8hmFcUc-aoMZu7U
Subject: Re: [Json] I-JSON Topic #5: Numbers
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Apr 2014 17:33:58 -0000

<no hat>

> "draft-i-json-01 says that you MUST not put in a string representing a
> number with greater precision/magnitude than IEEE754 doubles can
> support.   I think this is a good idea but I'm a little nervous
> because I've never written the code; if this is unreasonably hard at
> either the sending or receiving end someone should say so."

From the comments so far, it seems like it is not clear how to make such restrictions in some languages. If we can't be definitive about what we mean, we should remove it. RFC 7159 has pretty strong wording already.

--Paul Hoffman