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.
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.
Modification and Waivers The Indenture permits, with certain exceptions as therein provided (including, but not limited to the exceptions set forth in Section 15.11(i)), the amendment of the Indenture and the modification of the rights and obligations of the Issuer and the rights of the holders of the Notes under the Indenture at any time by the Issuer with the consent of the holders of not less than 66 2/3% in aggregate principal amount of the series of Notes of which this Note is a part then outstanding and all other Securities (as defined in the Indenture) then outstanding under the Indenture and affected by such amendment and modification. The Indenture also contains provisions permitting the holders of a majority in aggregate principal amount of the series of Notes of which this Note is a part then outstanding and all other Securities then outstanding under the Indenture and affected thereby, on behalf of the holders of all such Securities, to waive compliance by the Issuer with certain provisions of the Indenture and certain past defaults under the Indenture and their consequences. Any such consent or waiver by the holder of this Note shall be conclusive and binding upon such holder and upon all future holders of this Note and of any Note issued upon the registration of transfer hereof or in exchange herefor or in lieu hereof whether or not notation of such consent or waiver is made upon this Note. The determination of whether particular Securities are “outstanding” will be made in accordance with the Indenture. Any action by the holder of this Note shall bind all future holders of this Note, and of any Note issued in exchange or substitution hereof or in place hereof, in respect of anything done or permitted by the Issuer or by the Trustee in pursuance of such action. New Notes authenticated and delivered after the execution of any agreement modifying, amending or supplementing this Note may bear a notation in a form approved by the Issuer as to any matter provided for in such modification, amendment or supplement to the Indenture or the Notes. New Notes so modified as to conform, in the opinion of the Issuer, to any provisions contained in any such modification, amendment or supplement may be prepared by the Issuer, authenticated by the Trustee and delivered in exchange for this Note.
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
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.
Extensions and Waivers At any time prior to the Closing, the parties hereto entitled to the benefits of a term or provision may (a) extend the time for the performance of any of the obligations or other acts of the parties hereto, (b) waive any inaccuracies in the representations and warranties contained herein or in any document, certificate or writing delivered pursuant hereto, or (c) waive compliance with any obligation, covenant, agreement or condition contained herein. Any agreement on the part of a party to any such extension or waiver shall be valid only if set forth in an instrument or instruments in writing signed by the party against whom enforcement of any such extension or waiver is sought. No failure or delay on the part of any party hereto in the exercise of any right hereunder shall impair such right or be construed to be a waiver of, or acquiescence in, any breach of any representation, warranty, covenant or agreement.
Modifications and Waiver Except as provided in Section 17 above with respect to changes in Delaware law which broaden the right of Indemnitee to be indemnified by the Company, no supplement, modification or amendment of this Agreement shall be binding unless executed in writing by each of the parties hereto. No waiver of any of the provisions of this Agreement shall be deemed or shall constitute a waiver of any other provisions of this Agreement (whether or not similar), nor shall such waiver constitute a continuing waiver.
Modifications, Amendments and Waivers This Agreement may not be modified or amended, or any provision thereof waived, except in a writing signed by all the parties to this Agreement.
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.
Amendments, Modifications and Waivers No amendment, modification or waiver in respect of this Agreement shall be effective against any party unless it shall be in writing and signed by Parent, the Company and Stockholder.
