<!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><TITLE>Re: [council] Draft Revisions to the ICANN Bylaws Relating to GNSO Restructure</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16809" name=GENERATOR>
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Book Antiqua;
}
@font-face {
font-family: Verdana;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
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 {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 34
}
LI.MsoListParagraph {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 34
}
DIV.MsoListParagraph {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 34
}
SPAN.EmailStyle17 {
FONT-WEIGHT: normal; COLOR: #1f497d; FONT-STYLE: normal; FONT-FAMILY: "Book Antiqua","serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
OL {
MARGIN-BOTTOM: 0in
}
UL {
MARGIN-BOTTOM: 0in
}
</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-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=623580100-30032009><FONT face=Arial
color=#0000ff size=2>Jeff,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=623580100-30032009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=623580100-30032009><FONT face=Arial
color=#0000ff size=2>Note that the Bylaws changes are supposed to only relate to
the restructure of the Council to the new bicameral model and not to the broader
GNSO improvements effort for which implementation plans are being developed
by the work teams. It is true that the revised PDP will be a Bylaws
issue but I don't believe that is included in this draft of Bylaws
changes. The goal of this limited effort is to make sure that any Bylaws
changes are in place before the Council moves to the bicameral
model.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=623580100-30032009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=623580100-30032009><FONT face=Arial
color=#0000ff size=2>Chuck</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Neuman, Jeff
[mailto:Jeff.Neuman@neustar.us] <BR><B>Sent:</B> Sunday, March 29, 2009 6:30
PM<BR><B>To:</B> Gomes, Chuck; ken.bour@verizon.net;
stephane.vangelder@indom.com; Margie.Milam@icann.org; council@gnso.icann.org;
liaison6c@gnso.icann.org<BR><B>Subject:</B> Re: [liaison6c] RE: [council]
Draft Revisions to the ICANN Bylaws Relating to GNSO
Restructure<BR></FONT><BR></DIV>
<DIV></DIV>
<P><FONT face=Arial color=navy size=2>Speaking not as a councilor, but as one
who is still on these lists. There are many questions still being addressed by
the 5 work teams which seem to be (perhaps unintentionally) superseded by
Staff's work. As the chair of one of the work teams, one of our agenda items
to discuss within the team (notice I did not say council) what parts should be
in the bylaws and what should be in rules of operation. Again that is
dependent as Chuck said on how the rules of operation can be changed.<BR><BR>I
want to thank Staff for this work, but I fear this will be a distraction as
opposed to an aid for the community in doing the work of the 5 work teams. I
again thank staff for doing some of this work, but I am afraid much of it was
too premature. It is the community that needs to figure out how this will
work, not the staff.<BR><BR>Thanks. <BR>Jeffrey J. Neuman, Esq. <BR>Vice
President, Law & Policy <BR>NeuStar, Inc. <BR>Jeff.Neuman@neustar.biz
<BR><BR></FONT></P>
<P>
<HR tabIndex=-1 align=center width="100%" SIZE=2>
<FONT face=Tahoma size=2><B>From</B>: owner-liaison6c@gnso.icann.org
<OWNER-LIAISON6C@GNSO.ICANN.ORG><BR><B>To</B>: Ken Bour
<KEN.BOUR@VERIZON.NET>; Stéphane Van Gelder <STEPHANE.VANGELDER@INDOM.COM>;
Margie Milam <MARGIE.MILAM@ICANN.ORG>; council@gnso.icann.org
<COUNCIL@GNSO.ICANN.ORG>; liaison6c@gnso.icann.org
<LIAISON6C@GNSO.ICANN.ORG><BR><B>Sent</B>: Sun Mar 29 17:28:39
2009<BR><B>Subject</B>: [liaison6c] RE: [council] Draft Revisions to the ICANN
Bylaws Relating to GNSO Restructure <BR></FONT>
<P></P>
<DIV dir=ltr align=left><SPAN class=043241821-29032009><FONT face=Arial
color=#0000ff size=2>I support the suggestion to move voting thresholds to the
Rules but with a condition in the Rules that any changes to the
thresholds requires a high voting bar (at least 60% of both houses) and that
the Bylaws require Board approval of the Rules and any amendments to the
Rules. In my opinion, the consensus reached on GNSO restructure was
highly dependent on the interdependency of several elements of the restructure
recommendations. In particular, the recommended thresholds were a very
crucial part of the overall package that we agreed to, so if it is too easy to
change those, it could compromise the whole set of
recommendations.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=043241821-29032009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=043241821-29032009><FONT face=Arial
color=#0000ff size=2>I do not agree that this document is almost ready.
I think we have quite a bit of work to do still and this is much too important
to rush. I am all for doing it quickly, but let's make sure we carefully
deal with all the issues that are being identified. In that regard, I
think it would be helpful if Staff prepared a document organized similar to
what they have already done that integrates all the various comments including
their source with each section.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=043241821-29032009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=043241821-29032009><FONT face=Arial
color=#0000ff size=2>Chuck</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> owner-council@gnso.icann.org
[mailto:owner-council@gnso.icann.org] <B>On Behalf Of </B>Ken
Bour<BR><B>Sent:</B> Friday, March 27, 2009 2:59 PM<BR><B>To:</B> 'Stéphane
Van Gelder'; 'Margie Milam'; council@gnso.icann.org;
liaison6c@gnso.icann.org<BR><B>Subject:</B> [council] Draft Revisions to the
ICANN Bylaws Relating to GNSO Restructure<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">Stéphane:
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">Thank you for
your prompt initiative and the supportive observations. Please see my
embedded comments below.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">If there are any
other questions, please continue to raise them. In the interest
of time, we recognize and appreciate the Council’s active interest and
remain committed to timely and thorough replies.
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">Ken
Bour<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">
owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org] <B>On
Behalf Of </B>Stéphane Van Gelder<BR><B>Sent:</B> Friday, March 27, 2009
1:05 PM<BR><B>To:</B> Margie Milam; council@gnso.icann.org;
liaison6c@gnso.icann.org<BR><B>Subject:</B> Re: [council] Draft Revisions to
the ICANN Bylaws Relating to GNSO
Restructure<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'">Margie,<BR><BR>Thanks
for sending these on. As we are so pushed for time, allow me to get the ball
rolling on this discussion and make a few comments.<BR><BR>Section 3.
Article 1.<BR>Moving the “geographic regions goalposts” up from “no 2
members” to “no 3 members” seems like a sensible suggestion for those SGs
with 6 Council members. I agree with it.<SPAN
style="COLOR: #1f497d"><o:p></o:p></SPAN></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">[KAB: ] Staff
appreciates your support of this provision. </SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR><BR>Section
3. Article 3.<BR>What’s your rationale for recommending that “vacancy rules”
be moved to OR&Ps?<SPAN
style="COLOR: #1f497d"><o:p></o:p></SPAN></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">[KAB: ] The only
specific provision, in this section, deals with the removal of an NCA for
cause and includes the actual voting thresholds. One of Staff’s
sub-objectives in this re-drafting assignment was to eliminate any/all
provisions that, in its judgment, could be more effectively accommodated
within internal Council procedures. One area identified was
detailed voting thresholds and another involved this topic of vacancies,
removals, and resignations. Staff suggests that such provisions
do not rise to the level of being required in ICANN-level legal
Bylaws. In the event that new Council voting thresholds are
added or modified, in the future, such changes could be accomplished locally
versus requiring protracted formal Bylaws amendments. Similarly,
procedures for handling Council vacancies, resignations, and other
administrative matters seem more appropriate for OR&P vs. corporate
Bylaws. </SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR><BR>Section
3. Article 7.<BR>Are there no voting thresholds for selecting the chair and
vice-chairs?<SPAN style="COLOR: #1f497d"><o:p></o:p></SPAN></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">[KAB: ] Yes,
there are bicameral house voting thresholds for these positions and, as
discussed above, they will be prescribed in the Council’s OR&P currently
under revision by the GNSO Operations Work Team (Ray Fassett, Chair) under
the auspices of the Operations Steering Committee (OSC). The
Council Chair election requires 60% of both houses and the Vice-Chair
positions are prescribed in the following language, inserted below:
<o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">“The GNSO
Council shall also select two Vice Chairs, one elected from each of the two
voting houses. If the Council Chair is elected from one of the
houses, then the non-voting Council-Level Nominating Committee Appointee
shall serve as one of the Vice Chairs in lieu of the Vice Chair from the
house of the elected Chair. If the Chair is elected from one of
the houses, that person shall retain his/her vote in that house.”
<o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'">Section 3.
Article 8.<BR>I agree the voting threshold descriptions belong in the
OR&Ps, but it would be helpful for our discussion of the bylaws to have
a reminder of what they are. Can you provide a link to where they are
please?<SPAN style="COLOR: #1f497d"><o:p></o:p></SPAN></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">[KAB: ] The
voting thresholds originally prescribed by the Working Group on GNSO Council
Restructuring (WG-GCR) contained both PDP and non-PDP elements.
In this re-drafting exercise, Staff is recommending that they be parsed out
as follows: the non-PDP voting thresholds will be contained in Council
OR&P while the PDP thresholds will be included in Article XX–Transition
until such time as the Policy Process Steering Committee (PPSC) and PDP Work
Team (Jeff Neumann, Chair) have completed deliberations and are prepared to
recommend a formal revision to Annex A of the Bylaws. Since the
PDP thresholds are currently specified in Annex A, which is not being
revised as part of this restructuring effort, Staff recommends that the new
PDP thresholds should be included in Article XX vs. Council
OR&P. Article XX is a “transition” document only and, once
the PDP voting thresholds are successfully relocated from Annex A to the
Council OR&P (Staff’s recommendation), Article XX can be removed from
the Bylaws in its entirety (assuming all other transition matters are
completed). Below are the voting thresholds recast into
the two groupings: <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">
<B><U>Non-PDP: <o:p></o:p></U></B></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in; mso-list: l4 level1 lfo3"><![if !supportLists]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'"><SPAN
style="mso-list: Ignore">a)<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">Elect Council
Chair: requires 60% of both houses. <o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in; mso-list: l4 level1 lfo3"><![if !supportLists]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'"><SPAN
style="mso-list: Ignore">b)<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">Remove NCA for
Cause: requires 75% of both houses (excluding the NCA subject to
removal); subject to Board approval.<o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in; mso-list: l4 level1 lfo3"><![if !supportLists]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'"><SPAN
style="mso-list: Ignore">c)<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">All other GNSO
Council Business (default): requires majority of both houses.
<o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 6pt"><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">
<o:p></o:p></SPAN></P>
<P class=MsoNormal style="TEXT-INDENT: 0.5in"><B><U><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">PDP:<o:p></o:p></SPAN></U></B></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 54.2pt; TEXT-INDENT: -0.25in; mso-list: l2 level1 lfo4"><![if !supportLists]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'"><SPAN
style="mso-list: Ignore">a)<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">Create an Issues
Report: requires more than 25% vote of both houses or majority of one
house. <o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 54.2pt; TEXT-INDENT: -0.25in; mso-list: l2 level1 lfo4"><![if !supportLists]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'"><SPAN
style="mso-list: Ignore">b)<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">Initiate a PDP
within Scope: requires more than 33% vote of both houses or more than
66% vote of one house. <o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 54.2pt; TEXT-INDENT: -0.25in; mso-list: l2 level1 lfo4"><![if !supportLists]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'"><SPAN
style="mso-list: Ignore">c)<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">Initiate a PDP
not within Scope: requires a vote of more than 75% of one house and a
majority of the other house (“Super Majority”). <o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 54.2pt; TEXT-INDENT: -0.25in; mso-list: l2 level1 lfo4"><![if !supportLists]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'"><SPAN
style="mso-list: Ignore">d)<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">Approve a PDP
without a Super Majority: requires a majority of both houses and
further requires that one representative of at least 3 of the 4 Stakeholder
Groups supports. <o:p></o:p></SPAN></P>
<P class=MsoListParagraph
style="MARGIN-LEFT: 54.2pt; TEXT-INDENT: -0.25in; mso-list: l2 level1 lfo4"><![if !supportLists]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'"><SPAN
style="mso-list: Ignore">e)<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">Approve a PDP
with a Super Majority: requires greater than 75% majority in one house
and majority in the other house.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'">Apart from the
points raised above, I think this document is already very near completion.
Having seen it, I must admit I feel a lot more confident that we can move
ahead with sufficient speed to meet the deadlines set in your email for our
review of these proposed bylaws. Congratulations on a well-written
document.<SPAN style="COLOR: #1f497d"><o:p></o:p></SPAN></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'"> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">[KAB: ] Staff
appreciates the compliment and the vote of confidence toward a successful
June Council seating. Thank you! <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR><BR>Stéphane<BR><BR><BR>Le
27/03/09 00:34, « Margie Milam » <<A
href="Margie.Milam@icann.org">Margie.Milam@icann.org</A>> a
écrit :</SPAN><o:p></o:p></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Dear
All,<BR> <BR>As discussed in today’s GNSO call, ICANN Staff
has prepared Draft Bylaws Revisions (attached) that contain Staff
recommendations for changes relating to the GNSO restructure.
They are intended to serve as a starting point for the GNSO
Council’s discussions. <BR> <BR><U>General
Observations<BR></U><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: Symbol">· </SPAN><SPAN
style="FONT-SIZE: 11pt"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">These Bylaws were
drafted to be consistent with Board recommendations as to structure and
principles.<BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: Symbol">· </SPAN><SPAN
style="FONT-SIZE: 11pt"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Staff also
attempted to build in flexibility to accommodate changes in the future
without requiring Bylaws amendments. For example, Staff recommends
that some issues be moved from the Bylaws to GNSO Council Operating Rules
and Procedures that would be approved by the Board.<BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: Symbol">· </SPAN><SPAN
style="FONT-SIZE: 11pt"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Since the Board
approved improvements did not provide specific details with respect to all
topics, ICANN staff developed recommendations to address these gaps, which
are contained in footnotes throughout the document.<BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: Symbol">· </SPAN><SPAN
style="FONT-SIZE: 11pt"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">The Draft Bylaws
Revisions are subject to review by the ICANN Office of the General Counsel
for legal form as well as consistency. <BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: Symbol">· </SPAN><SPAN
style="FONT-SIZE: 11pt"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">A few additional
decisions will be needed to finalize these Bylaws, for example, Board
approval of the unresolved open issue concerning Board seats 13 and 14, and
further Council work on certain of the transition procedures (e.g. staggered
terms, elections). <BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><U><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Format of
Revisions<BR> <BR></SPAN></U><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: Symbol">· </SPAN><SPAN
style="FONT-SIZE: 11pt"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">To facilitate
reviewing these changes, the Draft Bylaws is organized as a side-by-side
comparison of the current language and the proposed
language.<BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: Symbol">· </SPAN><SPAN
style="FONT-SIZE: 11pt"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">The yellow
highlighted text refers to new or substantially revised language compared to
the current Bylaws.<BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: Symbol">· </SPAN><SPAN
style="FONT-SIZE: 11pt"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">The footnotes
include rationale statements where Staff thought an explanation might
be helpful. <BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"><BR><U>Next Steps
and Timing<BR> <BR></U></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: Symbol">· </SPAN><SPAN
style="FONT-SIZE: 11pt"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">The GNSO Council
will need to decide how it would like to review the Draft Bylaws to develop
its recommendations.<BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: Symbol">· </SPAN><SPAN
style="FONT-SIZE: 11pt"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">ICANN Staff will
be working with the GNSO Operations Work Team in developing the GNSO
Operating Rules and Procedures to incorporate those improvements that were
omitted from the Bylaws in order to provide flexibility.<BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: Symbol">· </SPAN><SPAN
style="FONT-SIZE: 11pt"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">In order to seat
the new Council by June, the Board would need to approve of the
revisions by no later than its May 21st meeting.<BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: Symbol">· </SPAN><SPAN
style="FONT-SIZE: 11pt"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">A public comment
period would need to take place before the May 21st meeting.<BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: Symbol">· </SPAN><SPAN
style="FONT-SIZE: 11pt"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">The Council would
need to complete its review/analysis by the next GNSO council meeting on
April 16th in order to accommodate the public comment
period.<BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: Symbol">· </SPAN><SPAN
style="FONT-SIZE: 11pt"> </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Due to this short
time period, the GNSO Council is currently evaluating the most effective way
to proceed. <BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Finally, ICANN
Staff is available to provide background and additional information on the
Draft Bylaws Revisions if it would be helpful for your
review.<BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Regards,<BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Margie
Milam<BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">Senior Policy
Counselor<BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'">ICANN
<BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR></SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Arial','sans-serif'"><BR> <BR> <BR> </SPAN><o:p></o:p></P></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>