Registry Continuity
Registry Continuity Sample Clauses
Related to Registry Continuity
Registry Services “Registry Services” are, for purposes of the Agreement, defined as the following: (a) those services that are operations of the registry critical to the following tasks: the receipt of data from registrars concerning registrations of domain names and name servers; provision to registrars of status information relating to the zone servers for the TLD; dissemination of TLD zone files; operation of the registry DNS servers; and dissemination of contact and other information concerning domain name server registrations in the TLD as required by this Agreement; (b) other products or services that the Registry Operator is required to provide because of the establishment of a Consensus Policy as defined in Specification 1; (c) any other products or services that only a registry operator is capable of providing, by reason of its designation as the registry operator; and (d) material changes to any Registry Service within the scope of (a), (b) or (c) above.
Business Continuity Registry Operator shall maintain a business continuity plan, which will provide for the maintenance of Registry Services in the event of an extraordinary event beyond the control of the Registry Operator or business failure of Registry Operator, and may include the designation of a Registry Services continuity provider. If such plan includes the designation of a Registry Services continuity provider, Registry Operator shall provide the name and contact information for such Registry Services continuity provider to ICANN. In the case of an extraordinary event beyond the control of the Registry Operator where the Registry Operator cannot be contacted, Registry Operator consents that ICANN may contact the designated Registry Services continuity provider, if one exists. Registry Operator shall conduct Registry Services Continuity testing at least once per year.
Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).
Continuity Except as expressly modified hereby, the terms and provisions of the Agreement and all instruments, agreements or other documents executed and delivered in connection therewith shall continue in full force and effect. Whenever the “Agreement” is referenced in the Agreement or any of the instruments, agreements or other documents executed and delivered in connection therewith, such references shall be deemed to mean the Agreement as modified hereby.
Security Management The Contractor shall comply with the requirements of the DOD 5200.1-M and the DD Form 254. Security of the Contractor’s electronic media shall be in accordance with the above documents. Effective Program Security shall require the Contractor to address Information Security and Operations Security enabled by the Security Classification Guides. The Contractor’s facility must be able to handle and store material up to the Classification Level as referenced in Attachment J-01, DD Form 254.
Distance Education 7.13.1 Expanding student access, not increasing productivity or enrollment, shall be the primary determining factor when a decision is made to schedule a distance education course. There will be no reduction in force of faculty (as defined in Article XXIII of this Agreement) as a result of the District’s participation in distance education.
Registry-‐Level Fees (a) Registry Operator shall pay ICANN a registry-‐level fee equal to (i) the registry fixed fee of US$6,250 per calendar quarter and (ii) the registry-‐level transaction fee (collectively, the “Registry-‐Level Fees”). The registry-‐level transaction fee will be equal to the number of annual increments of an initial or renewal domain name registration (at one or more levels, and including renewals associated with transfers from one ICANN-‐accredited registrar to another, each a “Transaction”), during the applicable calendar quarter multiplied by US$0.25; provided, however that the registry-‐level transaction fee shall not apply until and unless more than 50,000 Transactions have occurred in the TLD during any calendar quarter or any consecutive four calendar quarter period in the aggregate (the “Transaction Threshold”) and shall apply to each Transaction that occurred during each quarter in which the Transaction Threshold has been met, but shall not apply to each quarter in which the Transaction Threshold has not been met. Registry Operator’s obligation to pay the quarterly registry-‐level fixed fee will begin on the date on which the TLD is delegated in the DNS to Registry Operator. The first quarterly payment of the registry-‐level fixed fee will be prorated based on the number of calendar days between the delegation date and the end of the calendar quarter in which the delegation date falls.
