|
C28. Describe the technical performance (including quality-of-service
commitments) you propose to make. See http://www.icann.org/tlds/agreements/name/registry-agmt-appd-29jun01.htm
|
DNS |
|
Service Availability |
99.999% |
Performance Level |
must be able to handle 3 times the daily peak no of queries, averaged over the month on the most loaded name server |
Response Time |
meet the Cross-Network Name server Performance requirements of ICANN 95% of queries in 1.5s (not including network latency) |
Planned Outages |
None Allowed |
Planned Outage Day |
N/A |
Extended Planed Outages |
None Allowed |
Extended Planned Outage Day |
N/A |
REGISTRY SERVICE |
|
Service Availability |
99.9% |
Performance Level |
400tx/s (RRP) |
Response Time |
97% of tx in 4 seconds (not including network latency) @ performance level |
Planned Outages |
8 hours/month |
Planned Outage Day |
0600-1400 UTC Sunday |
Extended Planned Outages |
18 hours per ¼ year |
Extended Planned Outage Day |
0600-1400 UTC Sunday |
WHOIS SERVICE |
|
Service Availability |
99.95% |
Performance Level |
400tx/s |
Response Time |
97% of queries in 1.5 seconds (not including network latency) @ performance level |
Planned Outages |
8 hours/month |
Planned Outage Day |
0600-1400 UTC Sunday |
Extended Planed Outages |
18 hours per ¼ year |
Extended Planned Outage Day |
0600-1400 UTC Sunday |
REGISTRY SERVICE - ADMIN WEB SITE |
|
Service Availability |
99.9% |
Performance Level |
Not stated |
Response Time |
97% of tx in 4 seconds (not including network latency) @ performance level |
Planned Outages |
8 hours/month |
Planned Outage Day |
0600-1400 UTC Sunday |
Extended Planned Outages |
18 hours per ¼ year |
Extended Planned Outage Day |
0600-1400 UTC Sunday |
Unity Registry will ensure the update frequencies are:
Name Server = 15 minutes for 95%
WhoIs = 15 minutes for 95%.
Except in the case of nameserver performance requirements, Unity Registry will perform monitoring from internally located systems as a means to verify that the availability and performance measurements of this document are being met.
Details of measurement and monitoring are found in full in Section 17. Specific tools will be developed to measure each item.
Unity Registry will meet cross-network nameserver performance requirements, recognising that nameserver round-trip time and packet loss from the Internet are important elements of the quality of service provided by the Registry Operator. We expect to agree the requirement with ICANN in drawing up the Registry Agreement and for that requirement to form part of that agreement.
Unity Registry will make provision in its agreements with registrars for penalty payments to be made should system performance fall below agreed standards.
Timeframes for notice
Planned outage |
7 days notice |
Extended planned outage |
21 days notice |
DNS |
WHOIS |
REGISTRY SERVICES |
|
Service Availability |
P1 |
P2 |
P1 |
Response Time |
P4 |
P5 |
P4 |
Failure to notify planned or extended planned outage in timeframe allowed. |
N/A |
P6 |
P6 |
Update Frequency |
P2 |
P3 |
N/A |
ExcessPlannedOutageTime |
N/A |
P2 |
P2 |
Penalties are calculated monthly, the maximum penalty payable in any one period (month) shall not exceed $30,000, in the case where penalties to be paid are in excess of maximum amounts payable per registrar will be converted to percentages of total penalty, and then registrars will be paid the relevant percentage of the maximum penalty.
Each registrar will be entitled to the following
C = ar/m x svt x cp
Where
C = amount of credit given to Registrars
ar/m = average registrations per min for the registrar, over the last three months, registrations are defined as new domains, and renewals, this value is calculated using the below formula
ar/m = no registrations and renewals in last three months
/total service availability time in last three months in mins
svt = service violation time, this is the time in mins over the allowable time for the service to be unavailable.
cp = current price
e.g. Registry service where available in a month containing 31 days for a total time of 44485mins
mins in month = 31x24x60 = 44640mins
planned outage for month = 89mins
actual possible up time for month = 44640 - 89 = 44551mins
actual required up time (99.9%) = 44551x0.999 = 44506.5mins
recorded up time = 44485mins
svt = 44506.5-44485= 21.5mins
A registrar who has average registrations a min value of 0.5 would be entitled to
0.5x21.5x5 = 53.75
$53.75 credit back to their account.
Each registrar will be entitled to the following
C = ar/m x svt x cp x 0.5
Where
C = amount of credit given to Registrars
ar/m = average registrations per min for the registrar, over the last three months, registrations are defined as new domains, and renewals, this value is calculated using the below formula
ar/m = no registrations and renewals in last three months
/total service availability time in last three months in mins
svt = service violation time, this is the time in mins over the allowable time for the service to be unavailable.
cp = current price
see P1 above for an example
Each registrar will be entitled to the following
C = ar/m x svt x cp x 0.25
Where
C = amount of credit given to Registrars
ar/m = average registrations per min for the registrar, over the last three months, registrations are defined as new domains, and renewals, this value is calculated using the below formula
ar/m = no registrations and renewals in last three months
/total service availability time in last three months in mins
svt = service violation time, this is the time in mins over the allowable time for the service to be unavailable.
cp = current price
see P1 above for an example
Each registrar will be entitled to the following
C = ar/mth x svp x cp
Where
C = amount of credit given to registrars
ar/mth= average registrations per min for the registrar, over the last three months, registrations are defined as new domains, and renewals, this value is calculated using the below formula
ar/mth= no registrations and renewals in last three months/3
svp = % of service not within allowable response time - allowed slow response % or 30 which ever is lower expressed as a decimal.
cp = current price
eg. Registry service was responding slowly outside of the SLA for a total time of 2000mins throughout the current month which has a recorded up time of 44600mins
recorded up time for month = 44600mins
responding slowly for = 2000mins
responding slowly for % = 2000/44600x100 = 4.5%
svp = 4.5-3 = 1.5%
A registrar who has average registrations a month value of 500 would be entitled to
500x0.015x5 = 37.50
$37.50 credit back to there account.
Each registrar will be entitled to the following
C = ar/mth x svp x cp x 0.5
Where
C = amount of credit given to registrars
ar/mth= average registrations per min for the registrar, over the last three months, registrations are defined as new domains, and renewals, this value is calculated using the below formula
ar/mth= no registrations and renewals in last three months/3
svp = % of service not within allowable response time - allowed slow response % or 30 which ever is lower expressed as a decimal.
cp = current price
(See penalty 4 above for eg)
This is a fixed penalty of $500 per occurrence to be divided equally amongst registrars.
Unity Registry expects to enter into detailed discussion with ICANN about
the technical performance commitments and as part of the process of drawing
up the Registry Agreement.