Dear all<div><br></div><div>On behalf of the small group working on IDN recommendations, here are the amended recommendations, and findings (which are taken direct from the draft report findings).</div><div><br></div><div>
I believe that this wording now has consensus among the small group. The meaning is close to the original recommendations published for public comment, but the text is shorter.</div><div><br></div><div>I hope we can sign these off as soon as possible, so please let me have any comments before our call tomorrow. Those unable to join - please indicate your views. If I don't hear back I'll assume that everyone is happy.</div>
<div><br>Kind regards</div><div><br>Emily</div><div><br></div><div><br></div><div><br clear="all"><div><div><p class="MsoNormal"></p><p class="MsoNormal"><b><span style="font-size:14pt;font-family:Calibri,sans-serif">Findings:</span></b></p>
<p class="MsoNormal"><b><span style="font-size:14pt;font-family:Calibri,sans-serif"><br></span></b></p><p class="MsoNormal" style><span lang="EN-US" style="font-family:Calibri"><font size="4">Perhaps it should be no surprise that within this environment, policy and implementation have not kept pace with the real world. A significant example of this is Internationalised Domain Names (IDN), which have been available for registration at the second level for over a decade, and at the Top Level for more than a year. During this time, WHOIS policies were not amended to accommodate the obvious need to support non-ASCII character sets even though there was a recognition that Internationalisation is essential for the Internet’s development as a global resource.</font></span></p>
<p class="MsoNormal" style><span lang="EN-US" style="font-family:Calibri"><font size="4"><br></font></span></p><p class="MsoNormal" style><span lang="EN-US" style="font-family:Calibri"><font size="4">The NORC Study on Data Accuracy highlighted IDN contact data as a major cause of apparent inaccuracy.</font></span></p>
<p class="MsoNormal"><span style> </span></p><p class="MsoNormal"><b><span style="font-size:14pt;font-family:Calibri,sans-serif"><br></span></b></p><p class="MsoNormal"><b><span style="font-size:14pt;font-family:Calibri,sans-serif">Recommendations</span></b></p>
<p class="MsoNormal"><b><span style="font-size:14pt;font-family:Calibri,sans-serif">18. </span></b><span style="font-size:14pt;font-family:Calibri,sans-serif;background-color:rgb(255,255,255)">ICANN Community should task a working group within 6 months of publication to determine the relevant internationalized domain name registration data requirements and evaluate the available solutions, especially those being successfully implemented by ccTLDs, <span style="background-image:initial">at least for the adoption of IDN gTLDs, as already stipulated by the New gTLD Applicant Guidebook.</span>The working group should aim for consistency of approach across the gTLD and – on a voluntary basis – the ccTLD space<span style="background-image:initial">, and report within a year of being tasked.</span><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Calibri,sans-serif;background-color:rgb(255,255,255)"><u></u> <u></u></span></p><p class="MsoNormal"><b><span style="font-size:14pt;font-family:Calibri,sans-serif;background-color:rgb(255,255,255)">19.</span></b><span style="font-size:14pt;font-family:Calibri,sans-serif"><span style="background-color:rgb(255,255,255)"> The final data model, including <span style="background-image:initial">(any)</span> requirements for the translation or transliteration of the registration data, should be incorporated in <span style="background-image:initial">the relevant</span> Registrar and Registry agreements within 6 months of adoption of the working group’s recommendations by the ICANN Board. If these recommendations are not finalized in time for the next revision of such agreements, explicit placeholders for this purpos</span>e should be put in place in the agreements for the new gTLD program at this time, and in the existing agreements when they come up for renewal.<u></u><u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:14pt;font-family:Calibri,sans-serif"><u></u> </span></b></p><p></p><p class="MsoNormal"><b><span lang="EN-US" style="font-size:14pt;font-family:Calibri,sans-serif">20</span></b><span lang="EN-US" style="font-size:14pt;font-family:Calibri,sans-serif">. In addition, metrics should be developed to maintain and measure the accuracy of the internationalized registration data and corresponding data in ASCII, with clearly defined compliance methods and targets, as per the details in Recommendations 5-9 in this document.<u></u><u></u></span></p>
</div><p class="MsoNormal"><font color="#1f497d" face="Calibri, sans-serif"><span style="font-size:15px"><br></span></font></p></div><br><br><span style="color:rgb(153,51,153)"></span> <img src="http://www.etlaw.co.uk/images/stories/etlaw/etclogo250x60.gif"><br>
<br><div style="margin-left:80px"><u style="color:rgb(204,51,204)"> </u><br style="color:rgb(153,51,153)">
<br><span style="color:rgb(153,153,153)">76 Temple Road, Oxford OX4 2EZ UK</span><br style="color:rgb(153,153,153)"><span style="color:rgb(153,153,153)">t: <a href="tel:%2B44%20%280%291865%20582%20811" value="+441865582811" target="_blank">+44 (0)1865 582 811</a> • m: <a href="tel:%2B44%20%280%297540%20049%20322" value="+447540049322" target="_blank">+44 (0)7540 049 322</a></span><br style="color:rgb(153,153,153)">
<span style="color:rgb(153,153,153)"><a href="mailto:emily@emilytaylor.eu" target="_blank">emily@emilytaylor.eu</a> </span><br style="color:rgb(153,153,153)"><br style="color:rgb(153,153,153)"><b style="color:rgb(153,153,153)"><a href="http://www.etlaw.co.uk" target="_blank">www.etlaw.co.uk</a></b><br style="color:rgb(153,153,153)">
<br style="color:rgb(153,153,153)"><span style="color:rgb(153,153,153)">Emily Taylor Consultancy Limited is a company registered in England and Wales No. 7630471. VAT No. 114487713.</span><br></div><br>
</div>