<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">I would also support such a motion. The
suggested language keeps the door for alternative processes open
while shutting the door for a complete bypass without
accountability.<br>
<br>
Best,<br>
<br>
Volker<br>
<br>
</div>
<blockquote
cite="mid:AA2CD321EE9B1F4D99ECFC1A2B03423208C796@stntexmb12.cis.neustar.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:0in;
line-height:17.4pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.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">All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In the rationale used in the BGC’s
recommendation against the NCSG’s Reconsideration Request, the
BGC argues that:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">“There is no defined policy process within
ICANN 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 Policy
Development Process. Therefore, even if staff’s action here
was in direct contravention to the GNSO Council statement in a
letter, the Bylaws requirement for consultation does not
apply…”<br>
<br>
Technically and legally, the BGC is correct. As much as this
goes against the very nature of the multi-stakeholder model
(and frankly the message ICANN delivers to the world), the
ICANN Board/staff is free to ignore the GNSO Council (and thus
has no accountability for these actions). This is true
despite the fact that the Bylaws also state: “<span lang="EN">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.” Therefore, what the BGC is telling us is that
despite the fact that the Bylaws charges the GNSO with
developing and recommending substantive policies, it can
ignore the GNSO community at any time if the issue did not
go through a formal PDP.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN">I personally believe that
is broken. Therefore, I would like for the Council to
consider recommending to the ICANN Board a change to the
Bylaws for an additional measure of accountability that at a
minimum would require some form of consultation if the GNSO
Council (on behalf of the GNSO Community) issues a
recommendation or develops policy outside of a formal PDP.
As the former chair of the PDP Working Group that helped
revise the PDP process, I can tell you that we were
encouraged by the community to allow other mechanisms for
developing policy outside of formal PDPs. We spent
countless hours on this very topic. Yes, if it does not go
through a formal PDP, it may not trigger a 2/3 Board vote to
overturn the recommendation, but it was never our intention
that after going through that process, the Board to IGNORE
the GNSO Community. At a time when the community is trying
to find ways to develop policies outside of the stringent
PDP, this is NOT an incentive for doing that.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN"><br>
Therefore, I would like to see the following changes made to
the Bylaws (no pride in authorship here…so feel free to
suggest other words). This is language that is VERY similar
to the language the GAC has in the Bylaws:<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.5pt;font-family:"Arial","sans-serif";color:#555555"
lang="EN"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="background:white"><i><span
style="font-size:11.5pt;font-family:"Arial","sans-serif";color:#555555"
lang="EN">The substantive policies and recommendations of
the Generic Names Supporting Organization relating to
generic top-level domains shall be duly taken into
account, both in the formulation and adoption of policies,
whether or not the policy development process as set forth
in Article X, section 6 were followed. In the event that
the ICANN Board determines to take an action that is not
consistent with the GNSO policies or recommendations, it
shall so inform the GNSO and state the reasons why it
decided not to follow that advice. The GNSO and the ICANN
Board will then try, in good faith and in a timely and
efficient manner, to find a mutually acceptable solution.<a
moz-do-not-send="true" name="XI-2.1k"></a> 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.<o:p></o:p></span></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If the multi-stakeholder model truly has
any meaning, I view these changes as non-controversial and
essential to preserve what so many have so long been
advocating.<o:p></o:p></p>
<p class="MsoNormal"><br>
Thanks.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"
style="margin-top:6.0pt;mso-margin-bottom-alt:auto"><b><span
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
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D"><br>
46000 Center Oak Plaza, Sterling, VA 20166</span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray"><br>
</span><b><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">Office:</span></b><b><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#333333">
</span></b><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D">+1.571.434.5772</span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#000066">
</span><b><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">Mobile:
</span></b><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D">+1.202.549.5079</span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray">
</span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#000066"> </span><b><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">Fax:
</span></b><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D">+1.703.738.7965</span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray">
</span><b><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">/</span></b><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#3366FF">
</span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658"><a
moz-do-not-send="true"
href="mailto:jeff.neuman@neustar.biz"><span
style="color:#068658">jeff.neuman@neustar.biz</span></a>
</span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray"> </span><b><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">/</span></b><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#3366FF">
</span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658"><a
moz-do-not-send="true" href="http://www.neustar.biz/"><span
style="color:#068658">www.neustar.biz</span></a></span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray">
<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<br>
</body>
</html>