.COM Registry-Registrar Agreement This Registry ... - VeriSign

More documents

Recommendations

Info

determined to be a VNDS problem, the issue will become part of the UnplannedOutage Time.4) VNDS will perform monitoring from at least two external locations as a meansto verify that a) sessions can effectively be established and b) all RRP or EPPcommands can be successfully completed.5) Registrar must inform VNDS any time its estimated volume of transactions(excluding check domain commands), will exceed Registrar's previous month'svolume by more than 25%. In the event that Registrar fails to inform VNDS of aforecasted increase of volume of transactions of 25% or more and the Registrar'svolume increases 25% or more over the previous month, and should the totalvolume of transactions added by VNDS for all Registrars for that month exceedVNDS' 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) inthat Monthly Timeframe. The Registrar shall provide such forecast at least 30days prior to the first day of the next month. In addition, VNDS agrees to providemonthly transaction summary reports.6) VNDS will notify Registrar of Planned Outages outside the Planned OutagePeriod at least 7 days in advance of such Planned Outage. In addition, VNDS willuse reasonable commercial good faith efforts to maintain an accurate 30-dayadvance schedule of possible upcoming Planned Outages.7) VNDS will update the WHOIS Service once per day beginning at 1200 GMT.VNDS will notify Registrars in advance when changes to the WHOIS Serviceupdate schedule occur.8) VNDS will allow external monitoring of the SRS via an acceptable means toboth parties.9) VNDS will initiate the zone file transfer process at least twice daily atscheduled intervals. VNDS will notify Registrar in advance when changes to theschedule occur. VNDS will notify Registrars regarding any scheduledmaintenance and unavailability of the GTLD ROOT-SERVERs.10) VNDS will use commercial reasonable efforts to restore the critical systemsof the SRS within 24 hours in the event of a force majeure and restore full systemfunctionality within 48 hours. Outages due to a force majeure will not beconsidered SRS Unavailability.11) VNDS will publish weekly system performance and availability reports. Thesereports will include average round trip for the RRP or EPP Check and AddDomain commands for all Registrars as well as a summary of SRS Availability forthe previous week.com Registry Registrar Agreement 20070119 Page 24 of 25
12) VNDS 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, VNDS willprovide a credit to affected Registrar(s) who have complied with Sections B.1and B.5 above as follows:(i) In the case of SRS Unavailability as described in A.4.b, a credit will be givenfor the combined % total RRP or EPP add and check commands that fall belowthe 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 AddDomain volume x the average initial registration price charged to that Registrarduring the month. The maximum credit to each Registrar shall not exceed 5% ofthe Registrar's total monthly Add Domain volume x that average registrationprice.(ii) In the case of SRS Unavailability as described in A.4.a, and following theMonthly Timeframe when the Unplanned Outage began, VNDS will provide acredit to Registrar by multiplying Registrar's monthly Add Domain volume x theaverage initial registration price charged to that Registrar during the month andmultiplying that product by the percentage of time that the Monthly UnplannedOutage Time exceeded 0.6% of the minutes in the Monthly Timeframe. Themaximum credit to each Registrar under this subparagraph shall not exceed 10%of the Registrar's total monthly Add Domain volume x that average registrationprice.Under no circumstances shall credits be applied when the availability problemsare 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 inthis 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 Sections2.12,, 5.4, or 6.3 or any other applicable RRA contract term, will not bedetermined SRS Unavailability per this SLA..com Registry Registrar Agreement 20070119 Page 25 of 25
Page 1 and 2: .COM Registry-Registrar AgreementTh
Page 3 and 4: 2.6. Registrar's Registration Agree
Page 5 and 6: 3.1. License Grant. Subject to the
Page 7 and 8: (b) For a transfer approved by ICAN
Page 9 and 10: (h) Survival. In the event of termi
Page 11 and 12: 487 E. Middlefield RoadMountain Vie
Page 13 and 14: REGISTRAR'S REQUIREMENTS, OR THAT T
Page 15 and 16: Exhibit ARegistrar's Registration A
Page 17 and 18: Exhibit CConfidentiality AgreementT
Page 19 and 20: cured within three (3) calendar day
Page 21 and 22: Exhibit DREGISTRATION FEES1. Domain
Page 23: SRS system, back to the SRS Gateway

.COM Registry-Registrar Agreement This Registry ... - VeriSign

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?