1. Supplemental Notes

2. Best Practice Suggestions

1. SUPPLEMENTAL NOTES:

10 January 2012

1.2.A [Clarification on Supplemental Note 1.2 dated 15 November 2011] Documentation that describes the primary rules governing the management of the entity, which vary by jurisdiction, are examples of acceptable forms of “proof of legal establishment.” If no such documentation is required in the applying entity’s jurisdiction, the applicant may attach a statement indicating their jurisdictional requirements, including citation, in question 8(c).

15 November 2011

1.1 Proof of legal establishment is documentation of the applicant’s establishment as a specific type of entity in accordance with the applicable laws of its jurisdiction. All documents should be valid at the time of submission.

1.2 An example of acceptable form of valid proof of legal establishment is Articles of Incorporation. As documentation may vary by jurisdiction, ICANN has built flexibility into the program to accommodate documentations from various jurisdictions.

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.

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.