<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div class=""><br class="">
</div>
OOPs ... I thought I was typing a fictitious web address for the here link but I was wrong. There is a domain called
<a href="http://the.link" class="">the.link</a>. It looks to be a revenue parked website.
<div class=""><br class="">
</div>
<div class="">Next time, no matter how absurd and improbable I make my fictitious addresses, I will first check they are not real addresses before emailing.</div>
<div class=""><br class="">
</div>
<div class="">André Schappo<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 21 Feb 2018, at 18:01, Andre Schappo <<a href="mailto:A.Schappo@lboro.ac.uk" class="">A.Schappo@lboro.ac.uk</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div class=""><br class="">
</div>
I would argue that such security issues pale into near insignificance compared to the ubiquitous practice of link addresses not being self evident and up front.
<div class=""><br class="">
</div>
<div class="">eg ...please click <a href="http://thanks.for.clicking.the.link/I/have/now/emptied/your/bank/account" class="">here</a> for further information on ...</div>
<div class=""><br class="">
</div>
<div class="">I consider the up front presentation of link addresses should be common practice. I describe my working practice in <a href="http://schappo.blogspot.co.uk/2018/01/computer-science-internationalization_7.html" class="">schappo.blogspot.co.uk/2018/01/computer-science-internationalization_7.html</a></div>
<div class=""><br class="">
</div>
<div class="">My practice does not, of course, guarantee a website is safe, but if the up front presented address is different to the resultant address after clicking the link, this would help to arouse suspicion in users.</div>
<div class=""><br class="">
</div>
<div class="">So, yes, letʼs have IDNs presented up front to users as U-labels and not A-labels and not hidden behind a link labelled, for example, <a href="http://thanks.for.clicking.the.link/I/have/now/emptied/your/bank/account" class="">here</a></div>
<div class=""><br class="">
</div>
<div class="">André Schappo<br class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On 20 Feb 2018, at 08:54, Jim DeLaHunt <<a href="mailto:jfrom.uasg@jdlh.com" class="">jfrom.uasg@jdlh.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<p class="">Multiple people have made the argument that having a browser show A-labels ("punycode") instead of U-labels ("regular IDN") is desirable as a way of fighting phishing.</p>
<p class="">My rebuttal has three parts:</p>
<ol class="">
<li class="">The underlying problem is that the registry (here, .com) permitted registration of a domain name which was confusable with another one. The right place to fight this kind of phishing with confusable characters is at the domain registry level.
</li><li class="">Even if you could magically prevent all confusable 2nd-level domain name registrations, phishing would still be a problem. Fraudsters have many tools, confusable 2nd-level names is only one of them. There are also confusable names at the 4th or
5th levels (e.g. <a href="http://microsoft.com.innocuous.deceptive.com/" class="">
microsoft.com.innocuous.deceptive.com</a>), and misleading links in message bodies, and so on.<br class="">
</li><li class="">The people for whom A-labels instead of U-labels are a privileged set of latin-script reading Internet users. The second billion internet users will predominantly be people who read a different script than latin. U-labels are a requirement for
them to have legible domain names for legitimate sites. A-labels mean they don't get domain names which they can read. And they deserve to be able to read their domain names and email addresses.<br class="">
</li></ol>
<p class="">This is an excellent audience for me to test my rebuttal. Is it solid? Can I improve it? </p>
<p class="">Cheers,<br class="">
—Jim DeLaHunt, Vancouver, Canada<br class="">
</p>
<div class="moz-cite-prefix">On 2018-02-19 23:36, Ronald Geens wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:2441912C-9F34-41CD-9316-F69284513CD6@dnsbelgium.be" class="">
All,
<div class=""><br class="">
</div>
<div class=""> I am aware of the good work going on in the UASG to get IDN at all levels natively supported in web-adresses and email and I fully support that. </div>
<div class=""><br class="">
</div>
<div class="">On the other hand there is darker side of the web that people want to be protected from. </div>
<div class="">I just read this blog about some people that may actually find it better to see puny-code in stead of regular IDN in order to detect spam and phishing.</div>
<div class=""><a href="https://ma.ttias.be/show-idn-punycode-firefox-avoid-phishing-urls/" class="" moz-do-not-send="true">https://ma.ttias.be/show-idn-punycode-firefox-avoid-phishing-urls/</a> which is an opposite view of what UASG is trying to achieve.</div>
<div class=""><br class="">
</div>
<div class=""> Does/Will the UASG have a standpoint in this matter ? Is this in scope of UASG or will we rely on the anti-virus industry or even registrars/registries to protect the world from abuses like this ?</div>
<div class=""><br class="">
</div>
<div class="">Best regards,</div>
<div class=""><br class="">
</div>
<div class="">Ron Geens</div>
<div class="">DNS Belgium</div>
</blockquote>
<br class="">
<pre class="moz-signature" cols="72">--
--Jim DeLaHunt, <a class="moz-txt-link-abbreviated" href="mailto:jdlh@jdlh.com">jdlh@jdlh.com</a> <a class="moz-txt-link-freetext" href="http://blog.jdlh.com/">http://blog.jdlh.com/</a> (<a class="moz-txt-link-freetext" href="http://jdlh.com/">http://jdlh.com/</a>)
multilingual websites consultant
355-1027 Davie St, Vancouver BC V6E 4L2, Canada
Canada mobile +1-604-376-8953
</pre>
</div>
</div>
</blockquote>
</div>
<br class="">
<div class="">
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="font-family: "Arial Unicode MS"; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
🌏 🌍 🌎<br class="">
André Schappo<br class="">
<a href="mailto:%E5%B0%8F%E5%B1%B1@%E7%94%B5%E9%82%AE.%E5%9C%A8%E7%BA%BF?Subject=%E4%BD%A0%E5%A5%BD%E5%B0%8F%E5%B1%B1%F0%9F%98%9C" class="">小山@电邮.在线?Subject=你好小山😜</a><br class="">
<a href="https://schappo.blogspot.co.uk/" class="">schappo.blogspot.co.uk</a><br class="">
<a href="https://twitter.com/andreschappo" class="">twitter.com/andreschappo</a><br class="">
<a href="https://weibo.com/andreschappo?is_all=1" class="">weibo.com/andreschappo?is_all=1</a><br class="">
<a href="https://groups.google.com/forum/#!forum/computer-science-curriculum-internationalization" class="">groups.google.com/forum/#!forum/computer-science-curriculum-internationalization</a><br class="">
<br class="">
</div>
</div>
</div>
<br class="">
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
<div class="">
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); font-family: "Arial Unicode MS"; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
🌏 🌍 🌎<br class="">
André Schappo<br class="">
<a href="mailto:%E5%B0%8F%E5%B1%B1@%E7%94%B5%E9%82%AE.%E5%9C%A8%E7%BA%BF?Subject=%E4%BD%A0%E5%A5%BD%E5%B0%8F%E5%B1%B1%F0%9F%98%9C" class="">小山@电邮.在线?Subject=你好小山😜</a><br class="">
<a href="https://schappo.blogspot.co.uk" class="">schappo.blogspot.co.uk</a><br class="">
<a href="https://twitter.com/andreschappo" class="">twitter.com/andreschappo</a><br class="">
<a href="https://weibo.com/andreschappo?is_all=1" class="">weibo.com/andreschappo?is_all=1</a><br class="">
<a href="https://groups.google.com/forum/#!forum/computer-science-curriculum-internationalization" class="">groups.google.com/forum/#!forum/computer-science-curriculum-internationalization</a><br class="">
<br class="">
</div>
</div>
</div>
<br class="">
</div>
</body>
</html>