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.
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
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 Zone File Access Service Provider (the “ZFA 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 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 ZFA Plan.
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
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.

Related to Zone File Access Agreement

  • 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. Bid Attributes Disadvantaged/Minority/Women Business & Federal HUBZone 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 Historically Underutilized Business (HUB) 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 National Coverage Can the Vendor provide its proposed goods and services to all 50 US States? Yes

Time is Money Join Law Insider Premium to draft better contracts faster.