<div dir="ltr">Dear Petter<div><br>Thank you for your message, and apologies for the delay in responding to your points.</div><div><br></div><div><p class="MsoNormal"><font face="arial, helvetica, sans-serif" color="#000000">I wanted to address the claim that because contracted parties had not made noises about ICANN’s advisory they must be okay with it. </font><span style="color:rgb(0,0,0);font-family:arial,helvetica,sans-serif">I’ve attached a letter that I'm informed was provided by the RySG to ICANN staff as a result of the RySG being provided an early version of the advisor for comment. I understand that none of these comments were taken into account by ICANN when they published the advisory and despite being asked why, I don’t believe any answer was forthcoming.</span></p><p class="MsoNormal"><span style="color:rgb(0,0,0);font-family:arial,helvetica,sans-serif"><br></span></p><p class="MsoNormal"><span style="color:rgb(0,0,0);font-family:arial,helvetica,sans-serif">In short, there have been expressions of concern over the recent advisory, and my understanding from discussions on the RrSG list is that many have concerns over transliteration and translation of WHOIS data.</span></p><p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt"><br></span></p><p class="MsoNormal"><font color="#000000" face="arial, helvetica, sans-serif">Kind regards</font></p><p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt"><br></span></p><p class="MsoNormal"><font color="#000000" face="arial, helvetica, sans-serif">Emily</font><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt"> </span></p></div><div class="gmail_extra"><br><div class="gmail_quote">On 30 October 2014 13:20, Petter Rindforth <span dir="ltr"><<a href="mailto:petter.rindforth@fenixlegal.eu" target="_blank">petter.rindforth@fenixlegal.eu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br><blockquote type="cite"><div><div>Dear All,<div><br></div><div>Just a last minute summary of <br><div><b><span lang="EN-US">Some further comments/questions/inputs/suggestions:</span></b></div><div><b><span lang="EN-US"><br></span></b></div><div><font face="Verdana, sans-serif"><span style="line-height:15.3333320617676px">(collected from the IP point of view)</span></font></div><div><font face="Verdana, sans-serif"><span style="line-height:15.3333320617676px"><br></span></font></div><div><b><span lang="EN-US"><br></span></b></div><div>
<p style="margin:0cm;margin-bottom:.0001pt;background:white"><span lang="EN-US">Note that<span> </span>ICANN
issued an advisory last month clarifying technical aspects of provisions of the
2013 RAA and new gTLD Registry Agreement regarding uniform requirements for
presenting Whois data. </span><span><a href="https://www.icann.org/resources/pages/registry-agreement-spec4-raa-rdds-2014-09-12-en" target="_blank"><span style="color:windowtext">https://www.icann.org/resources/pages/registry-agreement-spec4-raa-rdds-2014-09-12-en</span></a><span> </span>. </span><span lang="EN-US">Significantly , it states that “<b><i>Registries and Registrars are
encouraged to only use US-ASCII encoding and character repertoire for
WHOIS port 43 output</i></b>.” The purpose is to facilitate parsing of
Whois data by automated tools such as ICANN’s centralized Whois data portal,<span> </span></span><span><a href="http://whois.icann.org/" target="_blank"><span lang="EN-US" style="color:windowtext">http://whois.icann.org/</span></a></span><span><span lang="EN-US"> </span></span><span lang="EN-US">. Similar arguments would apply to facilitating
machine translation. </span></p>
<p style="margin:0cm;margin-bottom:.0001pt;background:white"><span lang="EN-US"> </span></p>
<p style="margin:0cm;margin-bottom:.0001pt;background:white"><span lang="EN-US">Thus the status quo is (or will be, by February 2015)
that contracted parties are at least “encouraged” to transliterate into ASCII
if Whois data is submitted in some other script. </span></p>
<p style="margin:0cm;margin-bottom:.0001pt;background:white"><span lang="EN-US">Has anyone heard any howls of outrage from registries
and registrars over this? </span></p>
<p style="margin:0cm;margin-bottom:.0001pt;background:white"><span lang="EN-US">The advisory also states”<span> </span></span><span lang="EN">All domain name
labels in the values of any of the fields described in section 1.4.2 of the
2013 RAA, and sections 1.5, 1.6, and 1.7 of Specification 4 of the Registry
Agreement (e.g., Domain Name, Name Server, email) MUST be shown in
ASCII-compatible form (A-Label).</span></p>
<p style="margin:0cm;margin-bottom:.0001pt;background:white"><span lang="EN-US"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;background:white"><span lang="EN">For example, a name server with an IDN label should be
shown as:</span><span lang="EN-US"></span></p>
<p style="margin:0cm 0cm 0.0001pt 30pt;background:white"><i><span lang="EN">Name Server: ns1.xn--caf-dma.example.”</span></i></p>
<p style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:30.0pt;margin-bottom:.0001pt;background:white"><span lang="EN-US"> </span></p>
<p style="margin:0cm 0cm 0.0001pt;background:white"><span lang="EN-US">The referenced fields include virtually all the
registrant data we are concerned with. See the listing in section 1.4.2
of Specification 3 of the 2013 RAA,<span> </span></span><span><a href="https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en" target="_blank"><span lang="EN-US" style="color:windowtext">https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en</span></a></span><span><span lang="EN-US"> </span></span><span lang="EN-US">.</span></p>
<p style="margin:0cm;margin-bottom:.0001pt;background:white"><span lang="EN-US">I’m not certain whether this ASCII requirement applies
only to the labels (e.g., “Name Server”) or to the content following the label
--- the example given suggests the latter—which further solidifies the idea
that contracted parties are already required to transliterate Whois data into
ASCII. But I could be misreading this requirement. </span></p>
<p style="margin:0cm;margin-bottom:.0001pt;background:white"><span lang="EN-US"> </span></p>
<p style="margin:0cm;margin-bottom:.0001pt;background:white"><span lang="EN-US">§§§</span></p>
<p style="margin:0cm;margin-bottom:.0001pt;background:white"><span lang="EN-US"> </span></p>
<p style="margin:0cm;margin-bottom:.0001pt;background:white"><span lang="EN-US">· <span> "</span>I think it would be useful to suggest
the requirement that all Whois text be machine-readable text. I’m not sure if
that’s already a recommendation of the EWG report, but as one can imagine, the
Whois systems that substitute graphics for the e-mail (which, for all we know,
could spread to other fields) would stymie attempts at automated translation by
users of Whois.</span></p>
<p style="margin:0cm;margin-bottom:.0001pt;background:white"><span lang="EN-US"> </span></p>
<p style="margin:0cm;margin-bottom:.0001pt;background:white"><span lang="EN-US">· <span> </span>Does anyone have any ideas for
avoiding flight by bad actors to the least translatable languages? One idea
would be to require:</span></p>
<p style="margin:0cm;margin-bottom:.0001pt;background:white"><span lang="EN-US"> </span></p>
<p style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:72.0pt;margin-bottom:.0001pt;background:white"><span lang="EN-US" style="font-size:10.0pt">·<span style="font-stretch:normal;font-size:7pt;font-family:'Times New Roman'">
</span></span><span lang="EN-US">Whois info to be in
either the language of the registrar or registrant (i.e. can’t pick some random
language just to make it hard to translate),<span> </span><i><u>and</u></i></span></p>
<p style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:72.0pt;margin-bottom:.0001pt;background:white"><span lang="EN-US"> </span></p>
<p style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:72.0pt;margin-bottom:.0001pt;background:white"><span lang="EN-US" style="font-size:10.0pt">·<span style="font-stretch:normal;font-size:7pt;font-family:'Times New Roman'">
</span></span><span lang="EN-US">translation or
transliteration is required if it’s not in a) Latin characters, b) one of the
six U.N. languages, or c) possibly some larger but reasonable set of well-known
and widely translatable languages (say, 20 or so)."</span></p><br>-- <br>Petter Rindforth, LL M
<br>
<br>Fenix Legal KB
<br>Stureplan 4c, 4tr
<br>114 35 Stockholm
<br>Sweden
<br>Fax: <a href="tel:%2B46%280%298-4631010" value="+4684631010" target="_blank">+46(0)8-4631010</a>
<br>Direct phone: +46(0)702-369360
<br>E-mail: <a href="mailto:petter.rindforth@fenixlegal.eu" target="_blank">petter.rindforth@fenixlegal.eu</a>
<br><a href="http://www.fenixlegal.eu" target="_blank">www.fenixlegal.eu</a>
<br>
<br>
<br>NOTICE
<br>This e-mail message is intended solely for the individual or individuals to whom it is addressed. It may contain confidential attorney-client privileged information and attorney work product. If the reader of this message is not the intended recipient, you are requested not to read, copy or distribute it or any of the information it contains. Please delete it immediately and notify us by return e-mail.
<br>Fenix Legal KB, Sweden, <a href="http://www.fenixlegal.eu" target="_blank">www.fenixlegal.eu</a>
<br>Thank you<br><br></div></div></div></div></blockquote></blockquote></div><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><p style="font-size:small;font-family:arial;color:rgb(0,0,0);font-weight:bold;margin:0px"><font face="arial, helvetica, sans-serif">Emily Taylor</font></p><p style="font-size:small;font-family:arial;margin-top:0px;margin-bottom:1.5em"><font face="arial, helvetica, sans-serif"><i style="color:rgb(0,0,0)">MA(Cantab), MBA</i><br><font color="#38761d">Director</font></font></p><p style="font-size:small;margin-bottom:60px"><font face="arial, helvetica, sans-serif"><strong>Netistrar Ltd </strong>- Domain Names at Trade Prices<br><font color="#38761d" style="font-family:arial">W: <a href="http://www.netistrar.com/" style="color:rgb(17,85,204)" target="_blank">http://www.netistrar.com</a></font><font color="#000000" style="font-family:arial"> </font><font color="#38761d" style="font-family:arial">| M</font><font color="#38761d" style="font-family:arial">: </font><font color="#000000"><font face="arial">07540 049322 <font color="#38761d">| T:</font><font color="#000000"> 01283 617808 </font><br><br></font></font></font><font color="#1155cc"><img width="200" height="50" src="http://www.netistrar.com/wp-content/themes/carfax-child/assets/img/Netistrar_Domain_Name_Registrar.gif" style="font-family:arial,helvetica,san-serif"><br></font><span style="color:rgb(170,170,170);font-family:arial,helvetica,san-serif"><br>Repton House, Bretby Business Park, Bretby, Derbyshire, DE15 0YZ<br>Registered in England and Wales No. 08735583. VAT No. 190062332</span><br></p></div></div></div></div>
</div></div>