Discuss mailing list

["Kevin Holly [Fusl]" <opennic AT lists.dedilink.eu>]

On 02/16/2014 12:17 AM, Coyo wrote:
> 
> 
> On 2/15/2014 2:24 PM, Alex Hanselka wrote:
>> On 2/15/2014 2:08 PM, Coyo wrote:
>>> It looks like unicode is not directly supported, but has an
>>> encoded form called Punycode.
>>>> In other words, is a TLD like උʘຯᛜ, for instance, or ฿tc or Ⓐno
>>>> as
>> It sure is possible! They are called Internationalized Domain
>> Names (IDN).  Some browsers will do all the punycode on the backend
>> so you still see the unicode, some don't (and this applys for
>> second and third level too).  There are a handful in use at this
>> time with ICANN and more on the way. I know Japanese みんな meaning
>> all or everyone is currently in preorder status.
> 
>> Here are some links for future research :)
> 
>> http://en.wikipedia.org/wiki/Internationalized_country_code_top-level_domain
> 
> 
> http://en.wikipedia.org/wiki/Internationalized_domain_name
>> http://en.wikipedia.org/wiki/Punycode 
>> http://en.wikipedia.org/wiki/List_of_Internet_top-level_domains 
>> http://icannwiki.com/index.php/New_gTLD_IDN_Applications (this is a
>> list of all of the proposed new IDNs for the gTLD thingy)
> 
> Would it be possible to use DNS without punycode?
No.
> I realize this would
> be non-standard, and would break compatibility with DNS servers in the
> public Internet, but is there any protocol-specific reason you can't?
> 
> My understanding was that the engineers who came up with DNS decided
> allowable characters to be ASCII simply because they didn't expect the
> Internet to become international and huge.
Exactly this is the reason it isn't possible to implement such TLDs
without Punycode.
> 
> 
> 
> 
> 
> --------
> You are a member of the OpenNIC Discuss list. 
> You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org
> 

-- 
Best regards

Kevin Holly - root AT hallowe.lt - http://hallowe.lt/