<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<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:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Cambria;
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;
line-height:normal;
font-size:11.0pt;
font-family:"Calibri","sans-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
{mso-style-priority:99;
margin-top:0cm;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:0cm;
line-height:17.4pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
line-height:normal;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";}
span.estilocorreo18
{mso-style-name:estilocorreo18;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.estilocorreo19
{mso-style-name:estilocorreo19;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.estilocorreo20
{mso-style-name:estilocorreo20;
font-family:"Arial","sans-serif";
color:navy;}
p.BalloonText, li.BalloonText, div.BalloonText
{mso-style-name:"Balloon Text";
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
line-height:normal;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle26
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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=FR link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>The motion has been posted on the Wiki page at :<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><a href="https://community.icann.org/display/gnsocouncilmeetings/Motions+17+July+2013">https://community.icann.org/display/gnsocouncilmeetings/Motions+17+July+2013</a><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Thank you.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Kind regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Glen<o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></a></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De :</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Neuman, Jeff [mailto:Jeff.Neuman@neustar.us] <br><b>Envoyé :</b> vendredi 28 juin 2013 20:39<br><b>À :</b> 'Novoa, Osvaldo'; GNSO Council (council@gnso.icann.org)<br><b>Cc :</b> Glen de Saint Géry<br><b>Objet :</b> RE: Revised Motion on ICANN Bylaw Recoomendation<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Understood, which is why I sent this in several weeks early.</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p><div><p class=MsoNormal style='margin-top:6.0pt;mso-margin-bottom-alt:auto'><b><span lang=EN-US style='font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Jeffrey J. Neuman</span></b><b><span lang=EN-US style='font-size:9.0pt;font-family:"Arial","sans-serif";color:#3366FF'> <br></span></b><b><span lang=EN-US style='font-size:9.0pt;font-family:"Arial","sans-serif";color:#068658'>Neustar, Inc. / Vice President, Business Affairs</span></b><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D'><br><br><br></span><span lang=EN-US><o:p></o:p></span></p></div><p class=MsoNormal><span lang=EN-US style='color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Novoa, Osvaldo [<a href="mailto:onovoa@Antel.com.uy">mailto:onovoa@Antel.com.uy</a>] <br><b>Sent:</b> Friday, June 28, 2013 10:02 AM<br><b>To:</b> Neuman, Jeff; GNSO Council (<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>)<br><b>Cc:</b> 'Glen de Saint Géry'<br><b>Subject:</b> RE: Revised Motion on ICANN Bylaw Recoomendation</span><span lang=EN-US><o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Jeff,</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Even though I agree with you that it looks like a small change in the Bylaws that just clarifies a process that should have been there, any change in the Bylaws is important and should be analyze thoroughly. Also I need the opinion of my constituency and for that we have to discussed this internally. This said, I hope to have a position by Durban, if not I will be forced to ask for a deferral.</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Best regards,<br>Osvaldo</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'> </span><span lang=EN-US><o:p></o:p></span></p><div><div class=MsoNormal align=center style='text-align:center'><span lang=ES style='font-size:12.0pt;font-family:"Times New Roman","serif"'><hr size=2 width="100%" align=center></span></div><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"'> <a href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a> [<a href="mailto:owner-council@gnso.icann.org">mailto:owner-council@gnso.icann.org</a>] <b>En nombre de </b>Neuman, Jeff<br><b>Enviado el:</b> Viernes, 28 de Junio de 2013 09:46<br><b>Para:</b> Neuman, Jeff; GNSO Council (<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>)<br><b>CC:</b> 'Glen de Saint Géry'<br><b>Asunto:</b> [council] Revised Motion on ICANN Bylaw Recoomendation</span><span lang=EN-US><o:p></o:p></span></p></div><p class=MsoNormal><span lang=ES> </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>All,</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Overnight I got some fantastic comments from several people about the motion, so I have made a couple of changes. Here is the new motion, with the changed parts in red. Basically I added a second sentence to the definition of the GNSO recognizing the role that the GNSO has with respect to providing advice on implementation of policies relating to generic TLDs. What that process is and how to delineate whether something is policy or implementation is being worked on by the Policy v. implementation Working Group we have set up, but as the BGC recognizes, the Board should be coming to the GNSO community for advice on implementation issues as well as policy issues. </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Again, to be clear, all this is saying is that IF the GNSO issues advice AND the Board acts inconsistent with that advice, the only thing the Board should do is meet with the GNSO in good faith, offer its reasons, and attempt to work out a solution. That’s it. Seems like a no-brainer to me.</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p><p style='background:white'><span lang=EN-US style='font-family:"Calibri","sans-serif"'>WHEREAS, the ICANN Bylaws currently state: </span><span lang=EN style='font-family:"Calibri","sans-serif"'>There shall be a policy-development body known as the Generic Names Supporting Organization (GNSO), which shall be responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains;</span><span lang=EN-US><o:p></o:p></span></p><p style='background:white'><span lang=EN style='font-family:"Calibri","sans-serif"'>WHEREAS, the Board Governance Committee has recognized in Reconsideration Request 13-3 that “</span><span lang=EN-US style='font-family:"Calibri","sans-serif"'>As of now, there is <i>no defined policy or process within ICANN </i>that requires Board or staff consultation with the GNSO Council if the Board or staff is acting in contravention to a statement made by the GNSO Council outside of the PDP”; and</span><span lang=EN-US><o:p></o:p></span></p><p style='background:white'><span lang=EN-US style='font-family:"Calibri","sans-serif"'>WHEREAS, the GNSO Council believes that such a defined policy or process is now needed.</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><i><span lang=EN-US style='font-size:12.0pt'> </span></i><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><i><span lang=EN-US style='font-size:12.0pt'>RESOLVED: The GNSO Council recommends that the ICANN Bylaws be amended to:</span></i><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><i><span lang=EN-US style='font-size:12.0pt'> </span></i><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal style='text-indent:36.0pt'><i><span lang=EN-US style='font-size:12.0pt'>a) add a second sentence to Article X, Section 1 such that Section 1 would now read: “</span></i><span lang=EN-US>There shall be a policy-development body known as the Generic Names Supporting Organization (GNSO), which shall be responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains. <span style='color:red'>The GNSO is also responsible for providing advice to the ICANN Board on the implementation of policies relating to generic top-level domains.”</span><o:p></o:p></span></p><p class=MsoNormal style='text-indent:36.0pt'><i><span lang=EN-US style='font-size:12.0pt'> </span></i><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal style='text-indent:36.0pt'><i><span lang=EN-US style='font-size:12.0pt'>b) include language requiring a formal consultation process in the event that the ICANN Board determines to take an action that is not consistent with GNSO <span style='color:red'>advice</span>. Such process shall require the ICANN Board to state the reasons why it decided not to follow GNSO <span style='color:red'>advice</span>, and be followed in a timely manner, with a consultation in which the GNSO and the ICANN Board attempt in good faith to find a mutually acceptable solution. If no such solution can be found, the ICANN Board will state in its final decision the reasons why the GNSO <span style='color:red'>advice was </span>not followed. </span></i><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><i><span lang=EN-US style='font-size:12.0pt'> </span></i><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><i><span lang=EN-US style='font-size:12.0pt'>FURTHER RESOLVED that the GNSO recommends the above to apply whether or not the policy development process as set forth in Article X, section 6 were followed.</span></i><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p><div><p class=MsoNormal style='margin-top:6.0pt'><b><span lang=EN-US style='font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Jeffrey J. Neuman</span></b><b><span lang=EN-US style='font-size:9.0pt;font-family:"Arial","sans-serif";color:#3366FF'> <br></span></b><b><span lang=EN-US style='font-size:9.0pt;font-family:"Arial","sans-serif";color:#068658'>Neustar, Inc. / Vice President, Business Affairs</span></b><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D'><br><br><br><br><br></span><span lang=EN-US><o:p></o:p></span></p></div><p class=MsoNormal><span lang=EN-US style='color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a> [<a href="mailto:owner-council@gnso.icann.org">mailto:owner-council@gnso.icann.org</a>] <b>On Behalf Of </b>Neuman, Jeff<br><b>Sent:</b> Thursday, June 27, 2013 10:44 PM<br><b>To:</b> GNSO Council (<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>)<br><b>Cc:</b> 'Glen de Saint Géry'<br><b>Subject:</b> [council] Revised Rationale for Rejection of NCSG Reconsideration Request & Proposed Motion for Durban Council Meeting</span><span lang=EN-US><o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Although I am sure that some on the Council will still disagree with the new rationale posted at <a href="http://www.icann.org/en/groups/board/governance/reconsideration/recommendation-ncsg-25jun13-en.pdf">http://www.icann.org/en/groups/board/governance/reconsideration/recommendation-ncsg-25jun13-en.pdf</a>, I believe the rationale is much more consistent with, and recognizes, the value of the multi-stakeholder model. The tone has been softened considerably and is much more respectful, in my opinion. In addition, the rationale upon my quick read seems to be technically correct. I am grateful to the Board Governance Committee for having taken some of our comments very seriously and for making the appropriate changes to the rationale.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>The one item I would still like to see addressed by the Council (other than the Policy v. Implementation discussions within the GNSO Working Group process) is formalizing the requirement through a proposed Bylaws Amendment requiring consultation of the GNSO if the Board proposes to take an action that is inconsistent with a policy or statement of the GNSO. I intend to draft that motion for the Council’s consideration in Durban.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>To give all of the constituencies ample time to review the motion prior to Durban, although I am sure some will seek to defer the motion, claiming insufficient time to review, I am attaching this proposed resolution for consideration in Durban. I am happy to take comments, edits or suggestions:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p style='background:white'><span lang=EN-US style='font-family:"Calibri","sans-serif";color:red'>WHEREAS, the ICANN Bylaws currently state: </span><span lang=EN style='font-family:"Calibri","sans-serif";color:red'>There shall be a policy-development body known as the Generic Names Supporting Organization (GNSO), which shall be responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains;</span><span lang=EN-US><o:p></o:p></span></p><p style='background:white'><span lang=EN style='font-family:"Calibri","sans-serif";color:red'>WHEREAS, the Board Governance Committee has recognized in Reconsideration Request 13-3 that “</span><span lang=EN-US style='font-family:"Cambria","serif";color:red'>As of now, there is <i>no defined policy or process within ICANN </i>that requires Board or staff consultation with the GNSO Council if the Board or staff is acting in contravention to a statement made by the GNSO Council outside of the PDP”; and</span><span lang=EN-US><o:p></o:p></span></p><p style='background:white'><span lang=EN-US style='font-family:"Cambria","serif";color:red'>WHEREAS, the GNSO Council believes that such a defined policy or process is now needed.</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><i><span lang=EN-US style='font-size:12.0pt;color:red'>RESOLVED: The GNSO Council recommends that the ICANN Bylaws be amended to include language requiring a formal consultation process in the event that the ICANN Board determines to take an action that is not consistent with GNSO policies or recommendations. Such process shall require the ICANN Board to state the reasons why it decided not to follow GNSO recommendations or policies, and be followed in a timely manner, with a consultation in which the GNSO and the ICANN Board attempt in good faith to find a mutually acceptable solution. If no such solution can be found, the ICANN Board will state in its final decision the reasons why the GNSO recommendations or policies were not followed. </span></i><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><i><span lang=EN-US style='font-size:12.0pt;color:red'> </span></i><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><i><span lang=EN-US style='font-size:12.0pt;color:red'>FURTHER RESOLVED that the GNSO recommends the above to apply whether or not the policy development process as set forth in Article X, section 6 were followed.</span></i><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='margin-top:6.0pt'><b><span lang=EN-US style='font-size:9.0pt;font-family:"Arial","sans-serif"'>Jeffrey J. Neuman<span style='color:#3366FF'> <br></span><span style='color:#068658'>Neustar, Inc. / Vice President, Business Affairs</span></span></b><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D'><br>46000 Center Oak Plaza, Sterling, VA 20166</span><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:gray'><br></span><b><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658'>Office:</span></b><b><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#333333'> </span></b><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D'>+1.571.434.5772</span><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#000066'> </span><b><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658'>Mobile: </span></b><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D'>+1.202.549.5079</span><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:gray'> </span><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#000066'> </span><b><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658'>Fax: </span></b><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D'>+1.703.738.7965</span><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:gray'> </span><b><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658'>/</span></b><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#3366FF'> </span><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658'><a href="mailto:jeff.neuman@neustar.biz"><span style='color:#068658'>jeff.neuman@neustar.biz</span></a> </span><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:gray'> </span><b><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658'>/</span></b><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#3366FF'> </span><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658'><a href="http://www.neustar.biz/"><span style='color:#068658'>www.neustar.biz</span></a></span><span lang=EN-US style='font-size:8.5pt;font-family:"Arial","sans-serif";color:gray'> </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal><span lang=ES style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><span lang=EN-US><o:p></o:p></span></p><div class=MsoNormal align=center style='text-align:center'><span lang=ES style='font-size:12.0pt;font-family:"Times New Roman","serif"'><hr size=2 width="100%" align=center></span></div><p class=MsoNormal><span lang=ES style='font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'>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.</span><span lang=EN-US><o:p></o:p></span></p></div></body></html>