[Idna-update] FWD: Unicode IDNA2008 generated tables and release notifications

John C Klensin <klensin@jck.com> Thu, 13 August 2026 23:59 UTC

Return-Path: <klensin@jck.com>
X-Original-To: idna-update@mail2.ietf.org
Delivered-To: idna-update@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 0B2DD129794BF; Thu, 13 Aug 2026 16:59:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1786665591; bh=jwWGiuhyZDkGwik9bKA1xQEgTTJJ5YyPkEC1TisGgqU=; h=Date:From:To:cc:Subject; b=BOlWPCgtDnH30yMlAW0YqkcHAwR2+W3QonJ8lbppl/YBB2dYYInxYdeWoeCSl811x 14ej3Eg3YF+W78Pf4GO3GMllBUYO/Y7FaV0M2StWv3Jjmwvhc8fDSid+rZxBZlzSSZ 1aeYjuTTGFESefcnDsGy6tT1h6b87rup3R3XryO8=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 dF18ijJ_Id9e; Thu, 13 Aug 2026 16:59:50 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by mail2.ietf.org (Postfix) with ESMTP id 5EB52129794BA; Thu, 13 Aug 2026 16:59:49 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <klensin@jck.com>) id 1wufKp-0007ce-5U; Thu, 13 Aug 2026 19:59:43 -0400
Date: Thu, 13 Aug 2026 19:59:35 -0400
From: John C Klensin <klensin@jck.com>
To: Patrik Fältström <paf@paftech.se>, art-ads@ietf.org
Message-ID: <8A1228A1E0058CC7626DD618@PSB>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: klensin@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Message-ID-Hash: WPGCKYUYV62TKLDLFT6GKNX7WCMD4FXV
X-Message-ID-Hash: WPGCKYUYV62TKLDLFT6GKNX7WCMD4FXV
X-MailFrom: klensin@jck.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idna-update.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: idna-update@ietf.org, Asmus Freytag <asmusf@ix.netcom.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Idna-update] FWD: Unicode IDNA2008 generated tables and release notifications
List-Id: "Internationalized Domain Names in Applications (IDNA) implementation and update discussions" <idna-update.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idna-update/s3VSlmSCr0apatz59FLtayUj0_E>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idna-update>
List-Help: <mailto:idna-update-request@ietf.org?subject=help>
List-Owner: <mailto:idna-update-owner@ietf.org>
List-Post: <mailto:idna-update@ietf.org>
List-Subscribe: <mailto:idna-update-join@ietf.org>
List-Unsubscribe: <mailto:idna-update-leave@ietf.org>

FYI, both about this database/file specifically and whatever it might
imply for the state and future of IDN (and maybe i18n generally) work
in the IETF.  Some specifics to add to Asmus's comments...

As far as I can tell, these Idna2008.txt files started only with
Unicode 17.  If there are earlier versions, I could not find them.

I have not attempted to verify this against RFC 9233, much less RFC
8753, neither of which they mention.   Even if we accept the
statement made to Asmus that there were no incompatible changes
introduced with Unicode 18.0, verifying this table would require
checking for incompatibilities and other changes that might require
exceptions for Unicode 13.0 through 15.0 and maybe 16 (RFC 9233 goes
only through Unicode 12.0).

If someone could do that verification and/or was confident enough
that UTC had gotten this right, we should be preparing a short update
to RFC 8753 pointing to the current UTC document at the link given by
Asmus and probably mentioning the per-version files at
https://www.unicode.org/Public/17.0.0/idna/ and
https://www.unicode.org/Public/18.0.0/idna/ and presumably similarly
for each future Unicode version.

While I'd be happy to draft such a document if the IESG can figure
out how to declare rough consensus on the accuracy of the Unicode
idna2008.txt files (I suspect a somewhat more difficult task than one
person's verification as above) _and_ either figure out how we move
forward with the checks required by RFC 8753 or that rough consensus
exists for abandoning those checks. 

I don't have the time or energy to do the Unicode version by version
comparisons and checks.  Especially given some of the reception I've
gotten lately for trying to keep IETF i18n work on some approximation
to on-track, please do not expect me to continue carrying the torch
on this sort of issue.

best,
  john






---------- Forwarded Message ---------
Date: Thursday, August 13, 2026 14:13 -0700
From: Asmus Freytag <asmusf@ix.netcom.com>
To: John C Klensin <klensin@jck.com>
Subject: Unicode IDNA2008 generated tables and release notifications

John,

this is a reminder to you that Unicode, as part of every release,
updates this file:

https://www.unicode.org/Public/draft/idna/Idna2008.txt

My colleagues also tell me that there were no incompatible change
driven by underlying changes in the properties that contribute to the
derivations.


 They also said that they already reached out to their
IETF contacts, but go not reaction.

In the future, there may no longer be dedicated outreach, because
this file is a regular part of the alpha or beta pre-releases and the
way to get notified of those is to subscribe to one of the Unicode
lists and set a filter.

This came up here as part of streamlining the release checklist for
Unicode releases, so I wanted to make sure that if anyone was waiting
on dedicated pings that they won't necessarily happen.

A./


---------- End Forwarded Message ----------