Consents Amendments and Waivers 12.9.1. No amendment or modification of any provision of this Agreement shall be effective without the prior written agreement of the Required Lenders and Borrower, and no waiver of any Default or Event of Default shall be effective without the prior written consent of the Required Lenders; PROVIDED, HOWEVER, that, without the prior consent of all Lenders, no waiver of any Default or Event of Default shall be effective if the Default or Event of Default relates to Borrower's failure to observe or perform any covenant that may not be amended without the unanimous written consent of Lenders as hereinafter set forth in this Section 12.9.
1. Notwithstanding the immediately preceding sentence, the written agreement of all Lenders (except a defaulting Lender as provided in Section 3.2 of this Agreement) shall be required to effectuate any amendment, modification or waiver that would (a) alter the provisions of Sections 2.6, 2.7, 2.8, 2.9, 4.6, 4.7, 5.1, 12, 14.2 or 14.3, the definitions of "Availability Reserve," "Borrowing Base" and the other defined terms used in such definitions, "Pro Rata," "Required Lenders" or any provision of this Agreement obligating Agent to take certain actions at the direction of the Required Lenders, or any provision of any of the Loan Documents regarding the Pro Rata treatment or obligations of Lenders; (b) increase or otherwise modify any of the Commitments (other than to reduce proportionately each Lender's Commitment in connection with any overall reduction in the amount of the Commitments); (c) alter or amend the rate of interest payable in respect of the Loans (except as may be expressly authorized by the Loan Documents or as may be necessary, in Agent's judgment, to comply with Applicable Law); (d) waive or agree to defer collection of any fee, termination charge or other charge provided for under any of the Loan Documents (except to the extent that the Required Lenders agree after and during the continuance of any Event of Default to a waiver or deferral of any termination charge provided for in Section 5.2.3 hereof) or the unused line fee in Section 2.2.3 hereof; (e) subordinate the payment of any of the Obligations to any other Debt or the priority of any Liens granted to Agent under any of the Loan Documents to Liens granted to any other Person, except as currently provided in or contemplated by the Loan Documents in connection with Borrower's incurrence of Permitted Purchase Money Debt, and except for Liens granted by an Obligor to financial institutions with respect to amounts on deposit with such financial institutions to cover returned items, processing and analysis charges and other charges in the ordinary course of business that relate to deposit accounts with such financial institutions; (f) alter the time or amount of repayment of any of the Loans or waive any Event of Default resulting from nonpayment of the Loans on the due date thereof (or within any applicable period of grace); (g) forgive any of the Obligations, except any portion of the Obligations held by a Lender who consents in writing to such forgiveness; or (h) release any Obligor from liability for any of the Obligations. In no event shall any amendment to the provisions of Sections 1.3 or 3.1.3 be effective without the prior written consent of Fleet. No Lender shall be authorized to amend or modify any Note held by it, unless such amendment or modification is consented to in writing by all Lenders; PROVIDED, HOWEVER, that the foregoing shall not be construed to prohibit an amendment or modification to any provision of this Agreement that may be effected pursuant to this Section 12.9.1 by agreement of Borrower and the Required Lenders even though such an amendment or modification results in an amendment or modification of the Notes by virtue of the incorporation by reference in each of the Notes of this Agreement. The making of any Loans hereunder by any Lender during the existence of a Default or Event of Default shall not be deemed to constitute a waiver of such Default or Event of Default. Any waiver or consent granted by Lenders hereunder shall be effective only if in writing and then only in the specific instance and for the specific purpose for which it was given.
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.
Approvals, Consents and Waivers Each Group Company shall have obtained any and all approvals, consents and waivers necessary for consummation of the transactions contemplated by this Agreement, including, but not limited to, (i) all permits, authorizations, approvals, consents or permits of any governmental authority or regulatory body, and (ii) the waiver by the existing shareholders of the Company of any anti-dilution rights, rights of first refusal, preemptive rights and all similar rights in connection with the issuance of the Purchased Shares at the Closing.
Consents and Notices Seller shall have obtained or effected all consents, approvals, waivers, notices and filings required in connection with the execution and delivery by Seller of this Agreement or consummation by Seller of the transactions contemplated hereby, and any notice or waiting period relating thereto shall have expired with all requirements lawfully imposed having been satisfied in all material respects.
Consents and Filings (a) Subject to the terms and conditions of this Agreement, and except with respect to approval by the Bankruptcy Court, each of the parties will use their respective commercially reasonable efforts (i) to take promptly, or cause to be taken, all actions, and to do promptly, or cause to be done, all things necessary, proper or advisable to consummate and make effective the transactions contemplated by this Agreement and (ii) as promptly as practicable after the date of this Agreement, to obtain all Governmental Authorizations (including Environmental Authorizations) from, and make all filings with, all Governmental Authorities (including any other national antitrust authorities with mandatory pre-merger filing requirements that are deemed by the Seller and the Purchaser, after consulting with one another, to be applicable to the transactions contemplated by this Agreement (each “Governmental Antitrust Authority”)), and to obtain all other consents, waivers, approvals and other authorizations from, all other third parties, that are necessary or advisable in connection with the authorization, execution and delivery of this Agreement and the consummation of the transactions contemplated by this Agreement.
(b) The Seller and the Purchaser agree to file with the applicable Governmental Antitrust Authority, as soon as reasonably practicable following the date of this Agreement, any filings or similar information submissions required under applicable antitrust or other competition Laws of jurisdictions outside of the United States of America, including the Federal Republic of Germany. Notwithstanding the foregoing, the Purchaser will be solely responsible for all filing fees due under the HSR Act and any non-US applicable Laws in connection with the filings described above and neither the Seller nor any of its Affiliates will have any Liability with respect to the payment of such filing fees.
(c) The Seller and the Purchaser will promptly notify the other of any communication it or any of its Affiliates receives from any Governmental Antitrust Authority relating to the transactions contemplated by this Agreement, and will permit the other party to review in advance any proposed communication by such party to any Governmental Antitrust Authority. Neither party will agree to participate in any meeting with any Governmental Antitrust Authority in respect of any filings, investigation or other inquiry unless it consults with the other party in advance and, to the extent permitted by such Governmental Antitrust Authority, gives the other party the opportunity to attend and participate at such meeting. The Seller and the Purchaser will coordinate and cooperate fully with each other in exchanging such information and providing such assistance as the other party may reasonably request in connection with the foregoing and in seeking early termination of any applicable waiting periods including under the HSR Act. The Seller and the Purchaser will provide each other with copies of all correspondence, filings or communications between them or any of their representatives, on the one hand, and any Governmental Antitrust Authority or members of its staff, on the other hand, with respect to this Agreement and the transactions contemplated by this Agreement.
Filings, Consents and Approvals The Company is not required to obtain any consent, waiver, authorization or order of, give any notice to, or make any filing or registration with, any court or other federal, state, local or other governmental authority or other Person in connection with the execution, delivery and performance by the Company of the Transaction Documents, other than: (i) the filings required pursuant to Section 4.4 of this Agreement, (ii) the filing with the Commission of the Prospectus Supplement, (iii) application(s) to each applicable Trading Market for the listing of the Shares and Warrant Shares for trading thereon in the time and manner required thereby and (iv) such filings as are required to be made under applicable state securities laws (collectively, the “Required Approvals”).
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
Governmental Consents and Filings No consent, approval, order or authorization of, or registration, qualification, designation, declaration or filing with, any federal, state or local governmental authority is required on the part of the Purchaser in connection with the consummation of the transactions contemplated by this Agreement.
Consents and Requisite Governmental Approvals; No Violations (a) No consent, approval or authorization of, or designation, declaration or filing with, any Governmental Entity is required on the part of a Parent Party with respect to such Parent Party’s execution, delivery or performance of its obligations under this Agreement or the Ancillary Documents to which it is or will be party or the consummation of the transactions contemplated by this Agreement or by the Ancillary Documents, except for (i) the filing with the SEC of (A) the Registration Statement / Proxy Statement and the declaration of the effectiveness thereof by the SEC and (B) such reports under Section 13(a), 15(d) or 16 of the Exchange Act as may be required in connection with this Agreement, the Ancillary Documents or the transactions contemplated hereby or thereby, (ii) such filings with and approvals of Nasdaq to permit the Parent Common Stock to be issued in connection with the transactions contemplated by this Agreement and the other Ancillary Documents to be listed on Nasdaq, (iii) filing of the Certificates of Merger, (iv) the approvals and consents to be obtained by each Merger Sub pursuant to Section 5.9, or (v) the Parent Stockholder Approval.
(b) Subject to the receipt of the Consents, approvals, authorizations and other requirements set forth in Section 4.3(a), neither the execution, delivery or performance by a Parent Party of this Agreement nor the Ancillary Documents to which a Parent Party is or will be a party nor the consummation by a Parent Party of the transactions contemplated hereby or thereby will, directly or indirectly (with or without due notice or lapse of time or both) (i) result in any breach of any provision of the Governing Documents of a Parent Party, (ii) result in a violation or breach of, or constitute a default or give rise to any right of termination, cancellation, amendment, modification, suspension, revocation or acceleration under, any of the terms, conditions or provisions of any Contract to which a Parent Party is a party, (iii) violate, or constitute a breach under, any Order or applicable Law to which any such Parent Party or any of its properties or assets are bound or (iv) result in the creation of any Lien upon any of the assets or properties (other than any Permitted Liens) of a Parent Party, except, in the case of any of clauses (ii) through (iv) above, as would not, individually or in the aggregate, reasonably be expected to be material or prevent, materially delay or materially impair the ability of a Parent Party to consummate the Transactions.
Governmental Consents and Approvals The execution, delivery and performance by each of the Purchasers of this Agreement and the purchase of the Notes do not and will not require any consent, approval, authorization or other order of, action by, filing with, or notification to, any Governmental Authority.
