<div dir="ltr"><div class="gmail_extra">Hi Farzi,</div><div class="gmail_extra"><br></div><div class="gmail_extra">I propose</div><div class="gmail_extra"><br></div><div class="gmail_extra">- to draft the announcement composed of rational and explaining the background (Acknowledging the previous attempts and efforts, that we used their outputs, what drafting team did), also sharing relevant info and links . this should be ready by this weekend</div><div class="gmail_extra">- sharing the clean version against current charter (well-formatted and read-proofed)</div><div class="gmail_extra">- draft timeline :</div><div class="gmail_extra"> - call for input, first reading from 15th August till 15th September</div><div class="gmail_extra"> - first resolution of comments 16th September to 23rd September</div><div class="gmail_extra"> - call for input, second reading for amended draft 23rd September to 23rd October</div><div class="gmail_extra"> - Final call : 23rd October to 30th October , to take note of any objections</div><div class="gmail_extra"> - Final draft adapted by 5th November (during ICANN meeting)</div><div class="gmail_extra"> - planning the voting in parallel with NCUC election (dates TBC) to adopt the new charter</div><div class="gmail_extra"> - informing the ICANN staff about the new charter, process with ICANN board/staff/OEC starts</div><div class="gmail_extra"><br></div><div class="gmail_extra">working methods: sharing a google doc, for those who cannot access we can provide a doc version. comments are encouraged to be made in the google doc but discussion can happen in NCUC list. We need volunteers from EC to handle comments and to play the editors role . the editors should ensure that those comments are responded and reflected in the document</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_extra">during each readings, we will try to resolve comments, explain rational behind amendments. we will keep a clean version as output from a reading . the document will be in suggestion mode and keep trace of comments. </div><div class="gmail_extra"><br></div><div class="gmail_extra">we will organize a (monthly) confcall during each reading/consultation to respond to questions and resolve pending issues.</div><div class="gmail_extra"><br></div></div><div class="gmail_extra">We will organize a Q&A call about the process and inviting Rob to clarify about ICANN process side. We will create a page in oru website to document the process and keep the documents there</div><div class="gmail_extra"><br></div><div class="gmail_extra">it is quite agressive and time-consuming work but it need to be done.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Best,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Rafik <br><div class="gmail_quote"><br></div><div class="gmail_quote">2016-08-10 8:14 GMT+09:00 farzaneh badii <span dir="ltr"><<a href="mailto:farzaneh.badii@gmail.com" target="_blank">farzaneh.badii@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Rafik,<div><br></div><div>Thanks. I think we should provide the rationale and perhaps schedule a meeting with the members and Rob and us to clarify questions. </div><div><br></div><div>Best</div><div><br></div><div>Farzaneh </div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On 9 August 2016 at 01:37, Rafik Dammak <span dir="ltr"><<a href="mailto:rafik.dammak@gmail.com" target="_blank">rafik.dammak@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div><div class="h5"><div dir="ltr">Hi everyone,<div><br></div><div>I am sending here the memo from Rob about charter amendment process.</div><div>let's prepare for starting of the consultation process for next Monday as agreed in our last EC call:</div><div>- draft the announcement explaining the rationale</div><div>- sharing the clean version of draft document, in suggestion mode</div><div>- explaining the timeline, NCUC process and ICANN process for charter amendment.</div><div><br></div><div>our target remains to finish this by Hyderabad and that will also impact our NCUC election schedule.</div><div><br></div><div>Best,</div><div><br></div><div>Rafik<br>
<br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Robert Hoggarth</b> <br>Date: 2016-08-09 0:44 GMT+09:00<br>Subject: Info Sharing - Process For Board Review of GNSO Community Charter Amendments<br>To: Maryam Bakoshi <br>Cc: Rafik Dammak , Benedetta Rossi <br><br><br>
<div style="word-wrap:break-word;color:rgb(0,0,0)"><div>
<p class="MsoNormal"><font face="Calibri" size="3">Dear Maryam,<u></u><u></u></font></p>
<p class="MsoNormal"><font face="Calibri" size="3"> </font></p>
<p class="MsoNormal"><font face="Calibri" size="3">Rafik asked me to supply the NCUC Executive
Committee with the details of the process for ICANN Board review of GNSO community charter
amendments. Please pass this note on to
the Executive Committee list as appropriate.<u></u><u></u></font></p>
<p class="MsoNormal"><font face="Calibri" size="3"> </font></p>
<p class="MsoNormal"><font face="Calibri" size="3">At a high level, the GNSO Charter Amendment Process
involves a total of four basic phases – <u></u><u></u></font></p>
<p class="MsoNormal"><font face="Calibri" size="3"> </font></p>
<p><font face="Calibri" size="3">·
Amendment preparations and
approval by the charter-amending community;<u></u><u></u></font></p>
<p><font face="Calibri" size="3">·
Staff review and analysis of
amendments for potential ICANN organization impacts;<u></u><u></u></font></p>
<p><font face="Calibri" size="3">·
Review of amendments and
opportunity for comment by the multistakeholder community; and <u></u><u></u></font></p>
<p><font face="Calibri" size="3">·
Full Board review and action<u></u><u></u></font></p>
<p class="MsoNormal"><font face="Calibri" size="3"> </font></p>
<p class="MsoNormal"><font face="Calibri" size="3">From my observations the last few years, the timing of the community amendment development process (Phase 1) can vary widely depending on many individual community factors and can go very quickly or take a long time. The entire Board review process (which
involves the last three phases of the process) seems to now be taking about 6 or 7 months (calculating from the formal submission of the amendments to
staff). The specifics of the process look like this:<u></u><u></u></font></p>
<p class="MsoNormal"><font face="Calibri" size="3"> </font></p>
<p style="margin-left:0.5in;margin-bottom:0.0001pt;line-height:12pt;background-color:white"><b><i><u><font face="Calibri" size="3">SUMMARY OF GNSO CHARTER AMENDMENT PROCESS (Excerpts)<u></u><u></u></font></u></i></b></p>
<p style="margin-top:12pt;margin-bottom:12pt;margin-left:0.5in;background-color:white"><i><font face="Calibri" size="3">On 28 September 2013, the ICANN
Board established a process for the amendment of GNSO Stakeholder Group and
Constituency Charters. That process is as follows:<u></u><u></u></font></i></p>
<p style="margin-left:0.5in;margin-bottom:0.0001pt;background-color:white"><font face="Calibri" size="3"><strong><i>Phase I:
Amendment Preparation</i></strong><i><u></u><u></u></i></font></p>
<p style="margin-left:0.5in;margin-bottom:0.0001pt;background-color:white"><font face="Calibri" size="3"><i>GNSO Stakeholder Groups (SGs) and
Constituencies should formulate charter amendments through their own internal
processes and notify ICANN Staff as early as practicable (at </i><i><a href="mailto:policy-staff@icann.org" target="_blank"><span style="color:black">policy-staff@icann.org</span></a>) upon initiation and completion (approval) of such efforts.<u></u><u></u></i></font></p>
<p style="margin-left:0.5in;margin-bottom:0.0001pt;line-height:12pt;background-color:white"><strong><i><font face="Calibri" size="3"> </font></i></strong></p>
<p style="margin-left:0.5in;margin-bottom:0.0001pt;line-height:12pt;background-color:white"><font face="Calibri" size="3"><strong><i>Phase
II: Staff Review</i></strong><i><u></u><u></u></i></font></p>
<p style="margin-bottom:12pt;margin-left:0.5in;background-color:white"><i><font face="Calibri" size="3">Upon formal receipt of the
proposed amendment(s) approved by the community group, ICANN staff will analyze
the proposal and, within 10 business days, submit the community proposal with a
report to the appropriate Board committee identifying any fiscal or liability
concerns.<strong><span style="font-weight:normal"><u></u><u></u></span></strong></font></i></p>
<p style="margin-left:0.5in;margin-bottom:0.0001pt;line-height:12pt;background-color:white"><font face="Calibri" size="3"><strong><i>Phase
III: Public Comments</i></strong><i><u></u><u></u></i></font></p>
<p style="margin-bottom:12pt;margin-left:0.5in;background-color:white"><i><font face="Calibri" size="3">After Board committee review of
the Staff report and the proposed charter amendments, the Board committee will
direct the opening of a Public Comment Forum. Upon completion of the Forum,
within 30 calendar days, staff will provide a report to the Board committee
summarizing the community feedback.<strong><span style="font-weight:normal"><u></u><u></u></span></strong></font></i></p>
<p style="margin-left:0.5in;margin-bottom:0.0001pt;line-height:12pt;background-color:white"><font face="Calibri" size="3"><strong><i>Phase
IV: Board Review</i></strong><i><u></u><u></u></i></font></p>
<p style="margin-bottom:12pt;margin-left:0.5in;background-color:white"><i><font face="Calibri" size="3">At the next available opportunity
after the delivery and publication of the staff report, the appropriate Board
committee shall review the proposed charter amendments, the staff report and
any community feedback and make a recommendation to the Board.<u></u><u></u></font></i></p>
<p style="margin-left:0.5in;margin-bottom:0.0001pt;line-height:12pt;background-color:white"><i><font face="Calibri" size="3">After
receiving a recommendation from the committee, the Board shall either:<u></u><u></u></font></i></p>
<p class="MsoNormal" style="margin-bottom:6pt;margin-left:1.25in;background-color:white"><font face="Calibri" size="3"><i>a.<span style="font-style:normal">
</span></i><i>Recognize the proposed charter
amendment by a simple majority vote; or<u></u><u></u></i></font></p>
<p class="MsoNormal" style="margin-bottom:6pt;margin-left:1.25in;background-color:white"><font face="Calibri" size="3"><i>b.<span style="font-style:normal">
</span></i><i>Reject the proposed amendment by
a supermajority (2/3) vote and provide a specific rationale for its concerns.<u></u><u></u></i></font></p>
<p class="MsoNormal" style="margin-bottom:6pt;margin-left:1.25in;background-color:white"><font face="Calibri" size="3"><i>c.<span style="font-style:normal">
</span></i><i>If neither above condition is
met, the Board will ask for further explanation of the proposed amendments by
the community.<u></u><u></u></i></font></p>
<p class="MsoNormal" style="margin-left:0.5in"><font face="Calibri" size="3"><i>In its review of the proposed
amendments, the ICANN Board may ask questions and otherwise consult with the
affected SG or Constituency. If it is not feasible for the Board to take action
on the proposed amendments after two meetings, the Board shall report to the
affected SG or Constituency the circumstance(s) that prevented it from making a
final action and its best estimate of the time required to reach an action.
That report is deemed an "action" under this process. If it is not
feasible for the Board to take action on the proposed amendments after four
meetings (or after a total of six scheduled meetings), the proposed community
amendments will be deemed effective.</i><i><u></u><u></u></i></font></p>
<p class="MsoNormal"><font face="Calibri" size="3"> </font></p>
<p class="MsoNormal"><font face="Calibri" size="3">The full process is posted on the
<a href="http://ICANN.GNSO.org" target="_blank">ICANN.GNSO.org</a> web site at the bottom of this page – <a href="http://gnso.icann.org/en/about/stakeholders-constituencies" target="_blank">http://gnso.icann.org/en/about<wbr>/stakeholders-constituencies</a>. A pdf version of the process can be viewed
and downloaded from this link - <a href="http://gnso.icann.org/en/about/stakeholders-constituencies/charter-amendment-process-28sep13-en.pdf" target="_blank">http://gnso.icann.org/en/about<wbr>/stakeholders-constituencies/c<wbr>harter-amendment-process-28sep<wbr>13-en.pdf</a><u></u><u></u></font></p>
<p class="MsoNormal"><font face="Calibri" size="3"> </font></p>
<p class="MsoNormal"><font face="Calibri" size="3">Staff is available to support, assist and/or advise the NCUC in any phase of the amendments process and I would be happy to further brief the committee about this
process and answer any questions anyone might have.<u></u><u></u></font></p>
<p class="MsoNormal"><font face="Calibri" size="3"> </font></p>
<p class="MsoNormal"><font face="Calibri" size="3">Best regards,<u></u><u></u></font></p>
<p class="MsoNormal"><font face="Calibri" size="3"> </font></p>
<p class="MsoNormal"><font face="Calibri"><font size="3">Rob Hoggarth<u></u><u></u></font></font></p>
</div><div style="font-size:14px;font-family:Calibri,sans-serif"><div><br></div><div><br></div></div></div>
</div><br></div></div>
<br></div></div>______________________________<wbr>_________________<br>
NCUC-EC mailing list<br>
<a href="mailto:NCUC-EC@lists.ncuc.org" target="_blank">NCUC-EC@lists.ncuc.org</a><br>
<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec" rel="noreferrer" target="_blank">http://lists.ncuc.org/cgi-bin/<wbr>mailman/listinfo/ncuc-ec</a><br>
<br></blockquote></div><span class=""><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div data-smartmail="gmail_signature">Farzaneh </div>
</font></span></div>
</blockquote></div><br></div></div>