Partial Invalidity If any provision in this Agreement is held by a court of competent jurisdiction to be invalid, void, or unenforceable, the remaining provisions shall nevertheless continue in full force without being impaired or invalidated in any way.
Effect of Partial Invalidity The invalidity of any portion of this Agreement shall not affect the validity of any other provision. In the event that any provision of this Agreement is held to be invalid, the parties agree that the remaining provisions shall remain in full force and effect.
PARTIAL INVALIDITY; WAIVER 14.1 If at any time, any one or more of the provisions hereof is or becomes invalid, illegal or unenforceable in any respect under the law of any jurisdiction, such provision shall as to such jurisdiction, be ineffective to the extent necessary without affecting or impairing the validity, legality and enforceability of the remaining provisions hereof or of such provisions in any other jurisdiction. The invalid, illegal or unenforceable provision shall be deemed to be replaced with such valid, legal or enforceable provision which comes as close as possible to the original intent of the parties and the invalid, illegal or unenforceable provision. Should a gap (Regelungslücke) become evident in this Agreement, such gap shall, without affecting or impairing the validity, legality and enforceability of the remaining provisions hereof, be deemed to be filled in with such provision which comes as close as possible to the original intent of the parties.
14.2 No failure to exercise, nor any delay in exercising, on the part of the Pledgee, any right or remedy hereunder shall operate as a waiver thereof, nor shall any single or partial exercise of any right or remedy prevent any further or other exercise thereof or the exercise of any other right or remedy. The rights and remedies provided hereunder are cumulative and not exclusive of any rights or remedies provided by law.
Partial Invalidity; Severability If any of the provisions of this Agreement, or the application thereof to any person, party or circumstances, shall, to any extent, be invalid or unenforceable, the remainder of this Agreement, or the application of such provision or provisions to persons, parties or circumstances other than those as to whom or which it is held invalid or unenforceable, shall not be affected thereby, and every provision of this Agreement shall be valid and enforceable to the fullest extent permitted 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 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; Severability This Contract may be modified or amended only by a writing duly authorized and executed by the Superintendent and the Board. If any portion of this Contract shall be declared invalid or unenforceable by a court of competent jurisdiction, such declaration shall not affect the validity or enforceability of the remaining provisions of this Contract.
Governing Law; Invalidity This Agreement shall be governed by Wisconsin law, excluding the laws on conflicts of laws. To the extent that the applicable laws of the State of Wisconsin, or any of the provisions herein, conflict with the applicable provisions of the 1940 Act, the latter shall control, and nothing herein shall be construed in a manner inconsistent with the 1940 Act or any rule or order of the Commission thereunder. Any provision of this Agreement which may be determined by competent authority to be prohibited or unenforceable in any jurisdiction shall, as to such jurisdiction, be ineffective to the extent of such prohibition or unenforceability without invalidating the remaining provisions hereof, and any such prohibition or unenforceability in any jurisdiction shall not invalidate or render unenforceable such provision in any other jurisdiction. In such case, the parties shall in good faith modify or substitute such provision consistent with the original intent of the parties.
Partial Invalidity and Severability All rights and restrictions contained herein may be exercised and shall be applicable and binding only to the extent that they do not violate any applicable laws and are intended to be limited to the extent necessary to render this Agreement legal, valid and enforceable. If any terms of this Agreement not essential to the commercial purpose of this Agreement shall be held to be illegal, invalid or unenforceable by a court of competent jurisdiction, it is the intention of the parties that the remaining terms hereof shall constitute their agreement with respect to the subject matter hereof and all such remaining terms shall remain in full force and effect. To the extent legally permissible, any illegal, invalid or unenforceable provision of this Agreement shall be replaced by a valid provision which will implement the commercial purpose of the illegal, invalid or unenforceable provision.
Authorization of Agreement; Enforceability This Agreement has been duly and validly authorized, executed and delivered by the Company. This Agreement is valid, binding and enforceable against the Company in accordance with its terms, subject, as to enforcement, to bankruptcy, insolvency, reorganization and other laws of general applicability relating to or affecting creditors’ rights and to general equity principals.
