IETF Logo Mail Archive

Re: [Json] [Technical Errata Reported] RFC8259 (7673)

Carsten Bormann <cabo@tzi.org> Wed, 11 October 2023 15:30 UTC

Return-Path: <cabo@tzi.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 3D151C15109C for <json@ietfa.amsl.com>; Wed, 11 Oct 2023 08:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ABI-YECrdvY for <json@ietfa.amsl.com>; Wed, 11 Oct 2023 08:30:30 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 879BCC151089 for <json@ietf.org>; Wed, 11 Oct 2023 08:30:29 -0700 (PDT)
Received: from eduroam-pool10-229.wlan.uni-bremen.de (eduroam-pool10-229.wlan.uni-bremen.de [134.102.90.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4S5GtV5ZRSzDD5j; Wed, 11 Oct 2023 17:30:26 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <7b158d11-6472-e3d9-8745-48c0d8f8f503@gmail.com>
Date: Wed, 11 Oct 2023 17:30:26 +0200
Cc: json@ietf.org
X-Mao-Original-Outgoing-Id: 718731025.736739-c6a0bf16c4d70d98a558c6ad963d5b40
Content-Transfer-Encoding: quoted-printable
Message-Id: <267310E7-6732-44DB-A938-D08F8589ACB7@tzi.org>
References: <20231011065619.82BC5E6D69@rfcpa.amsl.com> <CE22DEB9-FA3A-439B-A4CD-79138DBB18A5@cursive.net> <CAHBU6is2zYR8V-BK8_OVe8iWhfxRym=+=4s1X26e1kfJzOWGdg@mail.gmail.com> <CAHBU6ismHz2bo6zUVeJ5cvDtz=VM=4_Ef_RSa0_oSnjFWwKUkw@mail.gmail.com> <7b158d11-6472-e3d9-8745-48c0d8f8f503@gmail.com>
To: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/pfELZCDG4kPgMJX1uA8Lx4BoiFo>
Subject: Re: [Json] [Technical Errata Reported] RFC8259 (7673)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 11 Oct 2023 15:30:35 -0000

On 2023-10-11, at 17:23, Peter F. Patel-Schneider <pfpschneider@gmail.com> wrote:
> 
> It would be reasonable to improve the wording in the RFC to make it align better with the wording in other places, i.e., use "and the control characters U+0000 through U+001F" instead of "and the control characters (U+0000 through U+001F)".  Whether this change is worth an errata is a separate issue.

This could become a HFDU(*), changing this to 

> and the C0 control characters (U+0000 through U+001F)

But I’d think there is absolutely no potential for misunderstanding here and the errata report should be rejected on those grounds.

Grüße, Carsten

(*) Which will never happen :-)

v2.23.0 | Report a Bug | By Email