IETF Logo Mail Archive

[Jsonpath] Re: RFC9839 and unicode chars to avoid

Mateusz Gienieczko <mat@gienieczko.com> Wed, 21 January 2026 21:47 UTC

Return-Path: <mat@gienieczko.com>
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 78CB2AB2B9F7 for <jsonpath@mail2.ietf.org>; Wed, 21 Jan 2026 13:47:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gienieczko.com
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 zjCqNDvUFgXt for <jsonpath@mail2.ietf.org>; Wed, 21 Jan 2026 13:47:24 -0800 (PST)
Received: from mail-4399.protonmail.ch (mail-4399.protonmail.ch [185.70.43.99]) (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 1CE36AB2B9EB for <jsonpath@ietf.org>; Wed, 21 Jan 2026 13:47:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gienieczko.com; s=protonmail3; t=1769032036; x=1769291236; bh=Buzk7wYV3KlSNmQLthUoaJtPZoIWNH1+CQ+wkIlCTQE=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=SarWiIfPS9gIwCaVuKLjj2K+tlqFi6d2gQFHZgF9zNNlObG91vseOxEc9iKPZbLv3 0d3P0e7O4i0vlJ4/NaYfs0Nluyli49gLoXJNz6PYMtmAzp6LtSy3XH654P2gNdxlMn Upc2HHFtd/tB+p0RvXuCACfGcPoVxtyQ1AsfeUzBEG04aU076d/98PLOlzGNgAntxH yFzpU8b2GMAPfOxe8/NR+1G1h/md4ar18gq8NMBTnqk+CvtaIIcJosF38r6dOohJ0M jVZNMOEQAUCDsQLhJRT7amuSaq9w8ipLeCzjcVAvnwBkTuPLyjJY1oTfFUe5nDWXyE LflSdCk/yPp+A==
Date: Wed, 21 Jan 2026 21:47:13 +0000
To: Carsten Bormann <cabo@tzi.org>
From: Mateusz Gienieczko <mat@gienieczko.com>
Message-ID: <2NXJudlkYI5zZPUfy_h5TTcRX0Qu51den_Z7UT8mYKSMEJR0SFAGdti6-4f5sW64cX89gOGReLWuKmx-XFvpIDBGQpkebYrxFqSSY_fqKR8=@gienieczko.com>
In-Reply-To: <8D1E6492-FC55-4066-B2C9-E0EA3348D483@tzi.org>
References: <CAN+GtW08id-8xoENup+q569cgr7qy4nFXhRi3Una_Up-bCBjFQ@mail.gmail.com> <41395C71-3320-4510-B4BE-795C14A847A4@saxonica.com> <CAN+GtW2eR344z9H_dVXcXOTMF5LCHo6JpjJOhYguD2rF8e7w5w@mail.gmail.com> <8D1E6492-FC55-4066-B2C9-E0EA3348D483@tzi.org>
Feedback-ID: 39860815:user:proton
X-Pm-Message-ID: 5387138553aac22a92c59f246fa8f6354a96bdb6
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="------b58ef88c5cff52b4b1f77fd5308e9c50661b36a024440fb36094a0e29db1718b"; charset="utf-8"
Message-ID-Hash: JAS4TQH72WLMTSNXZM5QFYOMQNXQVPVW
X-Message-ID-Hash: JAS4TQH72WLMTSNXZM5QFYOMQNXQVPVW
X-MailFrom: mat@gienieczko.com
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: Alan Painter <alan.painter@gmail.com>, Michael Kay <mike@saxonica.com>, jsonpath@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Jsonpath] Re: RFC9839 and unicode chars to avoid
List-Id: Discussion of JSONPath syntax <jsonpath.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/dD0kELqDBCZwdDl3wKrepwP9MxM>
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 Wednesday, 21 January 2026 at 22:01, Carsten Bormann <cabo@tzi.org> wrote:

> 

> 

> Hi Alan,
> 

> On Jan 21, 2026, at 12:34, Alan Painter alan.painter@gmail.com wrote:
> 

> > At great risk of belabouring the point, I think that the remarks are not taking into account the tenants of RFC9839.
> 

> 

> I don’t think the recommendations of RFC 9839 are relevant to JSONPath.
> RFC 9839 is about applications (protocols and data formats) choosing their "Unicode Character Repertoire Subsets”.
> JSONPath is not tied to any specific application, so it needs to work independent of what repertoire subset an application may have chosen.
> That includes applications that make use of \u0000 in their strings.

My reading of RFC9839 is that it is relevant precisely to things like JSONPath that define an application-independent protocol. RFC9839 describes issues that arise in applications implementing the protocol if Unicode inputs are unrestricted.

It's just that JSONPath already follows these recommendations since the spec -- I think -- was written with interoperability in mind.

> 

> Grüße, Carsten
> 

> 

> --
> JSONpath mailing list -- jsonpath@ietf.org
> To unsubscribe send an email to jsonpath-leave@ietf.org

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