IETF Logo Mail Archive

[Json] [Technical Errata Reported] RFC7493 (6861)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 25 February 2022 03:33 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1A863A1140 for <json@ietfa.amsl.com>; Thu, 24 Feb 2022 19:33:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 01vC8P9SBhGj for <json@ietfa.amsl.com>; Thu, 24 Feb 2022 19:33:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2ECEF3A113E for <json@ietf.org>; Thu, 24 Feb 2022 19:33:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id ECC44289E1; Thu, 24 Feb 2022 19:33:22 -0800 (PST)
To: tbray@textuality.com, superuser@gmail.com, francesca.palombini@ericsson.com, mamille2@cisco.com, paul.hoffman@vpnc.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rfc7493-errata@chrismorgan.info, json@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220225033322.ECC44289E1@rfc-editor.org>
Date: Thu, 24 Feb 2022 19:33:22 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/YnKz8KXtzGd2Ba9o9lQqzdhK5-8>
Subject: [Json] [Technical Errata Reported] RFC7493 (6861)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Feb 2022 03:33:28 -0000

The following errata report has been submitted for RFC7493,
"The I-JSON Message Format".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6861

--------------------------------------
Type: Technical
Reported by: Chris Morgan <rfc7493-errata@chrismorgan.info>

Section: 2.1

Original Text
-------------
   Object member names, and string values in arrays and object members,
   MUST NOT include code points that identify Surrogates or
   Noncharacters as defined by [UNICODE].

Corrected Text
--------------
   Object member names, and string values,
   MUST NOT include code points that identify Surrogates or
   Noncharacters as defined by [UNICODE].

Notes
-----
The expression “string values in arrays and object members” is overly qualified, excluding cases where the *entire message* is a string value, which should clearly be covered also. So the qualification “in arrays and object members” should be removed.

Supporting citations:

RFC 7493, section 2: “An I-JSON message is a JSON text, as defined by RFC 7159.”

RFC 7159, section 2: “A JSON text is a serialized value.  Note that certain previous specifications of JSON constrained a JSON text to be an object or an array. […]”

RFC 7159, section 2:

      JSON-text = ws value ws

RFC 7159, section 3:

      value = false / null / true / object / array / number / string

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  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC7493 (draft-ietf-json-i-json-06)
--------------------------------------
Title               : The I-JSON Message Format
Publication Date    : March 2015
Author(s)           : T. Bray, Ed.
Category            : PROPOSED STANDARD
Source              : JavaScript Object Notation
Area                : Applications
Stream              : IETF
Verifying Party     : IESG

v2.23.0 | Report a Bug | By Email