23 Provide name and full description of all the Registry Services to be provided
|gTLD||Full Legal Name||E-mail suffix||Detail|
|.casa||Go Daddy East, LLC||godaddy.com||View|
Go Daddy will provide a Shared Registration System (SRS). This system will provide the interfaces for the registrations of domain names and name servers. (Please see: (1) response to question 24 for more details on the SRS; and (2) the architecture diagrams in response to question 32.)
Go Daddy will maintain an extremely robust Domain Name System (DNS). Modeled on GoDaddy.comʹs current DNS, which is the largest DNS on the Internet. GoDaddy.com’s DNS handles more than 37 million zones and on average more than 9 billion queries per day. The SRS will feed data real-time into the DNS and will also facilitate and provide the infrastructure for the authorization and dissemination of related zone files. Go Daddy’s DNS will comply with relevant RFCs published by the Internet Engineering Task Force (IETF) and will be updated as needed to support all successor standards, modifications or additions relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. (For more details on Go Daddy’s DNS, please see: (1) the response to question 35; and (2) the architecture diagrams in response to question 32.)
The technical and business components of Go Daddy’s Registry Services will consist of multiple redundant data centers and backup systems, which follow standard industry practices, and are described as follows:
A. An Extensible Provisioning Protocol (EPP) protocol compliant gateway, supported by a Web-based registrar portal, enabling receipt of data from registrars concerning registration of domain names and name servers. Go Daddy’s EPP will be compliant with relevant Requests for Comments (RFCs) published by the Internet Engineering Task Force (IETF), which will be updated as needed to support all successor standards, modifications or additions relating to the provisioning and management of domain names using the EPP in conformance with RFCs 5910, 5730, 5731, 5732, 5733 and 5734. (Detailed specifically in the response to Question 25.)
B. Go Daddy will use a standard secure File Transfer Protocol (FTP) solution for dissemination of both TLD zone files and reports. Authentication and authorization (granted⁄suspended⁄ expired⁄deleted) will be controlled by the Go Daddy SRS.
C. The SRS will also support and feed into the Registration Data Directory Service (RDDS) (WHOIS Database Services). Go Daddy’s RDDS will be composed of three services: (1) a WHOIS service available through port 43; (2) a Web-based service providing free public query-based access; and (3) a Web-based service providing registrars query-based access. All three services access the same data store that will be updated in near real time. The complete RDDS will be deployed in multiple datacenters to provide higher levels of redundancy and stability. (Detailed specifically in the response to Question 26.)
D. Initially, no Internationalized Domain Name support will be offered.
E. Domain Name System Security Extensions (DNSSEC) will be offered. TLD zone files will be signed, implementing DNSSEC. The DNSSEC offering will comply with RFCs 4033, 4034, 4035, 4509 and will be updated as needed to support all their successor standards, modifications or additions relating to DNSSEC, and will follow the best practices described in RFC 4641 and its successor standards. (Detailed specifically in the response to Question 43.)
Supporting services provided will be: an operational test and evaluation environment (OT&E); domain release systems and associated billing and reporting systems; and data escrow services.
Similar gTLD applications: (2)
|gTLD||Full Legal Name||E-mail suffix||z||Detail|
|.home||Go Daddy East, LLC||godaddy.com||-2.24||Compare|
|.godaddy||Go Daddy East, LLC||godaddy.com||-1.75||Compare|