Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03 [rfc7159bis scope]

[Peter Cordell <[e-mail]>]

On 16/03/2017 20:25, Matthew A. Miller wrote:
> To keep the change from being too drastic, I think it necessary to leave
> in the text forbidding a byte order mark.
>
> For completeness, the complete text for 8.1 would be:
>
> """
>    JSON text SHALL be encoded in UTF-8 [UNICODE] (Section 3).
>
>    Implementations MUST NOT add a byte order mark to the beginning of a
>    JSON text.  In the interests of interoperability, implementations
>    that parse JSON texts MAY ignore the presence of a byte order mark
>    rather than treating it as an error.
> """
>
> That said, I'm not quite sure about going that far.  The web certainly
> uses UTF-8 and no other, but the scope is greater than that.  I would
> suggest keeping much of Peter's original text, with a small change to
> include the prohibition of encodings outside of UTF-8/-16/-32[1]:


I'm wondering, is it 'legally' permissible for the first paragraph of 
8.1 to be something along the lines of:

    JSON text SHOULD be encoded in UTF-8 [UNICODE] (Section 3).  JSON
    text associated with the application/json MIME media type MUST be
    encoded in UTF-8.

???

Cheers,

Pete Cordell
Codalogic Ltd