<html>
<body>
I think the issue is not a technical problem with the technical root
zone, but that increasingly SSAC is considering the potential for user
confusion. From a user perspective, that is a good thing. If they had
done so earlier in the gTLD process, we might be in a much better
position there than we are now. But yes, that is a change.<br><br>
Perhaps you can elaborate on how the potential problems "can be
mitigated by the registry or registrars at the local level". That
may help ensure that we are all talking about the same thing and perhaps
provide a path forward.<br><br>
Alan<br><br>
At 28/02/2017 04:01 PM, Andrei Kolesnikov wrote:<br>
<blockquote type=cite class=cite cite="">Thank you Maureen, good
report.<br><br>
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. <br><br>
best regards, --andrei<br><br>
2017-02-28 13:49 GMT+03:00 Maureen Hilyard
<<a href="mailto:maureen.hilyard@gmail.com">
maureen.hilyard@gmail.com</a>>:<br>
<dl>
<dd>Background notes for your information - for the ALAC
meeting<font color="#888888"><br><br>
<dd>Maureen<br>
</font><br>
<dd>_______________________________________________<br>
<dd>ALAC mailing list<br>
<dd><a href="mailto:ALAC@atlarge-lists.icann.org">
ALAC@atlarge-lists.icann.org</a><br>
<dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
<dd>At-Large Online:
<a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a>
<br>
<dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a>
<br><br>
</dl><br><br>
<br>
-- <br>
Andrey Kolesnikov<br>
<a href="http://RIPN.NET">RIPN.NET</a><br>
</blockquote></body>
</html>