Re: [Json] Limitations on number size?

Nico Williams <nico@cryptonector.com> Tue, 04 June 2013 18:43 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 DC1D121F918C for <json@ietfa.amsl.com>; Tue, 4 Jun 2013 11:43:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.815
X-Spam-Level:
X-Spam-Status: No, score=-1.815 tagged_above=-999 required=5 tests=[AWL=0.162, 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 vnUKEgI3IgCR for <json@ietfa.amsl.com>; Tue, 4 Jun 2013 11:42:59 -0700 (PDT)
Received: from homiemail-a25.g.dreamhost.com (caiajhbdcbef.dreamhost.com [208.97.132.145]) by ietfa.amsl.com (Postfix) with ESMTP id 0E66A21F9298 for <json@ietf.org>; Tue, 4 Jun 2013 11:36:01 -0700 (PDT)
Received: from homiemail-a25.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a25.g.dreamhost.com (Postfix) with ESMTP id AF60E67812E for <json@ietf.org>; Tue, 4 Jun 2013 11:36:00 -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=adyPF+pAEZZRKHgvLXtr 2oyM53A=; b=fvdcGZSvcQO+lYqOWHMMrSKX0lKfYSbIu97WQp4FanAnoMmbwgg9 tk2mcOzkWpisghXBkkXGoMFSUhLHEkkHamtIVtDBk41GhUEdrYcU2TZKQfJPHIKd mUQjqh35mQo3pqs2+S4uFD4sMN3Bt0u0TF/Pz9nBMXVvjUMU0TNAohc=
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a25.g.dreamhost.com (Postfix) with ESMTPSA id BAF54678248 for <json@ietf.org>; Tue, 4 Jun 2013 11:09:17 -0700 (PDT)
Received: by mail-we0-f172.google.com with SMTP id q56so516859wes.31 for <json@ietf.org>; Tue, 04 Jun 2013 11:09:13 -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=dTP2c7AQAlOhrVbMgf76MTntiI+lNnmMyUBeOyBVmXM=; b=YuKUmyGl1QAuoRfTXYCxclgZLCmiQrTPE+FK9xvNrRLPakz4F1Bg8xewHlPKbFJ/mq jgClzGNF3UEaq0LSOY8aa2aJoWRN5BdfapQe2v6wF9Zu+QVQuqowckXXuedf3xAXq9bf ITQUJyu9IR36uBkbSRFyTpxrUKu20drpzUZ/euFEc9uHGC23LDT1EIP3vsuyVcxOUZkV VI8amB5bLedH4/9v4bh2tLiVyoWd9le9HgBkaLxPZCz78Gv+YXuP0PN3yrm5bCslhtjK LOwVjbEjGBWii4pYYz5spVzcYqkW3dcSr9CNZy2yv8cgxu79JWL5KqjfH9sh3GAP6Bgl z3Cw==
MIME-Version: 1.0
X-Received: by 10.180.185.244 with SMTP id ff20mr2863509wic.0.1370369353646; Tue, 04 Jun 2013 11:09:13 -0700 (PDT)
Received: by 10.216.63.136 with HTTP; Tue, 4 Jun 2013 11:09:13 -0700 (PDT)
In-Reply-To: <51ADB5BF.4040504@drees.name>
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> <51ADB5BF.4040504@drees.name>
Date: Tue, 4 Jun 2013 13:09:13 -0500
Message-ID: <CAK3OfOh2u3NC8cvp8w-4mF=ACpNy4AusAsCYvce5HHrpG7vTbg@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: stefan@drees.name
Content-Type: text/plain; charset=UTF-8
Cc: Carsten Bormann <cabo@tzi.org>, Paul Hoffman <paul.hoffman@vpnc.org>, "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, 04 Jun 2013 18:43:04 -0000

On Tue, Jun 4, 2013 at 4:39 AM, Stefan Drees <stefan@drees.name> wrote:
> In the wild - and in my little eco system at least - JSON is used more like
> ONS (Object Notation Serialization), isn't it?

Often, yes.

> I regard the "indefinite-length stream of digits to be interpreted as a
> number" as a small price for the unversal usability and acceptance of JSON
> as a format.

Off-topic: Every value type in JSON (including null and booleans) has
indefinite-length encoding.  I think this is a highly valuable aspect
of JSON, except for the need to escape strings.

> In conclusion such a change should IMO a) not qualify as a change being
> covered by the charter of the WG and would b) break several interesting use
> cases, where implementers would then be forced to put potentially(!) non
> IEEE754 64-bit number literals always into quotes instead of as now happily
> producing and consuming "streams" of say:

I agree.

Nico
--