Zone File Access Agreement Sample Clauses

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.
Sample 1Sample 2Sample 3See All (2k)
AutoNDA by SimpleDocs
Zone File Access Agreement. Registry Operator will enter into an agreement with any Internet user that 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 (the “CZDA Provider”). Registry Operator will provide access to zone file data per Section 2.1.3 and do so using the file format described in Section
Sample 1Sample 2Sample 3See All (10)
Zone File Access Agreement. Registry Operator will enter into an agreement with any Internet user that 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 an independent third party provider established a Zone File Access Service Provider (the “ZFA Provider”) pursuant to the Zone File Access Implementation Plan (the “ZFA Plan”) dated [ ] available at <LINK> (the “ZFA Provider”). Registry Operator will cooperate with the CFAZFA Provider in establishing uniform access to zone file data. Notwithstanding the foregoing, (a) Registry Operator may reject the request for access of any user that Registry Operator reasonably believes will violate the terms of Section 2.1.5 below, and (b) the ZFA Provider may reject the request for access of any user that does not pass all the credentialing requirements established pursuant to the Zone File Access ImplementationZFA Plan available at <LINK>.
Sample 1
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 belowof this Specification; (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 belowof this Specification or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. belowof this Specification; 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
Sample 1
Zone File Access Agreement. Registry Operator will enter into an agreement with any Internet user that 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 FileData Access Service Provider (the “ZFACZDA Provider”) pursuant to the Zone File Access Implementation Plan (the “ZFA Plan”) dated [ ] available at <LINK>. Registry Operator will cooperate with the ZFA Provider in establishing uniformprovide access to zone file data per Section 2.1.3 and do so using the file format described in Section 2.1.4. Notwithstanding the foregoing, (a) Registry Operator may reject the request for access of any user that Registry Operator reasonably believes will violate the terms of Section 2.1.5 below, and (b) the ZFAthe CZDA Provider may reject the request for access of any user that does not pass allsatisfy the credentialing requirements established pursuant to the ZFA Xxxx.xx 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 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.
Sample 1

Related to Zone File Access Agreement

  • Data Access and Proprietary Information 6.1 The Fund acknowledges that the databases, computer programs, screen formats, report formats, interactive design techniques, and documentation manuals furnished to the Fund by the Transfer Agent as part of the Fund’s ability to access certain Fund Confidential Information maintained by the Transfer Agent on databases under the control and ownership of the Transfer Agent or other third party (“Data Access Services”) constitute copyrighted, trade secret, or other proprietary information of substantial value to the Transfer Agent or other third party (collectively, “Transfer Agent Proprietary Information”). In no event shall Transfer Agent Proprietary Information be deemed Fund Confidential Information. The Fund agrees to treat all Transfer Agent Proprietary Information as proprietary to the Transfer Agent and further agrees that it shall not divulge any Transfer Agent Proprietary Information to any person or organization except as may be provided hereunder. Without limiting the foregoing, the Fund agrees for itself and its employees and agents to: (a) Use such programs and databases (i) solely on the Fund’s computers or on computers of Federated Services Company or its affiliates (collectively, “Fund Computers”), or (ii) solely from equipment at the location agreed to between the Fund and the Transfer Agent and (iii) solely in accordance with the Transfer Agent’s applicable user documentation; (b) Refrain from copying or duplicating in any way (other than in the normal course of performing processing on the Fund Computers), the Transfer Agent Proprietary Information; (c) Refrain from obtaining unauthorized access to any portion of the Transfer Agent Proprietary Information, and if such access is inadvertently obtained, to inform Transfer Agent in a timely manner of such fact and dispose of such information in accordance with the Transfer Agent’s instructions; (d) Refrain from causing or allowing information transmitted from the Transfer Agent’s computer to the Fund’s terminal to be retransmitted to any other computer terminal or other device except as expressly permitted by the Transfer Agent (such permission not to be unreasonably withheld); (e) Allow the Fund to have access only to those authorized transactions as agreed to between the Fund and the Transfer Agent; and (f) Honor all reasonable written requests made by the Transfer Agent to protect at the Transfer Agent’s expense the rights of the Transfer Agent in the Transfer Agent Proprietary Information at common law, under federal copyright law and under other federal or state law. 6.2 The Fund shall take reasonable efforts to advise its employees of their obligations pursuant to this Section 6. The obligations of this Section shall survive any earlier termination of this Agreement. 6.3 If the Fund notifies the Transfer Agent that any of the Data Access Services do not operate in material compliance with the most recently issued user documentation for such services, the Transfer Agent shall use its best efforts in a timely manner to correct such failure. Organizations from which the Transfer Agent may obtain certain data included in the Data Access Services are solely responsible for the contents of such data and the Fund agrees to make no claim against the Transfer Agent arising out of the contents of such third-party data, including, but not limited to, the accuracy thereof; provided, however, that the Fund shall be entitled to insist that the Transfer Agent, and the Transfer Agent for the benefit of the Fund shall, enforce any and all rights under applicable contracts for the Data Access Services. SUBJECT TO THE FOREGOING OBLIGATIONS OF THE TRANSFER AGENT, DATA ACCESS SERVICES AND ALL COMPUTER PROGRAMS AND SOFTWARE SPECIFICATIONS USED IN CONNECTION THEREWITH ARE PROVIDED ON AN AS IS, AS AVAILABLE BASIS. EXCEPT AS OTHERWISE PROVIDED HEREIN TO THE CONTRARY, THE TRANSFER AGENT EXPRESSLY DISCLAIMS ALL WARRANTIES INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. 6.4 If the transactions available to the Fund include the ability to originate Proper Instructions through electronic instructions to the Transfer Agent in order to: (i) effect the transfer or movement of cash or Shares; or (ii) transmit Shareholder information or other information, then in such event the Transfer Agent shall be entitled to rely on the validity and authenticity of such Proper Instructions without undertaking any further inquiry as long as such Proper Instruction is undertaken in conformity with applicable security procedures.

  • Vendor Logo (Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No Can the Vendor provide its proposed goods and services to all 50 US States? Yes

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!