1. Supplemental Notes

2. Best Practice Suggestions

1. SUPPLEMENTAL NOTES:

16 December 2011

1.1 IDN tables, particularly "top level tables", should be submitted in a machine-readable format suitable for ICANN or another party to read them programmatically. A format such as the model format described in Section 5 of RFC 4290 would be ideal. The format used by RFC 3743 is an acceptable alternative. For variant generation algorithms that are more complex (such as those with contextual rules) and cannot be expressed using these table formats, it should be specified in a manner that could be re-implemented programmatically by ICANN. Ideally, for any complex table formats, a reference code implementation should be provided in conjunction with a description of the generation rules.

2. BEST PRACTICE SUGGESTIONS:

16 December 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.