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.
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.
Modifications; Amendments; Waivers The terms and provisions of this Agreement may not be modified or amended, nor may any provision be waived, except pursuant to a writing signed by the Corporation and the holders of at least a majority of the Registrable Shares then outstanding.
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.
Modifications; Amendment This Agreement shall not be modified, cancelled or terminated except by an instrument in writing signed by each Noteholder. Additionally, for as long as any Note is contained in a Securitization Trust, the Noteholders shall not amend or modify this Agreement without first receiving a Rating Agency Confirmation; provided that no such confirmation from the Rating Agencies shall be required in connection with a modification or amendment (i) to cure any ambiguity, to correct or supplement any provisions herein that may be defective or inconsistent with any other provisions herein or with the Servicing Agreement, (ii) entered into pursuant to Section 32 of this Agreement or (iii) to correct or supplement any provision herein that may be defective or inconsistent with any other provisions of this Agreement.
Amendments and Waiver No modification of or amendment to this Agreement shall be valid or binding unless set forth in writing and duly executed by both of the parties hereto and no waiver of any breach of any term or provision of this Agreement shall be effective or binding unless made in writing and signed by the party purporting to give the same and, unless otherwise provided, shall be limited to the specific breach waived.
Amendments; Waivers; Modifications This Security Agreement and the provisions hereof may not be amended, waived, modified, changed, discharged or terminated except as set forth in Section 9.1 of the Credit Agreement.
Amendments; Modifications This Agreement may not be modified, altered or amended except by an agreement in writing executed by all of the parties hereto.
Modifications, Waivers, Amendments and Consents (a) Subject to this Section 3.21, the Servicer may agree to any modification, waiver, forbearance, or amendment of any term of any Mortgage Loan without the consent of the Trustee or any Certificateholder. All modifications, waivers, forbearances or amendments of any Mortgage Loan shall be in writing and shall be consistent with Customary Servicing Procedures.
(b) The Servicer shall not agree to enter into, and shall not enter into, any modification, waiver (other than a waiver referred to in Section 3.13, which waiver, if any, shall be governed by Section 3.13), forbearance or amendment of any term of any Mortgage Loan if such modification, waiver, forbearance, or amendment would:
(i) affect the amount or timing of any related payment of principal, interest or other amount payable thereunder;
(ii) in the Servicer's judgment, materially impair the security for such Mortgage Loan or reduce the likelihood of timely payment of amounts due thereon; or
(iii) otherwise constitute a "significant modification" within the meaning of Treasury Regulations Section 1.860G-2(b); unless, in either case, (A) such Mortgage Loan is 90 days or more past due or (B) the Servicer delivers to the Trustee an Opinion of Counsel to the effect that such modification, waiver, forbearance or amendment would not affect the REMIC status of either the Upper-Tier REMIC or the Lower-Tier REMIC and, in either case, such modification, waiver, forbearance or amendment is reasonably likely to produce a greater recovery with respect to such Mortgage Loan than would liquidation. Subject to Customary Servicing Procedures, the Servicer may permit a forbearance for a Mortgage Loan which in the Servicer's judgment is subject to imminent default.
(c) Any payment of interest, which is deferred pursuant to any modification, waiver, forbearance or amendment permitted hereunder, shall not, for purposes hereof, including, without limitation, calculating monthly distributions to Certificateholders, be added to the unpaid principal balance of the related Mortgage Loan, notwithstanding that the terms of such Mortgage Loan or such modification, waiver or amendment so permit.
(d) The Servicer may, as a condition to granting any request by a Mortgagor for consent, modification, waiver, forbearance or amendment, the granting of which is within the Servicer's discretion pursuant to the Mortgage Loan and is permitted by the terms of this Agreement, require that such Mortgagor pay to the Servicer, as additional servicing compensation, a reasonable or customary fee for the additional services performed in connection with such request, together with any related costs and expenses incurred by the Servicer, which amount shall be retained by the Servicer as additional servicing compensation.
(e) The Servicer shall notify the Trustee, in writing, of any modification, waiver, forbearance or amendment of any term of any Mortgage Loan and the date thereof, and shall deliver to the Trustee (or, at the direction of the Trustee, the Custodian) for deposit in the related Mortgage File, an original counterpart of the agreement relating to such modification, waiver, forbearance or amendment, promptly (and in any event within ten Business Days) following the execution thereof; provided, however, that if any such modification, waiver, forbearance or amendment is required by applicable law to be recorded, the Servicer (i) shall deliver to the Trustee a copy thereof and (ii) shall deliver to the Trustee such document, with evidence of notification upon receipt thereof from the public recording office.
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
