Certification Regarding Prohibition of Certain Terrorist Organizations (Tex Gov. Code 2270) Vendor certifies that Vendor is not a company identified on the Texas Comptroller’s list of companies known to have contracts with, or provide supplies or services to, a foreign organization designated as a Foreign Terrorist Organization by the U.S. Secretary of State. Does Vendor certify? 3 Yes
Distribution of UDP and TCP queries DNS probes will send UDP or TCP “DNS test” approximating the distribution of these queries.
Transfers or Assignments to a Third Party Financing Agent It is understood and agreed by the parties that a condition precedent to the consummation of the purchase(s) under the Contract may be the obtaining of acceptable third party financing by the Authorized User. The Authorized User shall make the sole determination of the acceptability of any financing proposal. The Authorized User will make all reasonable efforts to obtain such financing, but makes no representation that such financing has been obtained as of the date of Bid receipt. Where financing is used, Authorized User may assign or transfer its rights in Licensed Products (existing or custom) to a third party financing entity or trustee (“Trustee”) as collateral where required by the terms of the financing agreement. Trustee’s sole rights with respect to transferability or use of Licensed Products shall be to exclusively sublicense to Authorized User all of its Licensee’s rights under the terms and conditions of the License Agreement; provided, further, however, in the event of any termination or expiration of such sublicense by reason of payment in full, all of Trustee’s rights in such Licensed Product shall terminate immediately and Authorized User’s prior rights to such Existing Licensed Product shall be revived.
Admission and Enrollment of Students For a student to be accepted and enrolled into a dual credit program, the STUDENT shall:
Periodic Access to Thin Registration Data In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-‐to-‐date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
Transfers From Other Plans We can receive amounts transferred to this Xxxx XXX from the trustee or custodian of another Xxxx XXX as permitted by the Code. In addition, we can accept rollovers of eligible rollover distributions from employer-sponsored retirement plans as permitted by the Code. We reserve the right not to accept any transfer.
Certification Regarding Termination of Contract for Non-Compliance (Tex Gov. Code 552.374)
Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
File Management and Record Retention relating to CRF Eligible Persons or Households Grantee must maintain a separate file for every applicant, Eligible Person, or Household, regardless of whether the request was approved or denied.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
