en

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 (.pro)

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

Unsponsored TLD Agreement: Appendix U (.pro)

Posted: 21 May 2004


Evaluation of Concepts

RegistryPro 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. RegistryPro shall provide the reports in hard copy and, to the extent feasible, in a common character-mapped electronic form.

Capitalized terms shall have the meanings defined in the Registry Agreement and its Appendices. As used in this Appendix U, the term "Authorized Registrar" refers to a registrar accredited by ICANN for the .pro TLD that has entered into, and has currently in effect, the Registry-Registrar Agreement (Appendix F).

The reports provided by RegistryPro 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 TLD Restricted to Professional Names

1.1 Sunrise Period Effectiveness - within 120 days after the end of the Sunrise Period for the each .pro sub-domain ("PS-SLD"), RegistryPro shall provide the following information and reports to ICANN.

1.1.1 Total number of Sunrise Period registrations by day.

1.1.2 Total number of Sunrise Period registrations by week.

1.1.3 Total number of Sunrise Period 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 Authorized Registrars qualified to submit registrations each week of the Sunrise Period.

1.1.5 Total number of Registered Names registered during the Sunrise Period, divided according to the sponsoring Authorized Registrar.

1.1.6 A summary of the complaints received from Authorized Registrars regarding the Registry Operator's operation of the Sunrise Period.

1.1.7 A description of significant technical difficulties encountered in operating during the Sunrise Period.

1.1.8 Registry Operator's assessment of whether the Sunrise Evaluation Period was useful.

1.1.9 A tabulation of the number of Sunrise Period registrations of various terms in years, broken down by Authorized Registrar.

1.1.10 A report detailing the modifications and adjustments to the Registry Database or Sunrise registration procedures during the Sunrise Evaluation Period.

1.2 Dispute Resolution Mechanism - within 120 days after the last day to make Sunrise Challenges for any PS-SLD, RegistryPro shall provide the following information and reports to ICANN.

1.2.1 A statement of the total number of Sunrise Challenges submitted.

1.2.2 A tabulation of the number of names subject to multiple Sunrise Challenges (i.e. x names were subject to exactly two challenges, y names were subject to exactly three challenges, etc.), other than challenges rejected for non-payment.

1.2.3 A tabulation of how many names sponsored by each Authorized Registrar were subject to at least one Sunrise Challenge.

1.2.4 A tabulation, broken down by sponsoring Authorized Registrar, of the number of names subject to successful Sunrise Challenge.

1.2.5 A tabulation, broken down by country of the trademark or service mark registration offered by the registrant, of the number of successful and unsuccessful Sunrise Challenges.

1.2.6 A tabulation, broken down by sponsoring Authorized Registrar, of the number of names involved in challenges where the registrant failed to submit any materials within the period of time provided by the Sunrise Challenge for response to a challenge.

1.2.7 A tabulation, broken down by the region of the registrant's address as described below, of the number of names subject to successful Sunrise Challenge:

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 tabulation, broken down by the region of the successful challenger's address as described below, of the number of names subject to successful Sunrise Challenge:

1.2.8.1 Africa;

1.2.8.2 Asia Pacific

1.2.8.3 Europe;

1.2.8.4 Latin America/Caribbean; and

1.2.8.5 North America.

1.2.9 A tabulation of the number of successful Sunrise 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.).

1.2.10 A summary of the complaints received from registrars regarding the Sunrise Challenge mechanism.

1.2.11 A description of significant technical difficulties encountered in connection with the Sunrise Challenge mechanism.

1.2.12 A written report detailing RegistryPro's evaluation of the overall effectiveness of the Sunrise Challenge.

1.2.13 A tabulation, broken down by sponsoring Authorized Registrar, of the number of Sunrise registrations that were subject to the Qualification Challenges (see Section II of Appendix M).

1.2.14 A statement of the total number of Qualification Challenges filed during the Sunrise Period.

1.3 Registry Live Effectiveness - within 120 days after the Registry Live Launch, for each PS-SLD, respectively, RegistryPro shall provide the following information and reports to ICANN.

