1. Supplemental Notes

2. Best Practice Suggestions

1. SUPPLEMENTAL NOTES

15 November 2011

1.1 It should be noted that critical registry functions are those specified in section 6 of Specification 10 of the Registry Agreement. Vital business functions are broader than critical registry functions and include those functions that are needed for a registry to be able to perform its operations and to meet its obligations under the Registry Agreement. Vital business functions are defined by the applicant in Question 39.

1.2 Applicants should describe how the proposed geo-diversity plan will support continued critical registry functions in the event of temporary outages. To score a “2 – exceeds requirements” the geo-diversity plan must support continued critical registry and vital business functions in the event of prolonged outages. For example, a single potentially disruptive event such as a natural disaster should not prevent the registry from meeting SLA obligations under the Registry Agreement. In addition, the applicant should consider and discuss likely threats for their respective geographic region(s).

2. BEST PRACTICE SUGGESTIONS:

15 November 2011

2.1 Applicants should read each evaluation question in its entirety, including the notes, criteria, and scoring text. The answer should address all criteria specified, and include detailed rationale demonstrating a thorough understanding of the criteria (i.e., show your work).

2.2 If acronyms are used, applicants should spell out the first instance, even if the acronyms represent a common term/product/service.

2.3 Applicants proposing to outsource a function or functions of their registry operations must address all criteria specified in each relevant question, and include detailed rationale demonstrating a thorough understanding of the criteria (i.e., show your work).

2.4 Simply providing a Curriculum Vitae (CVs/resume) will not be considered as demonstrating technical/operational capabilities nor does it necessarily establish “proof” that resources are on hand. The applicant should provide a detailed explanation of the resourcing plan and should including areas such as the resources required to manage/run a function, the skillset required, the hiring schedule, and so on. CVs may be used to augment this proposed resourcing plan.

2.5 If a policy/procedure is referenced in an answer, applicants should provide a summary of such policy/procedure. Applicants should not attach copies of the referenced policy/procedure, unless specifically requested.

2.6 If the applicant proposes custom developed software, the applicant should clarify the scope and the extent of the customization including the software development process. This clarification is meant to help evaluation panels understand the integrity of the customized software.

DISCLAIMER: This material is for information only and does not represent of all requirements and criteria that the applicant must satisfy. ICANN is not providing legal, financial, business or any other kind of advice. This material does not represent a modification to the Applicant Guidebook, or the terms and conditions to the new gTLD program. This material also does not represent a waiver of any ICANN policy, procedure or agreement. In the event that any information provided in this material appears to be inconsistent with any information published elsewhere by ICANN, please do not rely on this material without confirmation or clarification from ICANN.