Generic Top-Level Domain (gTLD) Registry Agreements

gTLD Registry Agreements establish the rights, duties, liabilities, and obligations ICANN requires of registry operators to run gTLDs.

Unsponsored TLD Agreement: Appendix U (.name)

ICANN | Unsponsored TLD Agreement: Appendix U (.name)
  ICANN Logo

Unsponsored TLD Agreement: Appendix U (.name)

(30 Jun 2001)


Evaluation of Concepts

Global Name Registry ("GNR") shall provide the following reports and related data to ICANN for use in its proof of concept evaluation. Such reports shall be provided according to the schedule described herein during the Term of the Registry Agreement. Capitalized terms shall have the meanings defined in the Registry Agreement and its Appendices. GNR shall provide the reports in hard copy and, to the extent feasible, in a common character-mapped electronic form.

The reports provided by GNR as described in this Appendix shall be subject to confidentiality restrictions according to categories described in Section 12.

1. Concept: Procedures for Maintaining Registry Stability and Fairness to Customers in the Launch of an Open TLD

1.1 Start-Up Phase1 Effectiveness - within 30 days after the end of the Start-Up Phase, GNR shall provide the following information and reports to ICANN.

1.1.1 Total number of Intellectual Property Namewatch Service ("NameWatch") registrations by day.

1.1.2 Total number of NameWatch registrations by week.

1.1.3 Total number of NameWatch initial registrations with registrant addresses in the regions described below:

1.1.3.1 Africa;

1.1.3.2 Asia Pacific;

1.1.3.3 Europe;

1.1.3.4 Latin America/Caribbean; and

1.1.3.5 North America.

1.1.4 Total number of ICANN-Accredited Registrars qualified to submit NameWatch registrations on each day during the Start-Up Phase.

1.1.5 Total number of NameWatch registrations during the Start-Up Phase under the sponsorship of each ICANN-Accredited Registrar.

1.1.6 Total number of Phase I Defensive Registrations by day.

1.1.7 Total number of Phase I Defensive Registrations by week.

1.1.8 Total number of Phase I Defensive Registrations with registrant addresses in the regions described below:

1.1.8.1 Africa;

1.1.8.2 Asia Pacific;

1.1.8.3 Europe;

1.1.8.4 Latin America/Caribbean; and

1.1.8.5 North America.

1.1.9 Total number of ICANN-Accredited Registrars qualified to submit Phase I Defensive Registrations on each day during the Start-Up Phase.

1.1.10 Total number of Phase I Defensive Registrations under the sponsorship of each ICANN-Accredited Registrar.

1.1.11 A description of significant technical difficulties encountered in operating during the NameWatch and Phase I Defensive Registration launches.

1.1.12 A report detailing the modifications and adjustments to the Registry Database during the NameWatch and Phase I Defensive Registration launches.

1.2 Dispute Resolution Mechanism - within 120 days after Live SRS Launch, GNR shall provide the following information and reports to ICANN.

1.2.1 A statement of the total number of challenges submitted to Phase I Defensive Registrations.

1.2.2 A tabulation of the number of Phase I Defensive Registrations subject to multiple Phase I Defensive Registration challenges (i.e. x Phase I Defensive Registrations were subject to exactly two challenges, y Phase I Defensive Registrations were subject to exactly three challenges, etc.).

1.2.3 A statement of how many Phase I Defensive Registrations sponsored by each Registrar were subject to at least one Phase I Defensive Registration challenge.

1.2.4 A breakdown by country of the registration offered by the domain-name holder of the number of successful and unsuccessful Phase I Defensive Registration challenges.

1.2.5 A statement, broken down by sponsoring registrar, of the number of Phase I Defensive Registrations involved in challenges where the Phase I Defensive Registrations holder failed to submit proof of a trademark registration corresponding to the Phase I Defensive Registration challenge after receiving notice of the challenge.

1.2.6 A statement, broken down by the region of the holder's address as described below, of the number of Phase I Defensive Registrations subject to successful challenges:

1.2.6.1 Africa;

1.2.6.2 Asia Pacific;

1.2.6.3 Europe;

1.2.6.4 Latin America/Caribbean; and

1.2.6.5 North America.

1.2.7 A statement, broken down by the region of the successful challenger's address as described below, of the number of Phase I Defensive Registrations subject to successful challenges:

1.2.7.1 Africa;

1.2.7.2 Asia Pacific;

1.2.7.3 Europe;

1.2.7.4 Latin America/Caribbean; and

1.2.7.5 North America.