1.3.1 Total number of domain name registrations resolved into the DNS thirty days after launch.

1.3.2 Total number of domain name registrations resolved into the DNS thirty days after launch, broken down by the registrant's address in the regions described below:

1.3.2.1 Africa;

1.3.2.2 Asia Pacific;

1.3.2.3 Europe;

1.3.2.4 Latin America/Caribbean; and

1.3.2.5 North America.

1.3.3 Total number of Authorized Registrars qualified to submit domain name registrations during the thirty days after launch.

1.3.4 Total number of domain names under sponsorship of each Authorized Registrar thirty days after launch.

1.3.5 A summary of the complaints received from Authorized Registrars regarding the launch.

1.3.6 A description of significant technical difficulties encountered in operating during the launch.

1.4 Effectiveness of Staggered, Multiple Launches. No later than one month after the anniversary date after the Commencement-of-Service Date, RegistryPro shall provide the following information and reports to ICANN.

1.4.1 A statement of the launch dates for each PS-SLD launched during the period of this report.

1.4.2 A summary of the complaints received from registrars regarding the launch of each PS-SLD.

1.4.3 A summary of the complaints received from registrants regarding the launch of each PS-SLD.

1.4.4 A description of significant technical difficulties encountered in the launch of each PS-SLD.

1.4.5 A written report detailing RegistryPro's evaluation of the overall effectiveness of multiple launches of the .pro PS-SLDs.

1.5 Miscellaneous.

1.5.1 Within 30 days after the first anniversary of the Commencement-of -Service Date, provide a tabulation of the number of Sunrise Period registrations that were transferred to another registrant during each month after the Commencement-of-Service Date.

1.5.2 Within 30 days of learning of any lawsuit that has been filed concerning the start-up activities in .pro, 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 180 days after the Commencement-of-Service Date, RegistryPro 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 Digital Credentials 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 Sunrise Period registration minimum term in limiting abusive registration practices. Include such items as lessons learned and methods of improvement.

2.3 Provide a written report detailing the effectiveness of each of the Manual, Toolkit, and Competitive Toolkit Verification procedures in limiting abusive registration practices. Include such items as lessons learned and methods of improvement.

3. Concept: Introducing a Professional Use 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, RegistryPro shall provide to ICANN an Annual Proof-of-Concept Report on Effectiveness of Competition, with the following information:

3.1 Marketing and Outreach Efforts

3.1.1 Total RegistryPro expenditures for marketing and outreach through professional associations and similar bodies the .pro 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 and outreach utilized by RegistryPro, broken down by calendar quarter ending in the year to which the report relates.

3.1.3 Total expenditure for each marketing media and outreach 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 and outreach expenditures during the Sunrise Period 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 Report by Quarter - Total number of Authorized Registrars registering domain names in the TLD, broken down by PS-SLD.

3.2.1 Total number of Authorized Registrars qualified to register domain names in each PS-SLD, broken down on a quarterly basis (include a geographic breakdown by global region).

3.2.2 Total number of Authorized Registrars newly qualified to register domain names in each PS-SLD broken down on a quarterly basis (include a geographic breakdown by global region).

3.2.3 Total number of Authorized Registrars qualified to register domain names in PS-SLD 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 discussed above.

3.2.5 Total number of registrations from each PS-SLD under management by each Authorized Registrar, broken down by quarterly basis.

3.3 Number of initial registrations during each calendar month ending in the year to which the report relates, broken down by PS-SLD.

3.4 Number of renewals during each calendar month ending in the year to which the report relates, broken down by PS-SLD.

3.5 Number of transfers of registrations between sponsoring registrars during each calendar month ending in the year to which the report relates, broken down by PS-SLD.

3.6 Provide the geographic breakdown of registrants by global region, for each PS-SLD.:

3.6.1 Africa;

3.6.2 Asia Pacific

3.6.3 Europe;

3.6.4 Latin America/Caribbean; and

3.6.5 North America.

3.7 Total domain names expiring and not renewed during each calendar month ending in the year to which the report relates, broken down by PS-SLD.

