Hi. On the call last Thursday, each of the topic leaders reported that a week or more will be needed to produce text. Also, it was reported that we will not get answers to some of our questions until the middle of April. This does not leave us much to talk about. Please use the time to get together with others working on your topic, proving clarification to the questions (see below), or writing. Staff reports that we should have a short list of potential technical writers will be provided to us in mid-April. So, we are on track to have a technical writer at the Brussels meeting in May. Russ
From: Jennifer Bryce <jennifer.bryce@icann.org> Subject: [Ssr2-review] New clarification request Date: March 28, 2019 at 7:54:49 AM EDT To: "ssr2-review@icann.org" <ssr2-review@icann.org>
Dear all,
Please see below for a new clarification request, and the 5 outstanding requests for clarification on questions asked to ICANN org.
New request: Review Team volunteers: Boban, Alain, Žarko Workstream: ICANN SSR Topic 2: Perform an assessment of ICANN's Business Continuity Management System.
Clarification requested: What is meant by “inter-org” dependencies? Which orgs? What is meant by “boundaries.” Does ICANN have documented boundaries and processes that have inter-org dependencies? Do they relate back to BC plans?
Outstanding requests: Review Team volunteers: Scott, Noorul Workstream: ICANN SSR Topic 4: Perform an assessment of how effectively ICANN has implemented its Security Incident Management and Response Processes to reduce (pro-active and reactive) the probability of DNS-related incidents.
Clarification requested: Can you please clarify if these questions are specific to the ICANN Managed Root Server or more generally for ICANN? Which certifications is ICANN pursuing for the organisation and staff? Which certifications and compliance frameworks has ICANN completed? Who are ICANN’s auditors, what audits are completed regularly?
Review Team volunteers: Eric, Denise, Norm, Boban Workstream: Future Challenges Topic: Coalescence of registrars/registry/backend operators for multiple TLDs
Clarification requested: Can you please provide further context behind the question or clarify the question? Has ICANN identified the issue of coalescence of registrars/registry operators in their risk management and what are the measures be taken? Are there any and if so, what are the control mechanisms for operational availability of the TLD’s?
Best, Jennifer