Re: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-04.txt

[Peter Saint-Andre - Filament <[e-mail]>]

I have three comments about this new sentence:

   When transmitting over a network protocol, or as a payload of a
   network protocol intended to be interpreted as part of a protocol,
   JSON text MUST be encoded in UTF-8 (Section 3 of [UNICODE]).

1. Is the term "network protocol" sufficiently clear? It might be
interpreted as a communications protocol at the network layer (e.g.,
IP), not as an application-layer protocol above the network layer -
which is where most or all usage of JSON occurs.

2. What are we trying to say with "as a payload of a network protocol
intended to be interpreted as part of a protocol"?

3. Why do we reference Section 3 of the Unicode Standard for the
definition of UTF-8, not RFC 3629? (Among other things, there's no
guarantee that Section 3 of http://www.unicode.org/versions/latest/ will
continue to talk about UTF-8.)

I suggest:

   When an entity transmits JSON text over a network, e.g. as the
   payload of an application protocol, it MUST encode that text using
   UTF-8 [RFC3629].

Peter

On 7/20/17 4:50 AM, Barry Leiba wrote:
> I've reviewed this version and I think it's ready to publish.
> 
> Barry
> 
> On Wed, Jul 19, 2017 at 4:03 PM, Alexey Melnikov
> <[e-mail]> wrote:
>> As requested by several people, this is the version that includes RFC Editor notes.
>>
>>> On 19 Jul 2017, at 15:45, [e-mail] wrote:
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>> This draft is a work item of the Javascript Object Notation Update WG of the IETF.
>>>
>>>        Title           : The JavaScript Object Notation (JSON) Data Interchange Format
>>>        Author          : Tim Bray
>>>    Filename        : draft-ietf-jsonbis-rfc7159bis-04.txt
>>>    Pages           : 15
>>>    Date            : 2017-07-18
>>>
>>> Abstract:
>>>   JavaScript Object Notation (JSON) is a lightweight, text-based,
>>>   language-independent data interchange format.  It was derived from
>>>   the ECMAScript Programming Language Standard.  JSON defines a small
>>>   set of formatting rules for the portable representation of structured
>>>   data.
>>>
>>>   This document removes inconsistencies with other specifications of
>>>   JSON, repairs specification errors, and offers experience-based
>>>   interoperability guidance.
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/
>>>
>>> There are also htmlized versions available at:
>>> https://tools.ietf.org/html/draft-ietf-jsonbis-rfc7159bis-04
>>> https://datatracker.ietf.org/doc/html/draft-ietf-jsonbis-rfc7159bis-04
>>>
>>> A diff from the previous version is available at:
>>> https://www.ietf.org/rfcdiff?url2=draft-ietf-jsonbis-rfc7159bis-04
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/