<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Jothan,</span></a></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">A very useful insight about inherent bias, and the challenge of overcoming it.</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">-Ram</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">------------------------------------------------------------------------------</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Ram Mohan</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">o: +1.215.706.5700 x103; m: +1.215.431.0958; f: +1.215.706.5701</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Skype:gliderpilot30 |@rmohan123|<a href="http://www.linkedin.com/in/rmohan">www.linkedin.com/in/rmohan</a></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><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""> Jothan Frakes [mailto:<a href="mailto:jothan@jothan.com">jothan@jothan.com</a>] <br><b>Sent:</b> Wednesday, September 28, 2016 8:33 PM<br><b>To:</b> Ram Mohan<br><b>Cc:</b> <a href="mailto:UA-discuss@icann.org">UA-discuss@icann.org</a><br><b>Subject:</b> Re: [UA-discuss] Some universal acceptance problems last 15+ years...</span></p><p class="MsoNormal"> </p><div><p class="MsoNormal">Ram-</p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">This example you provided is a good one - because it demonstrates something different within the UA which is potential bias by the programmer or user specifications of the development or IT team against non-COM/NET.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">On the one hand, there is the Y2K-like issue where 'VALID' TLDs were hard coded and caused exceptions due to lack of awareness. On the other hand this appears to be that there was awareness of other TLDs.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">I have found it particularly challenging to overcome such bias for status quo as a part of convincing developers that code requires revisiting to accommodate the new normal.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">-Jothan</p></div></div><div><p class="MsoNormal"><br clear="all"></p><div><div><div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>Jothan Frakes<br>Tel: +1.206-355-0230</p></div></div></div><p class="MsoNormal"> </p><div><p class="MsoNormal">On Wed, Sep 28, 2016 at 10:50 AM, Ram Mohan <<a href="mailto:rmohan@afilias.info" target="_blank">rmohan@afilias.info</a>> wrote:</p><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><div><div><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">On Sep 12, 2001, I helped launch the first non 2/3 character TLD, .INFO. Many of you have heard about how we struggled to get applications, browsers, web forms and email systems to recognize the world’s first four-character TLD as a legitimate extension, including my creation of the Office of the CTO (in a 3 person startup) to get large companies to return my calls.</p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> </p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Well, 15+ years later, today I was on the website of the Pennsylvania state government, and filled in my email address (ending in .INFO). I hit submit, and here is the prompt that came up. I hit OK, and the site accepted my email and I moved forward with my tasks, but it’s galling that some programmer _<i>recently</i>_ decided that a non 2/3 character TLD based email address merited a warning message.</p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> </p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><img border="0" width="945" height="366" id="_x0000_i1025" src="cid:image001.png@01D219C8.76D10890"></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> </p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Goes to show how long bad habits persist. Also goes to show why the UASG’s work is important.</p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> </p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">-Ram</p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> </p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">------------------------------------------------------------------------------</p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Ram Mohan</p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Executive Vice President & CTO</p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Afilias |Ireland|Canada|USA|India|China</p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">o: <a href="tel:%2B1.215.706.5700%20x103" target="_blank">+1.215.706.5700 x103</a>; m: <a href="tel:%2B1.215.431.0958" target="_blank">+1.215.431.0958</a>; f: <a href="tel:%2B1.215.706.5701" target="_blank">+1.215.706.5701</a></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Skype:gliderpilot30 |@rmohan123|<a href="http://www.linkedin.com/in/rmohan" target="_blank">www.linkedin.com/in/rmohan</a></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> </p></div></div></blockquote></div><p class="MsoNormal"> </p></div></div></body></html>