 |
Proposed TLD Sponsorship Agreement: Attachment 21 (.coop) Posted: 4 November 2001 |
Proof of Concepts
Sponsor shall provide the following reports and related data to ICANN for use in its proof of concept evaluation. Such reports shall be provided during the Term of the TLD Sponsorship Agreement. After ICANN's formal proof of concept evaluation is complete, the parties may agree to amend this Attachment and transfer the remaining relevant reporting requirements to Attachment 20. Capitalized terms shall have the meanings defined in the TLD Sponsorship Agreement and its Attachments.
The reports provided by Sponsor as described in this Attachment shall be subject to confidentiality restrictions according to categories described in Section 11.
1. Concept: Procedures for Maintaining Stability and Fairness in Launch of a Sponsored TLD ("sTLD")
1.1 Phase 1 Effectiveness - within 180 days after the end of Phase 11 Sponsor shall provide the following information and reports to ICANN.
1.1.1 A list of the representative group of cooperatives chosen to test the on-line application system.
1.1.2 A summary of the feedback provided by the representative group of cooperatives during Phase 1.
1.1.3 A description of significant technical difficulties encountered during Phase 1.
1.2 Phase 2 Effectiveness - within 120 days after the end of Phase 2, Sponsor shall provide the following information and reports to ICANN.
1.2.1 Total application volume by week during Phase 2.
1.2.2 Total initial Phase 2 application volume with holder addresses in the regions described below:
1.2.3 A list of all Founders admitted during the period of this report.
1.2.4 Total number of domain name applications submitted during Phase 2 by each Founder.
1.2.5 A summary of the complaints received from applicants regarding the processing of Phase 2 applications.
1.2.6 A description of significant technical difficulties encountered during Phase 2.
1.2.7 A report detailing the effectiveness of Sponsor's domain name dispute policy adapted for Founder registrations during Phase 2.
1.3 Phase 3 Effectiveness - within 120 days after the end of Phase 3, Sponsor, Sponsor shall provide the following information and reports to ICANN.
1.3.1 Total application (for Registered Names) volume by week during Phase 3.
1.3.2 Total initial Phase 3 application volume with holder addresses in the regions described below:
1.3.3 A list of all Innovators admitted during the period of this report.
1.3.4 Total number of domain name applications submitted during Phase 3 by each Innovator.
1.3.5 A summary of the complaints received from applicants regarding the processing of Phase 3 applications.
1.3.6 A description of significant technical difficulties encountered during Phase 3.
1.3.7 A report detailing the effectiveness of Sponsor's domain name dispute policy adapted during Phase 3.
1.4 Phase 4 Effectiveness - within 180 days after the start of Phase 4, Sponsor shall provide the following information and reports to ICANN.
1.4.1 Total initial registration volume by week.
1.4.2 Total initial Phase 4 registration volume for holder addresses in the regions described below:
1.4.3 A list of all VP partners admitted during the period of this report.
1.4.4 Total number of domain names registered during Phase 4 submitted by each VP Partner.
1.4.5 A summary of the complaints received from registrants regarding the processing of Phase 4 registrations.
1.4.6 A description of significant technical difficulties encountered during Phase 4.
1.4.7 A summary of difficulties encountered, if any, in the commencement of ENS Services.
1.5 Phase 5 Effectiveness - within 180 days after the start of Phase 5, Sponsor shall provide the following information and reports to ICANN.
1.5.1 The date registrar applications were first made available to ICANN-Accredited Registrars.
1.5.2 A list of all ICANN-Accredited Registrars submitting applications to Sponsor to become authorized in the Sponsored TLD, the date the application was submitted to the Sponsor, and the disposition or status of the application (e.g. accepted, rejected).
1.5.3 For each authorized ICANN-Accredited Registrar, provide a breakdown of the total number of domain names randomly transferred by Sponsor.
1.5.4 For each authorized ICANN-Accredited Registrar, provide a breakdown of the total number of domain names transferred pursuant to registrant choice.
1.5.5 A summary of complaints received from registrants, if any, regarding the transfer of their domain names to authorized ICANN-Accredited Registrars.
1.5.6 A summary of any significant technical difficulties encountered during the implementation of registrars.
1.6 Miscellaneous - within 30 days after learning of any lawsuit concerning the start-up activities of .coop (i.e. activities in Phase 1, Phase 2, or the first 140 days of Phase 3), please identify the lawsuit and provide a copy of the complaint or describe its allegations.
2. An sTLD can Provide Some Degree of Competition with Unrestricted TLDs Such as .com and .info, Even with a Limited Number of Authorized Registrars.
Annual Reports - no later than one month after each anniversary date after the Effective Date, Sponsor shall provide to ICANN an "Effectiveness of Competition Report" with the following information:
2.1 Total number of authorized ICANN-Accredited Registrars registering domain names in the sTLD.
2.1.1 Total number of ICANN-Accredited Registrars authorized to register domain names in the sTLD broken down on a quarterly basis (include a geographic breakdown by global region).
2.1.2 Total number of ICANN-Accredited Registrars authorized to register domain names in the sTLD that were terminated, broken down on a quarterly basis (include a geographic breakdown by global region).
2.1.3 Describe the reason for each termination listed above.
2.1.4 Total number of registrations under management by each authorized ICANN-Accredited Registrar, broken down on a quarterly basis.
2.2 A list of all registrars submitting applications to the Sponsor to become authorized in the Sponsored TLD, the date on which the application was submitted to the Sponsor, and the disposition or status of the application.
2.3 Number of registrations during each calendar month ending in the year to which the report relates.
2.4 Number of renewals during each calendar month ending in the year to which the report relates.
2.5 Number of registration transfers (not to include those registrations transferred by Sponsor as part of the start-up plan) during each calendar month ending in the year to which the report relates.
2.6 Provide the Geographic breakdown of registrants by global region:
2.7 Total domain names expiring and not renewed during each calendar month ending in the year to which the report relates.
2.8 Average term of new registrations during each calendar month ending in the year to which the report relates.
2.9 Average term of renewals during each calendar month ending in the year to which the report relates.
3. Concept: Adding a sTLD Will Result in an Expansion and Globalization of the Effective Namespace, Rather than Wasteful Duplication of Registrations
Annual Reports - No later than one month after each anniversary date after the Effective Date, Sponsor shall provide to ICANN an "Expansion of the DNS Report" with the following elements:
3.1 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.
3.2 An estimate of the percentage of such duplicate registrations registered to the same holder (e.g., example.coop and example.com registered to the same holder).
3.3 The estimated percentage of such duplicate registrations sharing at least one nameserver with respect to each of the five domains listed in 3.1.1 to 3.1.5.
4. Concept: Registry Services Can Effectively Be Provided by a Registry Operator Selected by Sponsor
Annual Reports - No later than one month after each anniversary date after the Effective Date, Sponsor shall provide to ICANN a "Registry Operator Report" with the following elements:
4.1 Ability to Effectively Operate the Registry.
4.1.1 Total number of registrations under management during each calendar month ending in the year to which the report relates.
4.1.2 A summary of the complaints received (if any) from registrants regarding the Registry Operator.
4.1.3 A description of significant technical difficulties encountered by Registry Operator during the period of this report.
4.2 Ability to Attract and Maintain Registrars.
4.2.1 A report summarizing the mechanisms used by Registry Operator for testing and evaluating registrars' technical ability to comply with registration policies and restrictions.
4.2.2 A summary of complaints received from registrars regarding technical testing and evaluation.
4.2.3 A discussion of the effectiveness of the technical testing and evaluation to include the number of registrars tested, number of registrars that failed testing and methods for improvement (if any).
4.3 Total Number of complaints received by Sponsor from authorized ICANN-Accredited Registrars regarding services provided by Registry Operator.
4.3.1 Identify and categorize the types of complaints received from authorized registrars.
4.3.2 List corrective actions, if any, in response to the categorized complaints.
5. Concept: Sponsor Can Institute Adequate Mechanisms for Ensuring that all Registrars Follow Sound Business Practices and are Treated Fairly
Annual Reports - No later than one month after each anniversary date after the Effective Date, Sponsor shall provide to ICANN a "Fair-Treatment Report" with the following elements:
5.1 Total number of complaints received by Sponsor from registrants regarding services provided by authorized ICANN-Accredited Registrars. Identify the registrar and categorize the nature/type of complaint (e.g. registrar failure to renew).
5.2 Total number of authorized ICANN-Accredited Registrars restricted from further registrations for non-payment of registration fees.
6. Concept: Capital Requirements in Operating the sTLD
Annual Reports - No later than one month after each anniversary date after the Effective Date, Sponsor shall provide to ICANN a "Funding Requirements Report" with the following elements:
6.1 Total expenditures by Sponsor and Registry Operator during the period of this report.
6.2 Breakdown of expenditures by Sponsor and Registry Operator for the following categories:
6.2.1 Marketing;
6.2.2 Software; and
6.2.3 Hardware.
6.3 Provide a list of the employee positions hired by Sponsor and Registry Operator during the following periods:
7. Concept: Introducing the sTLD will Enhance the Utility of the DNS
Annual Reports - no later than one month after each anniversary date after the Effective Date, Sponsor shall provide to ICANN an "Enhancement of DNS Utility Report" with the following elements:
7.1 Use of Sector Specific Second-Level Sub-Domains.
7.1.1 Identify each sector specific second-level sub-domain in the sTLD.
7.1.2 Total number of Registered Names in each sector specific second-level sub-domain.
7.2 A report summarizing the mechanisms for enforcement of disputes between owners of rights in names (such as trademarks) and registrants and the effectiveness of those mechanisms.
7.3 Sponsored TLD Community Participation.
7.3.1 Identify groups, associations and the like that are members of the Sponsored TLD Community and actively participate in the establishment, revision or enforcement of standards, policies, procedures and practices for the sTLD.
7.3.2 Identify each member of the Sponsor.
7.3.3 A report describing the effectiveness of the .coop e-mail discussion (if one exists) list in promoting sTLD Community discussion.
7.3.4 A report describing the effectiveness of the open forum for communication provided by the Sponsor as required by Attachment 23.
8. Concept: A Charter Eligibility Dispute Resolution Policy ("CEDRP") is in an Effective Means to Enforce the sTLD Charter
Annual Reports - no later than one month after each anniversary date after the Effective Date, Sponsor shall provide to ICANN a "Charter Eligibility Dispute Resolution Policy Report" with the following elements:
8.1 A statement of the total number of Charter Eligibility Dispute Resolution Policy ("CEDRP") Challenges filed.
8.2 A statement, broken down by the region of the Registered Name holder's address as described below, of the number of names subject to successful CEDRP challenges:
8.3 A statement, broken down by the region of the successful challenger's address as described below, of the number of names subject to successful CEDRP challenges:
9. Concept: Sponsor-Provided ENS Services Are an Effective Way to Enforce Registration Restrictions
Annual Reports - no later than one month after each anniversary date after the Effective Date, Sponsor shall provide to ICANN an "ENS Services Report" with the following elements:
9.1 A summary of complaints received from authorized ICANN-Accredited Registrars regarding ENS Services.
9.2 A summary of complaints received from registrants regarding ENS Services.
9.3 If applicable, a report detailing the sTLD Community's comments regarding whether ENS Services should be distributed on a broader collaborative basis among appropriate organizations selected by Sponsor. Include:
9.3.1 a list of appropriate organizations; and
9.3.2 the extent to which each organization is authorized to offer ENS Services. Provide a report detailing the effectiveness of the ENS Services in limiting abusive registration practices
9.4 Provide a report detailing the effectiveness of the ENS Services in limiting abusive registration practices.
10. Commercially Reasonable Efforts and Review
Many of the reports to be provided by Sponsor require access to data to which Sponsor may not be privy or that may not be reasonably available to Sponsor. Recognizing the importance of the proof of concept:
Sponsor shall use commercially reasonable efforts to obtain all necessary data and complete the required reports as set forth in this Attachment; and
In the event Sponsor 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 Sponsor and/or the 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.
The reports provided by Sponsor as described in this Attachment 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. |
Sponsor shall clearly label all reports and information provided pursuant to this Attachment with the appropriate confidentiality category prior to submission to ICANN.
ICANN shall use commercially reasonable efforts to prevent public disclosure prior to the times described in the table above.
The following table sets forth,
for each report, the confidentiality category (CC) that applies to it:
| Report ID | CC | Report ID | CC | Report ID | CC | Report ID | CC |
| 1.1.1 | 3 | 1.4.3 | 3 | 2.5 | 3 | 5.2 | 3 |
| 1.1.2 | 3 | 1.4.4 | 4 | 2.6 | 4 | 6.1 | 3 |
| 1.1.3 | 3 | 1.4.5 | 3 | 2.7 | 3 | 6.2 | 1 |
| 1.2.1 | 3 | 1.4.6 | 3 | 2.8 | 3 | 6.3 | 2 |
| 1.2.2 | 3 | 1.4.7 | 3 | 2.9 | 3 | 7.1.1 | 4 |
| 1.2.3 | 3 | 1.5.1 | 4 | 3.1 | 4 | 7.1.2 | 4 |
| 1.2.4 | 3 | 1.5.2 | 4 | 3.2 | 4 | 7.2 | 4 |
| 1.2.5 | 3 | 1.5.3 | 3 | 3.3 | 4 | 7.3.1 | 4 |
| 1.2.6 | 3 | 1.5.4 | 3 | 4.1.1 | 3 | 7.3.2 | 4 |
| 1.2.7 | 3 | 1.5.5 | 3 | 4.1.2 | 3 | 7.3.3 | 4 |
| 1.3.1 | 3 | 1.5.6 | 3 | 4.1.3 | 3 | 7.3.4 | 4 |
| 1.3.2 | 3 | 1.6 | 4 | 4.2.1 | 4 | 8.1 | 4 |
| 1.3.3 | 3 | 2.1.1 | 4 | 4.2.2 | 3 | 8.2 | 4 |
| 1.3.4 | 3 | 2.1.2 | 4 | 4.2.3 | 3 | 8.3 | 4 |
| 1.3.5 | 3 | 2.1.3 | 2 | 4.3 | 2 | 9.1 | 3 |
| 1.3.6 | 3 | 2.1.4 | 3 | 4.3.1 | 2 | 9.2 | 3 |
| 1.3.7 | 3 | 2.2 | 3 | 4.3.2 | 2 | 9.3 | 4 |
| 1.4.1 | 3 | 2.3 | 3 | 5.1 | 2 | 9.4 | 4 |
| 1.4.2 | 3 | 2.4 | 3 |
Note (to item 1.1):
1. Phases 1 through 5 are described in Attachment 8.
should be sent to webmaster@icann.org.
(c) 2001 The Internet Corporation for Assigned Names and Numbers. All rights reserved.