ICANN/GNSO GNSO Email List Archives

[ga]

<<< Chronological Index >>>    <<< Thread Index >>>

Re: [ga] RE: IDNs & the GNSO New TLD PDP

  • To: Vint Cerf <vint@xxxxxxxxxx>
  • Subject: Re: [ga] RE: IDNs & the GNSO New TLD PDP
  • From: Danny Younger <dannyyounger@xxxxxxxxx>
  • Date: Tue, 13 Dec 2005 08:25:03 -0800 (PST)
  • Cc: ga@xxxxxxxxxxxxxx
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=qFtYlmmwS1NmW30g/1gxDZo0iz3lUbZlMP2EYNK3C7kOgHrMSnZ5H4Cr9YN2XSUHFf8nadvhavpfjyRaMW4SGJPVNmu6HGp8Wa18RDl2q5mmmZGe/69/+Zd7WdjHCBklfBW6Zyae3di6aeL/XcnC6VbRVWkvy3rtURTf4cQhNt8= ;
  • In-reply-to: <20051213155315.57719.qmail@web53504.mail.yahoo.com>
  • Sender: owner-ga@xxxxxxxxxxxxxx
...a little more digging and I found the idn
committee's final report.  Their recommendation on
selections:

"There are at least two alternatives for top level
IDNs. First, ICANN can decide to allocate to each
ccTLD a single top level IDN, which identifies that
ccTLD. For example, ICANN can allocate to JPNIC .[JP
in Japanese script]. JPNIC then would be free to
register second level domains in Japanese script as
follows -- [Japanese script].[JP in Japanese script].
In this manner, the universe of IDN top-level domains
would in essence be limited to a translation of the
ccTLD identifiers.

Second, ICANN could select global top-level IDNs.
Presumably ICANN would perform this selection in
consultation with the relevant ccTLD managers and
regional organizations.

Not surprisingly, each approach has strengths and
weaknesses. The great virtue of the first approach is
its simplicity. ICANN would have to work out with the
ccTLD what its identifier would be in its local script
-- e.g., JP in Japanese script -- and that would be
the end of ICANN's involvement. The downside of this
approach is that all the global TLDs would remain in
ASCII; there would be no .[com or biz in Japanese
script]. This could lead to pressure for alternate
roots supporting such top level IDNs. Additionally,
this approach could lead to questions whether the
Internet was truly globalized and really represented
the global community of Internet stakeholders.

The second approach would address these concerns, but
would be extremely difficult for ICANN to administer.
Last November, ICANN has approved seven new gTLDs.
Could ICANN administer multiple gTLDs for each script?
This could amount to literally thousands of gTLDs.
Moreover, the process of selecting IDNgTLDs and their
registries could be extremely volatile for the more
desirable top level domains. The country code
registries might feel that they deserved a right of
first refusal for these domains.

Yet another approach would be for ICANN to start with
the easier, first approach, and then pursue the
second, more difficult one."

http://www.icann.org/committees/idn/final-report-28aug01.htm

The Committee's first approach seems reasonable to me.
 Anyone else have some thoughts on this?



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com
<<< Chronological Index >>>    <<< Thread Index >>>