3.8 Average term of new registrations during each calendar month ending in the year to which the report relates, broken down by PS-SLD.

3.9 Average term of renewals during each calendar month ending in the year to which the report relates, broken down by PS-SLD.

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

Sunrise Report - within 120 days after the end of the Sunrise Evaluation Period, RegistryPro shall provide to ICANN an "Expansion of the DNS" report with the following elements:

4.1 Total number of duplicate registrations (i.e. same name) with each of the following TLDs during the Sunrise Period:

4.1.1 .com;

4.1.2 .net;

4.1.3 .org;

4.1.4 .us; and

4.1.5 .co.uk.

For the purposes of this Subsection, a "duplicate registration" is a Registered Name (within .pro) in which the third-level label is identical to a second-level label in the .com, .net, .org or .us TLDs, or to a third-level label in the .co.uk TLD.

4.2 An estimate of the percentage of such duplicate registrations registered to the same registrant.

4.3 The percentage of such duplicate 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 (separately for each registration level) during the Sunrise Period with registrant 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 Authorized Registrars, broken down by global region, registering domain names during the Sunrise Period:

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, RegistryPro shall provide to ICANN an "Expansion of the DNS" report with the following elements:

4.6 Total number of duplicate 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 .us; and

4.6.5 .co.uk.

For the purposes of this Subsection, a "duplicate registration" is a Registered Name (within .pro) in which the second-level label or (for PS-SLD’s) the third-level label is identical to a second-level label in the .com, .net, .org or .us TLDs, or to a third-level label in the .co.uk TLD. In the case of redirects of second-levels to corresponding third-levels, such registrations should be counted as one dublicate and not one for each of the second and the third level.

4.7 An estimate of the percentage of such duplicate registrations registered to the same registrant.

4.8 The percentage of such duplicate 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 Post Live Launch on a quarterly basis with registrant 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 Authorized Registrars, broken down by global region, registering domain names post Live Launch Start Date:

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 Registry Operator Relying on an Independent Advisory Board

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, RegistryPro shall provide to ICANN a written report with the following elements:

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

5.1.2 Total number of Authorized Registrars during each calendar month ending in the year to which the report relates.

5.1.3 Total value of SLA Credits to Authorized Registrar Registrars during each calendar month ending in the year to which the report relates.

5.1.4 Total SLA Credits awarded to each Authroized Registrar 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, RegistryPro shall provide the following information and reports to ICANN.

5.2.1 Total number of ICANN-Accredited Registrars who participated in the Registry Operational Test and Evaluation process.

5.2.2 Total number of ICANN-Accredited Registrars who failed the Operational Test and Evaluation process.

5.2.3 Total number of ICANN-Accredited Registrars re-tested for the Operational Test and Evaluation process.

5.2.4 A summary of complaints received from ICANN-Accredited Registrars regarding the Operational Test and Evaluation process.

5.2.5 Provide a written report detailing the effectiveness of the Operational Test and Evaluation process. Include such items as lessons learned and methods of improvement.

5.3 Effectiveness of Advisory Board - within 180 days after the Commencement-of-Service Date, RegistryPro shall provide an initial Advisory Board Registry Report with the following information and reports to ICANN. Thereafter, no later than one year after the anniversary date of the initial report, RegistryPro shall provide to ICANN an Advisory Board Registry Report.

5.3.1 A statement of the number of members on the .pro TLD Advisory Board, broken down by the professional category each member represents (if any).

5.3.2 A statement of the number of Sub-Advisory Boards, if such are established, broken down by professional category and date formed.

5.3.2.1 Identify each member of each Sub-Advisory Board.

5.3.2.2 Identify the country and geographic region of each member of each Sub-Advisory Board.

5.3.3 A statement of the number of times and dates the Advisory Board and each subsidiary Advisory Board met in person, by video-conferencing, or by telephone during the period of the report.

5.3.4 A statement of the written notices, if any, sent by the Advisory Board to the RegistryPro Managing Board regarding alleged violations of restrictions.

5.3.4.1 For each written notice described above, provide a summary of the alleged violation(s).

