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. Critical Function Emergency Threshold 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.
Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include:
Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).
Adjustment events In the event the General Partner (i) declares or pays a dividend on any Class of its outstanding REIT Shares in REIT Shares or makes a distribution to all holders of any Class of its outstanding REIT Shares in REIT Shares, (ii) subdivides any Class of its outstanding REIT Shares, or (iii) combines any Class of its outstanding REIT Shares into a smaller number of REIT Shares with respect to any Class of REIT Shares, then a corresponding adjustment to the number of outstanding Partnership Units of the applicable Class necessary to maintain the proportionate relationship between the number of outstanding Partnership Units of such Class to the number of outstanding REIT Shares of such Class shall automatically be made. Additionally, in the event that any other entity shall become General Partner pursuant to any merger, consolidation or combination of the General Partner with or into another entity (the “Successor Entity”), the number of outstanding Partnership Units of each Class shall be adjusted by multiplying such number by the number of shares of the Successor Entity into which one REIT Share of such Class is converted pursuant to such merger, consolidation or combination, determined as of the date of such merger, consolidation or combination. Any adjustment to the number of outstanding Partnership Units of any Class shall become effective immediately after the effective date of such event retroactive to the record date, if any, for such event; provided, however, that if the General Partner receives a Notice of Redemption after the record date, but prior to the effective date of such dividend, distribution, subdivision or combination, or such merger, consolidation or combination, the number of outstanding Partnership Units of any Class shall be determined as if the General Partner had received the Notice of Redemption immediately prior to the record date for such dividend, distribution, subdivision or combination or such merger, consolidation or combination. If the General Partner takes any other action affecting the REIT Shares other than actions specifically described above and, in the opinion of the General Partner such action would require an adjustment to the number of Partnership Units to maintain the proportionate relationship between the number of outstanding Partnership Units to the number of outstanding REIT Shares, the General Partner shall have the right to make such adjustment to the number of Partnership Units, to the extent permitted by law, in such manner and at such time as the General Partner, in its sole discretion, may determine to be appropriate under the circumstances.
Thresholds The threshold of a sample to constitute a positive result alcohol, drugs, or their metabolites is contained in the standards of one of the programs listed in MN Statute §181.953, subd 1. The employer shall, not less than annually, provide the unions with a list or access to a list of substances tested for under this LOA and the threshold limits for each substance. In addition, the employer shall notify the unions of any changes to the substances being tested for and of any changes to the thresholds at least thirty (30) days prior to implementation.
Termination Events This Agreement may, by notice given prior to or at the Closing, be terminated:
Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.
Rating Impact on Student Learning Growth ESE will provide model contract language and guidance on rating educator impact on student learning growth based on state and district-determined measures of student learning. Upon receiving this model contract language and guidance, the parties agree to bargain with respect to this matter.
Market Disruption Event Section 6.3(a) of the Equity Definitions is hereby replaced in its entirety by the following:
Offense Level Calculations i. The base offense level is 7, pursuant to Guideline § 2B1.1(a)(1).
