<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="">Hi Becky<div class=""><br class=""></div><div class=""><br class=""></div><div class="">I agree with the suggestion of providing translation services in the context of a live hearing.</div><div class=""><br class=""></div><div class="">I think the initial claim must be in English. There are enough English speaking lawyers around the world, that they can prepare an initial claim.</div><div class=""><br class=""></div><div class="">I also think that parties may require translation of further documents. Given that complainants may be a mix of commercial and non-commercial parties, I would suggest we allow the panel the flexibility (on good cause shown) to consider a request and to determine that ICANN make a contribution towards the reasonable translation costs of non-commercial parties.</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Mike</div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 30 Mar 2020, at 21:34, Becky Burr <<a href="mailto:becky.burr@board.icann.org" class="">becky.burr@board.icann.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">FWIW, and understanding that this will be extremely controversial, I think that the translation issue is extremely complicated and there is a great risk that we will get this wrong without a more thorough study. My approach would be to start by providing translation services in the context of a live hearing, but not otherwise, and undertaking a survey of how translation issues are handled in similar contexts. The IRP IOT is an ongoing body, and there is nothing that would prevent the group from revisiting the issue once we have more information and/or more relevant experience.</div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Mar 28, 2020 at 2:34 AM Kurt Pritz <<a href="mailto:kurt@kjpritz.com" class="">kurt@kjpritz.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;" class="">Hi Susan and Everyone: <div class=""><br class=""></div><div class="">Here are my views on handling of translation expenses. I understand this is overly formulaic or specific beyond our needs but it might be of assistance in thinking through the creation of policy or rules for this issue. <div class=""><br class=""></div><div class="">Principles:</div><div class=""><br class=""></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class="">1) If one party makes the rules (ICANN), then those rules should construed in favor of the other party. (This has parallels in contract law.)</div><div class=""><br class=""></div><div class="">2) As a corollary: if one party decides the language of the proceedings (ICANN), that party should make reasonable accommodation for the other party, including bearing reasonable costs for translation. </div><div class=""><br class=""></div><div class="">3) “Reasonableness” should be carefully defined to provide an appropriate balance between accommodation, meeting the needs of the procedure, and avoiding abuse or unnecessary cost or procedure. </div><div class=""><br class=""></div><div class="">4) No party should be disadvantage by language. </div></blockquote><div class=""><br class=""></div><div class="">With that in mind, our rules could provide that:</div><div class=""><br class=""></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class="">1) Understanding that the official language of the proceedings are in English, ICANN will pay for translation into English. </div><div class=""><br class=""></div></blockquote><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class="">a) This includes the initial claim / pleadings. </blockquote><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><br class=""></blockquote><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class="">b) This applies to all languages (not only the UN languages).</blockquote></blockquote><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class=""><br class=""></div><div class="">2) In order to ensure cost predictability and prevent translation costs being used to dis-advantage one party: </div><div class=""><br class=""></div></blockquote><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class="">a) The translations will be done by ICANN retained translators. </blockquote><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><br class=""></blockquote><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class="">b) Understanding that evidentiary documents can be voluminous and also be of marginal relevance, they all need not be translated. The panel might decide that an issue is already conceded, that specific evidence is duplicative, or that the evidence is not relevant to the germane issues. The panel can make these decisions based upon the pleadings and arguments that refer to the evidence proffered. In these cases the panel can decide that the evidence need not be translated. When making this decision, the panel can indicate to both parties why the translation is not required. (Therefore in practice, the decision to not translate evidentiary documents will be a positive indication for the non-English-speaking party.)</blockquote></blockquote><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class=""><br class=""></div><div class="">3) In order to ensure that a non-English speaking party is not dis-advantaged and that translations are objectively performed: </div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><br class=""></blockquote></blockquote></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class=""><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class="">a) The ICANN-retained translators will be retained and managed by some type of double-blind process so the translators and their representatives will never speak with ICANN staff. In addition, ICANN legal staff will not be part of the engagement process. </blockquote></div><div class=""><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><br class=""></blockquote></div><div class=""><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class="">b) The non-English-speaking party (i.e., not ICANN) can retain their own translators to provide the pleadings and evidence in English but will bear the expense for that effort. That is, the party can provide the pleadings in English of they desire. </blockquote></div></blockquote><div class=""><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class=""><br class=""></div><div class="">4) Similar to the above, ICANN will pay for translations of its own pleadings and arguments into the language of the complainant, only if the complaining party used the ICANN-furnished translator to translate its documents and the complaining party requests the translation. </div><div class=""><br class=""></div><div class="">5) Similar to the above ICANN will pay for translation of evidentiary documents in line with item (2b) above, only if the complaining party used the ICANN-furnished translator to translate its documents and the complaining party requests the translation</div><div class=""><br class=""></div><div class="">6) Similar to the above, ICANN will pay for translation of the panel decisions and questions to the parties, only if the complainant used the ICANN translator to translate its documents and the complaining party requests the translation. </div><div class=""><br class=""></div><div class="">7) In summary, the complaining party will decide at the outset whether to bear any translation costs or to use ICANN translators throughout. However, there should be some mechanism for the complaining party to “change its mind,” given an appropriate set of circumstances.</div></blockquote><div class=""><br class=""></div><div class="">I am sure there are lots of holes in this but I hope it is helpful to think through and discuss the last set of translation issues. </div><div class=""><br class=""></div><div class="">I am happy to answer questions or join in our next discussion about this (or ignore it if it is not useful). </div><div class=""><br class=""></div><div class="">Best regards,</div><div class=""><br class=""></div><div class="">Kurt</div><div class=""><br class=""></div></div></div>_______________________________________________<br class="">
IOT mailing list<br class="">
<a href="mailto:IOT@icann.org" target="_blank" class="">IOT@icann.org</a><br class="">
<a href="https://mm.icann.org/mailman/listinfo/iot" rel="noreferrer" target="_blank" class="">https://mm.icann.org/mailman/listinfo/iot</a><br class="">
<br class="">
_______________________________________________<br class="">
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank" class="">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank" class="">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote></div>
_______________________________________________<br class="">IOT mailing list<br class=""><a href="mailto:IOT@icann.org" class="">IOT@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/iot<br class=""><br class="">_______________________________________________<br class="">By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</div></blockquote></div><br class=""></div></body></html>