<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=utf-8">
<meta name="Generator" content="Microsoft Word 12 (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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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;}
p.gmail-msolistparagraph, li.gmail-msolistparagraph, div.gmail-msolistparagraph
{mso-style-name:gmail-msolistparagraph;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EstiloCorreo18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
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="ES-UY" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hello all,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Sorry for answering so late by I’ve been travelling and on vacations till last Sunday. Although I was able to participate in ICANN 61, I arrived
on Sunday and had to leave early on Wednesday so I wasn’t able to be at the WG’s meeting.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I am Ok with Heather’s recommendation for the WG, I still think that the GNSO Working Group Guidelines are very clear on how to run a WG and on
the methodology to reach consensus and we should abide by it. I don’t think we need a facilitator to help the Chairmen with the WG, nor do I see any problem with an anonymous poll but would agree to non-anonymous poll. I think that some members of the group,
with different opinions, have reach a point where they don’t have room for more negotiations so we should try to decide if we have Consensus or Strong Support but significant opposition.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I continue to support Option 3, as it seems to satisfy some of the requirements requested by the IGOs.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Osvaldo Novoa<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">ISPCP Constituency<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="ES" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De:</span></b><span lang="ES" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Gnso-igo-ingo-crp [mailto:gnso-igo-ingo-crp-bounces@icann.org]
<b>En nombre de </b>Susan Kawaguchi<br>
<b>Enviado el:</b> viernes, 09 de marzo de 2018 03:35 p.m.<br>
<b>Para:</b> gnso-igo-ingo-crp@icann.org<br>
<b>CC:</b> gnso-chairs@icann.org; Heather Forrest<br>
<b>Asunto:</b> [Gnso-igo-ingo-crp] IGO-INGO Curative Rights PDP WG<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Dear IGO-INGO Curative Rights Policy Development Process Working Group members,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I write as the GNSO Council Liaison to this Working Group, to circulate a recommendation from Dr. Heather Forrest,
GNSO Chair, which I endorse and support. She and I both hope that the proposed approach can be a useful path forward in assisting the group to ascertain and develop consensus (if any) on the six options under consideration relating to the handling of IGO jurisdictional
immunity issues where a registrant who has lost a UDRP or URS proceeding against an IGO proceeds to file a court claim against that IGO.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">You will find details of the recommended approach in the attached Straw Man Paper (prepared by ICANN staff at Heather’s
request) and accompanying Annex. I will be very grateful if everyone can take a moment to provide feedback as to whether you support the suggested approach or not, since this will allow us all to see if the approach may be workable.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">As the Working Group has a session coming up next week at ICANN61 (on Wednesday 14 March from 1700-1830 Puerto
Rico time), the recommended approach also includes a suggestion for how to organize that session. In brief, the recommendation is:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
<p class="gmail-msolistparagraph"><span style="font-size:11.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Instead of a regular Working Group meeting or open community session, as has been the Working Group’s practice in recent ICANN meetings, the ICANN61 session will be run as a form of “open
office hours”, where any and all Working Group members are invited to discuss their views and questions on the topic of IGO jurisdictional immunity with me, including (and especially) the six options.</span><o:p></o:p></p>
<p class="gmail-msolistparagraph"><span style="font-size:11.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">ICANN policy staff will be on hand, to provide background information and process advice, and to assist me with taking accurate notes of the session.</span><o:p></o:p></p>
<p class="gmail-msolistparagraph"><span style="font-size:11.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">The session will not be recorded, to encourage frank sharing of views (note: this is the model that was adopted for a different group relatively recently to try to break an impasse in
that group).</span><o:p></o:p></p>
<p class="gmail-msolistparagraph"><span style="font-size:11.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Since not everyone will be able to attend the ICANN61 open office hours and, more importantly, because some Working Group members may prefer to provide their views in private, I will (with
ICANN staff assistance) hold additional 1:1 or small group conversations (as you may prefer) after ICANN61 – this will most likely be done through Adobe Connect and/or a conference phone bridge.</span><o:p></o:p></p>
<p class="gmail-msolistparagraph"><span style="font-size:11.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Following these office hour sessions, I will (with ICANN staff assistance) prepare a report for the Working Group on the discussions that took place. That report should form the basis
for an initial designation of consensus levels for each of the six options by Phil and Petter.</span><o:p></o:p></p>
<p class="gmail-msolistparagraph"><span style="font-size:11.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">While a non-anonymous poll may be useful at some later stage in this iterative process of finding consensus (consistent with the requirements in the GNSO Working Group Guidelines), it
is not necessary at this present time.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Thank you – and on behalf of Heather, thank you also for taking the time to provide me with any and all feedback
you may have in light of the procedural path forward noted in this message.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><o:p> </o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Susan Kawaguchi </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Councilor for the Business Constituency</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><o:p> </o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><o:p> </o:p></p>
</div>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este
mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje.
ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información<br>
<br>
<br>
This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy
of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.<br>
</font>
</body>
</html>