<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [gnso-osc-csg] Public Comments on CSG Work Team Recommendations
- To: ChuckGomes <cgomes@xxxxxxxxxxxx>, Julie Hedlund <julie.hedlund@xxxxxxxxx>, Rafik Dammak <rafik.dammak@xxxxxxxxx>, victoria@xxxxxxxxxx
- Subject: Re: [gnso-osc-csg] Public Comments on CSG Work Team Recommendations
- From: SS Kshatriy <sskshatriy@xxxxxxxxx>
- Date: Fri, 23 Jul 2010 00:33:39 -0700 (PDT)
<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top"
style="font: inherit;"><DIV id=yiv1914680863>
<TABLE id=yiv1914680863bodyDrftID class=yiv1914680863 border=0 cellSpacing=0
cellPadding=0>
<TBODY>
<TR>
<TD id=yiv1914680863drftMsgContent>
<DIV>Hello Victoria,</DIV>
<DIV>I have been following members' mails on Public Comments.</DIV>
<DIV>a. I find that though your queries and doubts are correct, but sometimes
these are difficult and un-comfortable to find right answer.</DIV>
<DIV>b. Two points appear to have been missed by all or do they find that
its beyond our mandate?<BR>1. We must congratulate ourselves that our
recommendations are clear and flawless as not to attract a single comment. Or
does it point to something else?</DIV>
<DIV>2. There was only one comment and that related to the intention/working of
ICANN.</DIV>
<DIV>Should this comment be brought to the notice of ICANN?</DIV>
<DIV> </DIV>
<DIV>SS<BR>--- On <B>Thu, 7/22/10, victoria@xxxxxxxxxx
<I><victoria@xxxxxxxxxx></I></B> wrote:<BR></DIV>
<BLOCKQUOTE style="BORDER-LEFT: rgb(16,16,255) 2px solid; PADDING-LEFT: 5px;
MARGIN-LEFT: 5px"><BR>From: victoria@xxxxxxxxxx
<victoria@xxxxxxxxxx><BR>Subject: Re: [gnso-osc-csg] Public Comments on
CSG Work Team Recommendations<BR>To: "Gomes, Chuck"
<cgomes@xxxxxxxxxxxx>, "Julie Hedlund" <julie.hedlund@xxxxxxxxx>,
"Rafik Dammak" <rafik.dammak@xxxxxxxxx><BR>Cc: "gnso-osc-csg"
<gnso-osc-csg@xxxxxxxxx><BR>Date: Thursday, July 22, 2010, 3:23 PM<BR><BR>
<DIV id=yiv1914680863yiv1359136671>
<STYLE>
<!--
#yiv1914680863 #yiv1914680863yiv1359136671
filtered #yiv1914680863yiv1359136671 {font-family:"Cambria Math";panose-1:2 4
5 3 5 4 6 3 2 4;}
#yiv1914680863 filtered #yiv1914680863yiv1359136671
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}
#yiv1914680863 filtered #yiv1914680863yiv1359136671
{font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}
#yiv1914680863 filtered #yiv1914680863yiv1359136671 {font-family:"Bookman Old
Style";panose-1:2 5 6 4 5 5 5 2 2 4;}
#yiv1914680863 #yiv1914680863yiv1359136671
#yiv1914680863yiv1359136671 p.yiv1914680863yiv1359136671MsoNormal,
#yiv1914680863 #yiv1914680863yiv1359136671
li.yiv1914680863yiv1359136671MsoNormal, #yiv1914680863
#yiv1914680863yiv1359136671 div.yiv1914680863yiv1359136671MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"serif";}
#yiv1914680863 #yiv1914680863yiv1359136671 a:link, #yiv1914680863
#yiv1914680863yiv1359136671 span.yiv1914680863yiv1359136671MsoHyperlink
{
color:blue;text-decoration:underline;}
#yiv1914680863 #yiv1914680863yiv1359136671 a:visited, #yiv1914680863
#yiv1914680863yiv1359136671 span.yiv1914680863yiv1359136671MsoHyperlinkFollowed
{
color:purple;text-decoration:underline;}
#yiv1914680863 #yiv1914680863yiv1359136671 p
{
margin-right:0in;
margin-left:0in;font-size:12.0pt;font-family:"serif";}
#yiv1914680863 #yiv1914680863yiv1359136671
p.yiv1914680863yiv1359136671MsoAcetate, #yiv1914680863
#yiv1914680863yiv1359136671 li.yiv1914680863yiv1359136671MsoAcetate,
#yiv1914680863 #yiv1914680863yiv1359136671
div.yiv1914680863yiv1359136671MsoAcetate
{
margin:0in;margin-bottom:.0001pt;font-size:8.0pt;font-family:"sans-serif";}
#yiv1914680863 #yiv1914680863yiv1359136671
span.yiv1914680863yiv1359136671BalloonTextChar
{
font-family:"sans-serif";}
#yiv1914680863 #yiv1914680863yiv1359136671
span.yiv1914680863yiv1359136671EmailStyle20
{
font-family:"serif";font-variant:normal;color:black;text-transform:none;text-shadow:none;font-weight:normal;font-style:normal;text-decoration:none
none;vertical-align:baseline;}
#yiv1914680863 #yiv1914680863yiv1359136671
span.yiv1914680863yiv1359136671EmailStyle21
{
font-family:"serif";font-variant:normal;color:black;text-transform:none;text-shadow:none;font-weight:normal;font-style:normal;text-decoration:none
none;vertical-align:baseline;}
#yiv1914680863 #yiv1914680863yiv1359136671
span.yiv1914680863yiv1359136671EmailStyle22
{
font-family:"sans-serif";color:#1F497D;}
#yiv1914680863 #yiv1914680863yiv1359136671
.yiv1914680863yiv1359136671MsoChpDefault
{
font-size:10.0pt;}
#yiv1914680863 filtered #yiv1914680863yiv1359136671 {
margin:1.0in 1.0in 1.0in 1.0in;}
#yiv1914680863 #yiv1914680863yiv1359136671
div.yiv1914680863yiv1359136671WordSection1
{}
-->
</STYLE>
Thanks Chuck --thats helpful. <BR><BR>I note that Art X of the Bylaws was very
recently amended after lengthy process ---only last year I believe, so as of
now Art X is inforce and will be until formally amended.<BR><BR>Annex A also
seems to apply when an issue originates with the Board--as here--as opposed to
starting with a PDP originated by the GNSO.<BR><BR>Prima facie in the absence
of another procedure ---it may have to be applied as far as possible as you
say. <BR><BR>Did the Council's own reforms go to the Board? This is the most
appropriate precedent here in my view also. <BR><BR>Reform and flexibility
sound good but there must be a place to find objective transparent practice and
procedure--and where issues are to be discretionary --that too should be
clear.<BR><BR>In company law ---all questions are answered by reference to the
bylaws and Board or member resolutions are needed for departure --when
permitted by the bylaws. <BR><BR>If the Board
delegates rule making functions ---it must be doing so under express or
implied powers--and that must be Art. X. It seems that the GNSO has no
independant formal legal standing whatsoever? Is this correct? If so, I don't
see how it can do anything at all under the bylaws ----except pass on
recomendations to the Board. Perhaps there is an official analysis of the
GNSO's legal status somewhere?<BR><BR>Such interesting questions.<BR><BR>Thanks
again Chuck for your answer.
<DIV>Sent from my BlackBerry® wireless device</DIV>
<HR>
<DIV><B>From: </B>"Gomes, Chuck" <cgomes@xxxxxxxxxxxx> </DIV>
<DIV><B>Date: </B>Thu, 22 Jul 2010 17:18:22 -0400</DIV>
<DIV><B>To: </B>Victoria McEvedy<victoria@xxxxxxxxxx>; Julie
Hedlund<julie.hedlund@xxxxxxxxx>; Rafik
Dammak<rafik.dammak@xxxxxxxxx></DIV>
<DIV><B>Cc: </B>gnso-osc-csg<gnso-osc-csg@xxxxxxxxx></DIV>
<DIV><B>Subject: </B>RE: [gnso-osc-csg] Public Comments on CSG Work Team
Recommendations</DIV>
<DIV><BR></DIV>
<DIV class=yiv1914680863yiv1359136671WordSection1>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: #1f497d;
FONT-SIZE: 11pt">Annex A contains the existing GNSO Policy Development Process
(PDP). A separate working team is currently working on recommendations to
revise the PDP under the direction of the Policy Process Steering Committee
(PPSC), the counterpart of the OSC. Annex A applies when the Council
initiates a PDP. The GNSO improvements efforts are not PDPs but rather
efforts to development recommendations for implementation of Board GNSO
improvement recommendations. At the same time, to the extent applicable,
principles of Annex A are applied. It should be noted though that Annex A
is terribly outdated and the GNSO has been moving to a more open and flexible
process for several years.</SPAN></DIV></DIV>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: #1f497d;
FONT-SIZE: 11pt"> </SPAN></DIV></DIV>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: #1f497d;
FONT-SIZE: 11pt">Chuck</SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: #1f497d;
FONT-SIZE: 11pt"> </SPAN>
<DIV style="BORDER-BOTTOM: medium none; BORDER-LEFT: blue 1.5pt solid;
PADDING-BOTTOM: 0in; PADDING-LEFT: 4pt; PADDING-RIGHT: 0in; BORDER-TOP: medium
none; BORDER-RIGHT: medium none; PADDING-TOP: 0in">
<DIV>
<DIV style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none;
PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df
1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=yiv1914680863yiv1359136671MsoNormal><B><SPAN style="FONT-SIZE:
10pt">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt"> Victoria McEvedy
[mailto:victoria@xxxxxxxxxx] <BR><B>Sent:</B> Thursday, July 22, 2010 4:47
PM<BR><B>To:</B> Victoria McEvedy; Julie Hedlund; Rafik Dammak; Gomes,
Chuck<BR><B>Cc:</B> gnso-osc-csg<BR><B>Subject:</B> RE: [gnso-osc-csg] Public
Comments on CSG Work Team Recommendations</SPAN></DIV></DIV></DIV></DIV>
<P class=yiv1914680863yiv1359136671MsoNormal>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black">Would
someone kindly answer the questions as to the Council’s own reforms and Board
approval also explain where we might find guidance on when Annex A is and is
not applied in relation to GNSO policy. Thank you. </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR:
black"> </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR:
black"> </SPAN>
<DIV>
<DIV style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none;
PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df
1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=yiv1914680863yiv1359136671MsoNormal><B><SPAN style="FONT-SIZE:
10pt">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt">
owner-gnso-osc-csg@xxxxxxxxx [mailto:owner-gnso-osc-csg@xxxxxxxxx] <B>On Behalf
Of </B>Victoria McEvedy<BR><B>Sent:</B> 22 July 2010 17:57<BR><B>To:</B> Julie
Hedlund; Rafik Dammak; Chuck Gomes<BR><B>Cc:</B>
gnso-osc-csg<BR><B>Subject:</B> RE: [gnso-osc-csg] Public Comments on CSG Work
Team Recommendations</SPAN></DIV></DIV></DIV>
<P class=yiv1914680863yiv1359136671MsoNormal>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR:
black"> </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black">If
ICANN wants to be a limited liability company –things will have to be actioned
by the Board to have any legal effect. These are constitutional changes
and warrant Board approval in my view –particularly as Chuck says that the GNSO
has no jurisdiction or power. </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR:
black"> </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black">I note
that Art. X of the Bylaws also say the GNSO is responsible for developing and
recommending to the ICANN Board substantive policies relating to generic
top-level domains. </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR:
black"> </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black">These
recommendations are policy –not that dissimilar to the GNSO’s recent reforms of
its own Council processes –what happened with those as to Board approval?
</SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR:
black"> </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black">It
seems that the following Procedure should apply –as appropriate. See Annex A to
the Bylaws. </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR:
black"> </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-11
rel=nofollow></A><B>11. Council Report to the Board</B>
<P class=yiv1914680863yiv1359136671MsoNormal>The Staff Manager will be present
at the final meeting of the Council, and will have five (5) calendar days after
the meeting to incorporate the views of the Council into a report to be
submitted to the Board (the "Board Report"). The Board Report must contain at
least the following:
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-11a
rel=nofollow></A>a. A clear statement of any Successful GNSO Vote
recommendation of the Council;
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-11b
rel=nofollow></A>b. If a Successful GNSO Vote was not reached, a clear
statement of all positions held by Council members. Each statement should
clearly indicate (i) the reasons underlying each position and (ii) the
constituency(ies) or Stakeholder Group(s) that held the position;
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-11c
rel=nofollow></A>c. An analysis of how the issue would affect each constituency
or Stakeholder Group, including any financial impact on the constituency or
Stakeholder Group;
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-11d
rel=nofollow></A>d. An analysis of the period of time that would likely be
necessary to implement the policy;
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-11e
rel=nofollow></A>e. The advice of any outside advisors relied upon, which
should be accompanied by a detailed statement of the advisor's (i)
qualifications and relevant experience; and (ii) potential conflicts of
interest;
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-11f
rel=nofollow></A>f. The Final Report submitted to the Council; and
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-11g
rel=nofollow></A>g. A copy of the minutes of the Council deliberation on the
policy issue, including the all opinions expressed during such deliberation,
accompanied by a description of who expressed such opinions.
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-12
rel=nofollow></A><B>12. Agreement of the Council</B>
<P class=yiv1914680863yiv1359136671MsoNormal>A. Successful GNSO Vote of the
Council members will be deemed to reflect the view of the Council, and may be
conveyed to the Board as the Council's recommendation. In the event a GNSO
Supermajority Vote is not achieved, approval of the recommendations contained
in the Final Report requires a majority of both houses and further requires
that one representative of at least 3 of the 4 Stakeholder Groups supports the
recommendations. Abstentions shall not be permitted; thus all Council members
must cast a vote unless they identify a financial interest in the outcome of
the policy issue. Notwithstanding the foregoing, as set forth above, all
viewpoints expressed by Council members during the PDP must be included in the
Board Report.
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-13
rel=nofollow></A><B>13. Board Vote</B>
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-13a
rel=nofollow></A>a. The Board will meet to discuss the GNSO Council
recommendation as soon as feasible after receipt of the Board Report from the
Staff Manager.
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-13b
rel=nofollow></A>b. In the event that the Council reached a GNSO Supermajority
Vote, the Board shall adopt the policy according to the GNSO Supermajority Vote
recommendation unless by a vote of more than sixty-six (66%) percent of the
Board determines that such policy is not in the best interests of the ICANN
community or ICANN.
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-13c
rel=nofollow></A>c. In the event that the Board determines not to act in
accordance with the GNSO Supermajority Vote recommendation, the Board shall (i)
articulate the reasons for its determination in a report to the Council (the
"Board Statement"); and (ii) submit the Board Statement to the Council.
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-13d
rel=nofollow></A>d. The Council shall review the Board Statement for discussion
with the Board within twenty (20) calendar days after the Council's receipt of
the Board Statement. The Board shall determine the method (e.g., by
teleconference, e-mail, or otherwise) by which the Council and Board will
discuss the Board Statement.
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-13e
rel=nofollow></A>e. At the conclusion of the Council and Board discussions, the
Council shall meet to affirm or modify its recommendation, and communicate that
conclusion (the "Supplemental Recommendation") to the Board, including an
explanation for its current recommendation. In the event that the Council is
able to reach a GNSO Supermajority Vote on the Supplemental Recommendation, the
Board shall adopt the recommendation unless more than sixty-six (66%) percent
of the Board determines that such policy is not in the interests of the ICANN
community or ICANN.
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-13f
rel=nofollow></A>f. In any case in which the Council is not able to reach GNSO
Supermajority vote, a majority vote of the Board will be sufficient to act.
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-13g
rel=nofollow></A>g. When a final decision on a GNSO Council Recommendation or
Supplemental Recommendation is timely, the Board shall take a preliminary vote
and, where practicable, will publish a tentative decision that allows for a ten
(10) day period of public comment prior to a final decision by the Board.
<P class=yiv1914680863yiv1359136671MsoNormal><A name=AnnexA-14
rel=nofollow></A><B>14. Implementation of the Policy</B>
<P class=yiv1914680863yiv1359136671MsoNormal>Upon a final decision of the
Board, the Board shall, as appropriate, give authorization or direction to the
ICANN staff to take all necessary steps to implement the policy.
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR:
black"> </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR:
black"> </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR:
black"> </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR:
black"> </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR:
black"> </SPAN>
<DIV>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black;
FONT-SIZE: 11pt" lang=EN-GB> </SPAN></DIV></DIV>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black;
FONT-SIZE: 10pt" lang=EN-GB>Victoria McEvedy</SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black;
FONT-SIZE: 10pt" lang=EN-GB>Principal </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black;
FONT-SIZE: 10pt" lang=EN-GB>McEvedys</SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><I><SPAN style="COLOR: black;
FONT-SIZE: 10pt" lang=EN-GB>Solicitors</SPAN></I><I><SPAN style="COLOR: black;
FONT-SIZE: 9pt" lang=EN-GB> and Attorneys </SPAN></I>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black;
FONT-SIZE: 11pt"><IMG id=yiv1914680863yiv1359136671Picture_x0020_1
alt=cid:669FC637-760A-4D2F-B56E-2C180C1870CC
src="cid:1.614656400@web57203.mail.re3.yahoo.com" width=142
height=62></SPAN><SPAN style="COLOR: black; FONT-SIZE: 11pt" lang=EN-GB></SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black;
FONT-SIZE: 9pt" lang=EN-GB> </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black;
FONT-SIZE: 8pt" lang=EN-GB>96 Westbourne Park Road </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black;
FONT-SIZE: 8pt" lang=EN-GB>London </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black;
FONT-SIZE: 8pt" lang=EN-GB>W2 5PL</SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black;
FONT-SIZE: 8pt" lang=EN-GB> </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black;
FONT-SIZE: 8pt" lang=EN-GB>T: +44 (0) 207 243 6122</SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black;
FONT-SIZE: 8pt" lang=EN-GB>F: +44 (0) 207 022 1721</SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black;
FONT-SIZE: 8pt" lang=EN-GB>M: +44 (0) 7990 625 169 </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><U><SPAN style="COLOR: black;
FONT-SIZE: 8pt" lang=EN-GB><SPAN style="TEXT-DECORATION:
none"> </SPAN></SPAN></U>
<P class=yiv1914680863yiv1359136671MsoNormal><U><SPAN style="COLOR: black;
FONT-SIZE: 8pt" lang=EN-GB>www.mcevedy.eu </SPAN></U><U><SPAN
style="COLOR: black; FONT-SIZE: 8pt" lang=EN-GB></SPAN></U>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: black;
FONT-SIZE: 10pt">Regulated by the Solicitors Regulation Authority
#465972</SPAN><SPAN style="COLOR: #999999; FONT-SIZE: 10pt"></SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: #999999;
FONT-SIZE: 7.5pt">This email and its attachments are confidential and intended
for the exclusive use of the addressee(s). This email and its attachments
may also be legally privileged. If you have received this in error, please let
us know by reply immediately and destroy the email and its attachments without
reading, copying or forwarding the contents.</SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: #999999;
FONT-SIZE: 7.5pt">This email does not create a solicitor-client relationship
and no retainer is created by this email communication. </SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR:
black"> </SPAN>
<DIV>
<DIV style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none;
PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df
1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=yiv1914680863yiv1359136671MsoNormal><B><SPAN style="FONT-SIZE:
10pt">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt"> Julie Hedlund
[mailto:julie.hedlund@xxxxxxxxx] <BR><B>Sent:</B> 22 July 2010
17:36<BR><B>To:</B> Rafik Dammak; Chuck Gomes<BR><B>Cc:</B> Victoria McEvedy;
gnso-osc-csg<BR><B>Subject:</B> Re: [gnso-osc-csg] Public Comments on CSG Work
Team Recommendations</SPAN></DIV></DIV></DIV>
<P class=yiv1914680863yiv1359136671MsoNormal>
<P style="MARGIN-BOTTOM: 12pt" class=yiv1914680863yiv1359136671MsoNormal><SPAN
style="FONT-SIZE: 11pt">Chuck and Rafik,<BR><BR>Rob Hoggarth has helpfully
provided the following relevant guidance from the BGC report:<BR><BR>Page
46;</SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="FONT-SIZE:
11pt">“Proposed Action Item: The Board requests: (i) The GNSO constituencies,
with assistance from Staff as needed, to develop a set of participation rules
and operating procedures, consistent with the principles outlined above, which
all constituencies should abide by. The ICANN Board should ask the
constituencies to develop and publicize common principles within six months;
and to implement operating rules and procedures consistent with those
principles at that time.” </SPAN>
<P style="MARGIN-BOTTOM: 12pt" class=yiv1914680863yiv1359136671MsoNormal><SPAN
style="FONT-SIZE: 11pt"><BR>He also noted that Staff will likely be asked to
notify the Board of the GNSO’s decisions, but no Board approval is
required.<BR><BR>Best regards,<BR><BR>Julie<BR><BR><BR>On 7/22/10 12:26 PM,
"Rafik Dammak" <<A rel=nofollow>rafik.dammak@xxxxxxxxx</A>> wrote:</SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="FONT-SIZE:
11pt">Thanks Chuck,<BR><BR>Rafik<BR><BR>2010/7/23 Gomes, Chuck <<A
rel=nofollow>cgomes@xxxxxxxxxxxx</A>></SPAN>
<P class=yiv1914680863yiv1359136671MsoNormal><SPAN style="COLOR: #1f497d;
FONT-SIZE: 11pt">No Rafik. Board approval is not required. The SIC
and Board will simply be informed of the action. Of course, the SIC and
Board could always come back and say that that the recommendations do not
satisfy the Board’s recommendations and ask for more work.
<BR> <BR>Chuck<BR> <BR></SPAN><SPAN style="FONT-SIZE:
11pt"><BR></SPAN><B><SPAN style="FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt"> Rafik Dammak [<A
href="http://us.mc572.mail.yahoo.com/mc/compose?to=rafik.dammak@xxxxxxxxx";
rel=nofollow target=_blank>mailto:rafik.dammak@xxxxxxxxx</A>] <BR><B>Sent:</B>
Thursday, July 22, 2010 12:12 PM<BR><B>To:</B> Gomes, Chuck<BR><B>Cc:</B>
Victoria McEvedy; gnso-osc-csg; Julie Hedlund<BR></SPAN><SPAN style="FONT-SIZE:
11pt"><BR><BR><B>Subject:</B> Re: [gnso-osc-csg] Public Comments on CSG Work
Team
Recommendations<BR> <BR><BR>Hi Chuck,<BR><BR>just for clarification,
after adoption of the motion and recommendation by GNSO council, the document
will be passed to SIC and board for
approval?<BR><BR> <BR><BR>Rafik<BR><BR> <BR><BR>2010/7/23 Gomes,
Chuck <<A rel=nofollow>cgomes@xxxxxxxxxxxx</A>><BR><BR><SPAN
style="COLOR: #1f497d">Please see below
Victoria.<BR> <BR>Chuck<BR> <BR></SPAN><BR></SPAN><B><SPAN
style="FONT-SIZE: 10pt">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt"> Victoria
McEvedy [<A
href="http://us.mc572.mail.yahoo.com/mc/compose?to=victoria@xxxxxxxxxx";
rel=nofollow target=_blank>mailto:victoria@xxxxxxxxxx</A>] <BR><B>Sent:</B>
Wednesday, July 21, 2010 8:58 AM<BR><B>To:</B> Gomes, Chuck<BR><B>Cc:</B>
gnso-osc-csg; Julie Hedlund<BR></SPAN><SPAN style="FONT-SIZE:
11pt"><BR><BR><B>Subject:</B> RE: [gnso-osc-csg] Public Comments on CSG Work
Team Recommendations<BR> <BR>Chuck –if that is the case then perhaps
the BGC should be tasked with determining compliance/enforcement instead of
the GNSO Council? It certainly cannot be fair to put Staff in the
position of enforcers for some of the structural and other reasons already
aired. <BR><B><I><SPAN style="COLOR: #1f497d">[Gomes, Chuck] That is not a
typical Board member responsibility. That it is the kind of task that
Directors would assign to staff. Compliance enforcement by ICANN has been
a very important concern in recent years; that has mostly related to registrar
agreements but it would seem to me to apply to SG/Constituency charters as
well.<BR></SPAN></I></B><BR> <BR>What models are there within ICANN for
follow up and enforcement of changes and what routes for stakeholders to raise
complaints as to compliance (other than the Ombudsman)? <BR><B><I><SPAN
style="COLOR: #1f497d">[Gomes, Chuck] There are specific mechanisms in place
for complaints about registrars and Whois
problems, but I am not aware of one for these kind of complaints. Maybe
Julie can comment on that. <BR></SPAN></I></B><BR> <BR>I do think a
deadline should be given for the Charters to be amended by. <BR><B><I><SPAN
style="COLOR: #1f497d">[Gomes, Chuck] That is not in the Council’s hands.
It is in the Board’s court.<BR></SPAN></I></B><BR> <BR>Best,
<BR> <BR><BR> <BR></SPAN><SPAN style="FONT-SIZE:
10pt">Victoria McEvedy<BR>Principal
<BR>McEvedys<BR><I>Solicitors</I></SPAN><I><SPAN style="FONT-SIZE: 9pt"> and
Attorneys <BR></SPAN></I><SPAN style="FONT-SIZE: 11pt"><IMG
id=yiv1914680863yiv1359136671_x0000_i1025 border=0
src="cid:1.614656400@web57203.mail.re3.yahoo.com" width=138
height=62><BR></SPAN><SPAN style="FONT-SIZE: 9pt"> <BR></SPAN><SPAN
style="FONT-SIZE: 8pt">96 Westbourne Park Road <BR>London <BR>W2
5PL<BR> <BR>T: +44 (0) 207 243
6122<BR>F: +44 (0)
207 022 1721<BR>M: +44 (0) 7990 625 169
<BR> <BR><U>www.mcevedy.eu <<A href="http://www.mcevedy.eu/";
rel=nofollow target=_blank>http://www.mcevedy.eu</A>>
<BR></U></SPAN><SPAN style="FONT-SIZE: 10pt">Regulated by the Solicitors
Regulation Authority #465972<BR></SPAN><SPAN style="COLOR: #999999; FONT-SIZE:
7pt">This email and its attachments are confidential and intended for the
exclusive use of the addressee(s). This email and its attachments may
also be legally privileged. If you have received this in error, please let us
know by reply immediately and destroy the email and its attachments without
reading, copying or forwarding the contents.<BR>This email does not create a
solicitor-client relationship and no retainer is created by this email
communication. <BR></SPAN><SPAN style="FONT-SIZE:
11pt"> <BR><BR></SPAN><B><SPAN style="FONT-SIZE:
10pt">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt"> Gomes, Chuck [<A
href="http://us.mc572.mail.yahoo.com/mc/compose?to=cgomes@xxxxxxxxxxxx";
rel=nofollow target=_blank>mailto:cgomes@xxxxxxxxxxxx</A>] <BR><B>Sent:</B> 21
July 2010 00:44<BR><B>To:</B> Victoria McEvedy<BR><B>Subject:</B> RE:
[gnso-osc-csg] Public Comments on CSG Work Team Recommendations<BR></SPAN><SPAN
style="FONT-SIZE: 11pt"> <BR><SPAN style="COLOR:
#1f497d">Victoria,<BR> <BR>The Council is not a governing body; it is a
manager of the policy development process. The Council has the task of
approving the Constituency & SG Operating Procedures but has no
responsibility to enforce them. The Board has the responsibility of
approving the Constituency and Stakeholder Group charters so it will ultimately
be up to the Board, with staff support, to decide whether the charters
appropriately reflect the Procedures as well as to enforce compliance of the
charters. If the motion was worded as you suggested, it could guarantee
that
certain members of the GNSO community would be up in
arms.<BR> <BR>Chuck<BR> <BR></SPAN><BR></SPAN><B><SPAN
style="FONT-SIZE: 10pt">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt"> <A
rel=nofollow>victoria@xxxxxxxxxx</A> [<A
href="http://us.mc572.mail.yahoo.com/mc/compose?to=victoria@xxxxxxxxxx";
rel=nofollow target=_blank>mailto:victoria@xxxxxxxxxx</A>] <BR><B>Sent:</B>
Tuesday, July 20, 2010 7:19 PM<BR><B>To:</B> Gomes, Chuck<BR><B>Subject:</B>
Re: [gnso-osc-csg] Public Comments on CSG Work Team
Recommendations<BR></SPAN><SPAN style="FONT-SIZE: 11pt"> <BR>But these are
all GNSO constituencies and stakeholder groups ---so within that SO ---in
relation to which the Council is the governing body. Please explain.<BR>Sent
from my BlackBerry® wireless device</SPAN>
<DIV style="TEXT-ALIGN: center" class=yiv1914680863yiv1359136671MsoNormal
align=center><SPAN style="FONT-SIZE: 11pt">
<HR align=center SIZE=2 width="100%">
</SPAN></DIV>
<DIV><B><SPAN style="FONT-SIZE: 11pt">From: </SPAN></B><SPAN style="FONT-SIZE:
11pt">"Gomes, Chuck" <<A rel=nofollow>cgomes@xxxxxxxxxxxx</A>>
<BR><BR><B>Date: </B>Tue, 20 Jul 2010 17:35:52 -0400<BR><BR><B>To: </B>Victoria
McEvedy<<A rel=nofollow>victoria@xxxxxxxxxx</A>>; Julie Hedlund<<A
rel=nofollow>julie.hedlund@xxxxxxxxx</A>>; Olga Cavalli<<A
rel=nofollow>olgacavalli@xxxxxxxxx</A>><BR><BR><B>Cc: </B>gnso-osc-csg<<A
rel=nofollow>gnso-osc-csg@xxxxxxxxx</A>><BR><BR><B>Subject: </B>RE:
[gnso-osc-csg] Public Comments on CSG Work Team
Recommendations<BR><BR> <BR><SPAN style="COLOR: #1f497d">Sorry
Victoria. This will not work because the Council has no authority over
SGs and Constituencies. <BR> <BR>Julie – I suggested one word
amendment choices that I think would
work.<BR> <BR>Chuck<BR> <BR></SPAN><BR></SPAN><B><SPAN
style="FONT-SIZE: 10pt">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt"> <A
rel=nofollow>owner-gnso-osc-csg@xxxxxxxxx</A> [<A
href="http://us.mc572.mail.yahoo.com/mc/compose?to=owner-gnso-osc-csg@xxxxxxxxx";
rel=nofollow target=_blank>mailto:owner-gnso-osc-csg@xxxxxxxxx</A>] <B>On
Behalf Of </B>Victoria McEvedy<BR><B>Sent:</B> Tuesday, July 20, 2010 5:15
PM<BR><B>To:</B> Julie Hedlund; Olga Cavalli<BR><B>Cc:</B>
gnso-osc-csg<BR><B>Subject:</B> RE: [gnso-osc-csg] Public Comments on CSG Work
Team Recommendations<BR></SPAN><SPAN style="FONT-SIZE: 11pt"> <BR>Julie
–suggested amendment:<BR> <BR>RESOLVED FURTHER, that the GNSO Council
approves [the CSG-WT majority recommendations [and/or] the minority
recommendations]. GNSO Stakeholder Groups and Constituencies are to
implement mandatory recommendations and any non-mandatory recommendations as
adopted by their general body on a vote by the full membership and shall
incorporate the changes in Charters and any other relevant documents, if any,
within two months
of the date of this resolution. Compliance with this recommendation to be
within the jurisdiction of and supervised by the GNSO Council:
<BR><SPAN style="COLOR: blue">·
<U>Recommended Common Operating
Principles and Participation Guidelines for GNSO Stakeholder Groups and
Constituencies; and <<A
href="http://gnso.icann.org/drafts/draft-csg-recommendations-task-27may10-en.pdf";
rel=nofollow
target=_blank>http://gnso.icann.org/drafts/draft-csg-recommendations-task-27may10-en.pdf</A>>
<BR>Recommendations on a GNSO Database of Community Members <<A
href="http://gnso.icann.org/drafts/draft-csg-recommendations-task-27may10-en.pdf";
rel=nofollow
target=_blank>http://gnso.icann.org/drafts/draft-csg-recommendations-task-27may10-en.pdf</A>>
<BR></U></SPAN> <BR> <BR><BR> <BR></SPAN><SPAN
style="FONT-SIZE: 10pt">Victoria McEvedy<BR>Principal
<BR>McEvedys<BR><I>Solicitors</I></SPAN><I><SPAN style="FONT-SIZE: 9pt"> and
Attorneys <BR></SPAN></I><SPAN style="FONT-SIZE: 11pt"><IMG
id=yiv1914680863yiv1359136671_x0000_i1027 border=0
src="cid:1.614656400@web57203.mail.re3.yahoo.com" width=138
height=62><BR></SPAN><SPAN style="FONT-SIZE: 9pt"> <BR></SPAN><SPAN
style="FONT-SIZE: 8pt">96 Westbourne Park Road <BR>London <BR>W2
5PL<BR> <BR>T: +44 (0) 207 243
6122<BR>F: +44 (0) 207 022 1721<BR>M: +44 (0)
7990 625 169 <BR> <BR><U>www.mcevedy.eu <<A
href="http://www.mcevedy.eu/"; rel=nofollow
target=_blank>http://www.mcevedy.eu</A>> <BR></U></SPAN><SPAN
style="FONT-SIZE: 10pt">Regulated by the Solicitors Regulation Authority
#465972<BR></SPAN><SPAN style="COLOR: #999999; FONT-SIZE: 7pt">This email and
its attachments are confidential and intended for the exclusive use of the
addressee(s). This email and its attachments may
also be legally privileged. If you have received this in error, please let us
know by reply immediately and destroy the email and its attachments without
reading, copying or forwarding the contents.<BR>This email does not create a
solicitor-client relationship and no retainer is created by this email
communication. <BR></SPAN><SPAN style="FONT-SIZE:
11pt"> <BR><BR></SPAN><B><SPAN style="FONT-SIZE:
10pt">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt"> Julie Hedlund [<A
href="http://us.mc572.mail.yahoo.com/mc/compose?to=julie.hedlund@xxxxxxxxx";
rel=nofollow target=_blank>mailto:julie.hedlund@xxxxxxxxx</A>] <BR><B>Sent:</B>
20 July 2010 16:28<BR><B>To:</B> Victoria McEvedy; Olga Cavalli<BR><B>Cc:</B>
gnso-osc-csg<BR><B>Subject:</B> Re: [gnso-osc-csg] Public Comments on CSG Work
Team Recommendations<BR></SPAN><SPAN style="FONT-SIZE: 11pt"> <BR>Dear
Victoria,<BR><BR>Please do suggest language. Staff language was merely a
suggestion.<BR><BR>Best,<BR><BR>Julie<BR><BR><BR>On 7/20/10 11:15 AM,
"Victoria McEvedy" <<A rel=nofollow>victoria@xxxxxxxxxx</A> <<A
href="http://victoria@xxxxxxxxxx"; rel=nofollow
target=_blank>http://victoria@xxxxxxxxxx</A>> > wrote:<BR>Thank you
Julie. <BR> <BR>The obvious issue with that language is that it renders
every single recommendation entirely optional and non-voluntary—and the whole
exercise nothing more than advisory or for reference—despite the fact that
after much discussion particular recommendations were agreed <I>by the
majority</I> as “<I>must</I>” recommendations and the balance ‘<I>should</I>’
recommendations. <BR> <BR>It’s currently a motion for each group to carry
on as these please and a recommendation for the status quo. I don’t think
that’s an acceptable outcome after our 18 months of work. <BR> <BR>I would
suggest that the recommendations should be accepted as the ‘musts’
or ‘shoulds’ as recommended in each case. <BR> <BR>I would be
happy to provide some language ---or perhaps the Staff would like to do that in
the first instance. <BR> <BR>Best, <BR><BR> <BR></SPAN><SPAN
style="FONT-SIZE: 10pt">Victoria McEvedy<BR>Principal
<BR>McEvedys<BR><I>Solicitors</I></SPAN><I><SPAN style="FONT-SIZE: 9pt"> and
Attorneys <BR></SPAN></I><SPAN style="FONT-SIZE: 11pt"><IMG
id=yiv1914680863yiv1359136671_x0000_i1028 border=0
src="cid:1.614656400@web57203.mail.re3.yahoo.com" width=138
height=62><BR></SPAN><SPAN style="FONT-SIZE: 9pt"><BR></SPAN><SPAN
style="FONT-SIZE: 8pt">96 Westbourne Park Road <BR>London <BR>W2
5PL<BR> <BR>T: +44 (0) 207 243 6122<BR>F:
+44 (0) 207 022 1721<BR>M: +44 (0) 7990 625 169
<BR><U><BR>www.mcevedy.eu <<A href="http://www.mcevedy.eu/"; rel=nofollow
target=_blank>http://www.mcevedy.eu</A>> <BR></U></SPAN><SPAN
style="FONT-SIZE: 10pt">Regulated by the Solicitors Regulation Authority
#465972<BR></SPAN><SPAN style="FONT-SIZE: 7pt">This email and its attachments
are confidential and intended for the exclusive use of the addressee(s).
This email and its attachments may also be legally privileged. If you
have received this in error, please let us know by reply immediately and
destroy the email and its attachments without reading, copying or forwarding
the contents.<BR>This email does not create a solicitor-client relationship and
no retainer is created by this email communication. <BR></SPAN><SPAN
style="FONT-SIZE: 11pt"><BR><BR></SPAN><B><SPAN style="FONT-SIZE:
10pt">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt"> Julie Hedlund [<A
href="http://us.mc572.mail.yahoo.com/mc/compose?to=julie.hedlund@xxxxxxxxx";
rel=nofollow target=_blank>mailto:julie.hedlund@xxxxxxxxx</A>] <BR><B>Sent:</B>
20 July 2010 16:03<BR><B>To:</B> Victoria McEvedy; Olga
Cavalli<BR><B>Cc:</B> gnso-osc-csg<BR><B>Subject:</B> Re: [gnso-osc-csg]
Public Comments on CSG Work Team Recommendations<BR></SPAN><SPAN
style="FONT-SIZE: 11pt"><BR>Dear Victoria,<BR><BR>Staff included that suggested
language for consideration in the motion since Constituencies and Stakeholder
Groups may need to amend their charters based on the recommendations in the
report.<BR><BR>Thanks,<BR>Julie <BR><BR><BR>On 7/20/10 10:54
AM, "Victoria McEvedy" <<A rel=nofollow>victoria@xxxxxxxxxx</A> <<A
href="http://victoria@xxxxxxxxxx"; rel=nofollow
target=_blank>http://victoria@xxxxxxxxxx</A>> > wrote:<BR>Dear WT,
<BR> <BR>Could someone explain what “for evaluation in amending their
charters, as appropriate” means? What is the origin of this language?
<BR> <BR>Thank you and regards, <BR><BR> <BR></SPAN><SPAN
style="FONT-SIZE: 10pt">Victoria McEvedy<BR>Principal
<BR>McEvedys<BR><I>Solicitors</I></SPAN><I><SPAN style="FONT-SIZE: 9pt"> and
Attorneys <BR></SPAN></I><SPAN style="FONT-SIZE: 11pt"><IMG
id=yiv1914680863yiv1359136671_x0000_i1029 border=0
src="cid:1.614656400@web57203.mail.re3.yahoo.com" width=138
height=62><BR></SPAN><SPAN style="FONT-SIZE: 9pt"><BR></SPAN><SPAN
style="FONT-SIZE: 8pt">96 Westbourne Park Road <BR>London <BR>W2
5PL<BR> <BR>T: +44 (0) 207 243 6122<BR>F:
+44 (0) 207 022 1721<BR>M: +44 (0) 7990 625 169
<BR><U><BR>www.mcevedy.eu <<A href="http://www.mcevedy.eu/"; rel=nofollow
target=_blank>http://www.mcevedy.eu</A>> <BR></U></SPAN><SPAN
style="FONT-SIZE: 10pt">Regulated by the Solicitors Regulation Authority
#465972<BR></SPAN><SPAN style="FONT-SIZE: 7pt">This email and its attachments
are confidential and intended for the exclusive use of the addressee(s).
This email and its attachments may also be legally privileged. If
you have received this in error, please let us know by reply immediately and
destroy the email and its attachments without reading, copying or forwarding
the contents.<BR>This email does not create a solicitor-client relationship and
no retainer is created by this email communication. <BR></SPAN><SPAN
style="FONT-SIZE: 11pt"><BR><BR></SPAN><B><SPAN style="FONT-SIZE:
10pt">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt"> <A
rel=nofollow>owner-gnso-osc-csg@xxxxxxxxx</A> <<A
href="http://owner-gnso-osc-csg@xxxxxxxxx"; rel=nofollow
target=_blank>http://owner-gnso-osc-csg@xxxxxxxxx</A>> [<A
href="http://us.mc572.mail.yahoo.com/mc/compose?to=owner-gnso-osc-csg@xxxxxxxxx";
rel=nofollow target=_blank>mailto:owner-gnso-osc-csg@xxxxxxxxx</A>] <B>On
Behalf Of </B>Julie Hedlund<BR><B>Sent:</B> 20 July 2010 14:54<BR><B>To:</B>
Olga Cavalli<BR><B>Cc:</B> gnso-osc-csg<BR><B>Subject:</B> Re: [gnso-osc-csg]
Public Comments on CSG Work Team
Recommendations<BR></SPAN><SPAN style="FONT-SIZE: 11pt"><BR>Dear
Olga,<BR><BR>Here is a draft motion for you to consider. Please feel free
to edit it, of course. Let me know if I can help in any way.<BR><BR>Best
regards,<BR><BR>Julie<BR><BR><B><U>DRAFT RESOLUTION: Final Council Action
on GCOT & CSG Deliverables<BR></U></B><BR>WHEREAS, the GNSO Council, at its
23 June 2010 meeting in Brussels, accepted a set of deliverables submitted by
the <SPAN style="COLOR: blue">GNSO Council Operations Work Team (GCOT)</SPAN>
<<U><SPAN style="COLOR: blue"><A
href="https://st.icann.org/icann-osc/index.cgi?gnso_operations_team";
rel=nofollow
target=_blank>https://st.icann.org/icann-osc/index.cgi?gnso_operations_team</A></SPAN></U>>
and the <SPAN style="COLOR: blue">Constituency and Stakeholder Group
Operations Work Team (CSG-WT)</SPAN> <<U><SPAN style="COLOR: blue"><A
href="https://st.icann.org/icann-osc/index.cgi?constituency_operations_team";
rel=nofollow
target=_blank>https://st.icann.org/icann-osc/index.cgi?constituency_operations_team</A></SPAN></U>>
;<BR> <BR>WHEREAS, a twenty-one (21) day Public Comment Forum
<<U><SPAN style="COLOR: blue"><A
href="http://www.icann.org/en/public-comment/#gcot-csg-recommendations";
rel=nofollow
target=_blank>http://www.icann.org/en/public-comment/#gcot-csg-recommendations</A></SPAN></U>>
completed between 28 June 2010 and 18 July 2010 and a Staff Summary and
Analysis <<U><SPAN style="COLOR: blue"><A
href="http://forum.icann.org/lists/gcot-csg-recommendations/msg00001.html";
rel=nofollow
target=_blank>http://forum.icann.org/lists/gcot-csg-recommendations/msg00001.html</A></SPAN></U>>
has been published; <BR>WHEREAS, the GNSO Council agreed to take action on the
these deliverables as soon as possible after the end of the public comment
period;<BR><BR>WHEREAS,
there were no public comments submitted that would amend any of the GCOT or
CSG-WT recommendations; <BR> <BR>NOW, BE IT
THEREFORE:<BR> <BR>RESOLVED, that the GNSO Council approves the following
set of GCOT documents, without further modification, and directs Staff to
publish a new version of the GNSO Operating Procedures (GOP) containing these
sections and chapters: <BR>·
<SPAN style="COLOR:
blue">Section 2.1-Council Member Term Limits</SPAN> <<U><SPAN style="COLOR:
blue"><A
href="http://gnso.icann.org/drafts/draft-gnso-op-procedures-term-limits-24may10-en.pdf";
rel=nofollow
target=_blank>http://gnso.icann.org/drafts/draft-gnso-op-procedures-term-limits-24may10-en.pdf</A></SPAN></U>>
<BR>· <SPAN
style="COLOR: blue">Section 2.4-Board Seat Elections</SPAN> <<U><SPAN
style="COLOR: blue"><A
href="http://gnso.icann.org/drafts/draft-gnso-op-procedures-board-seat-elections-24may10-en.pdf";
rel=nofollow
target=_blank>http://gnso.icann.org/drafts/draft-gnso-op-procedures-board-seat-elections-24may10-en.pdf</A></SPAN></U>>
<BR>· <SPAN
style="COLOR: blue">Section 3.8-Absences and Vacancies</SPAN> <<U><SPAN
style="COLOR: blue"><A
href="http://gnso.icann.org/drafts/draft-gnso-op-procedures-absences-vacancies-11jun10-en.pdf";
rel=nofollow
target=_blank>http://gnso.icann.org/drafts/draft-gnso-op-procedures-absences-vacancies-11jun10-en.pdf</A></SPAN></U>>
<BR>· <SPAN
style="COLOR: blue">Chapter 4.0-Voting</SPAN> <<U><SPAN style="COLOR:
blue"><A
href="http://gnso.icann.org/drafts/draft-gnso-op-procedures-voting-11jun10-en.pdf";
rel=nofollow
target=_blank>http://gnso.icann.org/drafts/draft-gnso-op-procedures-voting-11jun10-en.pdf</A></SPAN></U>>
<BR>· <SPAN
style="COLOR: blue">Chapter 5.0-Statements and Disclosures of Interest</SPAN>
<<U><SPAN style="COLOR: blue"><A
href="http://gnso.icann.org/drafts/draft-gnso-op-procedures-soi-doi-11jun10-en.pdf";
rel=nofollow
target=_blank>http://gnso.icann.org/drafts/draft-gnso-op-procedures-soi-doi-11jun10-en.pdf</A></SPAN></U>>
<BR>o Note that two sections, 5.3.2 and 5.3.3, are not
approved pending further Staff action to be determined. These sections
are footnoted in the document as “inactive” until subsequently approved by the
OSC and Council. <BR> <BR>RESOLVED FURTHER, that the GNSO Council approves
the following CSG-WT deliverable and directs Staff to provide these
recommendations to GNSO Stakeholder Groups and Constituencies for evaluation
in amending their charters, as appropriate: <BR><SPAN style="COLOR:
blue">· <U>Recommended Common
Operating Principles and Participation Guidelines for GNSO Stakeholder Groups
and Constituencies; and <<A
href="http://gnso.icann.org/drafts/draft-csg-recommendations-task-27may10-en.pdf";
rel=nofollow
target=_blank>http://gnso.icann.org/drafts/draft-csg-recommendations-task-27may10-en.pdf</A>>
<BR>Recommendations on a GNSO Database of Community Members <<A
href="http://gnso.icann.org/drafts/draft-csg-recommendations-task-27may10-en.pdf";
rel=nofollow
target=_blank>http://gnso.icann.org/drafts/draft-csg-recommendations-task-27may10-en.pdf</A>>
<BR></U></SPAN><BR>RESOLVED FURTHER, that the GCOT has successfully
completed its assignments, as chartered by the Operations Steering Committee
(OSC); therefore, the GNSO Council hereby discharges the GCOT with its
gratitude and appreciation
for the team’s dedication, commitment, and thoughtful recommendations.
<BR><BR><BR><BR><BR>On 7/19/10 4:36 PM, "Chuck Gomes" <<A
rel=nofollow>cgomes@xxxxxxxxxxxx</A> <<A href="http://cgomes@xxxxxxxxxxxx";
rel=nofollow target=_blank>http://cgomes@xxxxxxxxxxxx</A>> >
wrote:<BR>Sounds good. Hopefully a Councilor will make the motion and
another Councilor on the WT will second
it.<BR> <BR>Chuck<BR> <BR><BR></SPAN><B><SPAN style="FONT-SIZE:
10pt">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt"> <A
rel=nofollow>owner-gnso-osc-csg@xxxxxxxxx</A> <<A
href="http://owner-gnso-osc-csg@xxxxxxxxx"; rel=nofollow
target=_blank>http://owner-gnso-osc-csg@xxxxxxxxx</A>> [<A
href="http://us.mc572.mail.yahoo.com/mc/compose?to=owner-gnso-osc-csg@xxxxxxxxx";
rel=nofollow target=_blank>mailto:owner-gnso-osc-csg@xxxxxxxxx</A>] <B>On
Behalf Of </B>Julie Hedlund<BR><B>Sent:</B> Monday, July 19, 2010 3:27
PM<BR><B>To:</B> Olga
Cavalli<BR><B>Cc:</B> gnso-osc-csg<BR><B>Subject:</B> Re: [gnso-osc-csg]
Public Comments on CSG Work Team Recommendations<BR></SPAN><SPAN
style="FONT-SIZE: 11pt"><BR>Dear Olga,<BR><BR>I will forward the draft motion
to you as soon as it is ready. I think we can get it to you by
tomorrow.<BR><BR>Best,<BR><BR>Julie<BR><BR><BR>On 7/19/10 3:05 PM, "Olga
Cavalli" <<A rel=nofollow>olgacavalli@xxxxxxxxx</A> <<A
href="http://olgacavalli@xxxxxxxxx"; rel=nofollow
target=_blank>http://olgacavalli@xxxxxxxxx</A>> > wrote:<BR>Thanks Julie,
let me know once the motion is ready so we can move
it.<BR>Best<BR>Olga<BR><BR>2010/7/19 Julie Hedlund <<A
rel=nofollow>julie.hedlund@xxxxxxxxx</A> <<A
href="http://julie.hedlund@xxxxxxxxx"; rel=nofollow
target=_blank>http://julie.hedlund@xxxxxxxxx</A>> ><BR>Dear Work Team
members,<BR><BR>The public comment forum on the Task 1 recommendations ended
yesterday. There was only one comment and it
was not substantive. I have produced a summary and analysis that is
available here: <U><SPAN style="COLOR: blue"><A
href="http://forum.icann.org/lists/gcot-csg-recommendations/msg00001.html";
rel=nofollow
target=_blank>http://forum.icann.org/lists/gcot-csg-recommendations/msg00001.html</A></SPAN></U>.
In particular, the comment did not address the Work Team’s report.
It related to the ICANN comment process in general.<BR><BR>The next step
is for the GNSO Council to approve the report. Staff will prepare a draft
motion for consideration.<BR><BR>Best regards,<BR><SPAN style="COLOR:
#888888"><BR>Julie</SPAN> <BR><BR><BR><BR><BR>__________ Information from ESET
NOD32 Antivirus, version of virus signature database 5295
(20100720)__________<BR><BR>The message was checked by ESET NOD32
Antivirus.<BR><BR><A href="http://www.eset.com/"; rel=nofollow
target=_blank>http://www.eset.com</A><BR><BR><BR>__________ Information from
ESET NOD32
Antivirus, version of virus signature database 5295
(20100720)__________<BR><BR>The message was checked by ESET NOD32
Antivirus.<BR><BR><A href="http://www.eset.com/"; rel=nofollow
target=_blank>http://www.eset.com</A><BR><BR><BR>__________ Information from
ESET NOD32 Antivirus, version of virus signature database 5295
(20100720)__________<BR><BR>The message was checked by ESET NOD32
Antivirus.<BR><BR><A href="http://www.eset.com/"; rel=nofollow
target=_blank>http://www.eset.com</A><BR><BR><BR>__________ Information from
ESET NOD32 Antivirus, version of virus signature database 5295
(20100720)__________<BR><BR>The message was checked by ESET NOD32
Antivirus.<BR><BR><A href="http://www.eset.com/"; rel=nofollow
target=_blank>http://www.eset.com</A><BR><BR><BR>__________ Information from
ESET NOD32 Antivirus, version of virus signature database 5295
(20100720)__________<BR><BR>The message was checked by ESET NOD32
Antivirus.<BR><BR><A
href="http://www.eset.com/"; rel=nofollow
target=_blank>http://www.eset.com</A><BR><BR><BR>__________ Information from
ESET NOD32 Antivirus, version of virus signature database 5296
(20100720)__________<BR><BR>The message was checked by ESET NOD32
Antivirus.<BR><BR><A href="http://www.eset.com/"; rel=nofollow
target=_blank>http://www.eset.com</A><BR><BR><BR>__________ Information from
ESET NOD32 Antivirus, version of virus signature database 5296
(20100720)__________<BR><BR>The message was checked by ESET NOD32
Antivirus.<BR><BR><A href="http://www.eset.com/"; rel=nofollow
target=_blank>http://www.eset.com</A><BR><BR><BR>__________ Information from
ESET NOD32 Antivirus, version of virus signature database 5297
(20100721)__________<BR><BR>The message was checked by ESET NOD32
Antivirus.<BR><BR><A href="http://www.eset.com/"; rel=nofollow
target=_blank>http://www.eset.com</A><BR> </SPAN></DIV>
<P style="MARGIN-BOTTOM: 12pt" class=yiv1914680863yiv1359136671MsoNormal>
<P class=yiv1914680863yiv1359136671MsoNormal><BR><BR>__________ Information
from ESET NOD32 Antivirus, version of virus signature database 5301
(20100722)__________<BR><BR>The message was checked by ESET NOD32
Antivirus.<BR><BR><A href="http://www.eset.com/"; rel=nofollow
target=_blank>http://www.eset.com</A>
<P class=yiv1914680863yiv1359136671MsoNormal><BR><BR>__________ Information
from ESET NOD32 Antivirus, version of virus signature database 5301
(20100722)__________<BR><BR>The message was checked by ESET NOD32
Antivirus.<BR><BR><A href="http://www.eset.com/"; rel=nofollow
target=_blank>http://www.eset.com</A><BR><BR><BR>__________ Information from
ESET NOD32 Antivirus, version of virus signature database 5301
(20100722)__________<BR><BR>The message was checked by ESET NOD32
Antivirus.<BR><BR><A href="http://www.eset.com/"; rel=nofollow
target=_blank>http://www.eset.com</A><BR><BR><BR>__________ Information from
ESET NOD32 Antivirus, version of virus signature database 5303
(20100722)__________<BR><BR>The message was checked by ESET NOD32
Antivirus.<BR><BR><A href="http://www.eset.com/"; rel=nofollow
target=_blank>http://www.eset.com</A>
<P class=yiv1914680863yiv1359136671MsoNormal><BR><BR>__________ Information
from ESET NOD32 Antivirus, version of virus signature database 5303
(20100722)__________<BR><BR>The message was checked by ESET NOD32
Antivirus.<BR><BR><A href="http://www.eset.com/"; rel=nofollow
target=_blank>http://www.eset.com</A></DIV></BLOCKQUOTE></TD></TR></TBODY></TABLE></DIV></td></tr></table><br>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|