Consents Amendments and Override Sample Clauses

Consents Amendments and Override. 1Required consents This Agreement may be amended or waived only with the consent of each Party; provided, that the Glovis Countess Agent (for itself and on behalf of the Glovis Countess Creditors who hereby authorizes the Glovis Countess Agent) and the Green Bay Agent (for itself and on behalf of the Green Bay Creditors who hereby authorize the Green Bay Agent) may enter into an amendment, supplement, termination or other modification of this Agreement without the consent of the Obligors, so long as such amendment, supplement, termination or other modification does not impose any duty or responsibility on the Obligors that materially adversely affects them.
AutoNDA by SimpleDocs
Consents Amendments and Override. 1Required consents This Agreement may be amended or waived only with the consent of the Agent, the Senior Lenders, the Hedge Counterparties and the Security Agent.
Consents Amendments and Override. 25.1 Required consents (a) Subject to paragraph (b) below, Clause 25.4 (Exceptions), and Clause 25.5 (Disenfranchisement of Sponsor Affiliates), this Agreement may be amended and/or waived only with the consent of the Security Agent, the Company and the Agent and/or Bondholders Agent (acting in accordance with the terms of the Senior Facilities Agreement or any Bond Documents), provided that, to the extent that an amendment, waiver or consent only affects one class (including, for the avoidance of any doubt, any sub-class) of Creditors, and such amendment, waiver or consent could not reasonably be expected to materially and adversely affect the interests of the other classes of Creditors, only written agreement from the Agent and/or Bondholders Agent acting on behalf of the affected Creditor class (or sub-class). (b) Subject paragraphs (c) to (e) below and Clause 11 (Non-Distressed Disposals), an amendment or waiver that has the effect of changing or which relates to: (i) Clause 9 (Redistribution), Clause 10 (Enforcement of Transaction Security) Clause 16 (Application of Proceeds) or this Clause 25 (Consents, amendments and override); (ii) paragraphs (d)(iii), (e) and (f) of Clause 18.4 (Instructions) or Clause 10.2 (Enforcement Instructions); (iii) the order of priority or subordination under this Agreement (other than where consequential to a structural adjustment contemplated in the Senior Facilities Agreement and/or the Bond Terms); (iv) Clause 8 (Turnover of receipts) or Clause 17 (Equalisation), shall not be made without the consent of: (A) the Agent; (B) the Bondholders’ Agent; (C) the Senior Lenders (or the relevant class of Senior Lenders, as provided under paragraph (c) of clause 35.3 (Other exceptions) of the Senior Facilities Agreement) and/or the substantially equivalent provision under the Bond Terms ; (D) each Cash Management Provider which is party to this Agreement (but only to the extent that such amendment or waiver would materially and adversely affect the rights and obligations of that Cash Management Provider under this Agreement); (E) each Hedge Counterparty (but only to the extent that such amendment or waiver would materially and adversely affect the rights and obligations of that Hedge Counterparty under this Agreement); (F) the Security Agent; and (G) the Company. (c) Notwithstanding anything to the contrary in this Agreement or any other Debt Document, any Party may irrevocably unilaterally waive, relinquish, or otherwise releas...
Consents Amendments and Override. 25.1 Required consents (a) Subject to paragraphs (b) to (f) below, Clause 25.2 (Amendments and Waivers: Security Documents) and Clause 25.4 (Exceptions), this Agreement and/or a Security Document may be amended or waived only with the written consent of: (i) if the relevant amendment or waiver (the “Proposed Amendment”) is prohibited by the Revolving Facilities Agreement, the Revolving Agent (acting on the instructions of the Majority Revolving Lenders); (ii) if the Proposed Amendment is prohibited by the Senior Debt Documents, the relevant Senior Agent (acting on the instructions of the requisite Senior Secured Creditors) or, in respect of any Senior Notes that have been issued, the Senior Notes Trustee; (iii) if the Proposed Amendment is prohibited by the Second Lien Debt Documents, the relevant Second Lien Agent (acting on the instructions of the requisite Second Lien Secured Creditors) or, in respect of any Permitted Second Lien Financing Debt constitutes by notes, the Second Lien Notes Trustee in respect thereof; (iv) if any Senior Parent Notes have been issued and the Proposed Amendment is prohibited by the terms of the relevant Senior Parent Notes Indenture, the Senior Parent Notes Trustee; (v) if any Permitted Parent Financing Debt has been incurred and the Proposed Amendment is prohibited by the terms of the relevant Permitted Parent Financing Agreement, the Senior Parent Creditor Representative in respect of that Permitted Parent Financing Debt (if applicable, acting on the instructions of the Majority Permitted Parent Financing Creditors); (vi) if a Hedge Counterparty is providing hedging to a Debtor under a Hedging Agreement, that Hedge Counterparty (in each case only to the extent that the relevant amendment or waiver adversely affects the continuing rights and/or obligations of that Hedge Counterparty and is an amendment or waiver which is expressed to require the consent of that Hedge Counterparty under the applicable Hedging Agreement, as notified by the Parent to the Security Agent at the time of the relevant amendment or waiver); (vii) if an Operating Facility Lender is providing one or more facility to a Debtor under an Operating Facility Document, that Operating Facility Lender (in each case only to the extent that the relevant amendment or waiver adversely affects the continuing rights and/or obligations of that Operating Facility Lender and is an amendment or waiver which is expressed to require the consent of that Operating Facility ...
Consents Amendments and Override 

Related to Consents Amendments and Override

  • 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

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