1.2.8 A statement of the number of successful Phase I Defensive Registration challengers that did not register the challenged string (as either a domain name or SLD E mail address), broken down by priority of the challenger (i.e. x first-priority challengers chose not to register the challenged string; y second priority challengers were offered the opportunity to, but did not, register the challenged string, etc.).

1.2.9 A statement of the number of Phase I Defensive Registrations voluntarily cancelled.

1.2.10 A summary of the complaints received from Registrars regarding the challenges to Phase I Defensive Registration.

1.2.11 A description of significant technical difficulties encountered in connection with the Phase I Defensive Registrations.

1.2.12 A written evaluation of the overall effectiveness of Phase I Defensive Registrations.

1.3 Start-Up Phase - within 30 days after the end of the Start-Up Phase, GNR shall provide the following information and reports to ICANN.

1.3.1 Total initial domain name registration requests submitted by day.

1.3.2 Total initial domain name registration requests submitted by week.

1.3.3 Total initial domain name registration requests submitted with holder addresses in the regions described below:

1.3.3.1 Africa;

1.3.3.2 Asia Pacific;

1.3.3.3 Europe;

1.3.3.4 Latin America/Caribbean; and

1.3.3.5 North America.

1.3.4 Total number of ICANN-Accredited Registrars qualified to submit domain name registration requests on each day of the Start-Up Phase.

1.3.5 Total number of domain names registered during the Start-Up Phase under the sponsorship of each ICANN-Accredited Registrar.

1.3.6 A tabulation, by registrar, of the terms in years of Start-Up Phase domain name registration requests submitted to the random queue procedure.

1.3.7 A tabulation, by registrar, of the terms in years of Start-Up Phase domain name registration requests successfully filled by the random queue procedure.

1.3.8 Total initial SLD E-mail registration volume by day.

1.3.9 Total initial SLD E-mail registration volume by week.

1.3.10 Total initial Start-Up Phase SLD E-mail registration volume with holder addresses in the regions described below:

1.3.10.1 Africa;

1.3.10.2 Asia Pacific;

1.3.10.3 Europe;

1.3.10.4 Latin America/Caribbean; and

1.3.10.5 North America.

1.3.11 Total number of ICANN-Accredited Registrars qualified to submit SLD E-mail registrations on each day of the Start-Up Phase.

1.3.12 Total number of SLD E-mail names registered during the Start-Up Phase under the sponsorship of each ICANN-Accredited Registrar.

1.3.13 A tabulation, averaged by registrar, of the terms in years of Start-Up Phase SLD E-mail registration requests submitted to the random queue procedure.

1.3.14 A tabulation, averaged by registrar, of the terms in years of Start-Up Phase SLD E-mail registrations successfully filled by the random queue procedure.

1.3.15 Total number of registrants registering both a domain name and an SLD E-mail name (hereinafter "Dual Registrations").

1.3.16 Total number of Dual Registrations with holder addresses in the region described below:

1.3.16.1 Africa;

1.3.16.2 Asia Pacific;

1.3.16.3 Europe;

1.3.16.4 Latin America/Caribbean; and

1.3.16.5 North America.

1.3.17 Total number of registrants registering a domain name but not an SLD E-mail name.

1.3.18 Total number of registrants registering an SLD E-mail but not a domain name.

1.4 Operation Phase Effectiveness - within 120 days after the Live SRS Launch, GNR shall provide the following information and reports to ICANN.

1.4.1 Total number of SLD E-mail registrations made operational.

1.4.2 Total number of SLD E-mail registrations made operational, broken down by the holder's address in the regions described below:

1.4.2.1 Africa;

1.4.2.2 Asia Pacific;

1.4.2.3 Europe;

1.4.2.4 Latin America/Caribbean; and

1.4.2.5 North America.

1.4.3 Total number of domain name registrations resolved into the DNS.

1.4.4 Total number of domain name registrations resolved into the DNS, broken down by the holder's address in the regions described below:

1.4.4.1 Africa;

1.4.4.2 Asia Pacific;

1.4.4.3 Europe;

1.4.4.4 Latin America/Caribbean; and

1.4.4.5 North America.

1.4.5 A summary of the complaints received from registrars during the period of this report.

1.4.6 A description of significant technical difficulties encountered in operating during the period of this report.

1.5 Effectiveness of Land Rush Processing Periods. Within 30 days after the Live SRS Launch, GNR shall provide the following information and reports to ICANN.

1.5.1 A written report detailing the effectiveness of the random queue system during the Land Rush Primary Processing Period. Include such items as lessons learned during the process and methods of improvement.

1.5.2 For each round the random queue system was used in the Land Rush Primary Processing Period, as described in Appendix J:

