| |
 |
Revised VeriSign Registry
Agreements: Appendix E
Posted: 16 April 2001
|
Service Level Agreement
(SLA)
The VeriSign, Inc. ("VeriSign")
Registry strives to provide a world-class level of service to
its customers. This Service Level Agreement provides metrics
and remedies to measure performance of the VeriSign Registry
and to provide accredited and licensed Registrars with credits
for certain substandard performance by the VeriSign Registry
under the parties' Registrar License and Agreement.
A) DEFINITIONS:
1) Monthly Timeframe shall mean each single
calendar month beginning and ending at 12:00 am Greenwich Mean
Time (GMT).
2) Planned Outage shall mean the periodic
pre-announced occurrences when the SRS will be taken out of service
for maintenance or care. Planned Outages will be scheduled only
during the following window period of time each week, 0100 to
0900 GMT on Sunday (the "Planned Outage Period").
This Planned Outage Period may be changed from time to time by
the VeriSign Registry, in its sole discretion, upon prior notice
to each Registrar. Planned Outages will not exceed 4 hours per
calendar week beginning at 12:00 am GMT Monday nor total more
than 8 hours/per month. Notwithstanding the foregoing, each
year VeriSign may incur 2 additional Planned Outages of up to
12 hrs in duration during the Planned Outage Period for major
systems or software upgrades ("Extended Planned Outages").
These Extended Planned Outages represent total allowed Planned
Outages for the month.
3) Shared Registration System ("SRS")
Availability shall mean when the SRS is operational. By definition,
this does not include Planned Outages or Extended Planned Outages.
4) SRS Unavailability shall mean when,
as a result of a failure of systems within the VeriSign Registry's
control, the Registrar is unable to either:
a) establish a session with the SRS gateway
which shall be defined as:
1) successfully complete a TCP session
start,
2) successfully complete the SSL authentication
handshake, and
3) successfully complete the registry registrar
protocol ("RRP") session command.
b) execute a 3 second average round trip
for 95% of the RRP check domain commands and/or less than 5 second
average round trip for 95% of the RRP add domain commands, from
the SRS Gateway, through the SRS system, back to the SRS Gateway
as measured during each Monthly Timeframe.
5) Unplanned Outage Time shall mean all
of the following:
a) the amount of time recorded between
a trouble ticket first being opened by the VeriSign Registry
in response to a Registrar's claim of SRS Unavailability for
that Registrar through the time when the Registrar and VeriSign
Registry agree the SRS Unavailability has been resolved with
a final fix or a temporary work around, and the trouble ticket
has been closed. This will be considered SRS Unavailability
only for those individual Registrars impacted by the outage.
b) the amount of time recorded between
a trouble ticket first being opened by the VeriSign Registry
in the event of SRS Unavailability that affects all Registrars
through the time when the Registry resolves the problem with
a final fix or a temporary work around, and the trouble ticket
has been closed.
c) the amount of time that Planned Outage
time exceeds the limits established in A.2 above.
d) the amount of time that Planned Outage
time occurs outside the window of time established in A.2 above.
6) Monthly Unplanned Outage Time shall
be the sum of minutes of all Unplanned Outage Time during the
Monthly Timeframe. Each minute of Unplanned Outage Time subtracts
from the available Monthly Planned Outage Time up to 4 hours.
7) WHOIS Service shall mean the VeriSign
Registry Whois server running on port 43 of whois.crsnic.net
and whois.verisign-grs.net.
8) Global Top Level Domain ("GTLD")
Name Server shall mean any GTLD Name Server under SLD GTLD-SERVERS.NET
(e.g. A.GTLD-SERVERS.NET).
B) RESPONSIBILITIES OF THE PARTIES
1) Registrar must report each occurrence
of alleged SRS Unavailability to the VeriSign Registry customer
service help desk in the manner required by the VeriSign Registry
(i.e., e-mail, fax, telephone) in order for an occurrence to
be treated as SRS Unavailability for purposes of the SLA.
2) In the event that all Registrars are
affected by SRS Unavailability, the VeriSign Registry is responsible
for opening a blanket trouble ticket and immediately notifying
all Registrars of the trouble ticket number and details.
3) Both Registrar and the VeriSign Registry
agree to use reasonable commercial good faith efforts to establish
the cause of any alleged SRS Unavailability. If it is mutually
determined to be a VeriSign Registry problem, the issue will
become part of the Unplanned Outage Time.
4) VeriSign Registry will perform monitoring
from at least two external locations as a means to verify that
a) sessions can effectively be established and b) all RRP commands
can be successfully completed.
5) Registrar must inform the VeriSign Registry
any time its estimated volume of transactions (excluding check
domain commands), will exceed Registrar's previous month's volume
by more than 25%. In the event that Registrar fails to inform
VeriSign Registry of a forecasted increase of volume of transactions
of 25% or more and the Registrar's volume increases 25% or more
over the previous month, and should the total volume of transactions
added by the VeriSign Registry for all Registrars for that month
exceed the VeriSign Registry's actual volume of the previous
month's transactions by more than 20%, then Registrar will not
be eligible for any SLA credits (as defined in section C) in
that Monthly Timeframe. The Registrar shall provide such forecast
at least 30 days prior to the first day of the next month. In
addition, the VeriSign Registry agrees to provide monthly transaction
summary reports.
6) The VeriSign Registry will notify Registrar
of Planned Outages outside the Planned Outage Period at least
7 days in advance of such Planned Outage. In addition, VeriSign
Registry will use reasonable commercial good faith efforts to
maintain an accurate 30-day advance schedule of possible upcoming
Planned Outages.
7) The VeriSign Registry will update the
WHOIS Service once per day beginning at 1200 GMT. The VeriSign
Registry will notify Registrars in advance when changes to the
WHOIS Service update schedule occur.
8) The VeriSign Registry will allow external
monitoring of the SRS via an acceptable means to both parties.
9) The VeriSign Registry will initiate
the Registry zone file transfer process twice daily at 1000 GMT
and 2200 GMT. The VeriSign Registry will notify Registrar in
advance when changes to the schedule occur. The VeriSign Registry
will notify Registrars regarding any scheduled maintenance and
unavailability of the GTLD ROOT-SERVERs.
10) The VeriSign Registry will use commercial
reasonable efforts to restore the critical systems of the SRS
within 24 hours in the event of a force majeure and restore full
system functionality within 48 hours. Outages due to a force
majeure will not be considered SRS Unavailability.
11) The VeriSign Registry will publish
weekly system performance and availability reports. These reports
will include average round trip for the RRP Check and RRP Add
Domain commands for all Registrars as well as a summary of SRS
Availability for the previous week
12) The VeriSign Registry will provide
a 99.4% SRS Availability during each Monthly Timeframe.
C) CREDITS:
1) If SRS Availability is less than 99.4%
in any Monthly Timeframe, the VeriSign Registry will provide
a credit to affected Registrar(s) who have complied with Sections
B.1 and B.5 above as follows:
(i) In the case of SRS Unavailability
as described in A.4.b, a credit will be given for the combined
% total RRP add and check commands that fall below the 95% performance
threshold established in A.4.b. For each affected Registrar,
this will be calculated by multiplying the % below 95% by Registrar's
monthly Add Domain volume x the average initial registration
price charged to that Registrar during the month. The maximum
credit to each Registrar shall not exceed 5% of the Registrar's
total monthly Add Domain volume x that average registration price.
(ii) In the case of SRS Unavailability
as described in A.4.a, and following the Monthly Timeframe when
the Unplanned Outage began, VeriSign Registry will provide a
credit to Registrar by multiplying Registrar's monthly Add Domain
volume x the average initial registration price charged to that
Registrar during the month and multiplying that product by the
percentage of time that the Monthly Unplanned Outage Time exceeded
0.6% of the minutes in the Monthly Timeframe. The maximum credit
to each Registrar under this subparagraph shall not exceed 10%
of the Registrar's total monthly Add Domain volume x that average
registration price.
Under no circumstances shall credits be
applied when the availability problems are caused by network
providers and/or the systems of individual Registrars.
D) MISCELLANEOUS:
1) As an addendum to the Registry-Registrar
Agreement (RRA), no provision in this addendum is intended to
replace any term or condition in the RRA.
2) Dispute Resolution will be handled per
RRA Section 6.7.
3) Any interruption of SRS service that
occurs, as a direct result of RRA Sections 2.12,, 5.4, or 6.3
or any other applicable RRA contract term, will not be determined
SRS Unavailability per this SLA.
Comments concerning the layout, construction and
functionality of this site
should be sent to webmaster@icann.org.
Page Updated 16-April-2001
(c) 2001 The Internet
Corporation for Assigned Names and Numbers.
All rights reserved.
|