<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns="http://www.w3.org/TR/REC-html40" 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">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="MSHTML 8.00.6001.23536">
<style>@font-face {
font-family: Wingdings;
}
@font-face {
font-family: MS Mincho;
}
@font-face {
font-family: MS Mincho;
}
@font-face {
font-family: Cambria;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: @MS Mincho;
}
@page WordSection1 {size: 612.0pt 792.0pt; margin: 72.0pt 72.0pt 72.0pt 72.0pt; }
P.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-fareast-language: EN-US
}
LI.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-fareast-language: EN-US
}
DIV.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-fareast-language: EN-US
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoListParagraph {
MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-fareast-language: EN-US; mso-style-priority: 34
}
LI.MsoListParagraph {
MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-fareast-language: EN-US; mso-style-priority: 34
}
DIV.MsoListParagraph {
MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-fareast-language: EN-US; mso-style-priority: 34
}
SPAN.EmailStyle17 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: personal-compose
}
.MsoChpDefault {
FONT-FAMILY: "Calibri","sans-serif"; mso-fareast-language: EN-US; mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
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="EN-GB" link="blue" vlink="purple">
<div dir="ltr" align="left"><font color="#0000ff" size="2" face="Arial"><span class="293105216-17012014">Dear all,</span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" size="2" face="Arial"><span class="293105216-17012014">We should answer this request. How should we do it?</span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" size="2" face="Arial"><span class="293105216-17012014">Best regards,</span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" size="2" face="Arial"><span class="293105216-17012014">Osvaldo</span></font></div>
<div> </div>
<div align="left">
<p style="MARGIN: 0cm 0cm 0pt" class="MsoNormal"><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><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><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:293105216@17012014-0667">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>Jonathan Robinson<br>
<b>Enviado el:</b> Viernes, 17 de Enero de 2014 14:22<br>
<b>Para:</b> council@gnso.icann.org<br>
<b>CC:</b> Gomes, Chuck; jscottevans@outlook.com<br>
<b>Asunto:</b> [council] Request for input from the GNSO Policy & Implementation Working Group<br>
<b>Importancia:</b> Alta<br>
</font><br>
</div>
<div></div>
<div class="WordSection1">
<p class="MsoNormal">All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please be aware of the <span style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: black; FONT-SIZE: 10pt" lang="EN-US">
Request for input from the GNSO Policy & Implementation Working Group (see below). This is a working group of substantial interest and importance as evidenced by:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: black; FONT-SIZE: 10pt" lang="EN-US"><o:p> </o:p></span></p>
<p style="TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1" class="MsoListParagraph">
<![if !supportLists]><span style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><span style="mso-list: Ignore">1.<span style="FONT: 7pt 'Times New Roman'">
</span></span></span><![endif]>The level of interest that related topics have attracted during the roll-out of the new gTLD programme<o:p></o:p></p>
<p style="TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1" class="MsoListParagraph">
<![if !supportLists]><span style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><span style="mso-list: Ignore">2.<span style="FONT: 7pt 'Times New Roman'">
</span></span></span><![endif]>The level of interest indicated by the sheer number of participants in the working group.<o:p></o:p></p>
<p class="MsoNormal"><br>
Notwithstanding that, the Working Group has not received much in the way of input in response to its call for input (first sent out in October 2013).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Therefore, this note is to draw your attention to this and to ask you to please encourage your respective groups / constituencies to provide such input to the WG as soon as possible.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For information and completeness, the questions from the working group are copied below AND attached in long form (as sent to SO & ACs) to this note.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank-you.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jonathan<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">---<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="COLOR: black" lang="EN-US">This Working Group (P&I WG) has been tasked with providing the GNSO Council with a set of recommendations on the following issues:</span><span style="COLOR: black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="COLOR: black" lang="EN-US"> </span><span style="COLOR: black"><o:p></o:p></span></p>
<p style="TEXT-INDENT: -18pt; MARGIN-LEFT: 36pt; mso-list: l1 level1 lfo2; mso-add-space: auto" class="MsoNormalCxSpMiddle">
<![if !supportLists]><span style="FONT-FAMILY: 'Cambria','serif'; COLOR: black"><span style="mso-list: Ignore">-<span style="FONT: 7pt 'Times New Roman'">
</span></span></span><![endif]><span style="COLOR: black" lang="EN-US">A set of principles that would underpin any GNSO policy implementation related discussions, taking into account existing GNSO procedures;</span><span style="COLOR: black"><o:p></o:p></span></p>
<p style="TEXT-INDENT: -18pt; MARGIN-LEFT: 36pt; mso-list: l1 level1 lfo2; mso-add-space: auto" class="MsoNormalCxSpMiddle">
<![if !supportLists]><span style="FONT-FAMILY: 'Cambria','serif'; COLOR: black"><span style="mso-list: Ignore">-<span style="FONT: 7pt 'Times New Roman'">
</span></span></span><![endif]><span style="COLOR: black" lang="EN-US">A process for developing gTLD policy, perhaps in the form of “Policy Guidance,” including criteria for when it would be appropriate to use such a process (for a process developing something
other than “Consensus Policy”) instead of the GNSO Policy Development Process; </span>
<span style="COLOR: black"><o:p></o:p></span></p>
<p style="TEXT-INDENT: -18pt; MARGIN-LEFT: 36pt; mso-list: l1 level1 lfo2; mso-add-space: auto" class="MsoNormalCxSpMiddle">
<![if !supportLists]><span style="FONT-FAMILY: 'Cambria','serif'; COLOR: black"><span style="mso-list: Ignore">-<span style="FONT: 7pt 'Times New Roman'">
</span></span></span><![endif]><span style="COLOR: black" lang="EN-US">A framework for implementation related discussions associated with GNSO Policy recommendations;</span><span style="COLOR: black"><o:p></o:p></span></p>
<p style="TEXT-INDENT: -18pt; MARGIN-LEFT: 36pt; mso-list: l1 level1 lfo2; mso-add-space: auto" class="MsoNormalCxSpMiddle">
<![if !supportLists]><span style="FONT-FAMILY: 'Cambria','serif'; COLOR: black"><span style="mso-list: Ignore">-<span style="FONT: 7pt 'Times New Roman'">
</span></span></span><![endif]><span style="COLOR: black" lang="EN-US">Criteria to be used to determine when an action should be addressed by a policy process and when it should be considered implementation; and</span><span style="COLOR: black"><o:p></o:p></span></p>
<p style="TEXT-INDENT: -18pt; MARGIN-LEFT: 36pt; mso-list: l1 level1 lfo2; mso-add-space: auto" class="MsoNormalCxSpMiddle">
<![if !supportLists]><span style="FONT-FAMILY: 'Cambria','serif'; COLOR: black"><span style="mso-list: Ignore">-<span style="FONT: 7pt 'Times New Roman'">
</span></span></span><![endif]><span style="COLOR: black" lang="EN-US">Further guidance on how GNSO Implementation Review Teams, as defined in the PDP Manual, are expected to function and operate.</span><span style="COLOR: black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="COLOR: black" lang="EN-US"> </span><span style="COLOR: black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="COLOR: black" lang="EN-US">From the onset of this process, the WG would like to gain input.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="COLOR: black" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="COLOR: black" lang="EN-US">In this regard, the WG would ask organizations to consider and provide input on the following questions which are set out in the WG’s Charter.</span><span style="COLOR: black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="COLOR: black" lang="EN-US"> </span><span style="COLOR: black"><o:p></o:p></span></p>
<ol style="MARGIN-TOP: 0cm" type="1">
<li style="COLOR: black; mso-list: l2 level1 lfo3" class="MsoNormal"><span lang="EN-US">What guidance do the ICANN core values (Bylaws Article 1, Sec. 2) directly provide with regard to policy development work and policy implementation efforts?</span><o:p></o:p>
</li><li style="COLOR: black; mso-list: l2 level1 lfo3" class="MsoNormal"><span lang="EN-US">What guidance do other ICANN core values provide that relate indirectly to policy development and policy implementation?
</span><o:p></o:p></li><li style="COLOR: black; mso-list: l2 level1 lfo3" class="MsoNormal"><span lang="EN-US">“Questions for Discussion” contained in the Policy and Implementation Draft Framework prepared by ICANN staff. (See,
</span><span lang="FR"><a href="http://www.icann.org/en/news/public-comment/policy-implementation-31jan13-en.htm"><span lang="EN-US">http://www.icann.org/en/news/public-comment/policy-implementation-31jan13-en.htm</span></a></span><span lang="EN-US">).</span><o:p></o:p>
</li><li style="COLOR: black; mso-list: l2 level1 lfo3" class="MsoNormal"><span lang="EN-US">What lessons can be learned from past experience?
</span><o:p></o:p>
<ol style="MARGIN-TOP: 0cm" type="a">
<li style="COLOR: black; mso-list: l2 level2 lfo3" class="MsoNormal"><span lang="EN-US">What are the consequences of action being considered “policy” or
<br>
“implementation”?</span><o:p></o:p> </li><li style="COLOR: black; mso-list: l2 level2 lfo3" class="MsoNormal"><span lang="EN-US">Does it matter if something is “policy” or “implementation”?
</span><span lang="FR">If so, why?</span><o:p></o:p> </li><li style="COLOR: black; mso-list: l2 level2 lfo3" class="MsoNormal"><span lang="EN-US">Under what circumstances, if any, should the GNSO Council make recommendations or state positions to the Board on matters of policy and implementation as a representative
of the GNSO as a whole?</span><o:p></o:p> </li><li style="COLOR: black; mso-list: l2 level2 lfo3" class="MsoNormal"><span lang="EN-US">How do we avoid the current morass of outcome-derived labeling (i.e., I will call this “policy” because I want certain consequences or “handling instructions” to be attached
to it?)</span><o:p></o:p> </li><li style="COLOR: black; mso-list: l2 level2 lfo3" class="MsoNormal"><span lang="EN-US">Can we answer these questions so the definitions of “policy” and “implementation” matter less, if at all?</span><o:p></o:p></li></ol>
</li><li style="COLOR: black; mso-list: l2 level1 lfo3" class="MsoNormal"><span lang="EN-US">What options are available for policy (“Consensus Policy” or other) and implementation efforts and what are the criteria for determining which should be used?
</span><o:p></o:p>
<ol style="MARGIN-TOP: 0cm" type="a">
<li style="COLOR: black; mso-list: l2 level2 lfo3" class="MsoNormal"><span lang="EN-US">Are “policy” and “implementation” on a spectrum rather than binary?</span><o:p></o:p>
</li><li style="COLOR: black; mso-list: l2 level2 lfo3" class="MsoNormal"><span lang="EN-US">What are the variations of policy and what consequences should attach to each variation?</span><o:p></o:p>
</li><li style="COLOR: black; mso-list: l2 level2 lfo3" class="MsoNormal"><span lang="EN-US">What happens if you change those consequences?</span><o:p></o:p></li></ol>
</li><li style="COLOR: black; mso-list: l2 level1 lfo3" class="MsoNormal"><span lang="EN-US">Who determines the choice of whether something is “policy” or “implementation”?
</span><o:p></o:p>
<ol style="MARGIN-TOP: 0cm" type="a">
<li style="COLOR: black; mso-list: l2 level2 lfo3" class="MsoNormal"><span lang="EN-US">How is policy set/recommended/adopted and do different paths lead to different variations?</span><o:p></o:p>
</li><li style="COLOR: black; mso-list: l2 level2 lfo3" class="MsoNormal"><span lang="EN-US">How is the “policy” and “implementation” issue reviewed and approved?</span><o:p></o:p>
</li><li style="COLOR: black; mso-list: l2 level2 lfo3" class="MsoNormal"><span lang="EN-US">What happens if reviewing bodies come to a deadlock?</span><o:p></o:p></li></ol>
</li><li style="COLOR: black; mso-list: l2 level1 lfo3" class="MsoNormal"><span lang="EN-US">What is the process by which this identification, analysis, review and approval work is done?
</span><o:p></o:p>
<ol style="MARGIN-TOP: 0cm" type="a">
<li style="COLOR: black; mso-list: l2 level2 lfo3" class="MsoNormal"><span lang="EN-US">How are “policy and implementation” issues first identified (before, during and after implementation)?</span><o:p></o:p>
</li><li style="COLOR: black; mso-list: l2 level2 lfo3" class="MsoNormal"><span lang="EN-US">What is the role of the GNSO in implementation?</span><o:p></o:p>
</li><li style="COLOR: black; mso-list: l2 level2 lfo3" class="MsoNormal"><span lang="EN-US">In order to maintain the multi-stakeholder process, once policy moves to implementation, how should the community be involved in a way that is meaningful and effective?</span><o:p></o:p>
</li><li style="COLOR: black; mso-list: l2 level2 lfo3" class="MsoNormal"><span lang="EN-US">Should policy staff be involved through the implementation process to facilitate continuity of the multi-stakeholder process that already occurred?</span><o:p></o:p></li></ol>
</li></ol>
</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>