5.3.4.2 For each written notice described above, summarize the actions taken, if any, to resolve the alleged violation(s).

5.3.5 List the number and type of additional professional PS-SLDs, including second-level registrations in the .pro domain, proposed by the Advisory Board during the period of this report.

5.3.6 List the number and type of additional qualifications for the existing professional PS-SLDs proposed by the Advisory Board during the period of this report.

5.3.7 A written report regarding the RegistryPro Global Partnership of Associations ("RGPA") to include:

5.3.7.1 A list of members of the RGPA;

5.3.7.2 A list of the professional categories, broken down by each member, represented by the RGPA (i.e. doctors are represented by x member(s), y member(s), etc…); and

5.3.7.3 A breakdown of the country and geographic region of each member.

5.3.8 A written report detailing RegistryPro's evaluation of the overall effectiveness of the Advisory Board and each Sub-Advisory Board.

5.4 Effectiveness of Community Refund Program - No later than one month after the anniversary date after the Commencement-of-Service Date, RegistryPro shall provide the following information and reports:

5.4.1 Total amount of Community Refund distribution for the period of this report.

5.4.2 Total amount of Community Refund distribution provided for each of the following:

5.4.2.1 Support of DNSO;

5.4.2.2 Support for additional arbitration mechanisms;

5.4.2.3 Consumer-focused domain name education programs;

5.4.2.4 Support for ICANN policies; and

5.4.2.5 Bridging the Digital Divide.

5.4.3 A list of each party receiving Community Refund proceeds and the amount received for the period of this report.

6. Concept: Mechanisms in a Chartered Registry 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, RegistryPro 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 RegistryPro from registrars regarding services provided by RegistryPro.

6.2.1 Identify and categorize the types of complaints received from Authorized Registrars.

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

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

6.4 Total number of Authorized Registrars restricted from further registrations for non-compliance with RegistryPro policies, including verification requirements.

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, RegistryPro 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 Authorized 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 Whois query volume during the Sunrise Period.

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

7.6 Expanded Query-Based Searchability (as described in Section 5 of Appendix G):

7.6.1 Total number of subscribers (include a geographic breakdown by country and global region).

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

7.6.3 Total number of queries broken down by subscribers 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 Professional Use

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

8.1 Total expenditures during the Sunrise Period.

8.2 Total expenditures during the period after Live Launch on a quarterly basis.

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 Pre-Sunrise Period;

8.4.2 Sunrise Period; and

8.4.3 Period after Live Launch on a quarterly basis.

9. Concept: Deployment of a Digital Credentials Requirement will Enhance Utility of the DNS

Annual Reports - no later than one month after each anniversary date after the Commencement-of-Service Date, RegistryPro shall provide to ICANN an "Enhancement of DNS Utility" report with the following elements as applicable:

9.1 Total number of Commercial Certificate Authorities ("CCAs").

9.2 List each CCA categorized by the following regions described below:

9.2.1 Africa;

9.2.2 Asia Pacific;

9.2.3 Europe;

9.2.4 Latin America/Caribbean; and

9.2.5 North America.

9.3 Total number of CCAs authorized to issue digital credentials that were terminated (include a geographic breakdown by global region).

9.4 Total number of CCAs terminations that were appealed (include a geographic breakdown by global region).

9.5 Describe the reason for each termination above.

9.6 A description of significant technical difficulties encountered in utilizing digital credentials.

9.7 A summary of the complaints received from Authorized Registrars regarding the digital credential.

9.8 A written evaluation of the overall effectiveness of digital credentials and CCAs, focusing on operational challenges encountered, if any, the prevalence of use by users and user applications of digital credentials, and the added utility provided by the requirement for digital credentials in the .pro TLD .

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, RegistryPro 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, RegistryPro 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 Authorized Registrar were subject to at least one UDRP challenge.

10.1.4 A breakdown by country of the registrant of the number of successful and unsuccessful UDRP challenges.

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

10.1.6 A statement, broken down by the region of the registrant'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 RegistryPro Registrars regarding the UDRP.

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

