Amendments, Etc No supplement, modification or amendment of this Agreement shall be binding unless executed in writing by both 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 hereof (whether or not similar) nor shall such waiver constitute a continuing waiver.
Amendments, Supplements, Etc At any time this Agreement may be amended or supplemented by such additional agreements, articles or certificates, as may be determined by the parties hereto to be necessary, desirable or expedient to further the purposes of the Agreement, or to clarify the intention of the parties hereto, or to add to or modify the covenants, terms or conditions hereof or to effect or facilitate any governmental approval or acceptance of this Agreement or to effect or facilitate the filing or recording of this Agreement or the consummation of any of the transactions contemplated hereby. Any such instrument must be in writing and signed by all parties.
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.
Certain Voting Matters [To be inserted if the Charter provides for voting in proportion to liquidation preferences: Whether the vote or consent of the holders of a plurality, majority or other portion of the shares of Designated Preferred Stock and any Voting Parity Stock has been cast or given on any matter on which the holders of shares of Designated Preferred Stock are entitled to vote shall be determined by the Issuer by reference to the specified liquidation amount of the shares voted or covered by the consent as if the Issuer were liquidated on the record date for such vote or consent, if any, or, in the absence of a record date, on the date for such vote or consent. For purposes of determining the voting rights of the holders of Designated Preferred Stock under Section 7 of the Standard Provisions forming part of this [Certificate of Designations], each holder will be entitled to one vote for each $1,000 of liquidation preference to which such holder’s shares are entitled.] [To be inserted if the Charter does not provide for voting in proportion to liquidation preferences: Holders of shares of Designated Preferred Stock will be entitled to one vote for each such share on any matter on which holders of Designated Preferred Stock are entitled to vote, including any action by written consent.] 1 If Issuer desires to issue shares with a higher dollar amount liquidation preference, liquidation preference references will be modified accordingly. In such case (in accordance with Section 4.6 of the Securities Purchase Agreement), the issuer will be required to enter into a deposit agreement.
Additional Voting Powers and Voting Requirements for Certain Actions Notwithstanding any other provision of this Agreement, the Shareholders shall have power to vote to approve any amendment to Article VIII of this Agreement that would have the effect of reducing the indemnification provided thereby to Covered Persons or to Shareholders or former Shareholders, and any repeal or amendment of this sentence, and any such action shall require the affirmative vote or consent of Shareholders owning at least sixty-six and two-thirds percent (66 2/3%) of the Outstanding Shares entitled to vote thereon. In addition, the removal of one or more Trustees by the Shareholders shall require the affirmative vote or consent of Shareholders owning at least sixty-six and two-thirds percent (66 2/3%) of the Outstanding Shares entitled to vote thereon. The voting requirements set forth in this Section 6.2 shall be in addition to, and not in lieu of, any vote or consent of the Shareholders otherwise required by applicable law (including, without limitation, any separate vote by Portfolio (or Class) that may be required by the 1940 Act or by other applicable law) or by this Agreement.
Amendments; Waivers No provision of this Agreement may be waived or amended except in a written instrument signed, in the case of an amendment, by the Company and each Purchaser or, in the case of a waiver, by the party against whom enforcement of any such waiver is sought. No waiver of any default with respect to any provision, condition or requirement of this Agreement shall be deemed to be a continuing waiver in the future or a waiver of any subsequent default or a waiver of any other provision, condition or requirement hereof, nor shall any delay or omission of either party to exercise any right hereunder in any manner impair the exercise of any such right.
Amendments; Waiver This Agreement may be amended by the parties hereto and the terms and conditions hereof may be waived only by an instrument in writing signed on behalf of each of the parties hereto, or, in the case of a waiver, by an instrument signed on behalf of the party waiving compliance.
Proxies and Voting (a) On any matter that is to be voted on by Members, the Members may vote in person or by proxy, and such vote may be made, or proxy may be granted in writing, by means of electronic transmission or as otherwise permitted by applicable law. Any such proxy shall be delivered in accordance with the procedure established for the relevant meeting.
(b) For purposes of this Agreement, the term “electronic transmission” means any form of communication not directly involving the physical transmission of paper that creates a record that may be retained, retrieved and reviewed by a recipient thereof and that may be directly reproduced in paper form by such a recipient through an automated process. Any copy, facsimile telecommunication or other reliable reproduction of the writing or transmission created pursuant to this paragraph may be substituted or used in lieu of the original writing or transmission for any and all purposes for which the original writing or transmission could be used, provided that such copy, facsimile telecommunication or other reproduction shall be a complete reproduction of the entire original writing or transmission.
(c) The Board may, and to the extent required by law, shall, in advance of any meeting of Members, appoint one or more inspectors to act at the meeting and make a written report thereof. The Board may designate one or more alternate inspectors to replace any inspector who fails to act. If no inspector or alternate is able to act at a meeting of Members, the chairman of the meeting may, and to the extent required by law, shall, appoint one or more inspectors to act at the meeting. Each inspector, before entering upon the discharge of his or her duties, shall take and sign an oath faithfully to execute the duties of inspector with strict impartiality and according to the best of his or her ability. Every vote taken by ballots shall be counted by a duly appointed inspector or inspectors.
(d) With respect to the use of proxies at any meeting of Members, the Company shall be governed by paragraphs (b), (c), (d) and (e) of Section 212 of the DGCL and other applicable provisions of the DGCL, as though the Company were a Delaware corporation and as though the Members were shareholders of a Delaware corporation.
(e) In the event that the Company becomes subject to Regulation 14A under the Exchange Act, pursuant to and subject to the provisions of Rule 14a-16 under the Exchange Act, the Company may, but is not required to, utilize a Notice of Internet Availability of Proxy Materials, as described in such rule, in conjunction with proxy material posted to an Internet site, in order to furnish any proxy or related material to Members pursuant to Regulation 14A under the Exchange Act.
Waiver, Amendments, Etc The Trust shall not waive, modify, amend, supplement or consent to any waiver, modification, amendment of or supplement to, any of the provisions of the Certificate of Trust, the Trust Agreement or any of the other Transaction Documents unless, if no Insurer Default shall have occurred and be continuing, Financial Security shall have consented thereto in writing.
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