1.5.2.1 the last date on which registrars were allowed to submit requests for registrations into their request queues for each round;

1.5.2.2 processing time required to process the combined random queue;

1.5.2.3 the names of the registrars submitting requests for registrations;

1.5.2.4 the number of registration requests submitted by each registrar;

1.5.2.5 the number of requests filled for each registrar;

1.5.2.6 the number of requests submitted by each registrar that were not filled because of a successful request processed in an earlier random queue;

1.5.2.7 the number of requests submitted by each registrar that were not filled because of a successful request processed earlier in the same random queue;

1.5.2.8 a tabulation showing the number of names subject to multiple requests in the combined random queue (i.e. x names were subject to exactly two requests, y names were subject to exactly three requests, etc.); and

1.5.2.9 a tabulation showing the number of names subject to multiple requests in each registrar's random queue (i.e. x names were subject to exactly two requests, y names were subject to exactly three requests, etc.).

1.5.3 A written report detailing the effectiveness of the random queue system during the Land Rush Secondary Processing Period. Include such items as lessons learned during the process and methods of improvement.

1.5.4 A written report detailing the effectiveness of the pseudo-code used for Land Rush Secondary Processing Period. Include such items as lessons learned during the process and methods of improvement.

1.5.5 For each round the random queue system was used in the Land Rush Secondary Processing Period, as described in Appendix J, containing the elements of items 1.5.2.1 to 1.5.2.9.

1.5.6 A tabulation, by registrar, of the total number of random queues submitted after the deadline for queue submissions during the Land Rush Primary Processing Period.

1.5.7 A tabulation by registrar, of the total number of random queues submitted after the deadline for queue submissions during the Land Rush Secondary Processing Period.

1.5.8 A tabulation, by registrar, of the total number of random queues submitted in an invalid or malformed format during the Land Rush Primary Processing Period.

1.5.9 A tabulation, by registrar, of the total number of random queues submitted in an invalid or malformed format during the Land Rush Secondary Processing Period.

1.6 Miscellaneous.

1.6.1 Within 30 days after the first anniversary of the Commencement-of-Service Date, provide a tabulation of the number of Start-Up Phase SLD E-mail registrations which were transferred to another holder during each month after the Commencement-of-Service Date.

1.6.2 Within 30 days after the first anniversary of the Commencement-of-Service Date, provide a tabulation of the number of Start-Up Phase domain name registrations which were transferred to another holder during each month after the Commencement-of-Service Date.

1.6.3 Within 30 days of learning of any lawsuit concerning the start-up activities in .name, please identify the lawsuit and provide a copy of the complaint or describe its allegations.

2. Concept: Procedures for Minimizing Abusive Domain-Name Registration Practices

No later than 120 days after the Commencement-of-Service Date, GNR shall provide to ICANN a Proof-of-Concept Report on Minimizing Abusive Registration Practices, with the following information.

2.1 Provide a written report detailing the effectiveness of the Phase I Defensive Registrations in limiting abusive registration practices. Include such items as lessons learned and methods of improvement.

2.2 Provide a written report detailing the effectiveness of the NameWatch Service in limiting abusive registration practices. Include such items as lessons learned and methods of improvement.

3. Concept: Introducing a Personal Name TLD as a Means of Effective Competition with a Dominant, Well-Financed TLD Such as .com

No later than one month after each anniversary date after the Commencement-of-Service Date, GNR shall provide to ICANN an Annual Proof-of-Concept Report on Effectiveness of Competition, with the following information:

3.1 Marketing Efforts

3.1.1 Total GNR expenditures for marketing the .name TLD, broken down by calendar quarter ending in the year to which the report relates and by the region where the expenditure was made:

3.1.1.1 Africa;

3.1.1.2 Asia Pacific;

3.1.1.3 Europe;

3.1.1.4 Latin America/Caribbean; and

3.1.1.5 North America.

3.1.2 Types of marketing media utilized by GNR, broken down by calendar quarter ending in the year to which the report relates.

3.1.3 Total expenditure for each marketing media provided above, broken down by calendar quarter ending in the year to which the report relates.

3.1.4 (For the first annual report:) Provide a breakdown of marketing expenditures during the Start-Up Phase for the following global regions:

3.1.4.1 Africa;

3.1.4.2 Asia Pacific;

3.1.4.3 Europe;

3.1.4.4 Latin America/Caribbean; and

3.1.4.5 North America.

3.1.5 Total annual marketing expenditures.

3.2 Total number of ICANN-Accredited Registrars registering domain names in the TLD.

