Emergency Transition Clause Samples

Emergency Transition. Registry Operator agrees that, in the event that any of the emergency thresholds for registry functions set forth in Section 6 of Specification 10 is reached, ICANN may designate an emergency interim registry operator of the registry for the TLD (an “Emergency Operator”) in accordance with ICANN’s registry transition process (available at <▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/resources/registries/transition-­‐processes>) (as the same may be amended from time to time, the “Registry Transition Process”) until such time as Registry Operator has demonstrated to ICANN’s reasonable satisfaction that it can resume operation of the registry for the TLD without the reoccurrence of such failure. Following such demonstration, Registry Operator may transition back into operation of the registry for the TLD pursuant to the procedures set out in the Registry Transition Process, provided that Registry Operator pays all reasonable costs incurred (i) by ICANN as a result of the designation of the Emergency Operator and (ii) by the Emergency Operator in connection with the operation of the registry for the TLD, which costs shall be documented in reasonable detail in records that shall be made available to Registry Operator. In the event ICANN designates an Emergency Operator pursuant to this Section 2.13 and the Registry Transition Process, Registry Operator shall provide ICANN or any such Emergency Operator with all data (including the data escrowed in accordance with Section 2.3) regarding operations of the registry for the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such Emergency Operator. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event that an Emergency Operator is designated pursuant to this Section 2.13. In addition, in the event of such failure, ICANN shall retain and may enforce its rights under the Continued Operations Instrument.
View SourceView Similar (3k)
Emergency Transition. The parties agree to negotiate in good faith to amend this Agreement, including relevant appendices, if applicable, to incorporate an emergency transition process for the operation of the registry for the TLD within one hundred and twenty (120) days following the Effective Date. Such emergency transition process shall include mutually agreed upon requirements for ICANN's designation of an emergency interim registry operator of the registry for the TLD and objective standards under which Registry Operator would resume operation of the registry for the TLD.
View SourceView Similar (6)
Emergency Transition. ▇▇▇▇▇ agrees that, in the event that any of the emergency thresholds for registry functions set forth in Section 6 of Specification 9 is reached, cxDA may designate an emergency interim back-end Registry Operator of the registry for the TLD (an “Emergency Operator”) until such time as ▇▇▇▇▇ has demonstrated to cxDA’s reasonable satisfaction that it can resume operation of the registry for the TLD without the reoccurrence of such failure. Following such demonstration, ▇▇▇▇▇ may transition back into operation of the registry for the TLD provided that ▇▇▇▇▇ pays all reasonable costs incurred (i) by cxDA as a result of the designation of the Emergency Operator and (ii) by the Emergency Operator in connection with the operation of the registry for the TLD, which costs shall be documented in reasonable detail in records that shall be made available to ▇▇▇▇▇ . In the event cxDA designates an Emergency Operator pursuant to this Section 2.13 ▇▇▇▇▇ shall provide cxDA or any such Emergency Operator with all data (including the data escrowed in accordance with Section 2.3 regarding operations of the registry for the TLD necessary to maintain operations and registry functions that may be reasonably requested by cxDA or such Emergency Operator. ▇▇▇▇▇ agrees that cxDA may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event that an Emergency Operator is designated pursuant to this Section 2.13.
View SourceView Similar (2)
Emergency Transition. Registry Operator agrees that in the event that any of the registry functions set forth in Section 6 of Specification 10 fails for a period longer than the emergency threshold for such function set forth in Section 6 of Specification 10, ICANN may designate an emergency interim registry operator of the registry for the TLD (an “Emergency Operator”) in accordance
View SourceView Similar (2)

Related to Emergency Transition

  • Emergency Thresholds The following matrix presents the emergency thresholds that, if reached by any of the services mentioned above for a TLD, would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement. DNS Service (all servers) 4-hour total downtime / week DNSSEC proper resolution 4-hour total downtime / week EPP 24-hour total downtime / week RDDS (WHOIS/Web-based WHOIS) 24-hour total downtime / week Data Escrow Breach of the Registry Agreement as described in Specification 2, Part B, Section 6.

  • Emergency Service Leave ‌ Where employees' services are required for emergency operations by request from the Provincial Emergency Program or appropriate police authority, leave from work as required may be granted without loss of basic pay. If any remuneration, other than for expenses, is received, it shall be remitted to the Employer.

  • Emergency Closure Where there is a temporary closure as a result of an immediate emergency or a planned temporary closure due to renovations, repairs, or moves, the Employer will: a) First offer to the affected employees the choice of taking either a vacation day or an unpaid leave of absence with no loss of seniority or benefits; thereafter, at the Employer's discretion, one of the following: b) Reassign staff to another location; c) Reschedule the lost hours within two (2) pay periods; or d) Decide not to do either (b) or (c), in which case employees shall still be paid for their regularly scheduled hours which they did not work as a result of the temporary layoff.

  • Emergency Room Services This plan covers services received in a hospital emergency room when needed to stabilize or initiate treatment in an emergency. If your condition needs immediate or urgent, but non-emergency care, contact your PCP or use an urgent care center. This plan covers bandages, crutches, canes, collars, and other supplies incidental to your treatment in the emergency room as part of our allowance for the emergency room services. Additional services provided in the emergency room such as radiology or physician consultations are covered separately from emergency room services and may require additional copayments. The amount you pay is based on the type of service being rendered. Follow-up care services, such as suture removal, fracture care or wound care, received at the emergency room will require an additional emergency room copayment. Follow- up care services can be obtained from your primary care provider or a specialist. See Dental Services in Section 3 for information regarding emergency dental care services.

  • Emergency Mode Operation Plan Contractor must establish a documented plan to enable continuation of critical business processes and protection of the security of electronic County PHI or PI in the event of an emergency. Emergency means any circumstance or situation that causes normal computer operations to become unavailable for use in performing the work required under this Agreement for more than twenty-four (24) hours.