Common use of DNS service availability Clause in Contracts

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 Operator written notice of the failures (with backup data) and Registry Operator will have sixty days to cure the failure. If, following Registry Operator's opportunity to cure, the Nameservers continue to persistently fail CNNP Tests and Registry Operator fails to resolve the problem within thirty days after written notice of the continuing failures, Registry Operator 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 Operator with the opportunity to evaluate the testing tools and procedures to be used by ICANN. In the event that Registry Operator does not approve of such tools and procedures, ICANN will work directly with Registry Operator 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 Operator at regular intervals within such maximum processing time shall mean the Whois Service is considered unavailable.

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 under 300 ms and measured packet loss of fewer than under 10%. Cross-network Nameserver performance measurements will be conducted by ICANN at times of it’s its 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-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 not 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 Operator written notice of the failures (with backup data) and Registry Operator will have sixty days to cure the failure. If, following Registry OperatorRegistry's opportunity to cure, the Nameservers continue to persistently fail CNNP Tests and Registry Operator fails to resolve the problem within thirty days after written notice of the continuing failures, Registry Operator 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 Operator with the opportunity to evaluate the testing tools and procedures to be used by ICANN. In the event that Registry Operator does not approve of such tools and procedures, ICANN will work directly with Registry Operator 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 TimesAvailability. 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 Operator at regular intervals within such maximum processing time shall mean the committed Performance Specification for Whois Service is considered unavailable99.4% measured in Monthly Timeframes.

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-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 Operator written notice of the failures (with backup data) and Registry Operator will have sixty days to cure the failure. If, following Registry Operator's opportunity to cure, the Nameservers continue to persistently fail CNNP Tests and Registry Operator fails to resolve the problem within thirty days after written notice of the continuing failures, Registry Operator 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 Operator with the opportunity to evaluate the testing tools and procedures to be used by ICANN. In the event that Registry Operator does not approve of such tools and procedures, ICANN will work directly with Registry Operator 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 Operator at regular intervals within such maximum processing time shall mean the Whois Service is considered unavailable.

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 under 300 ms and measured packet loss of fewer than under 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 not 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 Operator written notice of the failures (with backup data) and Registry Operator will have sixty days to cure the failure. If, following Registry Operator's opportunity to cure, the Nameservers continue to persistently fail CNNP Tests and Registry Operator fails to resolve the problem within thirty days after written notice of the continuing failures, Registry Operator 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 Operator with the opportunity to evaluate the testing tools and procedures to be used by ICANN. In the event that Registry Operator does not approve of such tools and procedures, ICANN will work directly with Registry Operator 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 Operator at regular intervals within such maximum processing time shall mean the Whois Service is considered unavailable.

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-10- second intervals requesting ns records for arbitrarily selected second-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 Operator written notice of the failures (with backup data) and Registry Operator will have sixty days to cure the failure. If, following Registry Operator's opportunity to cure, the Nameservers continue to persistently fail CNNP Tests and Registry Operator fails to resolve the problem within thirty days after written notice of the continuing failures, Registry Operator 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 Operator with the opportunity to evaluate the testing tools and procedures to be used by ICANN. In the event that Registry Operator does not approve of such tools and procedures, ICANN will work directly with Registry Operator 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 Operator at regular intervals within such maximum processing time shall mean the Whois Service is considered unavailable.

DNS service availability. Service availability as it applies to the DNS Service refers to the ability of the Nameserversname servers, as a group, to resolve a DNS query from an Internet user. The committed Performance Specification is 99.999100% measured in Monthly Timeframes. Performance Level. At any time at which it is available, each Nameserver name server (including a cluster of Nameservers name servers 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 Nameservername server. Cross-Network Nameserver Name server Performance Requirements. The committed Performance Specification for cross-network Nameserver name server performance is a measured Round-trip time of less than 300 ms and measured packet loss of fewer than 10%. Cross-network Nameserver name server performance measurements will be conducted by ICANN at times of it’s its 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 name servers and observing the responses from the Nameserversname servers. (These strings of requests and responses are referred to as a "CNNP Test".) The measuring locations will be four root nameserver name server 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 name server must not exceed the required values. The Round-trip time to each of 75% of the Nameservers name servers from at least one of the measurement locations must not exceed the required value. The packet loss to each of the Nameservers name servers 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 name server performance requirement will be deemed not to have been met only if the Nameservers name servers 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 Operator Sponsor written notice of the failures (with backup data) and Sponsor and its designated Registry Operator will have sixty 60 (sixty) days to cure the failure. If, following Registry Operator's Sponsor’s opportunity to cure, the Nameservers name servers continue to persistently fail CNNP Tests and Sponsor and its Registry Operator fails to resolve the problem within thirty 30 (thirty) days after written notice of the continuing failures, Registry Operator Sponsor will be in breach of its obligations under the Registry Agreement. Sixty 60 (sixty) days before the commencement of testing under this provision, ICANN will provide Sponsor and its designated Registry Operator with the opportunity to evaluate the testing tools and procedures to be used by ICANN. In the event that Registry Operator Sponsor does not approve of such tools and procedures, ICANN will work directly with Sponsor and its designated Registry Operator 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 Each Whois Service willserver must, on average, be able to handle 50 a load of queries per secondthat is three times the measured daily peak (averaged over the Monthly Timeframe) of such requests on the most loaded Whois server. 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 (3three) consecutive rcPing commands initiated by the Registry Operator at regular intervals within such maximum processing time shall mean the Whois Service is considered unavailable.

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 under 300 ms and measured packet loss of fewer than under 10%. Cross-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 not 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 Operator written notice of the failures (with backup data) and Registry Operator will have sixty days to cure the failure. If, following Registry Operator's opportunity to cure, the Nameservers continue to persistently fail CNNP Tests and Registry Operator fails to resolve the problem within thirty days after written notice of the continuing failures, Registry Operator 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 Operator with the opportunity to evaluate the testing tools and procedures to be used by ICANN. In the event that Registry Operator does not approve of such tools and procedures, ICANN will work directly with Registry Operator 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 Operator at regular intervals within such maximum processing time shall mean the Whois Service is considered unavailable.

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 under 300 ms and measured packet loss of fewer than under 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-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 not 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 Operator written notice of the failures (with backup data) and Registry Operator will have sixty days to cure the failure. If, following Registry Operator's opportunity to cure, the Nameservers continue to persistently fail CNNP Tests and Registry Operator fails to resolve the problem within thirty days after written notice of the continuing failures, Registry Operator 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 Operator with the opportunity to evaluate the testing tools and procedures to be used by ICANN. In the event that Registry Operator does not approve of such tools and procedures, ICANN will work directly with Registry Operator 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 Operator at regular intervals within such maximum processing time shall mean the Whois Service is considered unavailable.

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 under 300 ms and measured packet loss of fewer than under 10%. Cross-network Nameserver performance measurements will be conducted by ICANN at times of it’s its 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-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 not 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 Operator written notice of the failures (with backup data) and Registry Operator will have sixty days to cure the failure. If, following Registry Operator's opportunity to cure, the Nameservers continue to persistently fail CNNP Tests and Registry Operator fails to resolve the problem within thirty days after written notice of the continuing failures, Registry Operator 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 Operator with the opportunity to evaluate the testing tools and procedures to be used by ICANN. In the event that Registry Operator does not approve of such tools and procedures, ICANN will work directly with Registry Operator 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 Operator at regular intervals within such maximum processing time shall mean the Whois Service is considered unavailable.