3.2.1 Total number of ICANN-Accredited Registrars authorized to register domain names in the .name TLD broken down on a quarterly basis (include a geographic breakdown by global region).

3.2.2 Total number of new ICANN-Accredited Registrars authorized to register domain names in the .name TLD broken down on a quarterly basis (include a geographic breakdown by global region).

3.2.3 Total number of ICANN-Accredited Registrars authorized to register domain names in the .name TLD who were terminated broken down on a quarterly basis (include a geographic breakdown by global region).

3.2.4 Describe the reason for each termination listed above.

3.2.5 Total number of domain name registrations under management by each ICANN-Accredited Registrar, broken down by quarterly basis.

3.2.6 Number of initial domain name registrations during each calendar month ending in the year to which the report relates.

3.2.7 Number of domain name renewals during each calendar month ending in the year to which the report relates.

3.2.8 Number of domain name registration transfers during each calendar month ending in the year to which the report relates.

3.2.9 Provide the Geographic breakdown of domain name registrants by global region:

3.2.9.1 Africa;

3.2.9.2 Asia Pacific;

3.2.9.3 Europe;

3.2.9.4 Latin America/Caribbean; and

3.2.9.5 North America.

3.2.10 Total domain names expiring and not renewed during each calendar month ending in the year to which the report relates.

3.2.11 Average term of new domain name registrations during each calendar month ending in the year to which the report relates.

3.2.12 Average term of domain name renewals during each calendar month ending in the year to which the report relates.

3.3 Total number of ICANN-Accredited Registrars registering SLD E-mail in the TLD.

3.3.1 Total number of ICANN-Accredited Registrars authorized to register SLD E-mail in the .name TLD broken down on a quarterly basis (include a geographic breakdown by global region).

3.3.2 Total number of new ICANN-Accredited Registrars authorized to register SLD E-mail in the .name TLD broken down on a quarterly basis (include a geographic breakdown by global region).

3.3.3 Total number of ICANN-Accredited Registrars authorized to register SLD E-mail in the .name TLD who were terminated broken down on a quarterly basis (include a geographic breakdown by global region).

3.3.4 Describe the reason for each termination listed above.

3.3.5 Total number of SLD E-mail domain name registrations under management by each ICANN-Accredited Registrar, broken down by quarterly basis to include members of GNR.

3.3.6 Number of initial SLD E-mail registrations during each calendar month ending in the year to which the report relates.

3.3.7 Number of SLD E-mail renewals during each calendar month ending in the year to which the report relates.

3.3.8 Number of SLD E-mail registration transfers during each calendar month ending in the year to which the report relates.

3.3.9 Provide the Geographic breakdown of SLD E-mail registrants by global region:

3.3.9.1 Africa;

3.3.9.2 Asia Pacific;

3.3.9.3 Europe;

3.3.9.4 Latin America/Caribbean; and

3.3.9.5 North America.

3.3.10 Total SLD E-mail registrations expiring and not renewed during each calendar month ending in the year to which the report relates.

3.3.11 Average term of new SLD E-mail registrations during each calendar month ending in the year to which the report relates.

3.3.12 Average term of SLD E-mail renewals during each calendar month ending in the year to which the report relates.

4. Concept: Adding a Personal Name TLD Will Result in an Expansion and Globalization of the Namespace, Rather than Wasteful Duplication of Registrations

Start-Up Phase Registration Report - within 30 days after the end of the Start-Up Phase, GNR shall provide to ICANN an "Expansion of the DNS" report with the following elements:

4.1 Total number of duplicate domain name registrations with each of the following TLDs during the Start-Up Phase:

4.1.1 .com;

4.1.2 .net;

4.1.3 .org;

4.1.4 .de; and

4.1.5 .co.uk.

For the purposes of this Subsection, a "duplicate domain name registration" is a Registered Name in which the second level domain name is identical to a second level domain name in the .com, .net, .org or .de TLDs, or to a third level domain name in the .co.uk TLD. (E.g., "tony.blair.name" matches "blair.com").

4.2 An estimate of the percentage of such duplicate domain name registrations registered to the same holder.

4.3 The percentage of such duplicate domain name registrations sharing at least one nameserver with respect to each of the five domains listed in 4.1.1 to 4.1.5.

4.4 Total number of domain names under management during the Start-Up Phase with holder addresses in the regions described below:

4.4.1 Africa;

4.4.2 Asia Pacific;

4.4.3 Europe;

4.4.4 Latin America/Caribbean; and

4.4.5 North America.

4.5 Number of ICANN-Accredited Registrars, broken down by global region, registering domain names during the Start-Up Phase:

