<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="MSHTML 8.00.6001.23536">
</head>
<body>
<div dir="ltr" align="left"><span class="472212717-25092014"><font color="#0000ff" size="2" face="Arial">All,</font></span></div>
<div dir="ltr" align="left"><span class="472212717-25092014"><font color="#0000ff" size="2" face="Arial">I think this might be of interest to you, I think it is quite in line with the RySG and our comments.</font></span></div>
<div dir="ltr" align="left"><span class="472212717-25092014"><font color="#0000ff" size="2" face="Arial">Best regards,</font></span></div>
<div> </div>
<div align="left">
<p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal">
<?xml:namespace prefix = v ns =
"urn:schemas-microsoft-com:vml" />
<v:shapetype id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"><v:stroke joinstyle="miter"></v:stroke><v:formulas><v:f eqn="if lineDrawn pixelLineWidth 0"></v:f><v:f eqn="sum @0 1 0"></v:f><v:f eqn="sum 0 0 @1"></v:f><v:f eqn="prod @2 1 2"></v:f><v:f eqn="prod @3 21600 pixelWidth"></v:f><v:f eqn="prod @3 21600 pixelHeight"></v:f><v:f eqn="sum @0 0 1"></v:f><v:f eqn="prod @6 1 2"></v:f><v:f eqn="prod @7 21600 pixelWidth"></v:f><v:f eqn="sum @8 21600 0"></v:f><v:f eqn="prod @7 21600 pixelHeight"></v:f><v:f eqn="sum @10 21600 0"></v:f></v:formulas><v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"></v:path>
<?xml:namespace prefix = o ns
= "urn:schemas-microsoft-com:office:office" />
<o:lock v:ext="edit" aspectratio="t"></o:lock></v:shapetype><v:shape style="Z-INDEX: 1; POSITION: absolute; MARGIN-TOP: 9pt; WIDTH: 1in; HEIGHT: 1in; MARGIN-LEFT: 0px; mso-wrap-distance-left: 0; mso-wrap-distance-top: 0; mso-wrap-distance-right: 0; mso-wrap-distance-bottom: 0; mso-position-horizontal: absolute; mso-position-horizontal-relative: text; mso-position-vertical: absolute; mso-position-vertical-relative: line" id="_x0000_s1026" type="#_x0000_t75" alt="" o:allowoverlap="f"><v:imagedata src="file:///D:\DOCUME~1\B279816\CONFIG~1\Temp\msohtml1\01\clip_image001.png" o:title="LOGO A"></v:imagedata>
<?xml:namespace prefix = w ns =
"urn:schemas-microsoft-com:office:word" />
<w:wrap type="square"></w:wrap></v:shape><span lang="ES-UY"> <o:p></o:p></span></p>
<p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><span style="FONT-FAMILY: Arial; FONT-SIZE: 10pt" lang="ES-UY"><img border="0" hspace="0" alt="" align="left" src="cid:472212717@25092014-0FB9">Osvaldo Novoa</span><span lang="ES-UY"><o:p></o:p></span></p>
<p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><span style="FONT-FAMILY: Arial; FONT-SIZE: 10pt" lang="ES-UY">Subgerente General</span><span lang="ES-UY"><o:p></o:p></span></p>
<p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><span style="FONT-FAMILY: Arial; FONT-SIZE: 10pt" lang="ES-UY">Antel</span><span lang="ES-UY"><o:p></o:p></span></p>
<p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><span style="FONT-FAMILY: Arial; FONT-SIZE: 10pt" lang="ES-UY">Guatemala 1075, Nivel 22</span><span lang="ES-UY"><o:p></o:p></span></p>
<p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><span style="FONT-FAMILY: Arial; FONT-SIZE: 10pt" lang="ES-UY">Montevideo, 11800</span><span lang="ES-UY"><o:p></o:p></span></p>
<p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><span style="FONT-FAMILY: Arial; FONT-SIZE: 10pt" lang="ES-UY">Uruguay</span><span lang="ES-UY"><o:p></o:p></span></p>
<p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><span lang="ES-UY"> <o:p></o:p></span></p>
<p style="TEXT-INDENT: 35.4pt; MARGIN: 0cm 0cm 0pt 35.4pt" class="MsoNormal"><span style="FONT-FAMILY: Arial; FONT-SIZE: 10pt" lang="ES-UY">Tel. +598 2928 6400</span><span lang="ES-UY"><o:p></o:p></span></p>
<p style="TEXT-INDENT: 35.4pt; MARGIN: 0cm 0cm 0pt 35.4pt" class="MsoNormal"><span style="FONT-FAMILY: Arial; FONT-SIZE: 10pt" lang="ES-UY">Fax. +598 2928 6401</span><span lang="ES-UY"><o:p></o:p></span></p>
<p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><span lang="ES-UY"><o:p> </o:p></span></p>
</div>
<div> </div>
<br>
<div dir="ltr" lang="es" class="OutlookMessageHeader" align="left">
<hr tabindex="-1">
<font size="2" face="Tahoma"><b>De:</b> owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org]
<b>En nombre de </b>john@crediblecontext.com<br>
<b>Enviado el:</b> Jueves, 25 de Septiembre de 2014 14:22<br>
<b>Para:</b> council@gnso.icann.org<br>
<b>Asunto:</b> [council] 9/25/14 ccNSO Council meeting recap<br>
</font><br>
</div>
<div></div>
<div>All,</div>
<div> </div>
<div>The dominant issues for the ccNSO Council this morning were IANA transition, Internet governance and ICANN accountability.</div>
<div> </div>
<div>On the transition, ccNSO Chair Byron Holland reported on the letter he co-signed with GNSO Council chair Jonathan Robinson noting the "unrealistic" deadline set for the process. As you know, there has been much discussion regarding how out-of-synch is
the expressed timetable for the transition in 2015 with the loud, messy and slow strength of the bottom-up, consensus-driven decision-making model of the multi-stakeholder community.</div>
<div> </div>
<div>On Internet governance, the ccNSO Council adopted the charter for the cross-community Working group on Internet Governance.</div>
<div> </div>
<div>And, on ICANN accountability, a statement was adopted that aligns with the broader community. I have cut-and-pasted the statement with my own
<strong>highlights</strong> at the bottom of this email.</div>
<div> </div>
<div>Cheers,</div>
<div> </div>
<div>Berard</div>
<div> </div>
<div>ccNSO Council Submission Enhancement ICANN’s Accountability Process</div>
<div> </div>
<div>25 September 2014</div>
<div> </div>
<div>The ccNSO Council welcomes ICANN’s decision to conduct a public consultation on<br>
the proposed “Enhancing Accountability” process and appreciates the responses to<br>
various questions posed by the community. As we have previously stated, improved<br>
<strong>accountability is both a means and a prerequisite</strong> for ICANN to achieve its 2016-2020<br>
strategic vision statement, to “enable ICANN to be trusted by all stakeholders.” It<br>
goes without saying that any process intended to enhance and reinforce trust must<br>
itself be trusted.</div>
<div> </div>
<div>Over time and through experience, ICANN stakeholders have come to trust the crosscommunity<br>
working group (CCWG) process. Having participated in and listened<br>
carefully to the exchange of views between ICANN staff and the SO/AC/SGs on this<br>
point over the past several weeks,<strong> the ccNSO Council is not persuaded that the</strong><br>
<strong>“community working group” proposed by ICANN improves upon or offers any benefits</strong><br>
<strong>or advantages over the trusted CCWG model</strong>. The main argument for creating the<br>
“community working group” appears to be ensuring the inclusion of persons in the<br>
process, who consider themselves either not affiliated with a Supporting Organization<br>
or Advisory Committee or a “newcomer”. Serious thought needs to be given to how to<br>
enable these persons to engage in the process as a whole effectively and in a way that<br>
does not undermine the existing engagement structure. Accordingly, <strong>we call on the</strong><br>
<strong>staff and board to endorse the creation of a standard CCWG as the locus for bottomup,</strong><br>
<strong>multistakeholder development of mechanism to enhance ICANN’s accountability.</strong></div>
<div> </div>
<div>As a standard CCWG, participating SO/AC/SGs should be charged with developing<br>
the group’s charter, including the scope of its responsibility. Consistent with the<br>
NetMundial conclusions, the goal of the Enhancing Accountability process should be<br>
to ensure that a system of checks and balances is in place to ensure that ICANN<br>
operates in accordance with an agreed set of principles and that meaningful redress is<br>
available to those who are harmed by ICANN actions or inactions in contravention of<br>
those principles. The CCWG should have full authority to explore and recommend<br>
approaches to achieve that goal.</div>
<div> </div>
<div><strong>The CCWG should have authority to determine the size and structure of the group, as</strong><br>
<strong>well as its working methodology.</strong> Given the importance of the work to be undertaken<br>
and the need to work to deadline, the ccNSO believes that ICANN should provide<br>
support for an independent secretariat, including a non-voting CCWG chair. It is also<br>
the view of the Council that the CCWG should select the Chair, who should have<br>
demonstrated skills and experience in chairing.</div>
<div> </div>
<div>Ideally, the CCWG itself should be responsible for selecting, through an open<br>
nomination process, non-voting advisors with predefined expertise (“Accountability<br>
Advisors”). In the interests of time, however, we acknowledge the potential utility in<br>
kicking off the selection process before the CCWG is set up. ICANN could usefully<br>
identify a pool of experts, among which the CCWG could select its Advisors, as soon as<br>
the CCWG is set up. <strong>The ccNSO Council also believes that the paramount concern</strong><br>
<strong>should be to look for independent experts with a proven track record in their area of</strong><br>
<strong>expertise. In this context we urge ICANN to reconsider its proposal not to compensate</strong><br>
<strong>the Accountability Advisors.</strong></div>
<div> </div>
<div>Under the circumstances, the ccNSO agrees that smaller subgroups consisting of<br>
members identified by the SO/AC/SGs and the Accountability Advisors could be<br>
formed within the CCWG in order to organize and deliver research and expert advice<br>
needed by the CCWG, as well as interface more intensely with ICANN and its counsel<br>
on accountability mechanisms recommended by the CCWG, or liaise with the IANA<br>
Transition working group, etc.</div>
<div> </div>
<div>The ccNSO has previously stated that <strong>adequate accountability mechanisms relative to</strong><br>
<strong>the IANA Stewardship Transition must be in place at the time of the IANA transition</strong> in<br>
one year from now. We have also recognized that the potential recommendations and<br>
mechanisms to enhance ICANN’s accountability may be broader i.e. not limited to<br>
accountability mechanisms related to the IANA Stewardship Transition Process and it<br>
may take time to considerable time to implement all of these recommendations and<br>
mechanisms. Accordingly, we also recommend that the CCWG and any coordinating<br>
body should work closely with ICANN to identify those mechanisms that must be in<br>
place for a successful IANA Stewardship Transition and to prioritize the implementation<br>
of those mechanisms. In addition the CCWG and any coordinating body should also<br>
agree on a timeline for full implementation, which may extend beyond the IANA<br>
Stewardship Transition.</div>
<div> </div>
<div>We understand that the ICANN Board must reach agreement on the process it will use<br>
to consider and act on recommendations developed through this process. The<br>
community has expressed a strong preference to have a clearly defined process,<br>
including dialogue and consultation with the community before any recommendation is<br>
rejected. <strong>The ccNSO Council believes that the presumption should be that community</strong><br>
<strong>recommendations will be accepted absent a compelling reason for rejection.</strong> We urge<br>
the Board to develop and publish for public comment its proposed methodology for<br>
considering and acting on accountability-related recommendations in the very near<br>
term, in any case before the process has commenced fully. As a suggestion the Board<br>
may look at the processes and mechanisms used to consider and act upon policy<br>
recommendations developed through the policy development processes of the<br>
Supporting Organizations and defined through the ICANN Bylaws</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1">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>