IETF Logo Mail Archive

Re: [Json] Limitations on number size?

"Matt Miller (mamille2)" <mamille2@cisco.com> Wed, 05 June 2013 01:46 UTC

Return-Path: <mamille2@cisco.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 7829A21F9A7C for <json@ietfa.amsl.com>; Tue, 4 Jun 2013 18:46:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.3
X-Spam-Level:
X-Spam-Status: No, score=-9.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 jpvV4MINrjCx for <json@ietfa.amsl.com>; Tue, 4 Jun 2013 18:46:16 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 109A921F9A6C for <json@ietf.org>; Tue, 4 Jun 2013 18:46:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7060; q=dns/txt; s=iport; t=1370396776; x=1371606376; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=SGoE8cgWATGipSdDWkWxTqjcLblilK1fgh/dHwCjREM=; b=kT8yQk8TOupXOcamfFMt9CZi6y2Hzmxbcpo4lU9VoeMUKD0uU3PSDcuh gH8FQYBv3BegyF7r6WGUp7Kk2Kz+8aYmASCzQB+5oDZKiukiSDi5Vcaaj mGqVvLqk3X7Dml3YPSbtra0IgJhzBZUJBXMw8dfvc+gJRrDJ7zZSqTlUc k=;
X-Files: smime.p7s : 4136
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApAFAICXrlGtJV2d/2dsb2JhbABagwmDJbw1gQAWdIIjAQEBAwF5BQsCAQgiJAIfESUCBA4FCAaHbQMJBrRuDYh1jEmCKjEHgnphA5AAgSyELI4EhSODD4In
X-IronPort-AV: E=Sophos; i="4.87,803,1363132800"; d="p7s'?scan'208"; a="218851566"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-8.cisco.com with ESMTP; 05 Jun 2013 01:46:15 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r551kFEZ025262 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 5 Jun 2013 01:46:15 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.24]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0318.004; Tue, 4 Jun 2013 20:46:15 -0500
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: R S <sayrer@gmail.com>
Thread-Topic: [Json] Limitations on number size?
Thread-Index: AQHOYKhtiMKtDlrMGkiV0TSaDl838JklWmSAgAAq/YCAAGawgIAAQpQAgABB84CAAD0dgIAAAbgA
Date: Wed, 05 Jun 2013 01:46:14 +0000
Message-ID: <BF7E36B9C495A6468E8EC573603ED9411527BC7D@xmb-aln-x11.cisco.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>
In-Reply-To: <CAChr6Szu11Qtbc9JGrG-bNvq=SCN-f81dZ1GoH_sz+KvddE0nw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.123.195]
Content-Type: multipart/signed; boundary="Apple-Mail=_2C4904B5-4160-47CD-9289-2AAB9129F3C7"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Cc: Nico Williams <nico@cryptonector.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Douglas Crockford <douglas@crockford.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: Wed, 05 Jun 2013 01:46:22 -0000

On Jun 4, 2013, at 7:40 PM, R S <sayrer@gmail.com>
 wrote:

> On Tue, Jun 4, 2013 at 3:01 PM, Douglas Crockford <douglas@crockford.com>wrote:
> 
>> 
>> Keep in mind that this format has been working successfully in the wild
>> for over a decade. The goal here should be to do the least that is
>> necessary to formally upgrade its status from Informational, not to attempt
>> to fix something that is already working well enough. It is only because it
>> has been working well enough that we are considering the upgrade.
> 
> 
> 
> Strongly agree. We should only be changing things that are incorrect or
> obsolete. You can't write an interoperable JSON implementation by reading
> RFC 4627 at the moment, but number precision is not one of the
> deal-breakers.
> 

Would you be willing to contribute specific wording proposals to address those deal-breakers?


- m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.

v2.23.0 | Report a Bug | By Email