4.5.1 Africa;

4.5.2 Asia Pacific;

4.5.3 Europe;

4.5.4 Latin America/Caribbean; and

4.5.5 North America.

Annual Reports - No later than one month after each anniversary date after the Commencement-of-Service Date, GNR shall provide to ICANN an "Expansion of the DNS" report with the following elements:

4.6 Total number of duplicate domain name registrations (i.e. same name) with each of the following TLDs at the end of each calendar month ending in the year to which the report relates.

4.6.1 .com;

4.6.2 .net;

4.6.3 .org;

4.6.4 .de; and

4.6.5 .co.uk.

For the purposes of this Subsection, a "duplicate domain name registration" is a Registered Name in which the second level domain name is identical to a second level domain name in the .com, .net, .org or .de TLDs, or to a third level domain name in the .co.uk TLD. (E.g., "tony.blair.name" matches "blair.com").

4.7 An estimate of the percentage of such duplicate domain name registrations registered to the same holder.

4.8 The percentage of such duplicate domain name registrations sharing at least one nameserver with respect to each of the five domains listed in 4.6.1 to 4.6.5.

4.9 Total number of domain names under management during the Operation Phase on a quarterly basis with holder addresses in the regions described below:

4.9.1 Africa;

4.9.2 Asia Pacific;

4.9.3 Europe;

4.9.4 Latin America/Caribbean; and

4.9.5 North America.

4.10 Number of ICANN-Accredited Registrars, broken down by global region, registering domain names during the Operation Phase Period:

4.10.1 Africa;

4.10.2 Asia Pacific;

4.10.3 Europe;

4.10.4 Latin America/Caribbean; and

4.10.5 North America.

5. Concept: Registry Services Can Effectively Be Provided by a Newly Accredited Registry Operator

5.1 Ability to Effectively Operate the Registry. Annual Report - No later than one month after each anniversary date after the Commencement-of-Service Date, GNR shall provide to ICANN a Registry Report with the following elements:

5.1.1 Total number of domain name registrations under management during each calendar month ending in the year to which the report relates.

5.1.2 Total number of ICANN-Accredited Registrars registering domain-names in the Registry TLD during each calendar month ending in the year to which the report relates.

5.1.3 Total number of SLD E-mail registration under management during each calendar month ending in the year to which the report relates.

5.1.4 Total number of ICANN-Accredited Registrars registering SLD E-mail in the Registry TLD during each calendar month ending in the year to which the report relates.

5.1.5 Total amount of SLA Credits to ICANN-Accredited Registrars during each calendar month ending in the year to which the report relates.

5.1.6 Total SLA Credits awarded to each ICANN-Accredited during each calendar month ending in the year to which the report relates.

5.2 Ability to Attract and Maintain Registrars - within 180 days after the Commencement-of-Service Date, GNR shall provide the following information and reports to ICANN.

5.2.1 Total number of ICANN-Accredited Registrars who participated in the Registry OT&E certification during the Start-Up Phase.

5.2.2 Total number of ICANN-Accredited Registrars who failed OT&E certification during the Start-Up Phase.

5.2.3 Total number of ICANN-Accredited Registrars re-tested for OT&E certification during the Start-Up Phase.

5.2.4 A summary of complaints received from ICANN-Accredited Registrars regarding the Start-Up Phase OT&E certification.

5.2.5 Provide a written report detailing the effectiveness of the Start-Up Phase OT&E certification. Include such items as lessons learned and methods of improvement.

5.2.6 Provide a written report detailing the effectiveness of the OT&E process. Include such items as lessons learned and methods of improvement.

5.2.7 Total number of ICANN-Accredited Registrars who participated in the Registry LOT&E certification.

5.2.8 Total number of ICANN-Accredited Registrars who failed LOT&E certification.

5.2.9 Total number of ICANN-Accredited Registrars re-tested for LOT&E certification.

5.2.10 A summary of complaints received from ICANN-Accredited Registrars regarding the LOT&E certification.

5.2.11 Provide a written report detailing the effectiveness of the LOT&E certification. Include such items as lessons learned and methods of improvement.

5.2.12 Provide a written report detailing the effectiveness of the LOT&E process. Include such items as lessons learned and methods of improvement.

5.3 Effectiveness of Cooperative Marketing - within 180 days after the Commencement-of-Service Date, Registry Operator shall provide the following information on reports to ICANN.

5.3.1 Total number of ICANN-Accredited Registrars participating in the cooperative marketing plan during each calendar month ending in the year to which the report relates.

