Draft Organization and Work Plan
Team (name and members) |
Risks and issues |
Risk sources, risk mitigators, interviewees, interlocutors |
Terms of Reference |
Governance |
Maintaining clear processes |
Mandate, bylaws, mission creep |
|
Implementation and Fulfillment of Responsibilities |
ccTLD and gTLD registry and registrar operations, contracted parties |
Registries/registrars |
|
Contingency |
Security threats, threat landscape |
|
|
Calendar considerations.
Scenario 1.
Work breakdown and planning done: March 17, published March 21
Teams go off to create interviews, questionnaires, inventories of documents to be requested and studied starting March 21.
Deadline for putting these forward for public comment: Singapore meeting of ICANN, June 19-24
Off for 45-day comment period, back during (Boreal) Summer.
Restart work, next deadline is 23-28 October 2011, ICANN meeting in Africa.
Desirable: to have a number of interviews done by this date, analyze in the ICANN meeting, continue.
This would allow for a draft report to be readied for the first ICANN meeting in 2012, March 11-16, 2012, Latin America.
Otherwise slide calendar one whole ICANN meeting.
Further considerations for San Francisco meeting:
Scope (for each team)
Budget (travel, other needs?)
DECIDE whether a consultant or other third party will be required; if so, start drafting Terms of Reference for contract, Request for Proposals
A list of people and organizations to interview which is not mechanically derived from the table (think John Klensin, Vinton Cerf, Paul Vixie, Bruce Schneier, Frederico Neves, Arbor Networks, Paul Twomey, Mike Roberts, KC Claffy...)
Boilerplate and substance re privacy, confidentiality, personal data protection, security for the Team's work, communications, archiving, etc.