[council] Feedback requested - CCT Review GNSO Requirements

[Marika Konings <marika.konings@xxxxxxxxx>]

Dear All,

As also mentioned in the chat, it would be helpful to know whether the Council 
supports the GNSO Council Requirements as set out on page two and for your 
convenience also copied here below so that staff can reach out to the 
candidates looking for GNSO endorsements to provide this information so that it 
can be received well in time for the next GNSO Council meeting. With regards to 
the time commitment which was flagged as one of the items to be discussed, I 
checked with my colleagues and they estimate that the following is required:

  *   Weekly meetings of around 1-2 hours each
  *   F2F meetings at ICANN meetings
  *   Possibly 1-2 F2F meetings (total) outside the ICANN meetings during 2016
  *   As the RT gets ready to publish its Final Report, activity may increase 
to about 5 hours a week, but that may only be for a couple of weeks.
  *   The hope is that the Final Report is published by the end of 2016, 
although it could take longer to get through all the issues

In light of that, maybe the requirement could be revised as follows:

An attestation that the applicant is able and willing to commit an estimated 
average of two hours per week during the review period, which may increase to 5 
hours per week towards the final stages of the project, in addition to 
participating in face to face review team meetings.

Please share any comments or edits you may have as soon as possible as we would 
like to get back to the candidates as soon as possible to collect this 
information if the Council agrees that this required information for the 
endorsement process.

Best regards,

Marika

Additional GNSO Requirements:

A person seeking GNSO endorsement must include the following information in the
application:


·      The applicant's full name, title, contact information and employer;

·      The ICANN Geographic Region(s) in which the applicant is a citizen and a 
resident;

·      Identification of the GSNO stakeholder group, if any, to which the 
applicant feels most closely affiliated;

·      An attestation that the applicant is able and willing to commit an 
estimated average of about ten hours per week during the review period, in 
addition to participating in face to face review team meetings;

·      Identification of any financial ownership or senior 
management/leadership interest of the applicant in registries, registrars or 
other entities that are stakeholders or interested parties in ICANN or any 
entity with which ICANN has a transaction, contract, or other arrangement;

·      Indication of whether the applicant would be representing any other 
party or person on the review team and, if so, identification of that party or 
person;

·      A two to three paragraph statement about the applicant's knowledge of 
the GNSO community's structures and operations and any participation therein;

·      A one to two paragraph statement about the applicant's specialized 
technical or other expertise of direct relevance to the responsibilities of the 
review team in question.

From: <owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx>> on 
behalf of Marika Konings 
<marika.konings@xxxxxxxxx<mailto:marika.konings@xxxxxxxxx>>
Date: Wednesday 18 November 2015 09:57
To: Council <council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>>
Subject: FW: [council] Agenda item 8 - GNSO Candidates for CCT Review Team

Dear All,

On behalf of Volker Greimann, please find attached the original process that 
GNSO Council used for its endorsements for the ATRT2 as well as a modified 
version that has been developed by Wolf-Ulrich Knoben that the Council may wish 
to consider for the purpose of the CCT endorsements. Specific items that will 
need to be discussed by the GNSO Council have been highlighted in yellow.

Best regards,

Marika