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

[Anders Rundgren <[e-mail]>]

On 2017-07-22 09:36, Pete Cordell wrote:
> On 21/07/2017 17:07, Carsten Bormann wrote:
<snip>
> Here's another attempt, based on the feedback:
> 
>       JSON text that is to be machine interpreted in a layer of a protocol
>       stack directly related to underlying network activity (e.g.
>       JSON text in a REST over HTTP application, as opposed to JSON text
>       transported opaquely over a generic data transfer protocol), and
>       JSON text identified with the application/json media type, MUST be
>       encoded using UTF-8 [RFC3629].


I don't have any text to offer but I believe that UFT-8 encoding is the
only recommendable way for transferring JSON data from one system to
another which includes lots of other use case than HTTP.  For example:
Writing JSON to databases, usage in WebSocket messages, or simply putting
JSON in file.

Yes, it seems to me that "Serialized format"/"External representation" is
really the common denominator rather than networks and/or protocols.

Anders