<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Thanks to Bill and Mary for this helpful information.<div><br></div><div>I agree that we should advocate for maintaining the diversity requirements on principal, even if the other SG's won't go along with them in the end.</div><div><br></div><div>I also agree that a preclusion against councilors on the review team seems a bit harsh and reactive to encode in the charter as a rule. Although I agree we'd likely want to choose someone who isn't a councilor - simply for workload issues, we don't need a rule forbidding us from making the choice of a councilor on the review team.</div><div><br></div><div>I'd like to encourage NCSG members to consider applying for membership on this team. It is important to get the non-commercial perspective into the Openness and Accountability Review Team so we should have a number of good candidates to provide to the GNSO and to choose from ourselves. </div><div><br></div><div>On how to select the NCSG candidates (at least 1 primary and 2 alternates?) Given the practical realities of holding a global online election in less than a week, a better option for selecting these candidates may be for the NCSG/NCUC Executive Committees and GNSO Councilors to appoint the candidates to the GNSO based upon who applies for the Review Team via NCSG. Do we know by when NCSG candidates would need to throw their hat in the ring?</div><div><br></div><div>Thanks,</div><div>Robin</div><div><br></div><div><br><div><div>On Feb 11, 2010, at 3:20 PM, Mary Wong wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"> <div>Thanks for this, Bill - it's not your fault the process and details are so arcane and torturous!</div> <div> </div> <div>I see no reason why the diversity requirements/language should be struck. It's important - especially as ICANN goes into the first AoC review phase - to demonstrate both the need for as well as the existence (as far as possible) of diverse representation in the ICANN community.</div> <div> </div> <div>Equally I agree that Councillors should not be precluded in principle from being eligible for a Review Team, for the reasons you stated.</div> <div> </div> <div>I too would very much welcome members' opinions on the questions/issues raised by Bill before we go into the Council meeting on the 18th.</div> <div> </div> <div>Cheers</div> <div>Mary</div> <div> </div> <div> <div><strong><font color="#800080">Mary W S Wong</font></strong></div> <div>Professor of Law & Chair, Graduate IP Programs</div> <div>Franklin Pierce Law Center</div> <div>Two White Street</div> <div>Concord, NH 03301</div> <div>USA</div> <div>Email: <a href="mailto:mwong@piercelaw.edu">mwong@piercelaw.edu</a></div> <div>Phone: 1-603-513-5143</div> <div>Webpage: <a href="http://www.piercelaw.edu/marywong/index.php">http://www.piercelaw.edu/marywong/index.php</a></div> <div>Selected writings available on the Social Science Research Network (SSRN) at: <a href="http://ssrn.com/author=437584">http://ssrn.com/author=437584</a></div><br><br>>>> </div> <table style="MARGIN: 0px 0px 0px 15px; FONT-SIZE: 1em" border="0" bgcolor="#f3f3f3"> <tbody> <tr> <td> <div style="BORDER-LEFT: #050505 1px solid; PADDING-LEFT: 7px"> <table style="FONT: 8pt Tahoma" bgcolor="#f3f3f3"> <tbody> <tr valign="top"> <td><strong>From: </strong></td> <td>William Drake <<a href="mailto:william.drake@GRADUATEINSTITUTE.CH">william.drake@GRADUATEINSTITUTE.CH</a>></td></tr> <tr valign="top"> <td><strong>To:</strong></td> <td><<a href="mailto:NCUC-DISCUSS@listserv.syr.edu">NCUC-DISCUSS@listserv.syr.edu</a>></td></tr> <tr valign="top"> <td><strong>Date: </strong></td> <td>2/11/2010 8:30 AM</td></tr> <tr valign="top"> <td><strong>Subject: </strong></td> <td>Re: AoC Accountability and Transparency Review Team selections</td></tr></tbody></table>Hi, <div><br></div> <div>Thanks Avri for passing along Chuck's message to SG chairs to get this started. As chair of the council drafting team that assembled the proposed process I guess it falls to me to walk through the details. Looong and somewhat complicated message follows, so get comfortable...</div> <div><br></div> <div>As members will recall, in December ICANN released an Affirmation Reviews Requirements and Implementation processes Draft Proposal <a href="http://www.icann.org/en/reviews/affirmation/affirmation-reviews-draft-proposal-26dec09-en.pdf">http://www.icann.org/en/reviews/affirmation/affirmation-reviews-draft-proposal-26dec09-en.pdf</a> that envisioned, inter alia, very small review teams carrying out the Affirmation of Commitments requirements. NCUC/SG members expressed concern about the staff proposal to limit GNSO participation to one or less representative per team, a concern that was shared by other SGs and thus incorporated into the council response filed in the public comment period <a href="http://forum.icann.org/lists/affrev-draft-processes/msg00008.html">http://forum.icann.org/lists/affrev-draft-processes/msg00008.html</a>, which we discussed a few weeks back on this list. We do not know the answer yet as to how many GNSO reps will be on the first review team, for Accountability and Transparency. However, there's reason to believe that the number will be raised to at least two, and the council has proceeded on that assumption. </div> <div><br></div> <div>ICANN announced its call for applicants <a href="http://www.icann.org/en/announcements/announcement-03feb10-en.htm">http://www.icann.org/en/announcements/announcement-03feb10-en.htm</a> before the GNSO or other SO/ACs had had a chance to determine how many names they would put forward, whether they wanted to set any additional qualification requirements for candidates, or how to structure their nomination processes. In addition, ICANN proposed a time line for submissions that was very short and utterly unworkable. The council drafting team therefore asked for an extension and managed to get a few more days, so now we have a timeline that is merely potentially unworkable. Anyway, this is why, when someone declared interest on the list the other day in being nominated, I suggested holding off until the process of being nominated by GNSO was clearer and we knew when applications would be due. The latter point is now settled; the application deadline is now 22 February. The former is now clearer, but there could be process revisions.</div> <div><br></div> <div>In order to give the Selectors sufficient options and to offer interested parties sufficient opportunities to participate, the drafting team decided to propose that the GNSO nominate up to six people, from which the Selectors (the GAC chair and chair of the Board) will pick, hopefully at least two. It was initially suggested in the drafting team that these all be selected by a majority vote of both houses' councilors, but as this could have resulted in a given SG (including us) not getting any, I counter-proposed allocating one fixed slot to each SG, reserving one slot for NCAs and others who don't self-identify with a given SG, and leaving one slot open to contention by anyone, including SG candidates. The latter two would be selected by a majority vote of both houses' councilors. This is the formula that was included in the drafting team's process proposal submitted yesterday to the council for a vote in its 18 February meeting. </div> <div><br></div> <div>In short then, the proposed nomination process (with arrows for action items) is as follows:</div> <div><br></div> <div>1. Each SG will select one nominee for a fixed allocation slot.</div> <div><br>2. Up to two additional nominees will be selected by a simple majority vote of each house. Again, one slot will be open to applicants of any kind, while the other slot will be reserved for candidates who do not self-identify with any particular stakeholder group, including NomCom appointees. (In the event that more than two candidates receive at least a simple majority from each house, ties will be broken as follows, in the order presented: geographical and/or gender diversity; and the total votes received.)</div> <div><br></div> <div>=> Hence, NCSG will need to select one person who'd definitely be included in the pool of nominees submitted to the Selectors. And we can also submit candidates for Council consideration in a competitive vote for the open to anyone slot. Council needs to decide how many candidates a SG can submit for that; some in the drafting team were thinking up to two, and that's what Chuck put in brackets in the message to SG chairs. If that's what happens in the 18 February meeting, then we will want to identify up to three names, a primary for the fixed slot and two competitors for the open slot. If instead the council decides on a larger number, or no limitations, then NCSG could pick more for the latter.</div> <div><br></div> <div>3. Some in the drafting team were concerned that if the Council did opt for a larger number, or no limitations, the council could be swamped with applications its member wouldn't have time to read carefully before the two houses vote. They therefore suggested that there be an Evaluation Team comprising one Councilor from each stakeholder group plus one NomCom appointee to assess the applications for the two voted slots and report to the Council. (the original idea was that the ET would actually rank applicants, but we decided not to specify ex ante how they'd proceed...will depend on the pool etc) Personally, I'm not clear that this additional machinery is needed since Council will probably limit the number for the open slot to something manageable, and even if it doesn't, SGs will probably vote their preferences irrespective of any ET advice. Also quite unclear is whether there will actually be time for this exercise. But as part of the compromising process this was left in for now. Hence, under the current plan, somehow/sometime prior to the vote the ET will assess the applications and somehow identify what it thinks are most plausible ones, which the Council can take under advisement if it likes.</div> <div><br></div> <div>=> Assuming we stick with this plan, NCSG therefore will need to select one person to represent it on the Evaluation Team.</div> <div><br></div> <div>A major bone of contention in the drafting team concerned diversity requirements. The language I drafted is pretty tame but apparently not tame enough, as it was supported by half the team and opposed by the other half. We agreed to leave the language in the plan that Council will vote on, but it is expected that CSG and perhaps the other industry SGs will propose an amendment to strike it from the plan. The language is as follows:</div> <div><br>3. Unless the applicant pool does not allow, no more than two nominees should come<br>from the same geographical region.<br>4. Unless the applicant pool does not allow, nominees must not all be of the same<br>gender, and the distribution between genders should be no greater than two-thirds to<br>one-third.<br>5. If the diversity goals in points 3 and 4 above are not achieved in the initial round of<br>selections, the Evaluation Team will consult with the stakeholder groups and<br>NomCom appointees to review the candidate pool, and then present to the Council an<br>alternative mix that would meet the goals. The Council would vote on the new list,<br>with a simple majority of both houses required for acceptance. If the vote fails, the<br>cycle will repeat until there is a successful outcome.<br><br></div> <div>=> It would be helpful if NCSG members could weigh in and provide our Councilors with input on how to approach this in the meeting on the 18th. The options are a) propose an amendment with stronger diversity language, which definitely will not pass, or weaker language (but why would we); b) support or oppose any amendment to strike this language from the plan; and c) if the language is struck, support or oppose the motion adopting the plan. I made clear in the drafting team that I will oppose an amendment to strike and will not vote for the final plan if it is (would be interesting to vote against a motion I made, but whatever), and speculated that some if not all other NCSG Councilors might do the same, in which case GNSO would be adopting its AoC process on a divided vote, which would be notably bad optics etc. But I don't know for sure how everyone feels about this.</div> <div><br></div> <div>=> NCSG members should be aware that there will probably be another amendment proposed by CSG and perhaps other industry SGs. This would be to make Councilors ineligible for nomination to review teams. Here too the drafting team was split 50/50 along the same lines as above. While one could argue that a Councilor might be hard pressed to handle both positions, thus of us who oppose restrictions see them as contrary to the AOC language, anti-democratic (people should be free to stand, and free to vote for whomever they like), a bit condescending (candidates presumably can assess their own ability to do the work or not), and likely to preclude valuable knowledge from being brought into the RTs. If Councilors don't think someone can handle the work, despite what they say, they should simply vote against the person, IMHO. Anyway, we might want to talk about this and how to vote on such an amendment.</div> <div><br></div> <div>The above all pertains to the nomination process. Moving on, the Council also wanted to add additional, GNSO-specific requirements on applicant qualifications to the generic ones listed by ICANN. These too are covered in the process plan. Some of them are kind of copy editorial (things ICANN might have specified but didn't), some are legalize of interest to corporate lawyers/reps, and some are of general import to applicants like NCSGers. I'll just mention the latter:</div> <div><br></div> <div>j. Applicants interested in being considered for endorsement by the GNSO must also<br>include in their submission to ICANN the following information:</div> <div><br></div> <div>[snip]</div> <div><br></div> <div>• An attestation that the applicant is able and willing to commit at least ten<br>hours per week during the review period, in addition to participating in the<br>planned face to face and/or teleconference review team meetings;</div> <div>• A two to three paragraph statement about the applicant’s knowledge of the<br>GNSO community and its structure and operations, and any details of his/her<br>participation therein; or<br>• In the event that an applicant has not been involved in the GNSO community,<br>a two to three paragraph description of his/her qualifications that would be of<br>relevance to the accountability and transparency review team.</div> <div><br></div> <div>=>Anyone from NCSG thinking of applying should therefore begin thinking about how they'd answer these questions, maybe draft some text. Again though, this is not final until the Council votes the 18th, and maybe the wording will change a little. So I'd suggest holding off on finalizing and submitting an application until the 19th earliest, remembering again that the deadline for submission is just a few days later, the 22nd. Tight window. Alas, just one of them.</div> <div><br></div> <div><br></div> <div>Here's an overview of the whole time line, with action items:</div> <div><br></div> <div>13-22 February </div> <div>*NCSG Councilors have to decide how to vote on the possible amendments to the plan, and on the plan as a whole, in Council 18 February. We might also want to revisit the utility of the Evaluation Team, in the event that Council caps SG apps for the open slot at two.</div> <div>*Potential candidates should work their applications and preferably announce their intention to stand.</div> <div>*NCSG should define the process by which it will make its selections; the earlier the better. Avri will be getting back to everyone to start that conversation.</div> <div><br></div> <div>22 February </div> <div>Applications due at ICANN</div> <div><br></div> <div>23-24 February (depending on whether the special Council meeting to vote is scheduled for 25 or 26 February)</div> <div>*Once all the applications have beens sent to ICANN and then forwarded from there to the GNSO Secretariat and then on to the NCSG, we will need to make our selections, basically in one to two days. This timeline may make it difficult to conduct an all-member election; we'd need to receive and distribute all applications, everyone would have to read and judge them, then the election machinery would have to be implemented, all at lightening speed. Another option might be for people to express views on the list and then the final decision on how to vote in Council is made by the policy comm & Councilors taking those views into account. An election is obviously preferable in principle, whether it's doable in practice is something we need to think through.</div> <div><br></div> <div>24 or 25 February (depending per above)</div> <div>*NCSG would then:<br>a. Endorse one [primary] candidate [and up to two alternates] from the applications received and notify the GNSO Secretariat of the same. [At least one alternate must be of different gender and from a different geographic region from the primary candidate.]<br>b. Provide direction for their Councilors regarding what candidates they should endorse for the two open endorsements described in item 2 above.</div> <div><br>24 or 25 February </div> <div>*Having received nominations from the SGs, the Evaluation Team would somehow do a lightening assessment of their candidates plus those for the unaffiliated slot and make a rec to Council </div> <div><br></div> <div>25 or 26 February Council has a special meeting to vote on the two open slots</div> <div>*If the result of this first round exercise is inadequate gender and geographic diversity, the Evaluation Team would consult with SGs and others involved and try to work out a compromise that meets the requirements listed above</div> <div><br></div> <div>1 March</div> <div>The Council notifies the Selectors of its nominations</div> <div><br></div> <div>Week of Nairobi meeting or just after</div> <div>*Selectors announce the RT's composition</div> <div><br></div> <div>And then the fun begins for RT members (see the timeline in the above mentioned ARR implementation plan draft)</div> <div><br></div> <div>This is all clear, right? :-) Obviously, it's a bit baroque, the time line is insanely compressed, and some bits (IMO the ET assessment, for which there's just no time) are problematic. But that's where things stand now.</div> <div><br></div> <div>If anyone has any questions I can try to clarify, probably I've botched the explanation of something....</div> <div><br></div> <div><br></div> <div> <div>Oh, and the relevant documents are:</div> <div><br></div> <div>Motion on the Proposed Process for GNSO Endorsements</div> <div><a href="https://st.icann.org/gnso-council/index.cgi?18_february_2010_motions">https://st.icann.org/gnso-council/index.cgi?18_february_2010_motions</a></div> <div><br></div>AoC DT Action Plan for Development of GNSO Endorsement of RT Volunteers<br> <div><a href="http://gnso.icann.org/drafts/gnso-endorsement-volunteers-action-plan-10feb10-en.pdf">http://gnso.icann.org/drafts/gnso-endorsement-volunteers-action-plan-10feb10-en.pdf</a></div> <div><br></div> <div>Proposed Process for GNSO Endorsement of Nominees to the Affirmation of Commitments Accountability and Transparency Review Team</div> <div><a href="http://gnso.icann.org/drafts/gnso-endorsement-nominees-process-proposal-10feb10-en.pdf">http://gnso.icann.org/drafts/gnso-endorsement-nominees-process-proposal-10feb10-en.pdf</a></div></div> <div><br></div> <div><br></div> <div>Best,</div> <div><br></div> <div>Bill</div> <div><br> <div> <div>On Feb 11, 2010, at 7:03 AM, Avri Doria wrote:</div><br class="Apple-interchange-newline"> <blockquote type="cite"> <div style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space"> <div><br></div>One of the Issues for the meeting on 17 Feb <div><br></div> <div>a.</div> <div><br> <div><br> <div>Begin forwarded message:</div><br class="Apple-interchange-newline"> <blockquote type="cite"> <div style="MARGIN: 0px"><span style="FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><b>From: </b></span><span style="FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium">"Gomes, Chuck" <<a href="mailto:cgomes@verisign.com">cgomes@verisign.com</a>><br></span></div> <div style="MARGIN: 0px"><span style="FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><b>Date: </b></span><span style="FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium">11 February 2010 01:01:57 GMT+01:00<br></span></div> <div style="MARGIN: 0px"><span style="FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><b>To: </b></span><span style="FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium">"David W. Maher" <<a href="mailto:dmaher@pir.org">dmaher@pir.org</a>>, "Mason Cole" <<a href="mailto:masonc@snapnames.com">masonc@snapnames.com</a>>, "Avri Doria" <<a href="mailto:avri@acm.org">avri@acm.org</a>>, "J. Scott Evans" <<a href="mailto:jscottevans@yahoo.com">jscottevans@yahoo.com</a>>, "Marilyn Cade" <<a href="mailto:marilynscade@hotmail.com">marilynscade@hotmail.com</a>>, <<a href="mailto:secretariat@ispcp.info">secretariat@ispcp.info</a>>, <<a href="mailto:KnobenW@telekom.de">KnobenW@telekom.de</a>>, "Jaime B Wagner" <<a href="mailto:j@bwagner.com.br">j@bwagner.com.br</a>><br></span></div> <div style="MARGIN: 0px"><span style="FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><b>Cc: </b></span><span style="FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium">Glen de Saint Géry <<a href="mailto:Glen@icann.org">Glen@icann.org</a>>, <<a href="mailto:gnso-arr-dt@icann.org">gnso-arr-dt@icann.org</a>><br></span></div><br> <div> <div><font size="2" face="Arial"><span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"><font size="3"><span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"> <div style="MARGIN: 0in 0in 0pt"><b style="mso-bidi-font-weight: normal"><span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"><font face="Times New Roman">Message to SG <span class="700403323-10022010">Chairs </span><span class="700403323-10022010">and Constituency Leaders</span></font></span></b></div><p style="MARGIN: 0in 0in 0pt" class="MsoNormal"><font face="Times New Roman"></font> </p> <div style="MARGIN: 0in 0in 0pt"><font face="Times New Roman">A GNSO Council motion has been made and seconded for action on 18 February to <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">approve a plan whereby the GNSO may endorse up to six volunteers for the 2010 Affirmation of Commitments Accountability and Transparency Review Team as follows:</span></font></div> <div style="TEXT-INDENT: -0.25in; MARGIN: 0in 0in 0pt 0.5in"><font face="Times New Roman"><span style="mso-list: Ignore">1.<span style="FONT: 7pt 'Times New Roman'"> </span></span><span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Each stakeholder group will</span> select one nominee.<span style="mso-spacerun: yes"> </span></font></div> <div style="TEXT-INDENT: -0.25in; MARGIN: 0in 0in 0pt 0.5in"><font face="Times New Roman"><span style="mso-list: Ignore">2.<span style="FONT: 7pt 'Times New Roman'"> </span></span>Up to two additional nominees will be selected by a simple majority vote of each house.<span style="mso-spacerun: yes"> </span>One of these slots will be reserved for candidates who do not self-identify with any particular stakeholder group, including NomCom appointees.</font></div><p style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto" class="MsoNormal"><span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"><font face="Times New Roman"></font></span> </p> <div style="MARGIN: 0in 0in 0pt"><span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"><font face="Times New Roman">If this plan is approved, all applications from volunteers requesting GNSO endorsement would be forwarded to the SGs as soon as possible after the application period closes on 22 February, and not later than 24 or 25 February (depending on whether a special Council meeting is scheduled for 25 or 26 February), the SGs would be requested to:</font></span></div> <div style="TEXT-INDENT: -0.25in; MARGIN: 0in 0in 0pt 0.5in"><font face="Times New Roman"><span style="mso-list: Ignore">a.<span style="FONT: 7pt 'Times New Roman'"> </span></span><span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Endorse one [primary] candidate [and up to two alternates] from the applications received and notify the GNSO Secretariat of the same.<span style="mso-spacerun: yes"> </span>[At least one alternate must be of different gender and from a different geographic region from the primary candidate.]</span></font><a style="mso-footnote-id: ftn1" title="" href="outbind://79/#_ftn1" name="_ftnref1"><span class="MsoFootnoteReference"><span style="mso-special-character: footnote"><span class="MsoFootnoteReference"><span style="FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">[1]</span></span></span></span></a></div> <div style="TEXT-INDENT: -0.25in; MARGIN: 0in 0in 0pt 0.5in"><font face="Times New Roman"><span style="mso-list: Ignore">b.<span style="FONT: 7pt 'Times New Roman'"> </span></span><span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Provide direction for their Councilors regarding what candidates they should endorse for the two open endorsements described in item 2 above</span>.</font></div><p style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto" class="MsoNormal"><font face="Times New Roman"></font> </p> <div style="MARGIN: 0in 0in 0pt"><font face="Times New Roman">With the understanding that the proposed plan could be amended on 18 February, anything you can do to prepare for the above tasks and facilitate success of the endorsement process will be greatly appreciated.<span style="mso-spacerun: yes"> </span>As you can tell, the SGs and the Council will have extremely short turn-around times for the above tasks.</font></div><p style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto" class="MsoNormal"><font face="Times New Roman"></font> </p> <div style="MARGIN: 0in 0in 0pt"><font face="Times New Roman">If you have any questions, please let me know.</font></div><p style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto" class="MsoNormal"><font face="Times New Roman"></font> </p> <div style="MARGIN: 0in 0in 0pt"><font face="Times New Roman">Chuck Gomes</font></div> <div style="mso-element: footnote-list"><br clear="all"><font face="Times New Roman"> <hr align="left" size="1" width="33%"> </font> <div style="mso-element: footnote" id="ftn1"> <div style="MARGIN: 0in 0in 0pt"><a style="mso-footnote-id: ftn1" title="" href="outbind://79/#_ftnref1" name="_ftn1"><span class="MsoFootnoteReference"><span style="mso-special-character: footnote"><span class="MsoFootnoteReference"><span style="FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">[1]</span></span></span></span></a><font size="2" face="Times New Roman"> Bracketed text was added by the Council Chair and not approved by the GNSO DT that developed the proposed endorsement process.<span style="mso-spacerun: yes"> </span>The GNSO community and the GNSO Council will have just 2 to 3 days to review applications from volunteers requesting GNSO endorsement, so if the SGs can provide the two alternates as described in addition to a primary candidate, it could greatly facilitate Council final action on the endorsements on either 25 or 26 February.</font></div></div></div></span></font></span><span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"><font face="Times New Roman"><font size="3"><span class="700403323-10022010"></span></font></font></span> <div style="mso-element: footnote-list"> <div style="mso-element: footnote" id="ftn1"><span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"><font face="Times New Roman"><font size="3"><span class="700403323-10022010"></span></font></font></span> </div> <div style="mso-element: footnote"><span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"><font face="Times New Roman"><font size="3"><span class="700403323-10022010">P.S. - In addressing this message, I realized that I was not sure who the NCSG and CSG chairs are so I included constituency leaders as best as I could determine so as to get this message out as soon as possible. If I missed anyone, please forward this message right away.</span></font></font></span></div></div></font></div></div></blockquote></div><br></div></div></blockquote></div><br> <div>***********************************************************<br>William J. Drake<br>Senior Associate<br>Centre for International Governance<br>Graduate Institute of International and<br> Development Studies<br>Geneva, Switzerland<br><a href="mailto:william.drake@graduateinstitute.ch">william.drake@graduateinstitute.ch</a><br>www.graduateinstitute.ch/cig/drake.html<br>***********************************************************<br><br></div><br></div></div></td></tr></tbody></table></blockquote></div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div><br class="Apple-interchange-newline"><br class="khtml-block-placeholder"></div><div><br class="khtml-block-placeholder"></div><div>IP JUSTICE</div><div>Robin Gross, Executive Director</div><div>1192 Haight Street, San Francisco, CA 94117 USA</div><div>p: +1-415-553-6261 f: +1-415-462-6451</div><div>w: <a href="http://www.ipjustice.org">http://www.ipjustice.org</a> e: <a href="mailto:robin@ipjustice.org">robin@ipjustice.org</a></div><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline"> </div><br></div></body></html>