5.3.2 Total amount of marketing dollars provided to each ICANN-Accredited Registrar under the cooperative marketing plan during each calendar month ending in the year to which the report relates.

5.3.3 Total amount of marketing dollars raised under the cooperative marketing plan during each calendar month ending in the year to which this report relates.

5.3.4 Total amount of unused cooperative marketing funds placed into the Marketing Development Fund.

5.3.5 Total amount of cooperative marketing dollars raised broken down by geographic area (North America, Europe, Asia, Africa and Latin America/Caribbean) during each calendar month ending in the year to which the report relates.

5.3.6 Total amount of cooperative marketing dollars expended broken down by geographic area (North America, Europe, Asia, Africa, and Latin America/Caribbean) during each calendar month ending in the year to which the report relates.

6. Concept: Mechanisms for Ensuring that all Registrars Are Treated Fairly

Annual Reports - No later than one month after each anniversary date after the Commencement-of-Service Date, GNR shall provide to ICANN a Fair-Treatment Report with the following elements:

6.1 A description of every known violation or alleged violation of the Code of Conduct during each calendar month ending in the year to which the report relates.

6.2 Total number of complaints received by GNR from registrars regarding services provided by GNR.

6.2.1 Identify and categorize the types of complaints received from registrars.

6.2.2 List corrective actions, if any, in response to the categorized complaints.

6.3 Total number of ICANN-Accredited Registrars restricted from further registrations for non-payment of registration fees.

7. Concept: Use of Centralized Registry-Level Whois to Enhance Transparency and Accountability in Domain-Name Registrations

Annual Reports - No later than one month after each anniversary date after the Commencement-of-Service Date, GNR shall provide to ICANN a Whois Report with the following elements:

7.1 Total number of complaints received from registrants regarding Whois information during each calendar month ending in the year to which the report relates.

7.2 Total number of complaints received from ICANN-Accredited Registrars regarding Whois service during each calendar month ending in the year to which the report relates.

7.3 Total number of complaints received from third parties regarding Whois information during each calendar month ending in the year to which the report relates.

7.4 (For the first annual report:) Total initial query volume during the Start-Up Phase.

7.5 (For the first annual report:) Total initial query volume during the Operation Phase.

7.6 Total number of queries during each calendar month ending in the year to which the report relates.

7.7 Privacy Complaints:

7.7.1 Total number of complaints relating to privacy issues during each calendar month ending in the year to which the report relates.

7.7.2 Identify and categorize types of privacy complaints.

8. Concept: Capital Requirements in Operating a TLD Restricted to Personal Use

Annual Reports - No later than one month after each anniversary date after the Commencement-of-Service Date, GNR shall provide to ICANN a Funding Requirements Report with the following elements:

8.1 Total expenditures during the Start-Up Phase.

8.2 Total expenditures during the Operations Phase.

8.3 Breakdown of expenditures for the following categories:

8.3.1 Marketing;

8.3.2 Software; and

8.3.3 Hardware.

8.4 Provide a list of the employee positions hired during the following periods:

8.4.1 Start-Up Phase; and

8.4.2 Operations Phase.

9. Concept: Introducing the .name TLD will Enhance the Utility of the DNS.

Annual Reports - no later than one month after each anniversary date after the Commencement-of-Service Date, GNR shall provide to ICANN an "Enhancement of DNS Utility" report with the elements to be agreed between ICANN and GNR concerning International Domain-Name registrations (if such are implemented) and other relevant developments.

10. Concept: Registrations Restrictions Can be Implemented by a Registry Operator in a Cost Effective and Timely Manner.

10.1 UDRP Violations - within 180 days after the Commencement-of-Service Date, GNR shall provide an initial report with the following information and reports to ICANN. Thereafter, no later than one year after the anniversary date of the initial report, GNR shall provide the following information and reports to ICANN.

10.1.1 A statement of the total number of UDRP challenges filed.

10.1.2 A tabulation of the number of names subject to multiple UDRP challenges (i.e., x names were subject to exactly two challenges, y names were subject to exactly three challenges, etc.).

10.1.3 A statement of how many names sponsored by each Registrar were subject to at least one UDRP challenge.

10.1.4 A breakdown by country of the registration offered by the domain-name holder of the number of successful and unsuccessful UDRP challenges.

10.1.5 A statement, broken down by sponsoring Registrar, of the number of names involved in UDRP challenges where the holder failed to submit any materials after notification of challenge.

10.1.6 A statement, broken down by the region of the holder's address as described below, of the number of names subject to successful UDRP challenges:

10.1.6.1 Africa;

10.1.6.2 Asia Pacific;

10.1.6.3 Europe;

