<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.ox-6d1e887e0c-msonormal, li.ox-6d1e887e0c-msonormal, div.ox-6d1e887e0c-msonormal
{mso-style-name:ox-6d1e887e0c-msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Answers inline<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Vittorio Bertola [mailto:vittorio.bertola@open-xchange.com] <br><b>Sent:</b> Wednesday, April 26, 2017 2:37 PM<br><b>To:</b> Dusan Stojicevic <dusan@dukes.in.rs><br><b>Cc:</b> ua-discuss@icann.org<br><b>Subject:</b> Re: [UA-discuss] UASG Response to WordFence IDN Phishing concerns<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-bottom:12.0pt'>Il 26 aprile 2017 alle 11.50 Dusan Stojicevic <<a href="mailto:dusan@dukes.in.rs">dusan@dukes.in.rs</a>> ha scritto:<o:p></o:p></p><div><p class=ox-6d1e887e0c-msonormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>If you want to change agreement with cc’s, in order to address their rules for registration, is not going to be easy task for ICANN, because of the nature of agreements. Some of them are just in the form of „exchange of letters“ and zou know which level of agreement is that. </span><o:p></o:p></p></div></blockquote><p>I really think that we are spending lots of energies on a non-problem here. If ICANN develops some good best practices/rules and pushes them to the gTLD registries, over which it has full regulatory powers, then these practices will naturally become the reference for everyone and I am sure that most ccTLDs which are affected by the problem will just voluntarily adopt them as well. <o:p></o:p></p><p>Also, most if not all of the potential phishing attempts will be focused on .com domains, because that is where most global businesses and paid services are, so fixing the .com namespace is the first and foremost issue and would already prevent the majority of the risks.<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>This idea of good practice for gTLDs usually wasn’t seen as good practice for ccTLDs. A lot of examples, like emoji…<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>But I would state that I can be wrong, and I would agree that ICANN need to solve .com, build best practices and we will see. Anyhow, we need that.<o:p></o:p></span></p><p>Other big ccTLDs will just follow, and anyway often they disallow the Cyrillic script altogether, as Cyrillic is not used in their country; and the ccTLDs for countries where Cyrillic is a national script have already been dealing with this issue for a long time anyway, so they're possibly well prepared already.<o:p></o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>As I said, scripts in ccTLD’s tables may be subject of domestic law, and it’s not that simple to disallow the whole script. Also, except .</span><span lang=SR-CYRL-RS style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>рф (</span><span lang=SR-LATN-RS style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Russian IDN) </span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>most of IDN ccTLDs on Cyrillic have little number of registered domain names, and this problem is not that often. Because of that, they are not fully aware of this problem. On the other hand, you are right, the money and brands are mostly under .com and there is no need to overheat this topic.<o:p></o:p></span></p><p><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Dusan<o:p></o:p></span></p><p>Regards,<o:p></o:p></p><div><p style='margin-bottom:12.0pt'>-- <br><br><strong>Vittorio Bertola</strong><br>Research & Innovation Engineer <o:p></o:p></p><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width="100%" style='width:100.0%;border-collapse:collapse'><tr><td width=120 style='width:90.0pt;padding:1.5pt 1.5pt 1.5pt 1.5pt'><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Verdana",sans-serif'>Cell:<o:p></o:p></span></p></td><td style='padding:1.5pt 1.5pt 1.5pt 1.5pt'><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Verdana",sans-serif'>+39 348 7015022<o:p></o:p></span></p></td></tr><tr><td width=120 style='width:90.0pt;padding:1.5pt 1.5pt 1.5pt 1.5pt'><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Verdana",sans-serif'>Skype:<o:p></o:p></span></p></td><td style='padding:1.5pt 1.5pt 1.5pt 1.5pt'><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Verdana",sans-serif'><a href="mailto:in-skype-ox@bertola.eu">in-skype-ox@bertola.eu</a><o:p></o:p></span></p></td></tr><tr><td width=100 style='width:75.0pt;padding:1.5pt 1.5pt 1.5pt 1.5pt'><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Verdana",sans-serif'>Email:<o:p></o:p></span></p></td><td style='padding:1.5pt 1.5pt 1.5pt 1.5pt'><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Verdana",sans-serif'><a href="mailto:vittorio.bertola@open-xchange.com">vittorio.bertola@open-xchange.com</a><o:p></o:p></span></p></td></tr></table><p class=MsoNormal><span style='display:none'><o:p> </o:p></span></p><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width="100%" style='width:100.0%;border-collapse:collapse'><tr><td colspan=2 style='padding:1.5pt 1.5pt 1.5pt 1.5pt'><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Verdana",sans-serif'> <o:p></o:p></span></p></td></tr><tr><td colspan=2 style='padding:1.5pt 1.5pt 1.5pt 1.5pt'><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Verdana",sans-serif'>Twitter: <a href="http://twitter.com/openexchange">@openexchange</a> - Facebook: <a href="https://www.facebook.com/OpenXchange">OpenXchange</a> - Web: <a href="http://www.open-xchange.com">www.open-xchange.com</a><o:p></o:p></span></p></td></tr><tr><td width=200 style='width:150.0pt;border:solid black 1.0pt;border-left:none;padding:1.5pt 1.5pt 1.5pt 1.5pt'><p class=MsoNormal align=center style='text-align:center'><img border=0 width=190 height=40 id="_x0035_be0f06900124bc5ac3f7591a0d1911f" src="cid:image001.png@01D2BEAF.8F46C5E0"><o:p></o:p></p></td><td style='border-top:solid black 1.0pt;border-left:none;border-bottom:solid black 1.0pt;border-right:none;padding:1.5pt 1.5pt 1.5pt 1.5pt'><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Verdana",sans-serif'>Open-Xchange AG, Rollnerstr. 14, 90408 Nuremberg, District Court Nuremberg HRB 24738<br>Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Uwe Reumuth <br>Chairman of the Board: Richard Seibt<br><br>European Office: <br>Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 <br>Managing Directors: Frank Hoberg, Martin Kauss<br><br>US Office: <br>Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA <o:p></o:p></span></p></td></tr><tr><td colspan=2 style='padding:1.5pt 1.5pt 1.5pt 1.5pt'><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Verdana",sans-serif'> <o:p></o:p></span></p></td></tr><tr><td colspan=2 style='padding:1.5pt 1.5pt 1.5pt 1.5pt'><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Verdana",sans-serif;color:#CCCCCC'>Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential, and may be privileged. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, and delete this message and any attachments from your system.<o:p></o:p></span></p></td></tr></table><p class=MsoNormal><o:p> </o:p></p></div></div><div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br />
<table style="border-top: 1px solid #D3D4DE;">
<tr>
<td style="width: 55px; padding-top: 13px;"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" width="46" height="29" style="width: 46px; height: 29px;" /></a></td>
<td style="width: 470px; padding-top: 12px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">Virus-free. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link" target="_blank" style="color: #4453ea;">www.avast.com</a>
</td>
</tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></body></html>