Regarding the GNSO endorsement of AoC applicants I have to correct what I've said yesterday. Sorry, I was a little bit confused about the process and may have confused others, too. The status is as follows: Timeline suggested by ICANN: October 1st - beginning activities RTs 2 and 4 September 20 - final list of candidates delivered to Selectors for selection of members August 1st - closing of the application period June 25 (end Bxl meeting) - launching of call for applicants This means that the GNSO council has to vote on endorsement process prior to the Brussels meeting. The intention is to vote on June 10.
From CSG side the IPC (Kristina R.) and CBUC (Zahid J.) and myself are in the draftind team. Although IPC and CBUC did not actively participate there was not yet any intervention from their side regarding the process intented. I myself think that the process is applicable and - in case 4 slots should be allocated to the GNSO - the best we could achieve.
I'd like to suggest that you'd comment on the process and the motion attached asap. E.g. the motion could be amended in parts, for example not to cover all futere RT's rather than RT's 2 and 4. Apologies for the confusion! Draft motion: Whereas, in furtherance of ICANN's responsibilities under the Affirmation of Commitment (AOC), the GNSO Council formed a drafting team to develop a process to endorse volunteers to serve on the each of the AOC review teams; Whereas, the AOC Review Requirements Drafting team (AOC-RR Drafting Team) has proposed a process to facilitate such GNSO Council endorsements; Whereas, the GNSO Council desires to adopt the AOC-RR Drafting Team proposed process for all future AOC review team selections; NOW THEREFORE, BE IT: Resolved, that the GNSO Council hereby approves the Endorsement Process described in the attached document <insert link to document>; Resolved further, that the GNSO Council should implement the Endorsement Process for all future AOC review team selections, including the "WHOIS Policy" and the "Security, Stability, and Resiliency of the DNS" Review Teams; and RESOLVED FURTHER, ICANN Staff is requested to post and distribute the Endorsement Process as widely as possible to all GNSO related groups in an effort to inform qualified applicants of the important work of the "WHOIS Policy" and "Security, Stability and Resiliency of the DNS" review teams. The Draft process is included in the document attached. Regards Wolf-Ulrich _____ Von: owner-ispcp@gnso.icann.org [mailto:owner-ispcp@gnso.icann.org] Im Auftrag von Tonyarholmes@btinternet.com Gesendet: Dienstag, 1. Juni 2010 23:26 An: ispcp@icann.org Betreff: [ispcp] ISPCP issues All Today conference call covered the following issues. 1. Response to Rod Beckstrom request to the ISPCP on security issues. The proposed draft was discussed. The plan is to forward the final version to ICANN tomorrow. The draft is attached. Please respond promptly with any final comments. 2. GNSO Priorities The proposed list of priorities will be discussed during next week's GNSO call. Please supply any comment to Wolf-Ulrich Knoben and Jaime Wagner in advance of that meeting. 3. GNSO endorsement of AoC applicants. Clarity was sought between the overall selection process and the role of the GNSO. It was noted that the GNSO is likely to be endorsing just 4 slots, instead of 6. The intention is to finalise the selection process ASAP, but this will still allow discussion to take place at the Brussels meeting before final agreements are in place. 4. Implementation of new gTLDs Concern has been voiced by some parties over the process where IDN applications are evaluated for string similarity against gTLDs in other scripts. Arguments have been made that in some cases the degree of confusion arising may greatly differ and in some cases where it is minor, a different approach may be considered. This will be discussed further at the Brussels meeting. 5. Date of next call Thursday 10th June at 15.00 UTC The agenda for the ISPCP meeting will be determined on this call.