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

<> Thu, 06 October 2016 17:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 260F312973C for <>; Thu, 6 Oct 2016 10:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ugEqem28Mpkp for <>; Thu, 6 Oct 2016 10:24:47 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 438321295DC for <>; Thu, 6 Oct 2016 10:24:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=s2048; t=1475774686; bh=V41Tswf8hLhRTCq7YD2MrFefcuPO5Vp1afpxjc4L7Mg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=Uqi3dVRBTi1pXn8qwudvdpBCHAXCFk7mJ0b2tqahLdDfB0NkrpF+whwzk6cxH9T8Ue07gg8tlE9drY6NiwKgLVaI3JmQ5X75VsyHjqKJL4g4xClNSyVce8/bLzJYFlXSvjx8gRpReC12HA1SXhh/q2OXntIJ4gk0uGk/Gf5vco6H764nGcGeyAnMKTKzxK/la02lrq2oyrhtjGAuWDBAdg6EdcYBdB4PLrKkU8FDgalm4L8FETJRgNVP6UMyvI8o+0Xgkll76/QwCuTp+iimYZcdh9M+T+5vE5Vw234ZaA3igy7aqqeqRs1GGL65bFxj6Gs4OIRt+uhK58C3eGOVNw==
Received: from [] by with NNFMP; 06 Oct 2016 17:24:46 -0000
Received: from [] by with NNFMP; 06 Oct 2016 17:24:46 -0000
Received: from [] by with NNFMP; 06 Oct 2016 17:24:46 -0000
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: xDZHSHUVM1kB2Kfz6NztPZcOeqH8p.lUMz1v9HwRm4dorhRXpEMwqK95CLPJ0ZI 0TFSBEaKF3vMNeqitClgQBCWzZQNNOEmXr_gEo226LOHVjUJXsBIYg_AVcwvlrnqDfFbltsxT8vv NAkzpMgQjGRZm3WtxBbcFWJaltfJ24YDchUbd9SJFQrwuCOUsm32S6m_Qpxib0TzNFciBT.nilOO 7ExxIprBB_UCOG6gIseXFoobxnToiex5xUQmtmyspNftHI6Ip7wdWAHvX3Nd.2OUBtqlr7ZO3QkC guatC6dijtIiv9AvOk3xVByWZOFpj0KUM2Zz1bXFU8K18R0RZnLY4NmuPkZtx9b6.x02KsJqquf9 Mm6rv8KcDnLXwx20ttSKj58ioIXwF7khPxmdq1DiAszxvvIhopJA0s4bPe8rASozm0EIiJMyGe7F ttnB8Cu64OaGH3i6GHaeEoQW0MqAjfFXcJSlWObpuXSb8v.kzkw0dcVVIOZulV4ezZx0K.X2uomk a4rlzb4YdxkKj8WedY.4R1agjWkQ1bf7crbUAUtpvJJiLnB_5cchJkECd0SpRWJu8.cey_p5SzGn Onntrxnypl.kTaTQTuC_25lSNpj3e7HMbPaE-
Received: from by; Thu, 06 Oct 2016 17:24:46 +0000; 1475774686.282
Date: Thu, 06 Oct 2016 17:24:36 +0000
To: Phillip Hallam-Baker <>, "" <>
Message-ID: <>
In-Reply-To: <>
References: <>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_314236_601315450.1475774676482"
Archived-At: <>
Cc: Harish Chowdhary <>
Subject: Re: [DNSOP] Looking for IANA registry for --xn
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 06 Oct 2016 17:24:49 -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.

Phil, this is very interesting.   
The 'xn--', of course, is the prefix for punycode used for International Domain Names.   I have seen it used for DNS resolution quite a bit in the last couple of months.   So, it is certainly used.   In fact, that appears to be the only way one can do DNS resolution (at least in my experience).  That is, do the translation from IDN to punycode.   Then, it seems to work like a charm.
Certainly sounds like an update somewhere is needed.
People may be interested in a draft that Harish and I have just posted:

>From our section 1.1 which explains punycode:

"Languages not based on the Latin script (A, B, C, etc) use unicode to represent the letters in their alphabet rather than ASCII. Punycode is used to show unicode characters in ASCII format. It is used in the transport of email. 

For example: 
English: NehruHindi: नेहरूPunycode: xn--l2bq0a0bw 

Punycode will start with the prefix: "xn--". An application handling IDN domains has to reference an IDN repository to know how to display them. Emails add to the complication since many email systems pre-date the introduction of IDNs. These systems often simply reject emails that don't work within the old domain name model. 
Nalini Elkins
Inside Products, Inc.
(831) 659-8360