<!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:x =
"urn:schemas-microsoft-com:office:excel" xmlns:p =
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =
"urn:schemas-microsoft-com:office:access" xmlns:dt =
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =
"urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b =
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =
"urn:schemas-microsoft-com:office:odc" xmlns:oa =
"urn:schemas-microsoft-com:office:activation" xmlns:html =
"http://www.w3.org/TR/REC-html40" xmlns:q =
"http://schemas.xmlsoap.org/soap/envelope/" XMLNS:D = "DAV:" xmlns:mt =
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 =
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois =
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =
"http://schemas.microsoft.com/data/udc" xmlns:xsd =
"http://www.w3.org/2001/XMLSchema" xmlns:sub =
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp =
"http://schemas.microsoft.com/sharepoint/" xmlns:sps =
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs =
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf =
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p =
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver =
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp =
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl =
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService"
XMLNS:Z = "urn:schemas-microsoft-com:" xmlns:st = ""><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><!--[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-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Verdana;
}
@font-face {
font-family: Book Antiqua;
}
@page {mso-endnote-separator: url("cid:header.htm\@01C9B11C.B25F9920") es; mso-endnote-continuation-separator: url("cid:header.htm\@01C9B11C.B25F9920") ecs; }
@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"
}
P.MsoFootnoteText {
FONT-SIZE: 10pt; MARGIN: 0in 0in 10pt; LINE-HEIGHT: 115%; FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority: 99; mso-style-link: "Footnote Text Char"
}
LI.MsoFootnoteText {
FONT-SIZE: 10pt; MARGIN: 0in 0in 10pt; LINE-HEIGHT: 115%; FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority: 99; mso-style-link: "Footnote Text Char"
}
DIV.MsoFootnoteText {
FONT-SIZE: 10pt; MARGIN: 0in 0in 10pt; LINE-HEIGHT: 115%; FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority: 99; mso-style-link: "Footnote Text Char"
}
SPAN.MsoFootnoteReference {
VERTICAL-ALIGN: super; mso-style-priority: 99
}
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 {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 99; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
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.FootnoteTextChar {
FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority: 99; mso-style-link: "Footnote Text"; mso-style-name: "Footnote Text Char"
}
SPAN.EmailStyle22 {
FONT-WEIGHT: normal; COLOR: #1f497d; FONT-STYLE: normal; FONT-FAMILY: "Book Antiqua","serif"; mso-style-type: personal
}
SPAN.EmailStyle23 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle24 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
</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=182595413-30032009><FONT face=Arial
color=#0000ff size=2>The voting thresholds are for the bicameral Council, not
the SGs. It will be up to the SGs to inform their Council reps how to vote
on the Council. The GNSO Operations work team is tasked with developing
revised Rules of Procedure for the Council and proposing those to the Council
for consideration. That of course will involve full community
input.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=182595413-30032009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=182595413-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> Monday, March 30, 2009 9:49
AM<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>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">We
are not revisiting those, but there are still so many unanswered questions
even around the voting thresholds (i.e., does voting results mean of those
present or does it mean of those in the stakeholder group as a whole) that
need to be explored and some believe that we should not implement any new
thresholds until these questions are answered by the community. In any
case, it is a subject for the work teams to consider (as opposed to just the
Council).<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal
style="MARGIN-TOP: 6pt; mso-margin-bottom-alt: auto"><B><SPAN
style="FONT-SIZE: 10pt; COLOR: #632423; FONT-FAMILY: 'Arial','sans-serif'">Jeffrey
J. Neuman, Esq</SPAN></B><B><SPAN
style="FONT-SIZE: 10pt; COLOR: #333333; FONT-FAMILY: 'Arial','sans-serif'">.</SPAN></B><B><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: 'Arial','sans-serif'">:</SPAN></B><B><SPAN
style="FONT-SIZE: 10pt; COLOR: #3366ff; FONT-FAMILY: 'Arial','sans-serif'">
</SPAN></B><B><SPAN
style="FONT-SIZE: 10pt; COLOR: #000066; FONT-FAMILY: 'Arial','sans-serif'">NeuStar,
Inc.</SPAN></B><B><SPAN
style="FONT-SIZE: 10pt; COLOR: #3366ff; FONT-FAMILY: 'Arial','sans-serif'"><BR></SPAN></B><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: 'Arial','sans-serif'">Vice
President, Law & Policy</SPAN><SPAN
style="FONT-SIZE: 8.5pt; COLOR: gray; FONT-FAMILY: 'Arial','sans-serif'">
<BR><BR><o:p></o:p></SPAN></P>
<DIV>
<DIV>
<DIV class=MsoNormal><SPAN
style="FONT-SIZE: 8pt; COLOR: gray; FONT-FAMILY: 'Calibri','sans-serif'">
<HR style="COLOR: #969696" align=left width="100%" noShade SIZE=1>
</SPAN></DIV></DIV></DIV>
<P class=MsoNormal
style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN
style="FONT-SIZE: 6.5pt; COLOR: gray; FONT-FAMILY: 'Arial','sans-serif'">The
information contained in this e-mail message is intended only for the use of
the recipient(s) named above and may contain confidential and/or privileged
information. If you are not the intended recipient you have received this
e-mail message in error and any review, dissemination, distribution, or
copying of this message is strictly prohibited. If you have received this
communication in error, please notify us immediately and delete the original
message.</SPAN><SPAN style="COLOR: #1f497d"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-TOP: 6pt; mso-margin-bottom-alt: auto"><SPAN
style="FONT-SIZE: 8.5pt; COLOR: gray; FONT-FAMILY: 'Arial','sans-serif'"><o:p> </o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-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'"> Gomes, Chuck
[mailto:cgomes@verisign.com] <BR><B>Sent:</B> Monday, March 30, 2009 9:32
AM<BR><B>To:</B> Neuman, Jeff; 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<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Jeff,</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">I
think we need to separate the voting thresholds from the PDP work, at least
for now. That would not necessarily mean that the thresholds could not
be revisited later if I problem was discovered relative to the revised PDP but
I would hope that that is an unlikely possibility. A lot of community
thought already went into the thresholds and I don't think it is a good idea
to start that over.</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Chuck</SPAN><o:p></o:p></P>
<BLOCKQUOTE
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=MsoNormal><o:p> </o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Neuman, Jeff
[mailto:Jeff.Neuman@neustar.us] <BR><B>Sent:</B> Sunday, March 29, 2009 9:25
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</SPAN><o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I
was reading Section 11 in the document (reprinted below) that jumped out at
me. The reason I made my comments was because one of the issues that
the work team was discussing was what needed to be accomplished prior to the
June date as opposed to after. It was also up for discussion as to
what would happen with the PDP if everything were not completed. The
assumption some had in the group was that even if the GNSO divided into
Stakeholder Groups at the June date, the PDP may very well be unaltered
until such time as the Work Team/Council and Board felt the changes could be
implemented. But this seems to envision a piece meal adoption of a new
PDP (namely adopting the voting thresholds with no explanation or context
until other pieces could be (if ever) adopted)).
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">The
registries and registrars may not like changing the PDP in this piecemeal
fashion since it would affect how consensus policies are developed. I
also fear that we (the Work Team/Council/Staff) could get bogged down
in discussing what should happen at transition date and never get to the
ultimate substance (the redesign of the PDP as a
whole).<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I
do not view this issue as a GNSO council issue, but rather as a community
issue that at the very least the work team will need to address.
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal
style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto">11. <SPAN
style="BACKGROUND: yellow; mso-highlight: yellow">In the absence of further
action by the Board to modify or amend Annex A to these Bylaws and/or this
Transition Article XX, Section 5, the newly seated GNSO Council will utilize
the following voting thresholds for all policy development activity
conducted commencing with the ICANN meeting in June 2009<A title=""
style="mso-footnote-id: ftn1" href="#_ftn1" name=_ftnref1><SPAN
class=MsoFootnoteReference>[1]</SPAN></A>: <o:p></o:p></SPAN></P>
<P class=MsoNormal
style="MARGIN-BOTTOM: 0pt; MARGIN-LEFT: 27.4pt; TEXT-INDENT: -13.7pt; MARGIN-RIGHT: 0in; mso-margin-top-alt: 6.0pt"><SPAN
style="BACKGROUND: yellow; mso-highlight: yellow">a. <U>Create an
Issues Report</U>: requires more than 25% vote of both houses or
majority of one house; <o:p></o:p></SPAN></P>
<P class=MsoNormal
style="MARGIN-BOTTOM: 0pt; MARGIN-LEFT: 27.4pt; TEXT-INDENT: -13.7pt; MARGIN-RIGHT: 0in; mso-margin-top-alt: 6.0pt"><SPAN
style="BACKGROUND: yellow; mso-highlight: yellow">b. <U>Initiate a
PDP</U> <U>Within Scope</U>: requires more than 33% vote of both
houses or more than 66% vote of one house; <o:p></o:p></SPAN></P>
<P class=MsoNormal
style="MARGIN-BOTTOM: 0pt; MARGIN-LEFT: 27.4pt; TEXT-INDENT: -13.7pt; MARGIN-RIGHT: 0in; mso-margin-top-alt: 6.0pt"><SPAN
style="BACKGROUND: yellow; mso-highlight: yellow">c. <U>Initiate a
PDP</U> <U>Not Within Scope</U>: 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=MsoNormal
style="MARGIN-BOTTOM: 0pt; MARGIN-LEFT: 27.4pt; TEXT-INDENT: -13.7pt; MARGIN-RIGHT: 0in; mso-margin-top-alt: 6.0pt"><SPAN
style="BACKGROUND: yellow; mso-highlight: yellow">d. <U>Approve a PDP
Without a Super Majority</U>: 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=MsoNormal><SPAN
style="BACKGROUND: yellow; mso-highlight: yellow">e. <U>Approve a PDP
With a Super Majority</U>: requires greater than 75% majority in one
house and majority in the other house.</SPAN> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal
style="MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; mso-margin-top-alt: 6.0pt"><B><SPAN
style="FONT-SIZE: 10pt; COLOR: #632423; FONT-FAMILY: 'Arial','sans-serif'">Jeffrey
J. Neuman, Esq</SPAN></B><B><SPAN
style="FONT-SIZE: 10pt; COLOR: #333333; FONT-FAMILY: 'Arial','sans-serif'">.</SPAN></B><B><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: 'Arial','sans-serif'">:</SPAN></B><B><SPAN
style="FONT-SIZE: 10pt; COLOR: #3366ff; FONT-FAMILY: 'Arial','sans-serif'">
</SPAN></B><B><SPAN
style="FONT-SIZE: 10pt; COLOR: #000066; FONT-FAMILY: 'Arial','sans-serif'">NeuStar,
Inc.</SPAN></B><B><SPAN
style="FONT-SIZE: 10pt; COLOR: #3366ff; FONT-FAMILY: 'Arial','sans-serif'"><BR></SPAN></B><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: 'Arial','sans-serif'">Vice
President, Law & Policy</SPAN><SPAN
style="FONT-SIZE: 8.5pt; COLOR: gray; FONT-FAMILY: 'Arial','sans-serif'">
<o:p></o:p></SPAN></P>
<DIV>
<DIV>
<DIV>
<DIV class=MsoNormal><SPAN
style="FONT-SIZE: 8pt; COLOR: gray; FONT-FAMILY: 'Calibri','sans-serif'">
<HR style="COLOR: #969696" align=left width="100%" noShade SIZE=1>
</SPAN></DIV></DIV></DIV></DIV>
<P class=MsoNormal
style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN
style="FONT-SIZE: 6.5pt; COLOR: gray; FONT-FAMILY: 'Arial','sans-serif'">The
information contained in this e-mail message is intended only for the use of
the recipient(s) named above and may contain confidential and/or privileged
information. If you are not the intended recipient you have received this
e-mail message in error and any review, dissemination, distribution, or
copying of this message is strictly prohibited. If you have received this
communication in error, please notify us immediately and delete the original
message.</SPAN><SPAN style="COLOR: #1f497d"><o:p></o:p></SPAN></P>
<P class=MsoNormal
style="MARGIN-TOP: 6pt; mso-margin-bottom-alt: auto"><SPAN
style="FONT-SIZE: 8.5pt; COLOR: gray; FONT-FAMILY: 'Arial','sans-serif'"><o:p> </o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-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'"> Gomes, Chuck
[mailto:cgomes@verisign.com] <BR><B>Sent:</B> Sunday, March 29, 2009 8:05
PM<BR><B>To:</B> Neuman, Jeff; 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<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Jeff,</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">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.</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Chuck</SPAN><o:p></o:p></P>
<BLOCKQUOTE
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=MsoNormal><o:p> </o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> 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</SPAN><o:p></o:p></P>
<P style="MARGIN-BOTTOM: 12pt"><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">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
</SPAN><o:p></o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<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-liaison6c@gnso.icann.org <BR><B>To</B>: Ken Bour ; Stéphane Van
Gelder ; Margie Milam ; council@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 </SPAN><o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">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.</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">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.</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Chuck</SPAN><o:p></o:p></P>
<BLOCKQUOTE
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=MsoNormal><o:p> </o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><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>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</SPAN><o:p></o:p></P>
<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"><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">a)</SPAN><SPAN
style="FONT-SIZE: 7pt; COLOR: #1f497d">
</SPAN><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"><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">b)</SPAN><SPAN
style="FONT-SIZE: 7pt; COLOR: #1f497d">
</SPAN><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"><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">c)</SPAN><SPAN
style="FONT-SIZE: 7pt; COLOR: #1f497d">
</SPAN><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"><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">a)</SPAN><SPAN
style="FONT-SIZE: 7pt; COLOR: #1f497d">
</SPAN><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"><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">b)</SPAN><SPAN
style="FONT-SIZE: 7pt; COLOR: #1f497d">
</SPAN><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"><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">c)</SPAN><SPAN
style="FONT-SIZE: 7pt; COLOR: #1f497d">
</SPAN><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"><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">d)</SPAN><SPAN
style="FONT-SIZE: 7pt; COLOR: #1f497d">
</SPAN><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"><SPAN
style="COLOR: #1f497d; FONT-FAMILY: 'Book Antiqua','serif'">e)</SPAN><SPAN
style="FONT-SIZE: 7pt; COLOR: #1f497d">
</SPAN><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></BLOCKQUOTE></BLOCKQUOTE>
<DIV>
<P class=MsoNormal><BR clear=all><o:p></o:p></P>
<DIV class=MsoNormal>
<HR align=left width="33%" SIZE=1>
</DIV></DIV></BLOCKQUOTE></DIV>
<DIV style="mso-element: footnote-list"><BR clear=all>
<HR align=left width="33%" SIZE=1>
<DIV id=ftn1 style="mso-element: footnote">
<P class=MsoFootnoteText style="MARGIN-BOTTOM: 0pt; LINE-HEIGHT: normal"><A
title="" style="mso-footnote-id: ftn1" href="#_ftnref1" name=_ftn1><SPAN
class=MsoFootnoteReference><B><I><SPAN
style="FONT-FAMILY: 'Times New Roman','serif'">[1]</SPAN></I></B></SPAN></A><I><SPAN
style="FONT-FAMILY: 'Times New Roman','serif'"> Note: The PPSC’s PDP Team may
recommend rewording the voting thresholds.
<o:p></o:p></SPAN></I></P></DIV></DIV></BLOCKQUOTE></BODY></HTML>