Supplements and Amendments Prior to the Distribution Date and subject to the next to last sentence of this Section 26, the Company may, by resolution of its Board of Directors and the Rights Agent shall, if the Company so directs, supplement or amend any provision of this Agreement without the approval of any holders of certificates representing Common Stock. From and after the Distribution Date and subject to the next to last sentence of this Section 26, the Company and the Rights Agent shall, if the Company so directs, supplement or amend this Agreement without the approval of any holders of Rights Certificates in order (i) to cure any ambiguity, (ii) to correct or supplement any provision contained herein which may be defective or inconsistent with any other provisions herein, (iii) to change or supplement the provisions hereunder in any manner which the Company may deem necessary or desirable and which shall not adversely affect the interests of the holders of Rights Certificates (other than an Acquiring Person or an Affiliate or Associate of an Acquiring Person), or (iv) to shorten or lengthen any time period hereunder; provided, this Agreement may not be supplemented or amended to lengthen, pursuant to clause (iv) of this sentence, (A) a time period relative to when the Rights may be redeemed at such time as the Rights are not then redeemable, or (B) any other time period unless such lengthening is for the purpose of protecting, enhancing or clarifying the rights of, and/or the benefits to, the holders of Rights. Upon the delivery of a certificate from an appropriate officer of the Company which states that the proposed supplement or amendment is in compliance with the terms of this Section 26, the Rights Agent shall execute such supplement or amendment. Notwithstanding anything contained in this Agreement to the contrary, no supplement or amendment shall be made which changes the Redemption Price, the Final Expiration Date, the Purchase Price, or the number of Preferred Stock Fractions for which a Right is exercisable. Prior to the Distribution Date, the interests of the holders of Rights shall be deemed coincident with the interests of the holders of Common Stock.
Authorization and Execution The execution, delivery and performance of this Agreement has been duly authorized by all necessary action on the part of such Purchaser, and, assuming due authorization, execution and delivery by the other parties hereto, this Agreement is a legal, valid and binding obligation of such Purchaser, enforceable against such Purchaser in accordance with its terms, except as enforcement thereof may be limited by bankruptcy, insolvency, reorganization, moratorium or other similar laws relating to or affecting creditors’ rights generally or by general equitable principles.
Amendments and Supplements The Company shall prepare and file with the Commission such amendments, including post-effective amendments, and supplements to such Registration Statement and the prospectus used in connection therewith as may be necessary to keep such Registration Statement effective and in compliance with the provisions of the Securities Act until all Registrable Securities and other securities covered by such Registration Statement have been disposed of in accordance with the intended method(s) of distribution set forth in such Registration Statement or such securities have been withdrawn.
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.
Counterparts and Execution The Transaction Documents may be executed in two or more counterparts, all of which when taken together shall be considered one and the same agreement and shall become effective when counterparts have been signed by each party and delivered to each other party, it being understood that the parties need not sign the same counterpart. In the event that any signature is delivered by email delivery of a “.pdf” format data file, such signature shall create a valid and binding obligation of the party executing (or on whose behalf such signature is executed) with the same force and effect as if such “.pdf” signature page was an original thereof.
Electronic Execution of Assignments and Certain Other Documents The words “execution,” “signed,” “signature,” and words of like import in any Assignment and Assumption or in any amendment or other modification hereof (including waivers and consents) shall be deemed to include electronic signatures or the keeping of records in electronic form, each of which shall be of the same legal effect, validity or enforceability as a manually executed signature or the use of a paper-based recordkeeping system, as the case may be, to the extent and as provided for in any applicable law, including the Federal Electronic Signatures in Global and National Commerce Act, the New York State Electronic Signatures and Records Act, or any other similar state laws based on the Uniform Electronic Transactions Act.
Amendments and Variations No amendment to or Variation of this Agreement shall be effective unless made in writing by duly authorized representatives of both Parties, if not provided otherwise herein. The Agreement can be amended in compliance with the provisions of Article 61 of the Public Procurement Law of the Republic of Latvia.
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
Amendments to this Agreement This Agreement may only be amended by the parties in writing.
Amendments to Original Agreement The Original Agreement is hereby amended and modified as follows:
