Emergency Escalation initiated by ICANN Sample Clauses

Emergency Escalation initiated by ICANN. Upon reaching 10% of the Emergency thresholds as described in Section 6 of this Specification, ICANN’s emergency operations will initiate an Emergency Escalation with the relevant Registry Operator. An Emergency Escalation consists of the following minimum elements: electronic (i.e., email or SMS) and/or voice contact notification to the Registry Operator’s emergency operations department with detailed information concerning the issue being escalated, including evidence of monitoring failures, cooperative trouble-­‐shooting of the monitoring failure between ICANN staff and the Registry Operator, and the commitment to begin the process of rectifying issues with either the monitoring service or the service being monitoring.
AutoNDA by SimpleDocs

Related to Emergency Escalation initiated by ICANN

  • Emergency Escalation initiated by Registrars Registry Operator will maintain an emergency operations department prepared to handle emergency requests from registrars. In the event that a registrar is unable to conduct EPP transactions with the registry for the TLD because of a fault with the Registry Service and is unable to either contact (through ICANN mandated methods of communication) the Registry Operator, or the Registry Operator is unable or unwilling to address the fault, the registrar may initiate an emergency escalation to the emergency operations department of ICANN. ICANN then may initiate an emergency escalation with the Registry Operator as explained above.

  • Emergency Escalation Escalation is strictly for purposes of notifying and investigating possible or potential issues in relation to monitored services. The initiation of any escalation and the subsequent cooperative investigations do not in themselves imply that a monitored service has failed its performance requirements. Escalations shall be carried out between ICANN and Registry Operators, Registrars and Registry Operator, and Registrars and ICANN. Registry Operators and ICANN must provide said emergency operations departments. Current contacts must be maintained between ICANN and Registry Operators and published to Registrars, where relevant to their role in escalations, prior to any processing of an Emergency Escalation by all related parties, and kept current at all times.

  • Emergency Maintenance LightEdge reserves the right to perform emergency Service maintenance as needed outside the Scheduled Maintenance window, in which case LightEdge will make a reasonable effort to notify the Customer if feasible under the circumstances. Any such maintenance will be considered an “Emergency Maintenance”. All Service SLAs will apply during Emergency Maintenance.

  • REDUCTION IN WORKFORCE 16.01 The employer will layoff employees in reverse order of seniority within the classification provided those retained have the ability to do the work. No new employee will be hired until all those qualified employees with recall rights have been given the opportunity to return to work and have failed to do so.

  • Escalation Procedure Tentative Rates for those species and products listed in A4a are subject to quarterly escalation in accordance with the following pro- cedures: The calendar quarter index average for each price index described in A5 is the arithmetic average of the three such monthly price indices preceding January 1, April 1, July 1, and October 1. The difference between calendar quarter index average and Base Index listed in A4a shall be the basis for quarterly escalation. To arrive at Current Contract Rates for timber Scaled during the preceding calendar quarter, Tentative Rates for each species shall be reduced or increased by such difference, except when the calendar quarter index average is:

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!