Generic Top-Level Domain (gTLD) Registry Agreements
TLD Sponsorship Agreement: Attachment 6
Minimum ICANN-Required Functional Specifications for Registry Services Pursuant to the responsibility delegated to it in Attachment 2, Sponsor will prescribe functional requirements for Registry Services provided by the Registry Operator for the Sponsored TLD. Those functional requirements shall ensure that at least the following minimum functional capabilities are provided. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in IETF RFC 2119. The nameservers for the Sponsored TLD MUST be operated in compliance with the following Requests for Comments (RFCs): 1034, 1035, 1101, 2181, 2182. In clarification of the statement of host-name rules in these RFCs, all Registered Names SHALL comply with the following syntax in augmented Backus-Naur Form (BNF) as described in RFC 2234:
There MUST be nameservers for the Sponsored TLD on at least five different network segments. So that the IANA has zone-file access, zone-file transfers MUST be enabled at all nameservers for transfers to at least 128.9.0.0/16 and 192.0.32.0/20. 3. Registry System Requirements The registry system MUST enforce the name reservations set forth in Attachment 11 and the Charter requirements set forth in Attachment 1. Whois service MUST meet at least the functional specifications set forth in Attachments 15, 16, and 17. Data escrow MUST meet at least the functional specifications set forth in Attachments 18 and 19. The registry shall be capable of storing the data to be escrowed. The registry system MUST provide data sufficient to meet the reporting requirements set forth in Attachments 20 and 21. Prior draft: Comments concerning the layout, construction and functionality of this site should be sent to webmaster@icann.org.
(c) 2001 The Internet Corporation for Assigned Names and Numbers. All rights reserved. |