Re: [DNSOP] Looking for IANA registry for --xn

Jim Reid <jim@rfc1035.com> Thu, 06 October 2016 19:14 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B613129760 for <dnsop@ietfa.amsl.com>; Thu, 6 Oct 2016 12:14:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.896
X-Spam-Level:
X-Spam-Status: No, score=-4.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.996] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nvcCVPzT0_bx for <dnsop@ietfa.amsl.com>; Thu, 6 Oct 2016 12:14:12 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5916912975E for <dnsop@ietf.org>; Thu, 6 Oct 2016 12:14:12 -0700 (PDT)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id D399B2421026; Thu, 6 Oct 2016 19:14:09 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <CAF4+nEGg9zGNzUkGz2_NgrxJnia7Wax6i_f3B-VNZw+1=KAEnA@mail.gmail.com>
Date: Thu, 06 Oct 2016 20:14:07 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F0F6F02A-F237-4D41-98D5-807B323DD3A3@rfc1035.com>
References: <CAMm+LwjcC6pJ+-LzwGyoG=VVzT_QQ9UrvM3LcZM1121XqCccow@mail.gmail.com> <1329930975.314237.1475774676486@mail.yahoo.com> <CAMm+LwhnGFR6hqD2PbXyq4OiyLnfAy1K9TbaesmX3A7XVyCiiw@mail.gmail.com> <CAF4+nEGg9zGNzUkGz2_NgrxJnia7Wax6i_f3B-VNZw+1=KAEnA@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/9edCaIXH5Gdyy4f8YNnNQB42-Ag>
Cc: IETF dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Looking for IANA registry for --xn
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2016 19:14:14 -0000

> On 6 Oct 2016, at 18:59, Donald Eastlake <d3e3e3@gmail.com> wrote:
> 
> I don't believe there is a registry.

Actually there is. Sort of:

% whois -h whois.iana.org テスト
% IANA WHOIS server
% for more information on IANA, visit http://www.iana.org
% This query returned 1 object

domain:       テスト
domain-ace:   XN--ZCKZAH
...

It should be a no-brainer for IANA to publish and maintain a list of these IDN encodings for delegated TLDs.

ISTR IANA's Root Zone Database web page used to contain the punycode representation for the non-ASCII TLDs. Though I could well have imagined that.