Functional and Performance Specifications
Pursuant to the responsibility delegated to it in Appendix S, Registry will prescribe functional requirements for Registry Services provided for the .cat sTLD that 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.
2. Nameserver Requirements
The nameservers for the .cat Sponsored TLD MUST be operated in compliance with the following Requests for Comments (RFCs): 1034, 1035, 1101, 2181, and 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:
dot = %x2E ; "."
There MUST be nameservers for the .cat 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 188.8.131.52/16 and 184.108.40.206/20.
3. Registry System Requirements
The registry system MUST enforce the name reservations and Charter requirements set forth in Appendix S.
4. Whois Service Requirements
Whois service MUST meet at least the functional specifications set forth in Appendix 5.
5. Data Escrow Requirements
Data escrow MUST meet at least the functional specifications set forth in Appendix 1. The Registry shall be capable of storing the data to be escrowed.
6. Reporting Requirements
The Registry system MUST provide data sufficient to meet the reporting requirements set forth in Appendix 4.
7. Performance Specifications
DNS Service Availability. Service availability as it applies to the DNS Service refers to the ability of the Nameservers, as a group, to resolve a DNS query from an Internet user. The committed Performance Specification is 99.999% measured in Monthly Timeframes.
Performance Level. At any time at which it is available, each Nameserver (including a cluster of Nameservers addressed at a shared IP address) MUST be able to handle a load of queries for DNS data that is three times the measured daily peak (averaged over the Monthly Timeframe) of such requests on the most loaded Nameserver.
Cross-Network Nameserver Performance Requirements. The committed Performance Specification for cross-network Nameserver performance is a measured Round-trip time of less than 300 ms and measured packet loss of fewer than 10%. Cross-network Nameserver performance measurements will be conducted by ICANN at times of it's choosing, in the following manner:
Whois Service Availability. The committed Performance Specification for Whois Service is 99.4% measured in Monthly Timeframes.
Whois Service Performance Level. The Whois Service will, on average, be able to handle 50 queries per second.
Whois Service Response Times. The Whois Service will have a maximum whois query response time of 1.5 seconds. Failure of the Whois Service to respond to three (3) consecutive rcPing commands initiated by the Registry at regular intervals within such maximum processing time shall mean the Whois Service is considered unavailable.
Whois Service Updates. The data provided by the Whois Service will be updated on at least a daily basis.
8. Location of Data Centers
The back-end provider, currently CORE Internet Council of Registrars, will provide data centers for registration services. The primary data center is currently located in Dortmund, Germany. Back-up data centers will be located in other locations in the future.