<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:11.0pt;
font-family:"Calibri",sans-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-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Dear members of the IRP IOT:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For background, please see my <a href="http://mm.icann.org/pipermail/iot/2017-September/000313.html">
e-mail</a> of Sept. 25<sup>th</sup> and you can also see the <a href="https://community.icann.org/pages/viewpage.action?pageId=69282208">
records</a> of our call on Oct 5<sup>th</sup> when we got into this subject. <o:p>
</o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In brief, while some commenters asked for these services on request, the bylaw speaks of the services on an as-needed basis. I propose we confirm these as a function of need.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">And, in my opinion, need does not reach instances where the claimant speaks/understands English even though claimant’s primary language is other than English. Put simply, these services would truly be a function of need, not convenience,
factoring in all of the languages in which the requester has reasonable competency.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In addition, given the practice by ICANN of using the six official UN languages (<span style="color:black;letter-spacing:.3pt;background:white">Arabic, Chinese, English, French, Russian and Spanish</span>) when it provides translation services
at ICANN meetings, I suggest these be given primacy, so that when a claimant speaks two languages (but not English), and one of them is an official UN language, then that official UN language would be the translation service provision.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I also believe that the Bylaw language “if needed” means that if ‘claimant’ includes more than one person (for instance claimant is a company), then if one of those persons (e.g. an officer of the company) speaks English that would suffice
for using English in the IRP. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">With respect to the issue of costs that Kavouss mentioned on our call of Oct. 5<sup>th</sup>, I suggest language along the line that the IRP Panel should assess, when considering the translation of documents, the fair balance to be accorded
to materiality of the document versus the costs/delay to translate – all in the context of ICDR Article 18 on Translation and Bylaw 4.3(n) on ensuring
<span style="background:white">fundamental fairness and due process.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thus, my suggestion is that we ask Sidley to incorporate these overall suggestions into draft
<b>Rule 5 </b>along with language that<b> </b>implementation issues are for the sound discretion of the IRP panel (e.g. whether claimant is sufficiently capable in English language, or how to weigh cost of translation in decision to hold/not hold a hearing).
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I hope we can move this to first reading on our next call on Nov. 14 at 19:00 UTC – please comment on list by that date if you cannot be on that call.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If you wish to suggest an alternative handling, please put that on list and state the rational and include
<u>specifically proposed alternative language</u>. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I look forward to seeing those of you who plan to attend ICANN 60.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">David<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">David McAuley<o:p></o:p></p>
<p class="MsoNormal">Sr International Policy & Business Development Manager<o:p></o:p></p>
<p class="MsoNormal">Verisign Inc.<o:p></o:p></p>
<p class="MsoNormal">703-948-4154<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>