Site Map       Search  
ARCHIVES

Please note: You are viewing archival ICANN material. Links and information may be outdated or incorrect. Visit ICANN's main website for current information.

New sTLD Application

Part E. Technical Specification

15 December 2003

Part A. Explanatory Notes | Part B. Application Form | Part C. Business Plan | Part D. Financial Model | Part E. Technical Specification | Part F. Application Checklist

 

Introduction

This document describes the minimum technical requirements necessary to comply with the technical specifications of the Request for Proposal.

If applicants subcontract the whole of the registry service function to a third party, this must be identified in all appropriate areas.

Where subcontractors are to be employed by the applicant for any significant portion of the business or technical operations (other than acquisition of standard hardware or software), the proposed subcontractors must be clearly identified and an explanation must be provided of the subcontracted work. The applicant is responsible for providing the information required as described in this document even if part of the work is to be performed by a subcontractor.

The Technical Capabilities and Plan section must address the following. Links to other materials must not be included:

1. Outline the Registry Operator's technical capabilities. Provide a description of the Registry Operator's technical capabilities, including information about key technical personnel (qualifications and experience), size of technical workforce and access to systems development tools. Outline any significant prior technical achievements.

2. Technical plan for the proposed registry operations. Present a technical plan for the proposed registry operations. In addition to providing basic information concerning the Registry Operator's proposed technical solution, this section offers the Registry Operator an opportunity to demonstrate that it has carefully analyzed the technical requirements of registry operation. Factors that must be addressed in the technical plan include:

a. General description of proposed facilities and systems. Address all system locations. Address the specific types of systems being used, their capacity and interoperability, general availability and level of security. Describe in appropriate detail buildings, hardware, software systems, environmental equipment and Internet connectivity. (Note that more detail may be provided in later sections.)

b. Describe the registry-registrar model and protocol.

c. Database capabilities including database software, size, throughput, scalability, procedures for object creation, editing, and deletion, change notifications, registrar transfer procedures, grace period implementation and reporting capabilities.

d. Zone file generation including procedures for changes, editing by registrars and updates. Address frequency, security, process, interface, user authentication, logging and data back-up.

e. Zone file distribution and publication. Locations of nameservers, procedures for and means of distributing zone files to them.

f. Billing and collection systems. Technical characteristics, system security, accessibility.

g. Backup. Describe frequency and procedures for backup of data. Describe hardware and systems used, data format, identity of suggested escrow agent(s) and procedures for retrieval of data/rebuild of database.

h. Escrow. Describe escrow arrangements, data formats, insurance arrangements and backup plans for data recovery.

i. Publicly accessible WHOIS service. Address software and hardware, connection speed, search capabilities and coordination with other WHOIS systems.

j. System security and physical security. Technical and physical capabilities and procedures to prevent system hacks, break-ins, data tampering and other disruptions to operations.

k. Peak capacities. Technical capability for handling a larger-than-projected demand for registration or load. Effects on load on servers, databases, back-up systems, support systems, escrow systems, maintenance and personnel.

l. System reliability. Define, analyze and quantify quality of service.

m. System outage prevention. Procedures for problem detection, redundancy of all systems, backup power supply, facility security and technical security. Outline the availability of backup software, operating system and hardware. Outline system monitoring, technical maintenance staff and server locations.

n. System recovery procedures. Procedures for restoring the system to operation in the event of a system outage, both expected and unexpected. Identify redundant/diverse systems for providing service in the event of an outage and describe the process for recovery from various types of failures. Describe the training of technical staff who will perform these tasks, the availability and backup of software and operating systems needed to restore the system to operation and the availability of the hardware needed to restore and run the system. Describe backup electrical power systems and the projected time for system restoration. Describe procedures for testing the process of restoring the system to operation in the event of an outage, the documentation kept on system outages and on potential system problems that could result in outages.

o. Technical and other support. Support for registrars and for Internet users and registrants. Describe technical help systems, personnel accessibility, web-based, telephone and other support services to be offered, time availability of support and language-availability of support.

By checking this box the applicant certifies (a) that he or she has authority to do so on behalf of the Registry Operator and, on his or her own behalf and on behalf of the Registry Operator, (b) that all information contained in this proposal are true and accurate to the best of its knowledge and information. By checking this box, the Registry Operator understands that any material misstatement or misrepresentation (or omission of material information) will reflect negatively on any application of which this proposal is a part and might result in cancellation of any delegation of a top-level domain based on such an application.

© Internet Corporation for Assigned Names and Numbers