Waivers and Extensions Any party to this Agreement may waive any right, breach or default which such party has the right to waive, provided that such waiver will not be effective against the waiving party unless it is in writing, is signed by such party, and specifically refers to this Agreement. Waivers may be made in advance or after the right waived has arisen or the breach or default waived has occurred. Any waiver may be conditional. No waiver of any breach of any agreement or provision herein contained shall be deemed a waiver of any preceding or succeeding breach thereof nor of any other agreement or provision herein contained. No waiver or extension of time for performance of any obligations or acts shall be deemed a waiver or extension of the time for performance of any other obligations or acts.
Delays and Extensions The CONSULTANT agrees that no charges or claim for damages shall be made by it for any minor delays from any cause whatsoever during the progress of any portion of the Services specified in this Contract. Such delays, if any, shall be compensated for by an extension of time for such period as may be determined by the LPA subject to the CONSULTANT's approval, it being understood, however, that permitting the CONSULTANT to proceed to complete any services, or any part of them after the date to which the time of completion may have been extended, shall in no way operate as a waiver on the part of the LPA of any of its rights herein. In the event of substantial delays or extensions, or change of any kind, not caused by the CONSULTANT, which causes a material change in scope, character or complexity of work the CONSULTANT is to perform under this Contract, the LPA at its sole discretion shall determine any adjustments in compensation and in the schedule for completion of the Services. CONSULTANT must notify the LPA in writing of a material change in the work immediately after the CONSULTANT first recognizes the material change.
DELAYS AND EXTENSIONS OF TIME 8.3.1 If the Contractor is delayed at any time in the progress of the Work by any act or failure to act by the State or the Architect, or by any employee of either, or by any separate contractor employed by the State, or by changes ordered in the Work, fire, unusual delay in transportation, adverse weather conditions not reasonably anticipatable, unavoidable casualties, or any causes beyond the Contractor's control, or by delay authorized by the State pending alternative dispute resolution proceedings, or by any other cause which may justify the delay, then the Contract Time shall be extended by Change Order for such reasonable time as recommended by the Architect and approved by the State. 8.3.2 Any claim for extension of time shall be made in writing to the Architect not more than twenty days after the commencement of the delay; otherwise it shall be waived. In the case of a continuing delay only one claim is necessary. The Contractor shall provide an estimate of the probable effect of such delay on the progress of the Work. 8.3.3 This Paragraph 8.3 does not exclude the recovery of damages for delay by either party under other provisions of the Contract Documents.
Expiration and Extension of the Offer (i) Unless the Offer is extended pursuant to and in accordance with this Agreement, the Offer shall expire at midnight, New York Time, on the date that is twenty (20) Business Days after the date the Offer is first commenced (within the meaning of Rule 14d-2 promulgated under the Exchange Act) (as such date and time may be extended, the “Expiration Time”). In the event that the Offer is extended pursuant to and in accordance with this Agreement, then the Offer shall expire on the date and at the time to which the Offer has been so extended. (ii) Notwithstanding the provisions of Section 2.1(d)(i) or anything to the contrary set forth in this Agreement: (A) Acquisition Sub shall extend the Offer for any period required by any Law or Order, or any rule, regulation, interpretation or position of the SEC or its staff or NASDAQ, in any such case that is applicable to the Offer; (B) in the event that any of the conditions to the Offer set forth on Annex A, other than the Minimum Condition, are not satisfied or waived (if permitted hereunder) as of any then scheduled expiration of the Offer, Acquisition Sub shall extend the Offer for successive extension periods of ten (10) Business Days each (or any longer period as may be approved in advance by the Company) in order to permit the satisfaction of all of the conditions to the Offer; and (C) in the event that all of the conditions to the Offer set forth on Annex A have been satisfied or waived (if permitted hereunder), except that the Minimum Condition has not been satisfied, as of any then scheduled expiration of the Offer, Acquisition Sub shall extend the Offer for an extension period of ten (10) Business Days (or any longer period as may be approved in advance by the Company), it being understood and agreed that Acquisition Sub shall not be required to extend the Offer pursuant to this clause (C) on more than two (2) occasions, but may, in its sole discretion, elect to do so; provided, however, that the foregoing clauses (A), (B) or (C) of this Section 2.1(d)(ii) shall not be deemed to impair, limit or otherwise restrict in any manner the right of the parties to terminate this Agreement pursuant to the terms of Article IX, and in no event shall Acquisition Sub be required to extend the Offer beyond the Termination Date. (iii) Neither Parent nor Acquisition Sub shall extend the Offer in any manner other than pursuant to and in accordance with the provisions of Section 2.1(d)(ii) without the prior written consent of the Company. (iv) Neither Parent nor Acquisition Sub shall terminate or withdraw the Offer prior to the then scheduled expiration of the Offer unless this Agreement is validly terminated in accordance with Article IX, in which case Acquisition Sub shall (and Parent shall cause Acquisition Sub to) irrevocably and unconditionally terminate the Offer promptly (but in no event more than one (1) Business Day) after such termination of this Agreement.
Delays and Extension of Time If the Contractor is delayed at any time in the progress of providing goods and/or services by an act or neglect of the District, or by changes ordered in the work, or by labor disputes, strikes, insurrections, fire, acts of God; unusual but well documented and excusable delays in performance, or other causes beyond the Contractor’s control, or by delay authorized by the District, then the contract Term of service may be extended by a contract amendment for such reasonable time as the District and the Contractor may agree.
Stay, Extension and Usury Laws The Company and each of the Guarantors covenants (to the extent that it may lawfully do so) that it will not at any time insist upon, plead, or in any manner whatsoever claim or take the benefit or advantage of, any stay, extension or usury law wherever enacted, now or at any time hereafter in force, that may affect the covenants or the performance of this Indenture; and the Company and each of the Guarantors (to the extent that it may lawfully do so) hereby expressly waives all benefit or advantage of any such law, and covenants that it will not, by resort to any such law, hinder, delay or impede the execution of any power herein granted to the Trustee, but will suffer and permit the execution of every such power as though no such law has been enacted.
Amendments and Supplements The Company shall prepare and file with the Commission such amendments, including post-effective amendments, and supplements to such Registration Statement and the prospectus used in connection therewith as may be necessary to keep such Registration Statement effective and in compliance with the provisions of the Securities Act until all Registrable Securities and other securities covered by such Registration Statement have been disposed of in accordance with the intended method(s) of distribution set forth in such Registration Statement or such securities have been withdrawn.
Amendments and Waivers (a) If the ICANN Board of Directors determines that an amendment to this Agreement (including to the Specifications referred to herein) and all other registry agreements between ICANN and the Applicable Registry Operators (the “Applicable Registry Agreements”) is desirable (each, a “Special Amendment”), ICANN may adopt a Special Amendment pursuant to the requirements of and process set forth in this Section 7.6; provided that a Special Amendment may not be a Restricted Amendment. (b) Prior to submitting a Special Amendment for Registry Operator Approval, ICANN shall first consult in good faith with the Working Group regarding the form and substance of such Special Amendment. The duration of such consultation shall be reasonably determined by ICANN based on the substance of the Special Amendment. Following such consultation, ICANN may propose the adoption of a Special Amendment by publicly posting such amendment on its website for no less than thirty (30) calendar days (the “Posting Period”) and providing notice of such proposed amendment to the Applicable Registry Operators in accordance with Section 7.9. ICANN will consider the public comments submitted on a Special Amendment during the Posting Period (including comments submitted by the Applicable Registry Operators). (c) If, within one hundred eighty (180) calendar days following the expiration of the Posting Period (the “Approval Period”), the ICANN Board of Directors approves a Special Amendment (which may be in a form different than submitted for public comment, but must address the subject matter of the Special Amendment posted for public comment, as modified to reflect and/or address input from the Working Group and public comments), ICANN shall provide notice of, and submit, such Special Amendment for approval or disapproval by the Applicable Registry Operators. If, during the sixty (60) calendar day period following the date ICANN provides such notice to the Applicable Registry Operators, such Special Amendment receives Registry Operator Approval, such Special Amendment shall be deemed approved (an “Approved Amendment”) by the Applicable Registry Operators, and shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice of the approval of such Approved Amendment to Registry Operator (the “Amendment Effective Date”). In the event that a Special Amendment does not receive Registry Operator Approval, the Special Amendment shall be deemed not approved by the Applicable Registry Operators (a “Rejected Amendment”). A Rejected Amendment will have no effect on the terms and conditions of this Agreement, except as set forth below. (d) If the ICANN Board of Directors reasonably determines that a Rejected Amendment falls within the subject matter categories set forth in Section 1.2 of Specification 1, the ICANN Board of Directors may adopt a resolution (the date such resolution is adopted is referred to herein as the “Resolution Adoption Date”) requesting an Issue Report (as such term is defined in ICANN’s Bylaws) by the Generic Names Supporting Organization (the “GNSO”) regarding the substance of such Rejected Amendment. The policy development process undertaken by the GNSO pursuant to such requested Issue Report is referred to herein as a “PDP.” If such PDP results in a Final Report supported by a GNSO Supermajority (as defined in ICANN’s Bylaws) that either (i) recommends adoption of the Rejected Amendment as Consensus Policy or (ii) recommends against adoption of the Rejected Amendment as Consensus Policy, and, in the case of (i) above, the Board adopts such Consensus Policy, Registry Operator shall comply with its obligations pursuant to Section 2.2 of this Agreement. In either case, ICANN will abandon the Rejected Amendment and it will have no effect on the terms and conditions of this Agreement. Notwithstanding the foregoing provisions of this Section 7.6(d), the ICANN Board of Directors shall not be required to initiate a PDP with respect to a Rejected Amendment if, at any time in the twelve (12) month period preceding the submission of such Rejected Amendment for Registry Operator Approval pursuant to Section 7.6(c), the subject matter of such Rejected Amendment was the subject of a concluded or otherwise abandoned or terminated PDP that did not result in a GNSO Supermajority recommendation. (e) If (a) a Rejected Amendment does not fall within the subject matter categories set forth in Section 1.2 of Specification 1, (b) the subject matter of a Rejected Amendment was, at any time in the twelve (12) month period preceding the submission of such Rejected Amendment for Registry Operator Approval pursuant to Section 7.6(c), the subject of a concluded or otherwise abandoned or terminated PDP that did not result in a GNSO Supermajority recommendation, or (c) a PDP does not result in a Final Report supported by a GNSO Supermajority that either (A) recommends adoption of the Rejected Amendment as Consensus Policy or (B) recommends against adoption of the Rejected Amendment as Consensus Policy (or such PDP has otherwise been abandoned or terminated for any reason), then, in any such case, such Rejected Amendment may still be adopted and become effective in the manner described below. In order for the Rejected Amendment to be adopted, the following requirements must be satisfied: (i) the subject matter of the Rejected Amendment must be within the scope of ICANN’s mission and consistent with a balanced application of its core values (as described in ICANN’s Bylaws); (ii) the Rejected Amendment must be justified by a Substantial and Compelling Reason in the Public Interest, must be likely to promote such interest, taking into account competing public and private interests that are likely to be affected by the Rejected Amendment, and must be narrowly tailored and no broader than reasonably necessary to address such Substantial and Compelling Reason in the Public Interest; (iii) to the extent the Rejected Amendment prohibits or requires conduct or activities, imposes material costs on the Applicable Registry Operators, and/or materially reduces public access to domain name services, the Rejected Amendment must be the least restrictive means reasonably available to address the Substantial and Compelling Reason in the Public Interest; (iv) the ICANN Board of Directors must submit the Rejected Amendment, along with a written explanation of the reasoning related to its determination that the Rejected Amendment meets the requirements set out in subclauses (i) through (iii) above, for public comment for a period of no less than thirty (30) calendar days; and (v) following such public comment period, the ICANN Board of Directors must (a) engage in consultation (or direct ICANN management to engage in consultation) with the Working Group, subject matter experts, members of the GNSO, relevant advisory committees and other interested stakeholders with respect to such Rejected Amendment for a period of no less than sixty (60) calendar days; and (b) following such consultation, reapprove the Rejected Amendment (which may be in a form different than submitted for Registry Operator Approval, but must address the subject matter of the Rejected Amendment, as modified to reflect and/or address input from the Working Group and public comments) by the affirmative vote of at least two-‐thirds of the members of the ICANN Board of Directors eligible to vote on such matter, taking into account any ICANN policy affecting such eligibility, including ICANN’s Conflict of Interest Policy (a “Board Amendment”). Such Board Amendment shall, subject to Section 7.6(f), be deemed an Approved Amendment, and shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice of the approval of such Board Amendment to Registry Operator (which effective date shall be deemed the Amendment Effective Date hereunder). Notwithstanding the foregoing, a Board Amendment may not amend the registry fees charged by ICANN hereunder, or amend this Section 7.6. (f) Notwithstanding the provisions of Section 7.6(e), a Board Amendment shall not be deemed an Approved Amendment if, during the thirty (30) calendar day period following the approval by the ICANN Board of Directors of the Board Amendment, the Working Group, on the behalf of the Applicable Registry Operators, submits to the ICANN Board of Directors an alternative to the Board Amendment (an “Alternative Amendment”) that meets the following requirements: (i) sets forth the precise text proposed by the Working Group to amend this Agreement in lieu of the Board Amendment; (ii) addresses the Substantial and Compelling Reason in the Public Interest identified by the ICANN Board of Directors as the justification for the Board Amendment; and (iii) compared to the Board Amendment is: (a) more narrowly tailored to address such Substantial and Compelling Reason in the Public Interest, and (b) to the extent the Alternative Amendment prohibits or requires conduct or activities, imposes material costs on Affected Registry Operators, or materially reduces access to domain name services, is a less restrictive means to address the Substantial and Compelling Reason in the Public Interest. Any proposed amendment that does not meet the requirements of subclauses (i) through
EXPIRATION DATE AND EXTENSION This Contract expires December 5, 2024, unless it is terminated sooner pursuant to Article XX of the General Terms and Conditions, which are incorporated into this Contract by reference. This Contract allows up to five additional one-year extensions upon the request of Sourcewell and written agreement with Contractor. Sourcewell retains the right to consider additional extensions beyond six years as required under exceptional circumstances.
Amendments, Supplements and Waivers The Company and the Trustee may amend or supplement the Indenture or the Notes or waive compliance with any provision of the Indenture or the Notes in the manner, and subject to the terms, set forth in Section 7.05 and Article 8 of the Indenture.
