What are the components of Application Evaluation?

Application Evaluation includes one mandatory evaluation for all applications. In addition, one or more conditional evaluations may be necessary, depending on the nature of the applied-for string and the applicant's specific needs.

1. Mandatory Evaluation:
   1. Registry Service Provider (RSP) Review: Verifies that every applicant selects an ICANN-approved RSP to provide the critical technical services necessary for the operation of the applied-for gTLD string, and ensures that the selected RSP is willing and able to support the applied-for string.
2. Conditional Evaluations:
   1. Geographic Names Review: This pertains only to applied-for strings identified as Geographic Names as a result of String Evaluation. This evaluation verifies whether the applied-for string meets all criteria as a Geographic Name and checks that all required supporting documentations are valid.
   2. Reserved Names Review: This pertains only to applied-for strings identified as Reserved Names during the pre-submission string validations. This evaluation verifies whether the correct entity has applied for the name and checks that all required supporting documentations are valid.
   3. .Brand TLD Eligibility Evaluation: This pertains only to applied-for strings designated by applicants as .Brand TLDs. This evaluation determines whether such strings qualify for a .Brand TLD designation.
   4. Variant String Evaluation: This pertains only to applications seeking allocatable variant strings associated with an applied-for primary string or an existing gTLD. Applicants must justify the need for each applied-for variant string.
   5. Name Collision High-Risk Mitigation Plan Evaluation: This pertains only to applied-for strings identified as high risk for Name Collision as a result of Name Collision Initial Assessment and Temporary Delegation. This evaluation assesses whether the applicant's proposed mitigation plan adequately addresses Name Collision concerns in order for the application to proceed in the program.
   6. Registry Operator Code of Conduct Exemption Evaluation: This pertains only to applicants that plan to operate the applied-for strings exclusively for use by themselves or their Affiliates (as defined in the Registry Agreement) and therefore request an exemption from the Registry Operator Code of Conduct in Specification 9 of the Base Registry Agreement.
   7. Registry Commitments Evaluation (RCE): This pertains to all Community Applications and any application proposing Registry Voluntary Commitments (RVCs) for inclusion in the Registry Agreement. This evaluation ensures the proposed RVCs and Community Registration Policies meet the criteria for inclusion in the Registry Agreement.