IETF Logo Mail Archive

[Jsonpath] Re: [Technical Errata Reported] RFC9535 (8343)

Carsten Bormann <cabo@tzi.org> Thu, 27 March 2025 16:20 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: jsonpath@mail2.ietf.org
Delivered-To: jsonpath@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 0902A1343C38 for <jsonpath@mail2.ietf.org>; Thu, 27 Mar 2025 09:20:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.189
X-Spam-Level:
X-Spam-Status: No, score=-4.189 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sn_s9Ybv-8XV for <jsonpath@mail2.ietf.org>; Thu, 27 Mar 2025 09:20:21 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 747861343C33 for <jsonpath@ietf.org>; Thu, 27 Mar 2025 09:20:21 -0700 (PDT)
Received: from [192.168.217.145] (p548dc3ec.dip0.t-ipconnect.de [84.141.195.236]) (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 4ZNpm30SjVzDCkk; Thu, 27 Mar 2025 17:20:18 +0100 (CET)
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: <c6a4f68a-48c9-4c3f-b705-873c41c639be@hxr.us>
Date: Thu, 27 Mar 2025 17:20:17 +0100
X-Mao-Original-Outgoing-Id: 764785217.447871-4ca4a0984750dbc767ac22960365042a
Content-Transfer-Encoding: quoted-printable
Message-Id: <EE91DAC9-336A-48F2-A6B4-801383513519@tzi.org>
References: <20250324144730.970D2210673@rfcpa.rfc-editor.org> <F5AABC54-3B2A-4621-A77E-07CC24B87642@tzi.org> <f87965d1-c1db-4c5a-a0c6-f5f9d61de921@hxr.us> <EBFD5D95-629B-4151-AEFF-A8651A0937A1@tzi.org> <CAKspqcVxWoWBZ2rB2MVRhhPYgXJGp285cMtL1TUCJCUtn4qvDw@mail.gmail.com> <52840452-8f98-4da2-8bea-d62e70638616@hxr.us> <CAKspqcWrHVaUPH2FGvi7+47HkmVWrNB-cTGkR8-d03J8-7aYoQ@mail.gmail.com> <3FAB5B50-2CEB-4E62-BF0A-9108EE4AE51F@tzi.org> <397a85f4-b7db-4def-a811-3d61c280ad5f@hxr.us> <CAKspqcV5dXjv5ZwdFMAQKV7ktRe21QiyteAkaWgM=2-SpDj=cA@mail.gmail.com> <FA32CC46-C83F-4A28-AF7D-58F7F4082E7D@tzi.org> <c6a4f68a-48c9-4c3f-b705-873c41c639be@hxr.us>
To: "Andrew Newton (andy)" <andy@hxr.us>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Message-ID-Hash: APWWIJOP2DALVSM7PR2K4LUVMM52KYMD
X-Message-ID-Hash: APWWIJOP2DALVSM7PR2K4LUVMM52KYMD
X-MailFrom: cabo@tzi.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Vladimir Gorej <vladimir.gorej@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>, stefan.goessner@fh-dortmund.de, glyn.normington@gmail.com, Orie Steele <orie@transmute.industries>, james.ietf@gmail.com, Tim Bray <tbray@textuality.com>, jsonpath@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Jsonpath] Re: [Technical Errata Reported] RFC9535 (8343)
List-Id: Discussion of JSONPath syntax <jsonpath.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/4TecGShvZr5PYnw05Qx0AAo3uuo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jsonpath>
List-Help: <mailto:jsonpath-request@ietf.org?subject=help>
List-Owner: <mailto:jsonpath-owner@ietf.org>
List-Post: <mailto:jsonpath@ietf.org>
List-Subscribe: <mailto:jsonpath-join@ietf.org>
List-Unsubscribe: <mailto:jsonpath-leave@ietf.org>

On 2025-03-27, at 16:09, Andrew Newton (andy) <andy@hxr.us> wrote:
> 
> https://www.rfc-editor.org/verify_errata_select.php?eid=8343
> 
> https://www.rfc-editor.org/verify_errata_select.php?eid=8352
> 
> https://www.rfc-editor.org/verify_errata_select.php?eid=8353
> 
> https://www.rfc-editor.org/verify_errata_select.php?eid=8354

I don’t think we have access to those.

> I was asked by the RFC Editor to have these be separate reports, which I was able to do.

I’m wondering about the rationale, because atomizing errata reports is definitely NOT how these things should be done.

Grüße, Carsten

v2.45.0 | Report a Bug | By Email | System Status