10.2.1 A tabulation of the total number of Qualification Challenges filed, broken down by PS-SLD.

10.2.2 A tabulation of the number of names subject to multiple Qualification Challenges (i.e., x names were subject to exactly two challenges, y names were subject to exactly three challenges, etc.), broken down by PS-SLD.

10.2.3 A breakdown for each PS-SLD of the Qualification Challenges by the type of verification utilized to qualify a registrant.

10.2.4 A breakdown for each PS-SLD of the Qualification Challenges by whether the challenge was prompted by a third party, the sponsoring Authroized Registrar, or RegistryPro.

10.2.5 A tabulation, broken down by PS-SLD, of how many names sponsored by each Authorized Registrar were subject to at least one Qualification Challenge.

10.2.6 A breakdown by country of the registration sponsored by each Authorized Registrar and by PS-SLD of the number of successful and unsuccessful Qualification Challenges.

10.2.7 A tabulation, broken down by sponsoring Authorized Registrar and PS-SLD, of the number of names involved in Qualification Challenges where the Registrant failed to submit any materials within the time period allotted by the Qualification Challenge Providers for responding to a challenge.

10.2.8 A tabulation, broken down by the region of the registrant's address as described below, of the number of names subject to successful Qualification Challenges:

10.2.8.1 Africa;

10.2.8.2 Asia Pacific;

10.2.8.3 Europe;

10.2.8.4 Latin America/Caribbean; and

10.2.8.5 North America.

10.2.9 A statement, broken down by the region of the successful challenger's address as described below, of the number of names subject to successful Qualification Challenges:

10.2.9.1 Africa;

10.2.9.2 Asia Pacific;

10.2.9.3 Europe;

10.2.9.4 Latin America/Caribbean; and

10.2.9.5 North America.

10.2.10 A statement of the number of successful challengers that did not register the challenged name,

10.2.11 A summary of the complaints received from Authroized Registrars regarding the Qualification Challenge, including complaints about any specific Qualification Challenge Providers.

10.2.12 A description of significant technical difficulties encountered in connection with the Qualification Challenge.

10.2.13 A written evaluation of the overall effectiveness of the Qualification Challenge.

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

10.3.1 Total number of Authorized Registrars verifying registrant information by utilizing Manual Registration Verification procedures (include a geographic breakdown by global region and a PS-SLD breakdown).

10.3.2 Total number of Authorized Registrars verifying registrant information by utilizing the RegistryPro Verification Toolkit (include a geographic breakdown by global region and a PS-SLD breakdown).

10.3.3 Total number of Authorized Registrars verifying registrant information by utilizing the Competitive Verification Toolkit (include a geographic breakdown by global region and a PS-SLD breakdown).

10.3.4 Total number of Registered Names registered utilizing the Manual Verification procedure, broken down by Authorized Registrar, registration level, registration redirect service,and PS-SLD.

10.3.5 Total number of Registered Names registered utilizing the RegistryPro Toolkit Verification, broken down by Authorized Registrar, registration level, registration redirect service, and PS-SLD.

10.3.6 Total number of domain names registered utilizing the Competitive Toolkit Verification, broken down by Authorized Registrar, registration level, registration redirect service, and PS-SLD.

10.3.7 Total number of successful registrations utilizing Toolkit or Competitive Toolkit Verifications, respectively, whereby the registrant was a member of an Advisory Board, Sub-Advisory Board or RGPA association.

10.3.8 A summary of the complaints received from Authorized Registrars regarding the Manual Verification process.

10.3.9 A summary of the complaints received from Authorized Registrars regarding the Toolkit or Competitive Toolkit Verification, respectively.

10.3.10 A description of significant technical problems encountered in operating the RegistryPro Toolkit Verification.

10.3.11 A description of significant technical problems encountered in operating the Competitive Toolkit Verification.

10.3.12 A statement of the total number of registrants notified pursuant to the Periodic Verification process that they no longer qualify for the professional category of their original or renewal registration.

10.3.13 Of those registrants notified, list the geographic location of the Registrant, the professional category, the sponsoring RegistryPro Registrar and whether the Periodic Verification was Manual, RegistryPro Toolkit or Competitive Toolkit.

