Very interesting, David, thanks for sharing that. I'm sure the group would be grateful for updates from time to time. Greetings from the UA workshop! S. *--* *Simon Cousins*, CEO Allegravita LLC & Allegravita HK Limited Email me: s <simon.cousins@illuminantpartners.com>imon@allegravita.com . Skype me: simoncousins . Web: allegravita.com USA mobile: +1 347 850-3360 . China mobile: +86 156 2502-6287 Hong Kong mobile: +852 5195-1085 . Macau mobile: +853 6540-3747 On Sun, Jun 21, 2015 at 9:31 AM, David Conrad <david.conrad@icann.org> wrote:

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@icann.org> on behalf of Andre Schappo <A.Schappo@lboro.ac.uk> Date: Sunday, June 21, 2015 at 5:31 AM To: "ua-international@icann.org" <ua-international@icann.org> Cc: "UA-discuss@icann.org" <UA-discuss@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

Ah! An answer I was not expecting😄 Interesting! When you have some info online it would be good if you post links. So will ICANN ever have any IDNs that resolve to icann.org web server? Or in other words, behave as regular website domain names. André Schappo On 21 Jun 2015, at 14:31, David Conrad wrote:

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@icann.org> on behalf of Andre Schappo <A.Schappo@lboro.ac.uk> Date: Sunday, June 21, 2015 at 5:31 AM To: "ua-international@icann.org" <ua-international@icann.org> Cc: "UA-discuss@icann.org" <UA-discuss@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

Hey David (and others): 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. More information at domaintest.foo. Jordyn On Sun, Jun 21, 2015 at 9:31 AM, David Conrad <david.conrad@icann.org> wrote:

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@icann.org> on behalf of Andre Schappo <A.Schappo@lboro.ac.uk> Date: Sunday, June 21, 2015 at 5:31 AM To: "ua-international@icann.org" <ua-international@icann.org> Cc: "UA-discuss@icann.org" <UA-discuss@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