<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>This looks good to me. <br><br>Sent from my iPhone</div><div><br>On Apr 10, 2013, at 11:19 PM, "Neuman, Jeff" <<a href="mailto:Jeff.Neuman@neustar.us">Jeff.Neuman@neustar.us</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><meta name="Generator" content="Microsoft Word 14 (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:0in;
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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]--><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Some revisions: <o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p>The GNSO Council would like to remind the ICANN staff and Board that it is the only entity charged with policy development and providing recommendations to the Board on substantive policies relating to generic top level domains. The GNSO Council recently provided advice in response to a letter from the CEO to the effect that an issue being considered was a matter of policy, rather than implementation. It was Staff’s view that the issue was implementation and not policy, and accordingly it was the Staff’s decision to proceed with implementation of what the majority of the Council believed was policy. It is the Council’s firmly held view that when there is not an agreement on whether or not such an item is policy, as in this case, that the Staff and/or the ICANN Board must refer back to the Council before proceeding further.<o:p></o:p></p><p>Indeed, as a general point, it is the Council’s view that should it provide policy advice to the Staff and/or the Board in the future, then in the event that Staff and/or Board seek to act in a manner that is not consistent with the Council’s advice, then the Staff and/or Board must consult with the GNSO Council, explain the rationale behind its decision, and allow the Council, at a minimum, to respond to the Staff or Board’s decision.<o:p></o:p></p><p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0in;margin-bottom:12.0pt;margin-left:0in"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D">Jeffrey J. Neuman</span></b><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#3366FF"> <br></span></b><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#068658">Neustar, Inc. / Vice President, Business Affairs</span></b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span 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>Jonathan Robinson<br><b>Sent:</b> Wednesday, April 10, 2013 6:54 PM<br><b>To:</b> GNSO Council List<br><b>Subject:</b> [council] Draft Statement for Public Forum<o:p></o:p></span></p><p class="MsoNormal"><o:p> </o:p></p><p>Draft Statement for Public Forum:<o:p></o:p></p><p>The GNSO Council recently provided advice in response to a letter from the CEO to the effect that an issue being considered was a matter of policy, rather than implementation. It was Staff’s view that the issue was implementation and not policy, and accordingly it was the Staff’s decision to proceed with the first steps of implementation. It is the Council’s firmly held view that when there is not an agreement on whether or not such an item is policy, as in this case, that the Staff must refer back to the Council before proceeding further.<o:p></o:p></p><p>Indeed, as a general point, it is the Council’s view that should it provide policy advice to the Staff and/or the Board in the future, then in the event that Staff and/or Board seek to act adverse to the Council’s advice, they should certainly not do so without further reference back to the Council.<o:p></o:p></p></div></div></blockquote></body></html>