<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
</head><body><p><br></p><blockquote type="cite">Il 21 aprile 2017 alle 12.15 Edmon Chung <edmon@registry.asia> ha scritto:<br><br><div class="ox-7b74a5ba0f-WordSection1"><p class="ox-7b74a5ba0f-MsoNormal"><span style="font-size: 11.0pt; font-family: 'Arial',sans-serif;">Starting a separate thread to focus on the IDN Implementation Guidelines Discussion.</span></p><p class="ox-7b74a5ba0f-MsoNormal"><span style="font-size: 11.0pt; font-family: 'Arial',sans-serif;"> </span></p><p class="ox-7b74a5ba0f-MsoNormal"><span style="font-size: 11.0pt; font-family: 'Arial',sans-serif;">For the Draft IDN Guidelines you pointed to, please do submit your comments into the still open public comments period (recently extended):</span></p><p class="ox-7b74a5ba0f-MsoNormal"><span style="font-size: 11.0pt; font-family: 'Arial',sans-serif;"><a href="https://www.icann.org/public-comments/idn-guidelines-2017-03-03-en" data-external="true">https://www.icann.org/public-comments/idn-guidelines-2017-03-03-en</a></span><br></p><p class="ox-7b74a5ba0f-MsoNormal"><span style="font-size: 11.0pt; font-family: 'Arial',sans-serif;"> </span></p><p class="ox-7b74a5ba0f-MsoNormal"><span style="font-size: 11.0pt; font-family: 'Arial',sans-serif;">To the specific issue of wholescript confusables, there is a further explanation in point 17 why the current recommendation is a "may" rather than a "must"... But if we feel strongly it should move to a must, please do submit your comments in.</span></p></div></blockquote><p>As I see it, point 17 is a justification for not blocking the registration of "g00gle.com", i.e. slightly less confusable stuff which can still be easily confused by people, and which looks more like a trademark plagiarism case than like a technical issue with a single letter shape having more than one encoding. But there is really no valid reason why you would want "epic.com" (with Latin "epic") and "еріс.com" (with Cyrillic "еріс") to exist and be assigned to different people, or why you cannot implement the technical standard that was developed exactly to allow computers to detect these cases.<br></p><p>By the way, I would also like to make the point that if these problems are not addressed in the registration phase, every ISP and Internet software developer has to think at how to deal with possible homoglyph attacks, building up a huge cost for the Internet as a whole.<br></p><p>Ciao<br></p><div class="io-ox-signature"><p>-- <br><br>kind regards,<br><br><strong>Vittorio Bertola</strong><br>Research & Innovation Engineer <br><br></p><table style="border-collapse: collapse;" class="mce-item-table" cellspacing="0" cellpadding="2" width="100%" border="0"><tbody><tr><td style="padding: 2px; font-family: verdana, sans-serif; font-size: 8pt;" width="120">Cell:</td><td style="padding: 2px; font-family: verdana, sans-serif; font-size: 8pt;">+39 348 7015022</td></tr><tr><td style="padding: 2px; font-family: verdana, sans-serif; font-size: 8pt;" width="120">Skype:</td><td style="padding: 2px; font-family: verdana, sans-serif; font-size: 8pt;">in-skype-ox@bertola.eu<br></td></tr><tr><td style="padding: 2px; font-family: verdana, sans-serif; font-size: 8pt;" width="100">Email:</td><td style="padding: 2px; font-family: verdana, sans-serif; font-size: 8pt;"><a href="mailto:vittorio.bertola@open-xchange.com" data-external="true">vittorio.bertola@open-xchange.com</a><br></td></tr></tbody></table><table style="border-collapse: collapse;" class="mce-item-table" cellspacing="0" cellpadding="2" width="100%" border="0"><tbody><tr><td colspan="2" style="padding: 2px; font-family: verdana, sans-serif; font-size: 8pt;"> </td></tr><tr><td colspan="2" style="padding: 2px; font-family: verdana, sans-serif; font-size: 8pt;">Twitter: <a href="http://twitter.com/openexchange" data-external="true">@openexchange</a> - Facebook: <a href="https://www.facebook.com/OpenXchange" data-external="true">OpenXchange</a> - Web: <a href="http://www.open-xchange.com" data-external="true"> www.open-xchange.com</a><br></td></tr><tr><td style="padding: 2px; border-bottom: 1px solid #000; border-right: 1px solid #000; border-top: 1px solid #000;" align="center" width="200"><img src="cid:5be0f06900124bc5ac3f7591a0d1911f" id="5be0f06900124bc5ac3f7591a0d1911f"></td><td style="padding: 2px; border-bottom: 1px solid #000; border-top: 1px solid #000; font-family: verdana, sans-serif; font-size: 8pt;">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 <br></td></tr><tr><td colspan="2" style="padding: 2px; font-family: verdana, sans-serif; font-size: 8pt;"> </td></tr><tr><td colspan="2" style="padding: 2px; font-family: verdana, sans-serif; font-size: 8pt; color: #ccc;">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.</td></tr></tbody></table></div></body></html>