[Json] [Technical Errata Reported] RFC7159 (3984)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 09 May 2014 07:46 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 CD1231A01FF for <json@ietfa.amsl.com>; Fri, 9 May 2014 00:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level:
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 JE3NgO3BbzSx for <json@ietfa.amsl.com>; Fri, 9 May 2014 00:46:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1F84D1A01FD for <json@ietf.org>; Fri, 9 May 2014 00:46:23 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 981D418000D; Fri, 9 May 2014 00:45:38 -0700 (PDT)
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: <20140509074538.981D418000D@rfc-editor.org>
Date: Fri, 09 May 2014 00:45:38 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/json/Hc-17qSHNjOOqtVDGoGQxJemJeo
Cc: rfc-editor@rfc-editor.org, json@ietf.org, alainb06@free.fr
Subject: [Json] [Technical Errata Reported] RFC7159 (3984)
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: Fri, 09 May 2014 07:46:25 -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=3984 -------------------------------------- Type: Technical Reported by: Alain BENEDETTI <alainb06@free.fr> 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
- [Json] [Technical Errata Reported] RFC7159 (3984) RFC Errata System
- Re: [Json] [Technical Errata Reported] RFC7159 (3… Tim Bray
- Re: [Json] [Technical Errata Reported] RFC7159 (3… Matt Miller
- [Json] [Errata Rejected] RFC7159 (3984) RFC Errata System