.CAT Registry Agreement | Functional and Performance Specifications
  icann logo
Appendix 7

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.

1. Conventions

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 ; "."
dash = %x2D ; "-"
alpha = %x41-5A / %x61-7A ; A-Z / a-z
digit = %x30-39 ; 0-9
ldh = alpha / digit / dash
id-prefix = alpha / digit
label = id-prefix [*61ldh id-prefix]
sldn = label dot label; not to exceed 254 characters
hostname = *(label dot) sldn; not to exceed 254 characters

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 and

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:

The measurements will be conducted by sending strings of DNS request packets from each of four measuring locations to each of the Nameservers and observing the responses from the Nameservers. (These strings of requests and responses are referred to as a "CNNP Test".) The measuring locations will be four root nameserver locations (on the US East Coast, US West Coast, Asia, and Europe).

Each string of request packets will consist of 100 UDP packets at 10-second intervals requesting ns records for arbitrarily selected second-level domains in the Sponsored TLD, preselected to ensure that the names exist in the Sponsored TLD and are resolvable. The packet loss (i.e. the percentage of response packets not received) and the average Round-trip time for response packets received will be noted.

To meet the packet loss and Round-trip-time requirements for a particular CNNP Test, all three of the following must be true:

The Round-trip time and packet loss from each measurement location to at least one Nameserver must not exceed the required values.

The Round-trip time to each of 75% of the Nameservers from at least one of the measurement locations must not exceed the required value.

The packet loss to each of the Nameservers from at least one of the measurement locations must not exceed the required value.

Any failing CNNP Test result obtained during an identified Core Internet Service Failure shall not be considered.

To ensure a properly diverse testing sample, ICANN will conduct the CNNP Tests at varying times (i.e. at different times of day, as well as on different days of the week). The cross-network Nameserver performance requirement will be deemed not to have been met only if the Nameservers persistently fail the CNNP Tests with no less than three consecutive failed CNNP Tests to be considered to have persistently failed.

In the event of persistent failure of the CNNP Tests, ICANN will give Registry written notice of the failures (with backup data) and Registry will have sixty days to cure the failure.

If, following Registry's opportunity to cure, the Nameservers continue to persistently fail CNNP Tests and Registry fails to resolve the problem within thirty days after written notice of the continuing failures, Registry will be in breach of its obligations under the Registry Agreement.

Sixty days before the commencement of testing under this provision, ICANN will provide Registry with the opportunity to evaluate the testing tools and procedures to be used by ICANN. In the event that Registry does not approve of such tools and procedures, ICANN will work directly with Registry to make necessary modifications.

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.