Re: [Json] I-D Action: draft-ietf-json-i-json-01.txt

Matt Miller <mamille2@cisco.com> Wed, 18 June 2014 15:13 UTC

Message-ID: <53A1AC89.7030004@cisco.com>
Date: Wed, 18 Jun 2014 09:13:13 -0600
From: Matt Miller <mamille2@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Tim Bray <tbray@textuality.com>
References: <20140613195805.1386.5992.idtracker@ietfa.amsl.com> <CAHBU6ivy-aVuSZPQ1gMp0bXW0yMYq9Vhi1Bydb809rfBR_ag=g@mail.gmail.com> <CFC1BCB7.4FE64%jhildebr@cisco.com> <CAHBU6isENp-JVJ6FVuhrKNsoWqq94dpzYBos0zGGrh9b6UwW2w@mail.gmail.com> <20140617193013.GD29802@mercury.ccil.org> <CAO1wJ5Rz2uDQ3-w=QESDmAo-tRAJdWSCasWkQx9n5NB8dS-+OQ@mail.gmail.com> <CAHBU6itGdvd=UCjoTDtNuA6MRoiqRX7Wpw0fT+wRYBOY3uwNCQ@mail.gmail.com>
In-Reply-To: <CAHBU6itGdvd=UCjoTDtNuA6MRoiqRX7Wpw0fT+wRYBOY3uwNCQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/json/N0bqa9ovIFwCzXz6HDexynI9YVc
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] I-D Action: draft-ietf-json-i-json-01.txt
Precedence: list

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 6/18/14, 9:07 AM, Tim Bray wrote:
> On Tue, Jun 17, 2014 at 3:48 PM, Jacob Davies <jacob@well.com 
> <mailto:jacob@well.com>> wrote:
> 
> "For applications such as cryptography, where exact interchange of 
> much larger numbers is required, it is RECOMMENDED to encode them
> in JSON string values."
> 
> The phrasing of "it is recommended to encode them" seems awkward
> to me. Maybe "it is recommended that such values be encoded as"?
> 
> "encoded" also seems off. Maybe "written", "stored",
> "represented"?
> 
> 
> ?The recommend/encode terminology has been around for a while and ?
> this is the first gripe I?ve heard. Anyone want to pile on? ???
> 
> ?? I am not sure that cryptography is the right example. The most
> common ?? surprising case will be people trying to store arbitrary
> 64-bit ?? integers ??
> 
> ? ?I confess to having cryptography on the brain.  I think he?s
> right, the simplest example is just a 64-bit integer, might as well
> say that; will change unless someone screams.
> 
> 

/me doffs hat

I think that makes sense.  It's a far more common issue for people to
run into than how to encode a key/ciphertext/signature.


- -- 
- - m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJToayJAAoJEDWi+S0W7cO1+l8H+wTF/RZaRP2GuEpsmmYFfbk1
nDRlwWTh9aIYG7a9AlHfp3JO56kDKXJxNvtt7vV4K4mAwSo9AjM53BJdPBTKekVu
BjhmVZD7wIGeUuI1kzSHaWkR9DCslcd5BtwQfwrZbGB6f7LRMsddVngT6cSWHtG8
zC7/rVDVEB1zzxe31fvV/6WJ6GSRi7tLMrsr6W0dDIL9o3MJk13t2aY9bWGuuv1/
YXqcnHuer6ocgie/gjHbQgvzTO5jE+XST6nHJDyI67H8+X79E+/uDrYmD6X3lrwr
R+QmXgGSyZ1lcJkzS0/yjam81+7can1fQPCdGDTCxGwot94iZjzpzYHQF/pDapg=
=Iw01
-----END PGP SIGNATURE-----

[Json] I-D Action: draft-ietf-json-i-json-01.txt internet-drafts
Re: [Json] I-D Action: draft-ietf-json-i-json-01.… Tim Bray
[Json] I-JSON(2014-06-13) Section 4.3. Time and D… Stefan Drees
Re: [Json] I-JSON(2014-06-13) Section 4.3. Time a… Tim Bray
Re: [Json] I-JSON(2014-06-13) Section 4.3. Time a… John Cowan
Re: [Json] I-D Action: draft-ietf-json-i-json-01.… Joe Hildebrand (jhildebr)
Re: [Json] I-D Action: draft-ietf-json-i-json-01.… Martin J. Dürst
Re: [Json] I-D Action: draft-ietf-json-i-json-01.… Tim Bray
Re: [Json] I-D Action: draft-ietf-json-i-json-01.… John Cowan
Re: [Json] I-D Action: draft-ietf-json-i-json-01.… Jacob Davies
Re: [Json] I-D Action: draft-ietf-json-i-json-01.… Tim Bray
Re: [Json] I-D Action: draft-ietf-json-i-json-01.… Tim Bray
Re: [Json] I-D Action: draft-ietf-json-i-json-01.… Matt Miller