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

[Julian Reschke <[e-mail]>]

On 2017-07-21 09:42, Pete Cordell wrote:
> On 21/07/2017 06:14, Carsten Bormann wrote:
>> On Jul 21, 2017, at 06:20, Julian Reschke <[e-mail]> wrote:
>>>
>>>>
>>>> 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].
>>>
>>> This gets us back to the suggestion to apply this rule to the use of 
>>> the application/json media type (and types derived from it).
>>
>> The nit-picking opportunity here is that we don’t want to change NFS 
>> in case someone accesses a file with UTF-32 JSON in it over the 
>> network protocol NFS.  We could recognize this as nit-picking, or use 
>> a phrase such as “intended by the protocol to be JSON” — media types 
>> are not the only way such an intention could take shape.
> 
> Clearly one person's nit-picking is another person's attempt to reduce 
> confusion (especially of those not party to this discussion)!

+1

> I think Allen Wirts-Brock's "IETF-specified protocol" is the clearest 
> and simplest 
> (https://mailarchive.ietf.org/arch/msg/json/0TVI13NELfsuC7FscgDvXZThenE 
> ).  e.g.
> 
>      IETF-specified protocols MUST encode JSON text using UTF-8
>      [RFC3629].
> 
> Pete Cordell
> Codalogic Ltd
> Read & write XML in C++, http://www.xml2cpp.com

-1

So if a specify a protocol outside the IETF, and use application/json as 
HTTP payload, I *can* use UTF-16?

Best regards, Julian