Excellent primer, Maureen! These are not topics I generally pay attention to but from reading this primer, I feel almost fully informed. Not to make too fine a point of this, here's just one more example why in pursuit of the At-Large interest, one will always need a good mix of talent - including some experienced by time in place - beyond the one-ICANN meeting cycle on which the ALM kerfuffle of the ITEMS report. -Carlton Thanks very much. -Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Planning, Governance, Assessment & Turnaround* ============================= On Tue, Feb 28, 2017 at 5:49 AM, Maureen Hilyard <maureen.hilyard@gmail.com> wrote:
Background notes for your information - for the ALAC meeting
Maureen
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+ Advisory+Committee+(ALAC)
Thank you Maureen, good report. The origin of this story goes years back when I was representing ccTLD with (still world largest) IDN obtained by Fast Track. I know how important it is for the local market, government and end users to have an ability to use local script in domain names. The process of similarity check was in place without expectations to see a real problematic cases anyday soon. But it happened. The similar process in new gTLD project was accurately timelin'ed and works well (until the real confusion case at least). I'd like to mention RFC6912 paragraph 6 one more time. The visually confusing labels are potential problem for a registry, not to a root zone in general. With IDN ccTLD registry procedures (particularly for mentioned Greek and Cyrillic scripts) if any domain name confusion case becomes real, it can be mitigated by the registry or registrars at the local level. I recommend to support ccNSO statement with all balances and checks they've included into the document. best regards, --andrei 2017-02-28 13:49 GMT+03:00 Maureen Hilyard <maureen.hilyard@gmail.com>:
Background notes for your information - for the ALAC meeting
Maureen
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+ Advisory+Committee+(ALAC)
-- Andrey Kolesnikov RIPN.NET
Remembering the case with .br with the Russian cyrilic script Vanda Scartezini Polo Consultores Associados Av. Paulista 1159, cj 1004 01311-200- Sao Paulo, SP, Brazil Land Line: +55 11 3266.6253 Mobile: + 55 11 98181.1464 Sorry for any typos. HAPPY 2017! From: <alac-bounces@atlarge-lists.icann.org> on behalf of Andrei Kolesnikov <andrei@rol.ru> Date: Tuesday, February 28, 2017 at 6:01 PM To: Maureen Hilyard <maureen.hilyard@gmail.com> Cc: 'ALAC List' <alac@atlarge-lists.icann.org>, Alan Greenberg <alan.greenberg@mcgill.ca> Subject: Re: [ALAC] cNSO-SSAC issue Thank you Maureen, good report. The origin of this story goes years back when I was representing ccTLD with (still world largest) IDN obtained by Fast Track. I know how important it is for the local market, government and end users to have an ability to use local script in domain names. The process of similarity check was in place without expectations to see a real problematic cases anyday soon. But it happened. The similar process in new gTLD project was accurately timelin'ed and works well (until the real confusion case at least). I'd like to mention RFC6912 paragraph 6 one more time. The visually confusing labels are potential problem for a registry, not to a root zone in general. With IDN ccTLD registry procedures (particularly for mentioned Greek and Cyrillic scripts) if any domain name confusion case becomes real, it can be mitigated by the registry or registrars at the local level. I recommend to support ccNSO statement with all balances and checks they've included into the document. best regards, --andrei 2017-02-28 13:49 GMT+03:00 Maureen Hilyard <maureen.hilyard@gmail.com<mailto:maureen.hilyard@gmail.com>>: Background notes for your information - for the ALAC meeting Maureen _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org<mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) -- Andrey Kolesnikov RIPN.NET<http://RIPN.NET>
I concur Andrei... On 1 Mar. 2017 8:01 am, "Andrei Kolesnikov" <andrei@rol.ru> wrote:
Thank you Maureen, good report.
The origin of this story goes years back when I was representing ccTLD with (still world largest) IDN obtained by Fast Track. I know how important it is for the local market, government and end users to have an ability to use local script in domain names. The process of similarity check was in place without expectations to see a real problematic cases anyday soon. But it happened. The similar process in new gTLD project was accurately timelin'ed and works well (until the real confusion case at least). I'd like to mention RFC6912 paragraph 6 one more time. The visually confusing labels are potential problem for a registry, not to a root zone in general. With IDN ccTLD registry procedures (particularly for mentioned Greek and Cyrillic scripts) if any domain name confusion case becomes real, it can be mitigated by the registry or registrars at the local level. I recommend to support ccNSO statement with all balances and checks they've included into the document.
best regards, --andrei
2017-02-28 13:49 GMT+03:00 Maureen Hilyard <maureen.hilyard@gmail.com>:
Background notes for your information - for the ALAC meeting
Maureen
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/di splay/atlarge/At-Large+Advisory+Committee+(ALAC)
-- Andrey Kolesnikov RIPN.NET
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+ Advisory+Committee+(ALAC)
Just a few collisions past 10 years through all TLDs. Most common case for physhing is misspelled names within one script. --andrei 2017-03-01 1:51 GMT+03:00 Cheryl Langdon-Orr <langdonorr@gmail.com>:
I concur Andrei...
On 1 Mar. 2017 8:01 am, "Andrei Kolesnikov" <andrei@rol.ru> wrote:
Thank you Maureen, good report.
The origin of this story goes years back when I was representing ccTLD with (still world largest) IDN obtained by Fast Track. I know how important it is for the local market, government and end users to have an ability to use local script in domain names. The process of similarity check was in place without expectations to see a real problematic cases anyday soon. But it happened. The similar process in new gTLD project was accurately timelin'ed and works well (until the real confusion case at least). I'd like to mention RFC6912 paragraph 6 one more time. The visually confusing labels are potential problem for a registry, not to a root zone in general. With IDN ccTLD registry procedures (particularly for mentioned Greek and Cyrillic scripts) if any domain name confusion case becomes real, it can be mitigated by the registry or registrars at the local level. I recommend to support ccNSO statement with all balances and checks they've included into the document.
best regards, --andrei
2017-02-28 13:49 GMT+03:00 Maureen Hilyard <maureen.hilyard@gmail.com>:
Background notes for your information - for the ALAC meeting
Maureen
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/di splay/atlarge/At-Large+Advisory+Committee+(ALAC)
-- Andrey Kolesnikov RIPN.NET
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/di splay/atlarge/At-Large+Advisory+Committee+(ALAC)
-- Andrey Kolesnikov RIPN.NET
I do not have experience with IDN as such but I do think the point Andrey makes about this not being a problem for the root but for registry/registrar makes technical sense. Regards On 1 Mar 2017 04:01, "Andrei Kolesnikov" <andrei@rol.ru> wrote:
Thank you Maureen, good report.
The origin of this story goes years back when I was representing ccTLD with (still world largest) IDN obtained by Fast Track. I know how important it is for the local market, government and end users to have an ability to use local script in domain names. The process of similarity check was in place without expectations to see a real problematic cases anyday soon. But it happened. The similar process in new gTLD project was accurately timelin'ed and works well (until the real confusion case at least). I'd like to mention RFC6912 paragraph 6 one more time. The visually confusing labels are potential problem for a registry, not to a root zone in general. With IDN ccTLD registry procedures (particularly for mentioned Greek and Cyrillic scripts) if any domain name confusion case becomes real, it can be mitigated by the registry or registrars at the local level. I recommend to support ccNSO statement with all balances and checks they've included into the document.
best regards, --andrei
2017-02-28 13:49 GMT+03:00 Maureen Hilyard <maureen.hilyard@gmail.com>:
Background notes for your information - for the ALAC meeting
Maureen
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/di splay/atlarge/At-Large+Advisory+Committee+(ALAC)
-- Andrey Kolesnikov RIPN.NET
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+ Advisory+Committee+(ALAC)
participants (6)
-
Andrei Kolesnikov -
Carlton Samuels -
Cheryl Langdon-Orr -
Maureen Hilyard -
Seun Ojedeji -
Vanda Scartezini