IDNs in the root

[Tina Dam]

For obvious reasosns I completely agree with Harald, and would like to add one more thing:

Registration under these TLDs will also be affected, so its not just the TLDs.

About which scripts people are interested in, the full overview will be posted, hopefully next week, when I return from a meeting in europe (currently). But meanwhile I don't think there is any harm in saying that there in fact is an interest expressed in a yiddish string.

Tina

----- Original Message -----
From: idna-update-bounces at alvestrand.no <idna-update-bounces at alvestrand.no>
To: Paul Hoffman <phoffman at imc.org>
Cc: idna-update at alvestrand.no <idna-update at alvestrand.no>
Sent: Thu Jan 22 20:37:02 2009
Subject: Re: IDNs in the root

Paul Hoffman skrev:
> At 4:55 AM +0100 1/23/09, Harald Tveit Alvestrand wrote:
>   
>> For one thing, that makes "IDNAv2" likely to be finished well after IDNs have been introduced in the root.
>>     
>
> Serious question: why is this at all relevant? Is there any IDNs that are meant to be entered in the root that will have a different encoding under IDNA2003 than under IDNA2008 or contain characters that make them unrenderable in IDNA2003?
>
>   
There are many strings for which registration could be requested under 
IDNA2003 that cannot be registered under IDNA2008 (the symbols being the 
most prominent example). ICANN is aghast at the idea of having to allow 
something to be registered in the root and then having to take it out 
when the rules change.

I haven't seen anyone claiming that they want to register a TLD in 
Dhivehi or Yiddish (the two BIDI cases where it matters that 2003 is 
more restrictive than 2008). But there are people arguing for 
registration of a TLD with a ZWNJ in it.

With the relatively restrictive rules that ICANN has put in place, it's 
not likely that any problems will be caused - but one reason for ICANN 
having to specify the restrictive rules in full rather than saying 
"stuff legal under 2008 is OK" and adding some short list of 
restrictions is that 2008 is not finished.

In my ICANN role, I want to have stable rules that I can reference, and 
the never-ending IDNA wrangling gives the impression of instability, 
even though the actual changes we're discussing in allowed strings at 
this stage of 2008's development range from small to microscopic.
("IDNAv2" is another matter. It means we have to do it all over again.)

                        Harald
_______________________________________________
Idna-update mailing list
Idna-update at alvestrand.no
http://www.alvestrand.no/mailman/listinfo/idna-update
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 4081 bytes
Desc: not available
Url : http://www.alvestrand.no/pipermail/idna-update/attachments/20090122/1fbf9376/attachment.bin