Re: [Json] Call for Consensus: Proposed Text for "8.1 Character Encoding"

["Matthew A. Miller" <[e-mail]>]

Hello all,

I see consensus for the updated text below.  A note to the RFC editor is
added to ensure publication does not move forward until section 8.1 is
updated, and the change noted in the appendix.

"""
8.1.  Character Encoding

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]).

Previous specifications of JSON have not required the use of UTF-8
when transmitting JSON text. However, the vast majority of
JSON-based software implementations have chosen to use the UTF-8
encoding, to the extent that it is the only encoding that achieves
interoperability.

Implementations MUST NOT add a byte order mark (U+FEFF) to the
beginning of a networked-transmitted 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.
"""


Thank you all that participated in the discussion.

- m&m

Matthew A. Miller
JSONbis Chair