Limited Waivers At the request of the Borrowers and the Guarantors the Administrative Agent and the Lenders hereby waive on a temporary basis, expiring on the Termination Date, the following Specified Events of Defaults: (a) Any failure by the Borrowers to comply with Section 6.03(a) of the Credit Agreement requiring the Borrowers to provide prompt notice of the occurrence of any Default in regards to the Specified Events of Default, which events shall include any occurrence during the Temporary Waiver Period of those events set forth on Schedule I hereto, is hereby waived (and any breach of a representation or warranty related to the Specified Events of Default is hereby similarly waived). (b) Any failure by the Borrowers to comply with Section 6.03(b) of the Credit Agreement requiring the Borrowers to provide prompt notice upon the occurrence of any matter that has resulted or could reasonably be expected to result in a Material Adverse Effect, is hereby waived (and any related existing breach of a representation or warranty is hereby similarly waived) insofar as, and only insofar as, such failure to provide notice (i) related to the non-renewal of the Cenovus Services Agreement and the Xxxxxx Services Agreement, and (ii) any occurrence during the Temporary Waiver Period of the events set forth on Schedule II hereto (and any existing breach of a representation or warranty related to (i) and (ii) above). (c) Any Event of Default pursuant to Section 8.01(g) of the Credit Agreement resulting from the Borrowers’ admission that they would become unable to pay their debts as they generally become due is hereby waived (and any related breach of a representation or warranty is hereby similarly waived), and to the extent any forecasting by the Loan Parties during the Temporary Waiver Period evidences the Borrowers’ inability to pay debts as they come due and owing or insolvency, any Default or Event of Default arising therefrom is waived. The Temporary Waiver in this Section 4 is effective only in respect of those Specified Events of Default, and except as expressly set forth in this Agreement, no other waivers, amendments or modifications are intended or made by this Agreement. No failure or delay on the part of the Administrative Agent, or any Lender in exercising any power or right under the Credit Agreement or any other Loan Document shall operate as a waiver thereof, nor shall any single or partial exercise of any such power or right preclude any other or further exercise thereof or the exercise of any other power or right. No waiver or approval by the Administrative Agent or any Lender under this Agreement, the Credit Agreement or any other Loan Document shall, except as may be otherwise stated in such waiver or approval, be applicable to any subsequent transaction or any Default or Event of Default under any Loan Document. Notwithstanding any language herein to the contrary, nothing herein is intended to nor shall waive (temporary or otherwise) or otherwise release the Borrowers or Guarantors from any other Event of Default under any Loan Document that is not a Specified Event of Default. Similarly, notwithstanding any language herein to the contrary, nothing herein is intended to nor shall release the Borrowers or Guarantors from any Specified Event of Default, except for such Temporary Waiver as specified herein. Further, any post-default interest payable at the Default Rate resulting from the Specified Events of Default which would otherwise apply, is hereby waived for the Specified Events of Default for the duration of the Temporary Waiver Period, unless (i) a Default or Event of Default other than the Specified Events of Default occurs or has occurred, or, (ii) following the Termination Date, the Administrative Agent elects in its sole discretion (or is otherwise directed by the Required Lenders), to assess post-default interest at the Default Rate in accordance with the Credit Agreement and so notifies the Borrowers.
REMEDIES AND WAIVERS No failure to exercise, nor any delay in exercising, on the part of any Finance Party, any right or remedy under the Finance Documents shall operate as a waiver, nor shall any single or partial exercise of any right or remedy prevent any further or other exercise or the exercise of any other right or remedy. The rights and remedies provided in this Agreement are cumulative and not exclusive of any rights or remedies provided by law.
Amendment and Waivers Any term or provision of this Agreement may be amended, and the observance of any term of this Agreement may be waived (either generally or in a particular instance and either retroactively or prospectively) only by a writing signed by the party to be bound thereby. The waiver by a party of any breach hereof for default in payment of any amount due hereunder or default in the performance hereof shall not be deemed to constitute a waiver of any other default or any succeeding breach or default.
Modifications and Waivers No provision of this Agreement shall be modified, waived or discharged unless the modification, waiver or discharge is agreed to in writing and signed by the Executive and by an authorized officer of the Company (other than the Executive). No waiver by either party of any breach of, or of compliance with, any condition or provision of this Agreement by the other party shall be considered a waiver of any other condition or provision or of the same condition or provision at another time.
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
Reliance Upon Documents and Instructions The Custodian shall be entitled to rely upon any certificate, notice or other instrument in writing received by it and reasonably believed by it to be genuine. The Custodian shall be entitled to rely upon any Written Instructions actually received by it pursuant to this Agreement.
Limitations on Subsequent Registration Rights From and after the date of this Agreement, the Company shall not, without the prior written consent of Holders holding a majority of the Registrable Securities enter into any agreement with any holder or prospective holder of any securities of the Company giving such holder or prospective holder any registration rights the terms of which are pari passu with or senior to the registration rights granted to the Holders hereunder.
Consents and Waivers No consent or waiver expressed or implied by either Party in respect of any breach or default by the other in the performance by such other of its obligations hereunder shall: (a) be valid unless it is in writing and stated to be a consent or waiver pursuant to this section; (b) be relied upon as a consent to or waiver of any other breach or default of the same or any other obligation; (c) constitute a general waiver under this Agreement; or (d) eliminate or modify the need for a specific consent or waiver pursuant to this section in any other or subsequent instance.
Limitation on Subsequent Registration Rights Other than as provided in Section 5.10, after the date of this Agreement, the Company shall not enter into any agreement with any holder or prospective holder of any securities of the Company that would grant such holder rights to demand the registration of shares of the Company’s capital stock, or to include such shares in a registration statement that would reduce the number of shares includable by the Holders.
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.
