.org Registry Agreement: Appendix U

23 October 2002

Transition Reports

PIR shall provide the following reports and related data to ICANN for use in its evaluation of the transition process. 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. As used in this Appendix U, the term "Authorized Registrar" refers to a registrar accredited by ICANN that has a PIR Registry-Registrar Agreement (Appendix F) for the .org TLD currently in effect. As used in this Appendix U, the word "Cutover" refers to the (short) process that changes the real-time transaction-service provider from VeriSign to PIR (on or around 1 January 2003).

1 Concept: Effect of Reassignment of TLD

1.1 .org domain names under management – within 120 days after the Cutover, PIR will provide the following information and reports to ICANN:

1.1.1 List of ICANN-Accredited Registrars authorized to sponsor .org domain names immediately prior to the Cutover, as reflected in the files that PIR obtains from VeriSign Global Registry Services (VGRS).

1.1.2 Total number of .org domain names under management by each ICANN-Accredited Registrar at the time of the Cutover, as reflected in the files that PIR obtains from VeriSign Global Registry Services (VGRS).

1.2 Effect of Cutover on ICANN-Accredited Registrars – within 120 days after the Cutover, PIR will provide the following information and reports to ICANN:

1.2.1 Total number of Authorized Registrars participating in the Operational Test and Evaluation process ("OT&E") Phase 1 (pre-Cutover) who pass each day leading up to the Cutover.

1.2.2 Total number of Authorized Registrars who failed OT&E Phase 1.

1.2.3 Total number of Authorized Registrars re-tested for OT&E Phase 1.

1.2.4 Number and types of the complaints received from Authorized Registrars participating in OT&E Phase 1 and the time required to resolve complaints.

1.2.5 A summary of the standard communications and correspondence provided by the Registry Operator to Authorized Registrars in preparation of the Cutover.

1.2.6 Total number of Authorized Registrars (i.e. having Registry-Registrar Agreements with successor Registry Operator) as of the Cutover.

1.2.7 Number of Authorized Registrars having passed OT&E Phase 1 as of the beginning of the Cutover.

1.2.8 An explanation of the circumstances in which any ICANN-Accredited Registrar(s) authorized to sponsor .org domain names immediately prior to the Cutover had not become Authorized Registrars and passed OT&E Phase 1 as of the beginning of the Cutover. If the registrar later became an Authorized Registrar or passed OT&E Phase 1, the timing and circumstances should be given.

1.2.9 A summary of complaints received from Registrars during the Cutover process.

1.2.10 A report detailing the ability of Authorized Registrars to perform RRP transactions immediately following the Cutover.

1.2.11 A written report detailing the Registry Operator's observations of the ability of registrars to Cutover from one Registry Operator to another.

1.3 Effect on Registry Operations – within 120 days after the Cutover, PIR will provide the following information and reports to ICANN:

1.3.1 A schedule of discovered discrepancies between SRS data received by successor Registry Operator and SRS data held in production-ready environment prior to the Cutover.

1.3.2 A schedule of discovered discrepancies between SRS data received by successor Registry Operator and SRS data held in production-ready environment after the Cutover.

1.3.3 Summary of the correspondence between the Registry Operator and Verisign in preparation for the Cutover, including average number of days by Verisign to resolve requests for assistance.

1.3.4 A schedule of the down time experienced during the Cutover for:

1.3.4.1 SRS

1.3.4.2 DNS

1.3.4.3 Whois

1.3.5 A description of significant technical difficulties encountered in performing the Cutover.

1.3.6 A report detailing the modifications and adjustments to the Registry database and SRS servers during the 30-day period after the Cutover.

1.4 Effect on DNS Operations – within 120 days after the migration of DNS operations from Verisign DNS servers to Registry Operator's DNS servers, PIR will provide the following information and reports to ICANN:

1.4.1 A schedule of discovered discrepancies in DNS zone data between data received by successor Registry Operator and DNS zone data published by Registry Operator.

1.4.2 A report detailing the modifications and adjustments to the zone file creation, publication and distribution systems as a result of the migration of DNS operations.

2 Concept: Migration from RRP and Thin Registry to EPP and Thick Registry

2.1 Effect on ICANN-Accredited Registrars – within 120 days after each three-month interval (the "Reporting Interval") after the Cutover until the migration to EPP is completed, PIR will provide the following information and reports to ICANN:

2.1.1 Total number of Authorized Registrars participating in the OT&E Phase 2 (post-Cutover) who pass each day during the Reporting Interval.

2.1.2 Total number of Authorized Registrars who failed OT&E Phase 2 during the Reporting Interval.

2.1.3 Total number of Authorized Registrars re-tested for OT&E Phase 2 during the Reporting Interval.

2.1.4 Number and types of the complaints received from Authorized Registrars participating in OT&E Phase 2 during the Reporting Interval and the time required to resolve complaints.

2.1.5 A summary of the standard communications and correspondence provided by the Registry Operator to Authorized Registrars during the Reporting Interval in preparation of the migration to the EPP thick registry.

2.1.6 A schedule of Authorized Registrars who migrated from RRP to EPP each week during the Reporting Interval.

2.2 Effect on Registry Operation – within 120 days after each Reporting Interval, PIR will provide the following information and reports to ICANN:

2.2.1 A schedule by Authorized Registrar of the discrepancies between Whois data provided by the Registrar and the Whois data in the Registry Operator's Whois database after the migration of the Registrar to the thick EPP model.

2.2.2 A report of the effect the migration from RRP had on the SRS Protocol Interface.

3 Evaluation Of 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, PIR shall provide to ICANN a Whois Report with the following elements:

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

b. 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.

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

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

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

f. Identify and categorize types of privacy complaints.

4 Commercially Reasonable Efforts and Review

Some of the reports listed above to be provided by Registry Operator require access to data to which Registry Operator may not be privy or which may not be reasonably available to Registry Operator. Recognizing the importance of the proof of concept:

• Registry Operator shall use commercially reasonable efforts to obtain all necessary data and complete the required reports as set forth in this Appendix; and
• In the event Registry Operator 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 Registry Operator 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.

Page Updated 23-Oct-2002
©2002  The Internet Corporation for Assigned Names and Numbers. All rights reserved.