IETF Logo Mail Archive

[DNSOP] Looking for IANA registry for --xn

Phillip Hallam-Baker <phill@hallambaker.com> Thu, 06 October 2016 17:08 UTC

Return-Path: <hallam@gmail.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 53948129721 for <dnsop@ietfa.amsl.com>; Thu, 6 Oct 2016 10:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 mjjHTCe0VTIB for <dnsop@ietfa.amsl.com>; Thu, 6 Oct 2016 10:08:31 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9C21129650 for <dnsop@ietf.org>; Thu, 6 Oct 2016 10:08:30 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id b201so60689897wmb.0 for <dnsop@ietf.org>; Thu, 06 Oct 2016 10:08:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to; bh=V4+PL6/HiinqpJVoPcVfz/MtjH8z8BzJZzCMT+EVSpU=; b=MOAbTedFZnjIVtl/m4FLVgvn9c/cb12SiKH4lpKtn11iO/Nt9DvsZjZAGsFSVyoMVS HzS5IzRsuBLuIplqcjABsvlwhed02mCw8iOxsaLwd/GpGjwvu6K0RNknJpQNc6AEjhtI lpvI9aEcKN1kW3ZuMPJ5qnCXamDb8AJNlZR+HncJvkubnbwlplNcvK2Y7RKsy+keP3fS S/qNyZR45ixlWlkZ2VJpng/Zcq08x19hKtncakU/KwW1wWjQGHtKjEW06zRtUdh1aunN 67nEENrFqmNyVDQt3sYOsCRORsFv+wBpBGVd1oIuPhyg9ahONP9d4o+dmtuSH3+0pLX6 cXtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=V4+PL6/HiinqpJVoPcVfz/MtjH8z8BzJZzCMT+EVSpU=; b=eAosl7eB6nG/lg1K40oshxw6ksMMWVu/FneKrDs4c6oM9MZ9Z4NJdvOSPviuE5VhW+ PqmXWlGap59Io94/YVV0I24/VpAasOPv3jkUwFYKoEeUr3c2kSu+p8W6ByPRSHMEMM8A /qfP9X/SqHpbjeJkuJi3gA+aBinuhtbsiQvFRNMxy3CLTi32Y6BZe4Q6e9zZvrec9rDG fDGVhmcRxsR7qJprVnzsasTU9EhVi9ZIbbEipZx90xZub/Me0aTSftd8sfRlGgftP1G9 +x+Yl5NLgRJOT95H6Csbl8ExfWB62ZVqfuS8da0x++JTa433Wlt6vCZismO+X19bZQ6I b48g==
X-Gm-Message-State: AA6/9RlXKcGp6f18DsFNquMT7s9Lv8hg/+b2CwAzwrbCmM32QJMfPG6amGW17qSWFbs9c9yVmq72gSCIuSs0lw==
X-Received: by 10.28.52.209 with SMTP id b200mr1610235wma.104.1475773709274; Thu, 06 Oct 2016 10:08:29 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.194.167.69 with HTTP; Thu, 6 Oct 2016 10:08:28 -0700 (PDT)
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 06 Oct 2016 13:08:28 -0400
X-Google-Sender-Auth: Acdqunj28AyLZOZjnyqlie1F3w4
Message-ID: <CAMm+LwjcC6pJ+-LzwGyoG=VVzT_QQ9UrvM3LcZM1121XqCccow@mail.gmail.com>
To: "dnsop@ietf.org" <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a1143578eb5d40e053e355712"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/51a0_EtPTHkgrf2qCIkwb3ovRFA>
Subject: [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 17:08:33 -0000

I have been looking for the IANA registry in which the IDNA prefix xn-- is
allocated and have not been able to find it. I can see the following
possibilities

1) There isn't such a registry. The allocation is purely ad hoc

2) There is a registry but none of the IDNA RFCs bother to list it as a
normative reference.

Either one would be bad. The existence or non existence of a registry, the
allocation or non allocation of a code point is not going to cause me to
decide whether or not to use functionality. All that the registry achieves
is to avoid collisions.


Phill

v2.23.0 | Report a Bug | By Email