The following errata report has been submitted for RFC7158,
"The JavaScript Object Notation (JSON) Data Interchange Format".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=7158&eid=3907

--------------------------------------
Type: Technical
Reported by: Marc Lehmann <rfc7158@schmorp.de>

Section: 1.3, 2.0, 3.

Original Text
-------------
   This document's goal is to apply the errata, remove inconsistencies
   with other specifications of JSON, and highlight practices that can
   lead to interoperability problems.

   A JSON value MUST be an object, array, number, or string, or one of
   the following three literal names:


Corrected Text
--------------


Notes
-----
Since RFC7158 breaks compatibility with the specifications, this should be
duly noted.

The original specification (both in RFC4627 and on www.json.org, I know of
no other JSON "specifications") specify JSON as a self-delimited format,
that is, each JSON text can be parsed without extra delimiters or length
wrapping, and some network protocols came to rely on this by asking for
back-to-back JSON texts.

RFC7158 changes this, so protocols that formerly consumed JSON texts
without any extra wrapping are no longer compliant to this new
specification. These protocols are now in violation of RFC7158, and they
can't be fixed in a backwards compatible way.

This introduces a big incompatibility between RFC7158 implementations and
older ones, and this is not at all reflected in the introduction nor, as
far as I could see, anywhere else in the new rfc.

Thus it is likely that this is a specification error - the new RFC
should either warn that the new RFC is not compatible with the existign
specifications, or be fixed to be compatible.

I think changing JSON in an incompatible way at this stage would be an
extremely bad idea.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC7158 (draft-ietf-json-rfc4627bis-10)
--------------------------------------
Title               : The JavaScript Object Notation (JSON) Data Interchange Format
Publication Date    : March 2014
Author(s)           : T. Bray, Ed.
Category            : PROPOSED STANDARD
Source              : JavaScript Object Notation
Area                : Applications
Stream              : IETF
Verifying Party     : IESG