The ICANN New gTLD Applicant Guidebook Online Viewer

presented by Cloud Registry.



Included in public posting


Practice RFCs sponsored by the IETF, or (2) creates a condition that adversely affects the throughput, response time, consistency or coherence of responses to Internet servers or end systems, operating in accordance with applicable relevant standards that are authoritative and published by a well-established, recognized and authoritative standards body, such as relevant Standards-Track or Best Current Practice RFCs and relying on Registry Operator's delegation information or provisioning. The questions in this section (24-44) are intended to give applicants an opportunity to demonstrate their technical and operational capabilities to run a registry. In the event that an applicant chooses to outsource one or more parts of its registry operations, the applicant should still provide the full details of the technical arrangements. Note that the resource plans provided in this section assist in validating the technical and operational plans as well as informing the cost estimates in the Financial section below. Questions 24-30(a) are designed to provide a description of the applicant’s intended technical and operational approach for those registry functions that are outward-facing, i.e., interactions with registrars, registrants, and various DNS users. Responses to these questions will be published to allow review by affected parties.

Scoring Range



Demonstration of Technical & Operational Capability (External)


Shared Registration System (SRS) Performance: describe • the plan for operation of a robust and reliable SRS. SRS is a critical registry function for enabling multiple registrars to provide domain name registration services in the TLD. SRS must include the EPP interface to the registry, as well as any other interfaces intended to be provided, if they are critical to the functioning of the registry. Please refer to the requirements in Specification 6 (section 1.2) and Specification 10 (SLA Matrix) attached to the Registry Agreement; and • resourcing plans for the initial implementation of, and ongoing maintenance for, this aspect of the criteria (number and description of personnel roles allocated to this area). A complete answer should include, but is not limited to: • • • • • • A high-level SRS system description; Representative network diagram(s); Number of servers; Description of interconnectivity with other registry systems; Frequency of synchronization between servers; and Synchronization scheme (e.g., hot standby, cold standby).



Complete answer demonstrates: (1) a plan for operating a robust and reliable SRS, one of the five critical registry functions; (2) scalability and performance consistent with the overall business approach, and planned size of the registry; (3) a technical plan that is adequately resourced in the planned costs detailed in the financial section; and (4) evidence of compliance with Specification 6 (section 1.2) to the Registry Agreement.

1 - meets requirements: Response includes (1) An adequate description of SRS that substantially demonstrates the applicant’s capabilities and knowledge required to meet this element; (2) Details of a well-developed plan to operate a robust and reliable SRS; (3) SRS plans are sufficient to result in compliance with Specification 6 and Specification 10 to the Registry Agreement; (4) SRS is consistent with the technical, operational and financial approach described in the application; and (5) Demonstrates that adequate technical resources are already on hand, or committed or readily available to carry out this function. 0 - fails requirements: Does not meet all the requirements to score 1.

A complete answer is expected to be no more than



« Q24 - Q30(a): Technical & Op (ext)