Common use of Heightened Alert State Clause in Contracts

Heightened Alert State. ‌ An exhaustive list of conditions used to evaluate the decision to trigger EBERO is not detailed in this high-level description. Example of conditions sufficient to invoke a state of heightened alert might include a registry requesting a transition to EBERO or a registry reaching a failure state that has utilized 10% of the emergency threshold timing window as described in Specification 10 of the new gTLD agreement. During a Heightened Alert State, ICANN will be trying to work with the registry to remediate the service problems. Service Specification 10 Emergency Threshold To Trigger Heightened Alert DNS 24 minutes of total downtime / week DNSSEC 24 minutes of total downtime / week RDDS 144 minutes of total downtime / week SRS 144 minutes of total downtime / week Data Escrow 1008 minutes after the issuance of a Compliance notice of (a) failure to receive notification of required escrow deposits; or (b) failure of deposits to pass verification.

Appears in 3 contracts

Samples: Operator Agreement, Registry Operator Agreement, Registry Operator Agreement

AutoNDA by SimpleDocs

Heightened Alert State. An exhaustive list of conditions used to evaluate the decision to trigger EBERO a heightened alert is not detailed in this high-level description. Example Examples of conditions sufficient to invoke a state of heightened alert might include a registry operator requesting a transition to EBERO or the ICANN risk assessment specialists concluding that there is a substantial risk and credible threat that the registry reaching a failure state that has utilized 10% of the emergency threshold timing window as described in Specification 10 of the new gTLD operator would—within 48 hours—fail to meet its obligations under its registry agreement. During a any Heightened Alert State, ICANN will be trying attempt to work with the registry operator to remediate the service problemsunderlying problem(s). Service Specification 10 Emergency Threshold To Trigger Example Triggers for Heightened Alert DNS 24 60 minutes of total downtime / week DNSSEC 24 60 minutes of total downtime / week RDDS 144 720 minutes of total downtime / week SRS 144 720 minutes of total downtime / week Data Escrow 1008 minutes after the issuance of a Uncured Compliance notice of (a) failure to receive notification of required escrow deposits; or (b) failure of deposits to pass verification, for a period of 6 or more days.

Appears in 3 contracts

Samples: Registry Operator Agreement, Registry Operator Agreement, Registry Operator Agreement

AutoNDA by SimpleDocs
Time is Money Join Law Insider Premium to draft better contracts faster.