Re: [regext] [I18ndir] [Last-Call] [art] Artart last call review of draft-ietf-regext-epp-eai-12

John C Klensin <> Fri, 26 August 2022 19:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BAD8CC14F73D; Fri, 26 Aug 2022 12:39:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fJPhoL7s94bR; Fri, 26 Aug 2022 12:39:02 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 36161C14F736; Fri, 26 Aug 2022 12:39:02 -0700 (PDT)
Received: from [] (helo=PSB) by with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <>) id 1oRfAO-0007Mz-DH; Fri, 26 Aug 2022 15:38:56 -0400
Date: Fri, 26 Aug 2022 15:38:50 -0400
From: John C Klensin <>
To: Asmus Freytag <>, "Martin J. Dürst" <>
Message-ID: <B1671A5614C14D2E0F97A709@PSB>
In-Reply-To: <>
References: <> <8510291CFDD59E597396E0A4@PSB> <> <C8F21E176669FD9E43DC976B@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-Scanned: No (on; SAEximRunCond expanded to false
Archived-At: <>
Subject: Re: [regext] [I18ndir] [Last-Call] [art] Artart last call review of draft-ietf-regext-epp-eai-12
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Registration Protocols Extensions <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 26 Aug 2022 19:39:06 -0000

--On Friday, August 26, 2022 12:02 -0700 Asmus Freytag
<> wrote:

> On 8/26/2022 11:48 AM, John C Klensin wrote:
>>   there have been periodic proposals to reduce chaos in
>> the DNS and on the Internet by getting of all gTLDs that do
>> not serve an obvious international purpose and restricting TLD
>> labels to ISO 3166-1 alpha-2 codes and a_very_  small number
>> of exceptions, none of them involving non-Latin characters.
> While to the making of many proposals is no end (to paraphrase
> an early source), this doesn't mean that they are likely to go
> anywhere.


> Adoption of any such proposals would run into very
> serious headwinds in regions that see this as a perfect issue
> to assert national identity via domain names.

Actually, some of those places wanting to assert national
identity are among the source of some of the proposals to shift
things more toward nationally-rooted names.

> That alone would be a good enough reason to not spending time
> on mentioning them.

probably, yes. But they do go to Martin's point/suggestions.

> PS: it's not clear to me whether "strings" as means of
> accessing resources that are exposed in the UI or document
> contents will remain the preferred technology. So far, search
> and the use of apps have resulted in some inroads, but we are
> still far from an inflection point. If and when we reach it,
> any of these considerations, but also the proposals you
> mentioned are automatically moot.

Yes.  But, again, for email addresses as contact information or
identifiers -- a different problem than "accessing resources"
more generally -- I note that there have been proposals around
for international directories of such addresses (probably a
prerequisite for any form of searching or inexact matching that
does not depend on the strings themselves) since at least the
early 1980s.  Progress so far, zero.

While these are interesting issues, none of them have anything
to do with whether having a way to transmit an all-ASCII
alternative to a non-ASCII email address, when the latter may be
used in unpredictable international contexts, is desirable or