RUS's Agreement Clause Samples

RUS's Agreement. In the event that the Borrower delivers a replacement Bond for a lost, stolen, destroyed, or mutilated Bond, as provided in section 6.1 of this Agreement, RUS shall execute and deliver an RUS Guarantee of the replacement Bond in replacement of the RUS Guarantee of the lost, stolen, destroyed, or mutilated Bond.
RUS's Agreement. If FFB elects to sell, assign, or transfer all or any part of the Bond or any participation share thereof, and if the respective purchaser, assignee, or transferee requests the Borrower to issue a replacement Bond or Bonds as provided in section 15.4.4(a) of this Agreement, RUS agrees that it will, upon the written request of FFB, execute and deliver an RUS Guarantee of the replacement Bond in replacement of the RUS Guarantee of the sold, assigned, or transferred Bond.

Related to RUS's Agreement

  • Client Agreement We are not required to enter into a written agreement complying with the Code relating to the services that are to be provided to you.

  • Student Agreement It is important that I work to the best of my ability. Therefore, I shall strive to do the following:

  • Assignment of Management Agreement As additional collateral security for the Loan, Borrower conditionally transfers, sets over, and assigns to Lender all of Borrower’s right, title and interest in and to the Management Agreement and all extensions and renewals. This transfer and assignment will automatically become a present, unconditional assignment, at Lender’s option, upon a default by Borrower under the Note, the Loan Agreement, the Security Instrument or any of the other Loan Documents (each, an “Event of Default”), and the failure of Borrower to cure such Event of Default within any applicable grace period.

  • Client Agreements Supplier will have a direct contract with, or provide its standard Product or Service terms directly to, Client, which will be enforceable solely between Client and Supplier, for all terms related to Client’s receipt and use of Products and Services (each a “Client Agreement”), other than the payment, risk of loss, and delivery terms that are contracted directly with Accenture.

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.