10.1.6.4 Latin America/Caribbean; and

10.1.6.5 North America.

10.1.7 A statement, broken down by the region of the successful challenger's address as described below, of the number of names subject to successful UDRP challenges:

10.1.7.1 Africa;

10.1.7.2 Asia Pacific;

10.1.7.3 Europe;

10.1.7.4 Latin America/Caribbean; and

10.1.7.5 North America.

10.1.8 A statement of the number of successful UDRP challengers that did not register the challenged name, broken down by priority of the challenger (i.e. x first-priority challengers chose not to register the challenged name; y second priority challengers were offered the opportunity to, but did not, register the challenged name, etc.).

10.1.9 A summary of the complaints received from Registrars regarding the UDRP.

10.2 Registration Restrictions - within 120 days after the Commencement-of-Service Date, GNR shall provide the following information and reports to ICANN. Thereafter, no later than one year after the anniversary date of the initial report, GNR shall provide the following information and reports to ICANN.

10.2.1 A statement of the total number of Eligibility Requirements Dispute Resolution Policy ("ERDRP") Challenges filed.

10.2.2 A tabulation of the number of names subject to multiple ERDRP challenges (i.e., x names were subject to exactly two challenges, y names were subject to exactly three challenges, etc.).

10.2.3 A statement of how many names sponsored by each Registrar were subject to at least one ERDRP challenge.

10.2.4 A breakdown by country of the registration offered by the domain-name holder of the number of successful and unsuccessful ERDRP challenges.

10.2.5 A statement, broken down by sponsoring Registrar, of the number of names involved in ERDRP challenges where the holder failed to submit any materials after notification of challenge.

10.2.6 A statement, broken down by the region of the holder's address as described below, of the number of names subject to successful ERDRP challenges:

10.2.6.1 Africa;

10.2.6.2 Asia Pacific;

10.2.6.3 Europe;

10.2.6.4 Latin America/Caribbean; and

10.2.6.5 North America.

10.2.7 A statement, broken down by the region of the successful challenger's address as described below, of the number of names subject to successful ERDRP challenges:

10.2.7.1 Africa;

10.2.7.2 Asia Pacific;

10.2.7.3 Europe;

10.2.7.4 Latin America/Caribbean; and

10.2.7.5 North America.

10.2.8 A statement of the number of successful ERDRP challengers that did not register the challenged name, broken down by priority of the challenger (i.e. x first-priority challengers chose not to register the challenged name; y second priority challengers were offered the opportunity to, but did not, register the challenged name, etc.).

10.2.9 A statement, broken down by sponsoring Registrar, of the number of names forfeited on the basis that the name was registered solely for the purpose of (1) selling, trading or leasing the domain name for compensation, or (2) the unsolicited offering to sell, trade or lease the domain name for compensation.

10.2.10 A summary of the complaints received from Registrars regarding the ERDRP.

10.2.11 A description of significant technical difficulties encountered in connection with the ERDRP resolution.

10.2.12 A written evaluation of the overall effectiveness of the ERDRP adopted for the Registry TLD.

10.2.13 A written evaluation of the overall effectiveness of each dispute resolution policy adopted by the Registry TLD described below:

10.2.13.1 ERDRP; and

10.2.13.2 UDRP.

11. Commercially Reasonable Efforts and Review

Many of the reports to be provided by GNR require access to data to which GNR may not be privy or which may not be reasonably available to GNR. Recognizing the importance of the proof of concept:

11.1 GNR shall use commercially reasonable efforts to obtain all necessary data and complete the required reports as set forth in this Appendix; and

11.2 In the event GNR is unable through commercially reasonable efforts to obtain the requisite data to complete the required reports or the compilation of a specific report proves unreasonably costly, ICANN shall, to the fullest extent possible, assist GNR and/or the Registry community in obtaining or coordinating efforts to obtain the data, or alternative data (including as appropriate data of reduced scope) useful in connection with the proof of concept, in a less costly way.

12. Confidentiality

The reports provided by GNR as described in this Appendix shall be subject to confidentiality restrictions according to categories described in the following table:

Category Restrictions
1 May be publicly disclosed by ICANN 18 months after the information is reported to ICANN.
2 May be publicly disclosed by ICANN 6 months after the information is reported to ICANN.
3 May be publicly disclosed by ICANN 3 months after the last date to which the information relates.
4 No confidentiality restrictions.

ICANN will use commercially reasonable efforts to prevent public disclosure prior to the times described in the table above.

GNR shall clearly label all reports and information provided pursuant to this Appendix with the appropriate confidentiality category prior to submission to ICANN.

