Re: [Json] [Technical Errata Reported] RFC7159 (3984)

[Matt Miller <[e-mail]>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

RFC Editor: please reject this erratum.

The WG's consensus was to leave the full range present in the ABNF and
add the interoperability guidance about values outside the Unicode
accepted range.


Thank you,

- -- 
- - m&m

Matt Miller < [e-mail] >
Cisco Systems, Inc.

On 5/9/14, 1:45 AM, RFC Errata System wrote:
> The following errata report has been submitted for RFC7159, "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=7159&eid=3984
> 
> -------------------------------------- Type: Technical Reported by:
> Alain BENEDETTI <[e-mail]>
> 
> Section: 7
> 
> Original Text ------------- unescaped = %x20-21 / %x23-5B /
> %x5D-10FFFF
> 
> Corrected Text -------------- unescaped = %x20-21 / %x23-5B /
> %x5D-D7FF / %xE000-10FFFF
> 
> Notes ----- Section 1 says: [START QUOTE] A string is a sequence of
> zero or more Unicode characters [UNICODE]. Note that this citation
> references the latest version of Unicode rather than a specific
> release. [END QUOTE]
> 
> Section 8.2 emphasizes on the characters not allowed by the Unicode
> norm: [START QUOTE] However, the ABNF in this specification allows
> member names and string values to contain bit sequences that cannot
> encode Unicode characters; for example, "\uDEAD" (a single unpaired
> UTF-16 surrogate). [END QUOTE]
> 
> The ABNF cannot at the same time allow non conformant Unicode
> codepoints (section 7) and states conformance to Unicode (section
> 1).
> 
> Therefore, there is an incoherence that must be fixed between
> section 1 (and 8.2 that emphasizes it) and section 7. Hence the
> proposition of modification in section 7.
> 
> The other less preferable solution to this fix incoherence in
> RFC7159 would have been to NOT require Unicode conformance.
> 
> 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.
> 
> -------------------------------------- RFC7159
> (draft-ietf-json-rfc4627bis-rfc7159bis) 
> -------------------------------------- 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
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTbP3IAAoJEDWi+S0W7cO1mjIH/3v6dAZl59zVAo47htMfnuHB
lnv9lcP7exnHwf6fygF807CXVa5nknq8W24DyaSZWscnVm+BuHCU6/3e/ra+8Hhk
ZSuOqnb3Axt0tkGOvXys8HNq25tfGmnaaV6FGLPHRr/ZNcQSh9VohFcbcisi/5tc
aGh0kp6PbZdGslMczZMPBEvwTUD1+z7IhcC4M2MSIHjIr7OZoFklmzRsglaCu2+l
iWz3bZCezKjFjCm9PwP6adQ0/myKEOGKzMUBi1eddGNTJ2+pmcmNgi+3aLxAsR1B
Rpd9UB/FfbibyRI7p4voQgxqowM/0zrUAlWyuzrQZLAH8r+UWeV0hQ2qjRAEB7A=
=Oju4
-----END PGP SIGNATURE-----