10.3.14 A summary of the complaints received from Authroized Registrars regarding the Periodic Verification process.

11. Commercially Reasonable Efforts and Review

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

11.1 RegistryPro 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 RegistryPro 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 RegistryPro 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 RegistryPro 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.

RegistryPro 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 Report ID Confidentiality Category Report ID Confidentiality Category Report ID Confidentiality Category
1.1.1 4 2.2 3 5.3.1 4 9.8 3
1.1.2 4 2.3 3 5.3.2 4 10.1.1 4
1.1.3.1 -1.1.3.5 4 3.1.1.1 - 3.1.1.5 1 5.3.2.1 4 10.1.2 4
1.1.4 4 3.1.2 1 5.3.2.2 4 10.1.3 3
1.1.5 3 3.1.3 1 5.3.3 3 10.1.4 4
1.1.6 3 3.1.4.1 - 3.1.4.5 1 5.3.4 2 10.1.5 4
1.1.7 3 3.1.5 2 5.3.4.1 2 10.1.6.1 - 10.1.6.5 4
1.1.8 4 3.2.1 4 5.3.4.2 2 10.1.7.1 - 10.1.7.5 4
1.1.9 3 3.2.2 4 5.3.5 3 10.1.8 4
1.1.10 4 3.2.3 4 5.3.6 3 10.1.9 4
1.2.1 4 3.2.4 2 5.3.7.1 – 5.3.7.3 4 10.2.1 4
1.2.2 4 3.2.5 3 5.3.8 3 10.2.2 3
1.2.3 2 3.3 3 5.4.1 3 10.2.3 3
1.2.4 2 3.4 3 5.4.2.1- 5.4.2.5 3 10.2.4 3
1.2.5 4 3.5 3 5.4.3 3 10.2.5 3
1.2.6 4 3.6.1 - 3.6.5 3 6.1 2 10.2.6 3
1.2.7.1 -1.2.7.5 4 3.7 3 6.2 2 10.2.7 3
1.2.8.1 -1.2.8.5 4 3.8 3 6.2.1 - 6.2.2 2 10.2.8.1 - 10.2.8.5 4
1.2.9 4 3.9 3 6.3 3 10.2.9.1 - 10.2.9.5 4
1.2.10 2 4.1.1 - 4.1.5 4 6.4 2 10.2.10 4
1.2.11 4 4.2 4 7.1 3 10.2.11 4
1.2.12 4 4.3 4 7.2 3 10.2.12 2
1.2.13 4 4.4.1 - 4.4.5 4 7.3 3 10.2.13 3
1.2.14 4 4.5.1 - 4.5.5 4 7.4 3 10.3.1 4
1.3.1 3 4.6.1 - 4.6.5 4 7.5 3 10.3.2 4
1.3.2.1 – 1.3.2.5 4 4.7 4 7.6.1 – 7.6.3 3 10.3.3 4
1.3.3 4 4.8 4 7.7.1 – 7.7.2 2 10.3.4 4
1.3.4 4 4.9.1 - 4.9.5 4 8.1 2 10.3.5 4
1.3.5 3 4.10.1 - 4.10.5 4 8.2 2 10.3.6 4
1.3.6 3 5.1.1 3 8.3.1 - 8.3.3 2 10.3.7 4
1.4.1 4 5.1.2 4 8.4.1 - 8.3.3 2 10.3.8 2
1.4.2 3 5.1.3 3 9.1 4 10.3.9 2
1.4.3 3 5.1.4 3 9.2.1 - 9.2.5 4 10.3.10 3
1.4.4 3 5.2.1 4 9.3 3 10.3.11 3
1.4.5 3 5.2.2 4 9.4 3 10.3.12 4
1.5.1 4 5.2.3 4 9.5 2 10.3.13 4
1.5.2 4 5.2.4 3 9.6 3 10.3.14 3
2.1 3 5.2.5 3 9.7 3    

Earlier Draft:

4 March 2002


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

Page Updated 21-May-2004

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