Miscellaneous Amendments Notwithstanding anything contained herein to the contrary, whenever any of the terms “Leased Premises”, “Demised Premises” or “Premises” (and whether or not capitalized) is used herein, it shall be understood to mean the “premises leased hereby”; and whenever the term “Entire Premises” is used herein (and whether or not capitalized), it shall be understood to mean all of the contiguous land and buildings owned by Landlord at this location, which include the premises leased hereby. The term “Non-leased Premises” shall mean the Entire Premises less the Leased Premises.
Waivers; Amendments (a) No failure or delay by the Administrative Agent or any Lender in exercising any right or power under this Agreement or any Loan Document shall operate as a waiver thereof, nor shall any single or partial exercise of any such right or power, or any abandonment or discontinuance of steps to enforce such a right or power, preclude any other or further exercise thereof or the exercise of any other right or power. The rights and remedies of the Administrative Agent and the Lenders hereunder and under the other Loan Documents are cumulative and are not exclusive of any rights or remedies that they would otherwise have. No waiver of any provision of this Agreement or any Loan Document or consent to any departure by any Loan Party therefrom shall in any event be effective unless the same shall be permitted by paragraph (b) of this Section, and then such waiver or consent shall be effective only in the specific instance and for the purpose for which given. Without limiting the generality of the foregoing, the making of a Loan shall not be construed as a waiver of any Default, regardless of whether the Administrative Agent or any Lender may have had notice or knowledge of such Default at the time. No notice or demand on the Borrower or Holdings in any case shall entitle the Borrower or Holdings to any other or further notice or demand in similar or other circumstances. (b) Except as provided in Section 2.18 with respect to any Incremental Revolving Facility Amendment or Incremental Term Facility Amendment (including to provide for provisions relating to the issuance of letters of credit and swingline loans and provisions with respect to “defaulting lenders”), Section 2.19 with respect to any Refinancing Amendment or Section 6.15 with respect to a change in the fiscal year of Holdings and the Borrower, neither this Agreement nor any Loan Document nor any provision hereof or thereof may be waived, amended or modified except, in the case of this Agreement, pursuant to an agreement or agreements in writing entered into by Holdings, the Borrower and the Required Lenders or, in the case of any other Loan Document, pursuant to an agreement or agreements in writing entered into by the Administrative Agent and the Loan Party or Loan Parties that are parties thereto, in each case with the consent of the Required Lenders, provided that no such agreement shall (i) increase the Commitment of any Lender without the written consent of such Lender (it being understood that a waiver of any condition precedent set forth in Section 4.02 or the waiver of any Default, mandatory prepayment or mandatory reduction of the Commitments shall not constitute an extension or increase of any Commitment of any Lender), (ii) reduce the principal amount of any Loan or reduce the rate of interest thereon, or reduce any fees payable hereunder, without the written consent of each Lender directly and adversely affected thereby (it being understood that any change to the definition of Total Leverage Ratio, Total Net Leverage Ratio or in the component definitions thereof shall not constitute a reduction of interest or fees), provided that only the consent of the Required Lenders shall be necessary to waive any obligation of the Borrower to pay default interest pursuant to Section 2.11(c), (iii) postpone the maturity of any Loan, or the date of any scheduled amortization payment of the principal amount of any Term Loan under Section 2.08 or the applicable Refinancing Amendment, or any date for the payment of any interest or fees payable hereunder, or reduce the amount of, waive or excuse any such payment, or postpone the scheduled date of expiration of any Commitment, without the written consent of each Lender directly and adversely affected thereby, (iv) change Section 2.16(b) or (c) in a manner that would alter the pro rata sharing of payments required thereby, without the written consent of the Lenders holding a Majority in Interest of the outstanding Loans and unused Commitments of each adversely affected Class, (v) change any of the provisions of this Section without the written consent of each Lender directly and adversely affected thereby, (vi) change the percentage set forth in the definition of “Required Lenders” or any other provision of any Loan Document specifying the number or percentage of Lenders (or Lenders of any Class) required to waive, amend or modify any rights thereunder or make any determination or grant any consent thereunder, without the written consent of each Lender (or each Lender of such Class, as the case may be), (vii) release all or substantially all the value of the Guarantees under the Guarantee Agreement (except as expressly provided in the Guarantee Agreement) without the written consent of each Lender (except as expressly provided in the Security Documents), (viii) release all or substantially all the Collateral from the Liens of the Security Documents, without the written consent of each Lender, (ix) change any provisions of any Loan Document in a manner that by its terms adversely affects the rights in respect of payments due to Lenders holding Loans of any Class differently than those holding Loans of any other Class, without the written consent of Lenders holding a Majority in Interest of the outstanding Loans and unused Commitments of each affected Class, or (x) change the rights of the Term Lenders to decline mandatory prepayments as provided in Section 2.09 or the rights of any Additional Lenders of any Class to decline mandatory prepayments of Term Loans of such Class as provided in the applicable Refinancing Amendment, without the written consent of a Majority in Interest of the Term Lenders or Additional Lenders of such Class, as applicable; provided further that (A) no such agreement shall amend, modify or otherwise affect the rights or duties of the Administrative Agent without the prior written consent of the Administrative Agent and (B) any provision of this Agreement or any other Loan Document may be amended by an agreement in writing entered into by Holdings, the Borrower and the Administrative Agent to cure any ambiguity, omission, defect or inconsistency so long as, in each case, the Lenders shall have received at least five Business Days’ prior written notice thereof and the Administrative Agent shall not have received, within five Business Days of the date of such notice to the Lenders, a written notice from the Required Lenders stating that the Required Lenders object to such amendment. Notwithstanding the foregoing, (a) this Agreement may be amended (or amended and restated) with the written consent of the Required Lenders, the Administrative Agent, Holdings and the Borrower (i) to add one or more additional credit facilities to this Agreement and to permit the extensions of credit from time to time outstanding thereunder and the accrued interest and fees in respect thereof to share ratably in the benefits of this Agreement and the other Loan Documents and (ii) to include appropriately the Lenders holding such credit facilities in any determination of the Required Lenders on substantially the same basis as the Lenders prior to such inclusion and (b) guarantees, collateral security documents and related documents executed by Foreign Subsidiaries in connection with this Agreement may be in a form reasonably determined by the Administrative Agent and may be, together with this Agreement, amended and waived with the consent of the Administrative Agent at the request of the Borrower without the need to obtain the consent of any other Lender if such amendment or waiver is delivered in order (i) to comply with local law or advice of local counsel, (ii) to cure ambiguities or defects or (iii) to cause such guarantee, collateral security document or other document to be consistent with this Agreement and the other Loan Documents. (c) In connection with any proposed amendment, modification, waiver or termination (a “Proposed Change”) requiring the consent of all Lenders or all directly and adversely affected Lenders, if the consent of the Required Lenders (and, to the extent any Proposed Change requires the consent of Lenders holding Loans of any Class pursuant to clause (iv), (ix) or (x) of paragraph (b) of this Section, the consent of a Majority in Interest of the outstanding Loans and unused Commitments of such Class) to such Proposed Change is obtained, but the consent to such Proposed Change of other Lenders whose consent is required is not obtained (any such Lender whose consent is not obtained as described in paragraph (b) of this Section being referred to as a “Non-Consenting Lender”), then, so long as the Lender that is acting as Administrative Agent is not a Non-Consenting Lender, the Borrower may, at its sole expense and effort, upon notice to such Non-Consenting Lender and the Administrative Agent, require such Non-Consenting Lender to assign and delegate, without recourse (in accordance with and subject to the restrictions contained in Section 9.04), all its interests, rights and obligations under this Agreement to an Eligible Assignee that shall assume such obligations (which Eligible Assignee may be another Lender, if a Lender accepts such assignment), provided that (a) the Borrower shall have received the prior written consent of the Administrative Agent to the extent such consent would be required under Section 9.04(b) for an assignment of Loans or Commitments, as applicable, which consent shall not unreasonably be withheld, (b) such Non-Consenting Lender shall have received payment of an amount equal to the outstanding par principal amount of its Loans, accrued interest thereon, accrued fees and all other amounts payable to it hereunder (including pursuant to Section 2.09(a)(i)) from the Eligible Assignee (to the extent of such outstanding principal and accrued interest and fees) or the Borrower (in the case of all other amounts) and (c) unless waived, the Borrower or such Eligible Assignee shall have paid to the Administrative Agent the processing and recordation fee specified in Section 9.04(b). (d) Notwithstanding anything in this Agreement or the other Loan Documents to the contrary, each Affiliated Lender (other than an Affiliated Debt Fund) hereby agrees that, if a proceeding under the United States Bankruptcy Code or any other Federal, state or foreign bankruptcy, insolvency, receivership or similar law shall be commenced by or against the Borrower or any other Loan Party at a time when such Lender is an Affiliated Lender, such Affiliated Lender irrevocably authorizes and empowers the Administrative Agent to vote on behalf of such Affiliated Lender with respect to the Loans held by such Affiliated Lender in any manner in the Administrative Agent’s sole discretion, unless the Administrative Agent instructs such Affiliated Lender to vote, in which case such Affiliated Lender shall vote with respect to the Loans held by it as the Administrative Agent directs; provided that such Affiliated Lender shall be entitled to vote in accordance with its sole discretion (and not in accordance with the direction of the Administrative Agent) in connection with any plan of reorganization to the extent any such plan of reorganization proposes to treat any Secured Obligations held by such Affiliated Lender in a manner that is less favorable in any material respect to such Affiliated Lender than the proposed treatment of similar Secured Obligations held by Lenders that are not Affiliates of the Borrower.
Waivers, Amendments, etc The Secured Party's delay or failure at any time or times hereafter to require strict performance by Company of any undertakings, agreements or covenants shall not waiver, affect, or diminish any right of the Secured Party under this Agreement to demand strict compliance and performance herewith. Any waiver by the Secured Party of any Event of Default shall not waive or affect any other Event of Default, whether such Event of Default is prior or subsequent thereto and whether of the same or a different type. None of the undertakings, agreements and covenants of the Company contained in this Agreement, and no Event of Default, shall be deemed to have been waived by the Secured Party, nor may this Agreement be amended, changed or modified, unless such waiver, amendment, change or modification is evidenced by an instrument in writing specifying such waiver, amendment, change or modification and signed by the Secured Party.
6Amendments 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 (iii) in the immediately preceding sentence shall not be considered an Alternative Amendment hereunder and therefore shall not supersede or delay the effectiveness of the Board Amendment. If, following the submission of the Alternative Amendment to the ICANN Board of Directors, the Alternative Amendment receives Registry Operator Approval, the Alternative Amendment shall supersede the Board Amendment and shall be deemed an Approved Amendment hereunder (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 Alternative Amendment to Registry Operator, which effective date shall deemed the Amendment Effective Date hereunder), unless, within a period of sixty (60) calendar days following the date that the Working Group notifies the ICANN Board of Directors of Registry Operator Approval of such Alternative Amendment (during which time ICANN shall engage with the Working Group with respect to the Alternative Amendment), the ICANN Board of Directors 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, rejects the Alternative Amendment. If (A) the Alternative Amendment does not receive Registry Operator Approval within thirty (30) calendar days of submission of such Alternative Amendment to the Applicable Registry Operators (and the Working Group shall notify ICANN of the date of such submission), or (B) the ICANN Board of Directors rejects the Alternative Amendment by such two-thirds vote, the Board Amendment (and not the Alternative Amendment) 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 to Registry Operator (which effective date shall deemed the Amendment Effective Date hereunder). If the ICANN Board of Directors rejects an Alternative Amendment, the board shall publish a written rationale setting forth its analysis of the criteria set forth in Sections 7.6(f)(i) through 7.6(f)(iii). The ability of the ICANN Board of Directors to reject an Alternative Amendment hereunder does not relieve the Board of the obligation to ensure that any Board Amendment meets the criteria set forth in Section 7.6(e)(i) through 7.6(e)(v). (g) In the event that Registry Operator believes an Approved Amendment does not meet the substantive requirements set out in this Section 7.6 or has been adopted in contravention of any of the procedural provisions of this Section 7.6, Registry Operator may challenge the adoption of such Special Amendment pursuant to the dispute resolution provisions set forth in Article 5, except that such arbitration shall be conducted by a three-person arbitration panel. Any such challenge must be brought within sixty (60) calendar days following the date ICANN provided notice to Registry Operator of the Approved Amendment, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. The Approved Amendment will be deemed not to have amended this Agreement during the pendency of the dispute resolution process. (h) Registry Operator may apply in writing to ICANN for an exemption from the Approved Amendment (each such request submitted by Registry Operator hereunder, an “Exemption Request”) during the thirty (30) calendar day period following the date ICANN provided notice to Registry Operator of such Approved Amendment. Each Exemption Request will set forth the basis for such request and provide detailed support for an exemption from the Approved Amendment. An Exemption Request may also include a detailed description and support for any alternatives to, or a variation of, the Approved Amendment proposed by such Registry Operator. An Exemption Request may only be granted upon a clear and convincing showing by Registry Operator that compliance with the Approved Amendment conflicts with applicable laws or would have a material adverse effect on the long-term financial condition or results of operations of Registry Operator. No Exemption Request will be granted if ICANN determines, in its reasonable discretion, that granting such Exemption Request would be materially harmful to registrants or result in the denial of a direct benefit to registrants. Within ninety (90) calendar days of ICANN’s receipt of an Exemption Request, ICANN shall either approve (which approval may be conditioned or consist of alternatives to or a variation of the Approved Amendment) or deny the Exemption Request in writing, during which time the Approved Amendment will not amend this Agreement. If the Exemption Request is approved by ICANN, the Approved Amendment will not amend this Agreement; provided, that any conditions, alternatives or variations of the Approved Amendment required by ICANN shall be effective and, to the extent applicable, will amend this Agreement as of the Amendment Effective Date. If such Exemption Request is denied by ICANN, the Approved Amendment will amend this Agreement as of the Amendment Effective Date (or, if such date has passed, such Approved Amendment shall be deemed effective immediately on the date of such denial), provided that Registry Operator may, within thirty (30) calendar days following receipt of ICANN’s determination, appeal ICANN’s decision to deny the Exemption Request pursuant to the dispute resolution procedures set forth in Article 5. The Approved Amendment will be deemed not to have amended this Agreement during the pendency of the dispute resolution process. For avoidance of doubt, only Exemption Requests submitted by Registry Operator that are approved by ICANN pursuant to this Section 7.6(j), agreed to by ICANN following mediation pursuant to Section 5.1 or through an arbitration decision pursuant to Section 5.2 shall exempt Registry Operator from any Approved Amendment, and no Exemption Request granted to any other Applicable Registry Operator (whether by ICANN or through arbitration) shall have any effect under this Agreement or exempt Registry Operator from any Approved Amendment. (i) Except as set forth in this Section 7.6, Section 7.7 and as otherwise set forth in this Agreement and the Specifications hereto, no amendment, supplement or modification of this Agreement or any provision hereof shall be binding unless executed in writing by both parties, and nothing in this Section 7.6 or Section 7.7 shall restrict ICANN and Registry Operator from entering into bilateral amendments and modifications to this Agreement negotiated solely between the two parties. No waiver of any provision of this Agreement shall be binding unless evidenced by a writing signed by the party waiving compliance with such provision. No waiver of any of
WAIVERS, AMENDMENTS AND REMEDIES No delay or omission of the Administrative Agent or any Holder of Secured Obligations to exercise any right or remedy granted under this Security Agreement shall impair such right or remedy or be construed to be a waiver of any Default or an acquiescence therein, and any single or partial exercise of any such right or remedy shall not preclude any other or further exercise thereof or the exercise of any other right or remedy. No waiver, amendment or other variation of the terms, conditions or provisions of this Security Agreement whatsoever shall be valid unless in writing signed by the Administrative Agent with the concurrence or at the direction of the Lenders required under Section 8.2 of the Credit Agreement and each Grantor, and then only to the extent in such writing specifically set forth, provided that the addition of any Domestic Subsidiary as a Grantor hereunder by execution of a Security Agreement Supplement in the form of Annex I (with such modifications as shall be acceptable to the Administrative Agent) shall not require receipt of any consent from or execution of any documentation by any other Grantor party hereto. All rights and remedies contained in this Security Agreement or by law afforded shall be cumulative and all shall be available to the Administrative Agent and the Holders of Secured Obligations until the Secured Obligations have been paid in full.