<div dir="ltr">Hey David (and others):<div><br></div><div>Not sure if you're familiar with the "domaintest" infrastructure that a number of registries launched last year. It's intended as a developer tool to facilitate acceptance of new TLDs, but provides a fairly useful test endpoint across dozens of TLDs.</div><div><br></div><div>More information at <a href="http://domaintest.foo">domaintest.foo</a>.</div><div><br></div><div>Jordyn</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jun 21, 2015 at 9:31 AM, David Conrad <span dir="ltr"><<a href="mailto:david.conrad@icann.org" target="_blank">david.conrad@icann.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Sorry for not commenting on this thread earlier -- due to a bit of<br>
overload, I haven't been following discussions closely.<br>
<br>
No, they aren't defensive registrations.<br>
<br>
ICANN is using those domain names as part of a series of experiments,<br>
which makes use of an incredibly useful testing infrastructure built and<br>
utilized by APNIC, that will verify the ability to look up a domain name<br>
from millions of browsers all over the planet. A high-level description of<br>
the experiments would be that the APNIC infrastructure uses Google<br>
advertisements to run a bit of flash code that does a lookup for a unique<br>
domain name within one of the icann.* domains. Over time, millions of<br>
these experiments will be run, which should give us a baseline of how many<br>
of the new gTLDs are blocked from resolution from an end user's<br>
perspective. We plan on running the test periodically to see if things are<br>
getting better/worse over time.<br>
<br>
As such, the registrations aren't integrated into websites in a way that<br>
anyone would normally see.<br>
<br>
Happy to answer questions on this if anyone is curious.<br>
<br>
Regards,<br>
-drc<br>
ICANN CTO<br>
<div class="HOEnZb"><div class="h5"><br>
-----Original Message-----<br>
From: <<a href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@icann.org</a>> on behalf of Andre Schappo<br>
<<a href="mailto:A.Schappo@lboro.ac.uk">A.Schappo@lboro.ac.uk</a>><br>
Date: Sunday, June 21, 2015 at 5:31 AM<br>
To: "<a href="mailto:ua-international@icann.org">ua-international@icann.org</a>" <<a href="mailto:ua-international@icann.org">ua-international@icann.org</a>><br>
Cc: "<a href="mailto:UA-discuss@icann.org">UA-discuss@icann.org</a>" <<a href="mailto:UA-discuss@icann.org">UA-discuss@icann.org</a>><br>
Subject: Re: [UA-discuss] [UA-International] icann IDNs<br>
<br>
><br>
>Here is an updated list of New gTLD IDNs registered by icann. I will test<br>
>the other New gTLD IDNs when I have time.<br>
><br>
>icann.在线<br>
>icann.中文网<br>
>icann.みんな<br>
>icann.移动<br>
>icann.我爱你 which is may favourite as it means - icann. I Love You 😂<br>
><br>
>I assume that these are not just defensive registrations.<br>
><br>
>I consider it crucial that when these IDNs are implemented they are<br>
>properly integrated into the icann website. So this excludes redirecting<br>
>to the ascii <a href="http://icann.org" rel="noreferrer" target="_blank">icann.org</a> and excludes frame redirects. The IDN should show<br>
>in the address bar and follow the pathname navigation. If icann have used<br>
>relative url addressing in their site then this should not be a problem.<br>
><br>
>And … in the longer term the pathname part should be in the current<br>
>language. Using aliasing/links this is not difficult to implement. More<br>
>explanation another time.<br>
><br>
>André Schappo<br>
><br>
</div></div></blockquote></div><br></div>