[UA-discuss] [UA-International] icann IDNs

[David Conrad]

Hi,

Sorry for not commenting on this thread earlier -- due to a bit of
overload, I haven't been following discussions closely.

No, they aren't defensive registrations.

ICANN is using those domain names as part of a series of experiments,
which makes use of an incredibly useful testing infrastructure built and
utilized by APNIC, that will verify the ability to look up a domain name
from millions of browsers all over the planet. A high-level description of
the experiments would be that the APNIC infrastructure uses Google
advertisements to run a bit of flash code that does a lookup for a unique
domain name within one of the icann.* domains. Over time, millions of
these experiments will be run, which should give us a baseline of how many
of the new gTLDs are blocked from resolution from an end user's
perspective. We plan on running the test periodically to see if things are
getting better/worse over time.

As such, the registrations aren't integrated into websites in a way that
anyone would normally see.

Happy to answer questions on this if anyone is curious.

Regards,
-drc
ICANN CTO

-----Original Message-----
From: <ua-discuss-bounces at icann.org> on behalf of Andre Schappo
<A.Schappo at lboro.ac.uk>
Date: Sunday, June 21, 2015 at 5:31 AM
To: "ua-international at icann.org" <ua-international at icann.org>
Cc: "UA-discuss at icann.org" <UA-discuss at icann.org>
Subject: Re: [UA-discuss] [UA-International] icann IDNs

>
>Here is an updated list of New gTLD IDNs registered by icann. I will test
>the other New gTLD IDNs when I have time.
>
>icann.在线
>icann.中文网
>icann.みんな
>icann.移动
>icann.我爱你 which is may favourite as it means - icann. I Love You 😂
>
>I assume that these are not just defensive registrations.
>
>I consider it crucial that when these IDNs are implemented they are
>properly integrated into the icann website. So this excludes redirecting
>to the ascii icann.org and excludes frame redirects. The IDN should show
>in the address bar and follow the pathname navigation. If icann have used
>relative url addressing in their site then this should not be a problem.
>
>And … in the longer term the pathname part should be in the current
>language. Using aliasing/links this is not difficult to implement. More
>explanation another time.
>
>André Schappo
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4673 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/ua-discuss/attachments/20150621/319d33c6/smime.p7s>