<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">Dear Jeff,<br>
<br>
I believe this motion sends a strong signal regarding the role of
the GNSO and will help ensure that the GNSO council will be taken
into account in future policy decisions. I therefore second this
motion. <br>
<br>
Best,<br>
<br>
Volker Greimann<br>
<br>
<br>
</div>
<blockquote
cite="mid:AA2CD321EE9B1F4D99ECFC1A2B0342320C2762@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: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: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.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{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: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="color:#1F497D">All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p style="background:white"><span
style="font-family:"Calibri","sans-serif"">WHEREAS,
the ICANN Bylaws currently state:
</span><span
style="font-family:"Calibri","sans-serif""
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;<o:p></o:p></span></p>
<p style="background:white"><span
style="font-family:"Calibri","sans-serif""
lang="EN">WHEREAS, the Board Governance Committee has
recognized in Reconsideration Request 13-3 that “</span><span
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<o:p></o:p></span></p>
<p style="background:white"><span
style="font-family:"Calibri","sans-serif"">WHEREAS,
the GNSO Council believes that such a defined policy or
process is now needed.<o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:12.0pt"><o:p> </o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:12.0pt">RESOLVED:
The GNSO Council recommends that the ICANN Bylaws be
amended to:<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:12.0pt"><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="text-indent:.5in"><i><span
style="font-size:12.0pt">a) add a second sentence to
Article X, Section 1 such that Section 1 would now read: “</span></i>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></p>
<p class="MsoNormal" style="text-indent:.5in"><i><span
style="font-size:12.0pt"><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="text-indent:.5in"><i><span
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. <o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:12.0pt"><o:p> </o:p></span></i></p>
<p class="MsoNormal"><i><span 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.<o:p></o:p></span></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<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";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:#7D7D7D"><br>
<br>
</span><span
style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<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 class="moz-txt-link-abbreviated" href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a>
[<a class="moz-txt-link-freetext" 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 class="moz-txt-link-abbreviated" 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<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Although I am sure that some on the Council
will still disagree with the new rationale posted at
<a moz-do-not-send="true"
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></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="background:white"><span
style="font-family:"Calibri","sans-serif";color:red">WHEREAS,
the ICANN Bylaws currently state:
</span><span
style="font-family:"Calibri","sans-serif";color:red"
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;<o:p></o:p></span></p>
<p style="background:white"><span
style="font-family:"Calibri","sans-serif";color:red"
lang="EN">WHEREAS, the Board Governance Committee has
recognized in Reconsideration Request 13-3 that “</span><span
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<o:p></o:p></span></p>
<p style="background:white"><span
style="font-family:"Cambria","serif";color:red">WHEREAS,
the GNSO Council believes that such a defined policy or
process is now needed.<o:p></o:p></span></p>
<p class="MsoNormal"><i><span 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.
<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:12.0pt;color:red"><o:p> </o:p></span></i></p>
<p class="MsoNormal"><i><span 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.<o:p></o:p></span></i></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"><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>
<br>
<pre class="moz-signature" cols="72">--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.
</pre>
</body>
</html>