The following table sets forth, for each item in each report, the confidentiality category (CC) that applies to it:

Report ID

Confidentiality Category (CC)

Report ID

Confidentiality Category (CC)

Report ID

Confidentiality Category (CC)

Report ID

Confidentiality Category (CC)

1.1.1

4

1.3.18

3
3.3.4
2

5.3.5

1

1.1.2

4

1.4.1

4
3.3.5
3

5.3.6

1

1.1.3.1-1.1.3.5

4

1.4.2.1-1.4.2.5

4
3.3.6
3

6.1

2

1.1.4

4

1.4.3

4
3.3.7
3

6.2.1-6.2.2

2

1.1.5

4

1.4.4.1-1.4.4.5

4
3.3.8
3

6.3

3

1.1.6

4

1.4.5

3

3.3.9.1-3.3.9.5

4

7.1

3

1.1.7

4

1.4.6

3

3.3.10

3

7.2

3

1.1.8.1-1.1.8.5

4

1.5.1

4

3.3.11

3

7.3

3

1.1.9

4

1.5.2.1-1.5.2.9

4

3.3.12

3

7.4

3

1.1.10

4

1.5.3

4

4.1.1-4.1.5

4

7.5

3

1.1.11

4

1.5.4

4

4.2

4

7.6

3

1.1.12

4

1.5.5

4

4.3

4

7.7.1-7.7.2

2

1.2.1

4

1.5.6

4

4.4.1-4.4.5

4

8.1

3

1.2.2

4

1.5.7

4

4.5.1-4.5.5

4

8.2

3

1.2.3

2

1.5.8

4

4.6.1-4.6.5

4

8.3.1-8.3.3

2

1.2.4

4

1.5.9

4

4.7

4

8.4.1 –8.4.2

2

1.2.5

2

1.6.1

3

4.8

4

9

To be agreed

1.2.6.1-1.2.6.5

4

1.6.2

4

4.9.1-4.9.5

4

10.1.1

4

1.2.7.1-1.2.7.5

4

1.6.3

4

4.10.1-4.10.5

4

10.1.2

4

1.2.8

4

2.1

3

5.1.1

3

10.1.3

2

1.2.9

4

2.2

3

5.1.2

4

10.1.4

4

1.2.10

3

3.1.1.1-3.1.1.5

1

5.1.3

3

10.1.5

4

1.2.11

3

3.1.2

1

5.1.4

4

10.1.6.1-10.1.6.5

4

1.2.12

3

3.1.3

1

5.1.5

3

10.1.7.1-10.1.7.5

4

1.3.1

3

3.1.4.1-3.1.4.5

1

5.1.6

3

10.1.8

4

1.3.2

3

3.1.5

2

5.2.1

4

10.1.9

4

1.3.3.1-1.3.3.5

3

3.2.1

4

5.2.2

4

10.2.1

4

1.3.4

4

3.2.2

4

5.2.3

4

10.2.2

4

1.3.5

3

3.2.3

4

5.2.4

3

10.2.3

2

1.3.6

3

3.2.4

2

5.2.5

3

10.2.4

4

1.3.7

3

3.2.5

3

5.2.6

3

10.2.5

4

1.3.8

3

3.2.6

3

5.2.7

4

10.2.6.1-10.2.6.5

4

1.3.9

3

3.2.7

3

5.2.8

4

10.2.7.1-10.2.7.5

4

1.3.10.1-1.3.10.5

3

3.2.8

3

5.2.9

4

10.2.8

4

1.3.11

3
3.2.9.1-3.2.9.5
4

5.2.10

3

10.2.9

3

1.3.12

3

3.2.10
3

5.2.11

3

10.2.10

2
1.3.13
3
3.2.11
3

5.2.12

3

10.2.11

2
1.3.14
3
3.2.12
3

5.3.1

2

10.2.12

3
1.3.15
3
3.3.1
4

5.3.2

1

10.2.13.1-10.2.13.2

3
1.3.16.1-1.3.16.5

3
3.3.2
4

5.3.3

1
   

1.3.17

3
3.3.3
4

5.3.4

1
   

1 The Start-Up Plan and Launch Dates are described in Appendix J. For purposes of this Appendix, the Start-Up Phase shall include all dates up to the Live SRS Launch referred to in Appendix J as Commencement-of-Service Date +120 days. The Operation Phase shall include all dates after the Live SRS Launch.


Comments concerning the layout, construction and functionality of this site
should be sent to webmaster@icann.org.

Page Updated 24-Dec-2002

©2001  The Internet Corporation for Assigned Names and Numbers. All rights reserved.