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

"Paul Hoffman" <paul.hoffman@vpnc.org> Thu, 06 October 2016 18:10 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 0F2BB12955B for <dnsop@ietfa.amsl.com>; Thu, 6 Oct 2016 11:10:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 Fm0qv9xD92dy for <dnsop@ietfa.amsl.com>; Thu, 6 Oct 2016 11:10:10 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13899120726 for <dnsop@ietf.org>; Thu, 6 Oct 2016 11:10:10 -0700 (PDT)
Received: from [10.32.60.113] (50-1-99-230.dsl.dynamic.fusionbroadband.com [50.1.99.230]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id u96IA3FY086142 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 6 Oct 2016 11:10:04 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-99-230.dsl.dynamic.fusionbroadband.com [50.1.99.230] claimed to be [10.32.60.113]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Phillip Hallam-Baker" <phill@hallambaker.com>
Date: Thu, 06 Oct 2016 11:10:04 -0700
Message-ID: <FBA3D8F9-76CB-43C0-B6CA-DF8DA727E4C0@vpnc.org>
In-Reply-To: <CAMm+LwjcC6pJ+-LzwGyoG=VVzT_QQ9UrvM3LcZM1121XqCccow@mail.gmail.com>
References: <CAMm+LwjcC6pJ+-LzwGyoG=VVzT_QQ9UrvM3LcZM1121XqCccow@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.5r5263)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/vpIW-rzj58_dyIRCVnttqAK-m_g>
Cc: "dnsop@ietf.org" <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 18:10:11 -0000

On 6 Oct 2016, at 10:08, Phillip Hallam-Baker wrote:

> 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.

It is #1. It is defined in the IDNA RFCs as a single value. If you want 
to change IDNA, you need to update the RFC.

--Paul Hoffman