<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;}
span.EstiloCorreo17
{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;}
/* List Definitions */
@list l0
{mso-list-id:1342119588;
mso-list-template-ids:1460554592;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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">Personally I would prefer that the GNSO representative to the EC Admin was not from the leadership team, I accepted it since it seemed to be the
position of the majority of the SSC.<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 think that it is better if the representative has what I think in English is call it an “arm length” separation from the Council. This way we
can ensure that the representative has to consult the GNSO in every occasion and we diminish the possibility that the representative gives what he thinks is the position of the GNSO Council without consulting previously. This does not mean that I distrust
the actual Council leadership team, it is just that it is a good way to prevent any misunderstanding.<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<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-ssc-bounces@icann.org [mailto:gnso-ssc-bounces@icann.org]
<b>En nombre de </b>Susan Kawaguchi<br>
<b>Enviado el:</b> martes, 13 de junio de 2017 01:42 p.m.<br>
<b>Para:</b> Marika Konings<br>
<b>CC:</b> gnso-ssc@icann.org<br>
<b>Asunto:</b> Re: [Gnso-ssc] For your review - draft process to designate GNSO Rep to EC Admin<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Thank you Marika for clarifying the process required for the EC admin. I agree we can still recommend that the EC Admin role be filled by Council leadership team. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Anyone else have thoughts on this additional information? <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Susan <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, Jun 8, 2017 at 5:30 PM, Marika Konings <<a href="mailto:marika.konings@icann.org" target="_blank">marika.konings@icann.org</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt">Dear All,</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt">Per the SSC discussion, I reached out to our legal colleagues to obtain some further information in relation to whether it would be possible
to have the collective of the GNSO Leadership team (GNSO Chair and Council Vice-Chairs) designated as the GNSO representative to the Empowered Community Administration. They pointed out that the Bylaw language states that “Each Decisional Participant shall
deliver annually a written certification from its chair or co-chairs to the Secretary designating
<u>the individual</u> who shall represent the Decisional Participant on the EC Administration”. As such, under the scenario that the SSC is currently considering, it would be a requirement for the GNSO Leadership team to make a determination who would serve
in the role of representative to EC Administration so that this person subsequently can be designated by the GNSO Council. This, however, does not preclude those on the leadership team that have not been designated to step in if/when needed but it would be
recommendable to include this possibility as part of the designation so there is clarity around this possibility of an alternate. Based on this information, the process, based on the scenario of having the leadership team make a determination of who from the
leadership team would serve in the role as representative to the EC Admin could look as follows:</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span lang="EN-US" style="font-size:11.0pt">GNSO Chair election takes place at ICANN Annual Meeting
</span><span lang="EN-US"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span lang="EN-US" style="font-size:11.0pt">Noting that the Vice-Chair cannot be from the same Stakeholder Group as the Chair, Vice-Chairs may be confirmed prior to the Chair Election only if there is a single Chair candidate or all Chair candidates are from
the SG. Otherwise, confirmation of Vice-Chairs may happen after the Chair election.</span><span lang="EN-US"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span lang="EN-US" style="font-size:11.0pt">GNSO Chair is confirmed upon election as the interim representative to the EC Admin, until such time as the leadership team has had an opportunity to meet and decide who is taking on this role. In case the GNSO Council
fails to select a Chair, the existing representative to the EC Admin will remain in that role until such time as a Chair has been elected.
</span><span lang="EN-US"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span lang="EN-US" style="font-size:11.0pt">As soon as possible upon confirmation of the leadership team, the leadership team will meet to decide who is to be designated as GNSO Representative to the EC Admin. Following this determination, this decision is
to be confirmed by the GNSO Council as part of the consent agenda. The decision on the designation of the permanent representative to the EC Admin is then communicated to the ICANN Secretary and EC Admin.
</span><span lang="EN-US"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span lang="EN-US" style="font-size:11.0pt">Should at any point during term of the Chair and/or Vice-Chairs there be a change (for example, a resignation or a change in circumstances which may mean the representative is no longer able to perform in this role),
the leadership team will communicate this to the GNSO Council as soon as possible together with the name of the individual on the leadership team who will take on this role so that a new designation can be made.
</span><span lang="EN-US"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span lang="EN-US" style="font-size:11.0pt">As part of the designation, it will be made clear that in case of absence or conflict, another member of the leadership team may step in to replace the representative on the EC Admin.
</span><span lang="EN-US"><o:p></o:p></span></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt">As noted, this is a possible way in which the scenario of having a member of the GNSO leadership team (GNSO Chair and Council Vice-Chairs)
serve as the designated representative to the EC Admin, but as always, please feel free to share any comments, edits or alternative scenarios you may have. Following your feedback, the proposed process could be written up in the form of a motion which can
then be shared with the GNSO Council for its consideration ahead of ICANN59.</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt">Best regards,</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt">Marika </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><i><span lang="EN-US" style="font-size:11.0pt">Marika Konings</span></i></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i><span lang="EN-US" style="font-size:11.0pt">Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) </span></i><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i><span lang="EN-US" style="font-size:11.0pt">Email:
<a href="mailto:marika.konings@icann.org" target="_blank">marika.konings@icann.org</a> </span></i><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i><span lang="EN-US" style="font-size:11.0pt"> </span></i><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i><span lang="EN-US" style="font-size:11.0pt">Follow the GNSO via Twitter @ICANN_GNSO</span></i><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i><span lang="EN-US" style="font-size:11.0pt">Find out more about the GNSO by taking our <a href="http://learn.icann.org/courses/gnso" target="_blank">interactive courses</a> and
visiting the <a href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers" target="_blank">GNSO Newcomer pages</a>. </span></i><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><br>
_______________________________________________<br>
Gnso-ssc mailing list<br>
<a href="mailto:Gnso-ssc@icann.org">Gnso-ssc@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-ssc" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-ssc</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><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>