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.
Supplements and Amendments This Agreement may be amended by the Depositor and the Owner Trustee, without the consent of any of the Noteholders or the Certificateholder, to cure any ambiguity, to correct or supplement any provisions in this Agreement or for the purpose of adding any provisions to or changing in any manner or eliminating any of the provisions in this Agreement or of modifying in any manner the rights of the Noteholders or the Certificateholder; provided, however, that such action shall not, as evidenced by an Opinion of Counsel, adversely affect in any material respect the interests of any Noteholder or the Certificateholder, provided further that 10 days’ (or, in the case of Fitch, 10 Business Days’) prior written notice of any such amendment be made available to each Rating Agency by the Administrator and, if Moody’s notifies the Owner Trustee that such amendment will result in a downgrading or withdrawal of the then-current rating of any class of the Notes, such amendment shall become effective with the consent of the Holders of Notes evidencing not less than a majority of the Outstanding Amount of the Notes; provided further that any solicitation of such consent shall disclose the downgrading or withdrawal that would result from such amendment. This Agreement may also be amended from time to time by the Depositor and the Owner Trustee, with prior written notice made available to the Rating Agencies by the Administrator, with the consent of the Holders of Notes evidencing not less than a majority of the Outstanding Amount of the Notes and the consent of the Certificateholder (which consents will not be unreasonably withheld) for the purpose of adding any provisions to or changing in any manner or eliminating any of the provisions of this Agreement or of modifying in any manner the rights of the Noteholders or the Certificateholder; provided, however, that no such amendment shall (a) increase or reduce in any manner the amount of, or accelerate or delay the timing of, collections of payments on Receivables or distributions that shall be required to be made for the benefit of the Noteholders or the Certificateholder or (b) reduce the aforesaid percentage of the Outstanding Amount of the Notes required to consent to any such amendment or eliminate the consent of the Certificateholder to any such amendment, without the consent of the holders of all the outstanding Notes and the Certificate. Promptly after the execution of any such amendment or consent, the Owner Trustee shall furnish written notification of the substance of such amendment or consent to the Certificateholder, the Indenture Trustee and the Administrator, which shall make such notification available to each of the Rating Agencies. It shall not be necessary for the consent of the Certificateholder, the Noteholders or the Indenture Trustee pursuant to this Section to approve the particular form of any proposed amendment or consent, but it shall be sufficient if such consent shall approve the substance thereof. Promptly after the execution of any amendment to the Certificate of Trust, the Owner Trustee shall cause the filing of such amendment with the Secretary of State. Prior to the execution of any amendment to this Agreement or the Certificate of Trust, the Owner Trustee shall be entitled to receive and rely upon an Opinion of Counsel stating that the execution of such amendment is authorized or permitted by this Agreement and that all conditions precedent to the execution of such amendment have been satisfied. The Owner Trustee may, but shall not be obligated to, enter into any such amendment which affects the Owner Trustee’s own rights, duties or immunities under this Agreement or otherwise.
Amendments and Changes The Contracting Parties may make amendments and changes to this Agreement by mutual consent Such amendments and changes shall be made in the form of additional protocols which, upon entry into force in the manner prescribed in Article 15, shall constitute an integral and inseparable part of this Agreement
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.
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
Supplements and Amendments; Whole Agreement This Warrant may be amended or supplemented only by an instrument in writing signed by the parties hereto. This Warrant contains the full understanding of the parties hereto with respect to the subject matter hereof and thereof and there are no representations, warranties, agreements or understandings other than expressly contained herein and therein.
Entire Agreement; Amendments and Waivers This Agreement (including the schedules and exhibits hereto) represents the entire understanding and agreement between the parties hereto with respect to the subject matter hereof and can be amended, supplemented or changed, and any provision hereof can be waived, only by written instrument making specific reference to this Agreement signed by the party against whom enforcement of any such amendment, supplement, modification or waiver is sought. No action taken pursuant to this Agreement, including without limitation, any investigation by or on behalf of any party, shall be deemed to constitute a waiver by the party taking such action of compliance with any representation, warranty, covenant or agreement contained herein. The waiver by any party hereto of a breach of any provision of this Agreement shall not operate or be construed as a further or continuing waiver of such breach or as a waiver of any other or subsequent breach. No failure on the part of any party to exercise, and no delay in exercising, any right, power or remedy hereunder shall operate as a waiver thereof, nor shall any single or partial exercise of such right, power or remedy by such party preclude any other or further exercise thereof or the exercise of any other right, power or remedy. All remedies hereunder are cumulative and are not exclusive of any other remedies provided by law.
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 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.
Filing of Amendments and 1934 Act Documents The Company will give the Representatives notice of its intention to file or prepare any amendment to the Registration Statement (including any filing under Rule 462(b)) or any amendment, supplement or revision to either the prospectus included in the Registration Statement at the time it became effective or to the Prospectus, and will furnish the Representatives with copies of any such documents a reasonable amount of time prior to such proposed filing or use, as the case may be, and will not file or use any such document to which the Representatives or counsel for the Underwriters shall reasonably object. The Company will give the Representatives notice of its intention to make any filings pursuant to the 1934 Act or the 1934 Act Regulations from the Applicable Time to the Closing Time and will furnish the Representatives with copies of any such documents a reasonable amount of time prior to such proposed filing, as the case may be, and will not file or use any such document to which the Representatives or counsel for the Underwriters shall reasonably object.
