[Json] [Technical Errata Reported] RFC7159 (4220)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 05 January 2015 22:04 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 037F21A8F50 for <json@ietfa.amsl.com>; Mon, 5 Jan 2015 14:04:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wwubSezm2SDL for <json@ietfa.amsl.com>; Mon, 5 Jan 2015 14:04:07 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 02B271A8F46 for <json@ietf.org>; Mon, 5 Jan 2015 14:04:07 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E7E1F1832B6; Mon, 5 Jan 2015 14:03:44 -0800 (PST)
To: tbray@textuality.com, barryleiba@computer.org, presnick@qti.qualcomm.com, mamille2@cisco.com, paul.hoffman@vpnc.org
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150105220344.E7E1F1832B6@rfc-editor.org>
Date: Mon, 05 Jan 2015 14:03:44 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/json/M6Uq4Ei9peXiM-o8e5o3m1vTUz4
Cc: rfc-editor@rfc-editor.org, json@ietf.org, tg@mirbsd.org
Subject: [Json] [Technical Errata Reported] RFC7159 (4220)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jan 2015 22:04:09 -0000
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=4220 -------------------------------------- Type: Technical Reported by: mirabilos <tg@mirbsd.org> Section: 7 Original Text ------------- [â¦] All Unicode characters may be placed within the quotation marks, except for the characters that must be escaped: quotation mark, reverse solidus, and the control characters (U+0000 through U+001F). [â¦] unescaped = %x20-21 / %x23-5B / %x5D-10FFFF Corrected Text -------------- [â¦] All Unicode characters may be placed within the quotation marks, except for the characters that must be escaped: quotation mark, reverse solidus, the control characters (U+0000 through U+001F), and codepoints beyond the BMP (U-00010000 through U-0010FFFF). [â¦] unescaped = %x20-21 / %x23-5B / %x5D-FFFF Notes ----- ECMA-262 states that "ECMAScript source text is assumed to be a sequence of 16-bit code units", and everything must be converted to UTF-16 first. This stems from the fact that Javaâ¢, like Win32, used UCS-2, which only later got extended to allow UTF-16. This means that SMP codepoints must always be escaped into their twelve-character form. This is also an interoperability issue: implementations may wish to parse (or generate) JSON by using a wchar_t data type (in C) which, depending on the platform, may be only 16 bits wide. ECMAscript allows for this. Instructions: ------------- This erratum 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
- [Json] [Technical Errata Reported] RFC7159 (4220) RFC Errata System
- Re: [Json] [Technical Errata Reported] RFC7159 (4… Bjoern Hoehrmann
- Re: [Json] [Technical Errata Reported] RFC7159 (4… Carsten Bormann
- Re: [Json] [Technical Errata Reported] RFC7159 (4… Carsten Bormann
- Re: [Json] [Technical Errata Reported] RFC7159 (4… Paul Hoffman
- [Json] [Errata Rejected] RFC7159 (4220) RFC Errata System