Common use of Grant of Access Clause in Contracts

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP (or other Registry supported) service for an ICANN-­‐specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP (or other Registry supported) service for an ICANN-­‐specified ICANN-specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenon-exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level top-level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level top-level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>-yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP SFTP (or other Registry supported) service for an ICANN-­‐specified ICANN-specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenon-exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level top-level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTPSFTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level top-level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>-yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP SFTP (or other Registry supported) service for an ICANN-­‐specified ICANN‐specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenon‐exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level top‐level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTPSFTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level top‐level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>‐yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP SFTP (or other Registry supported) service for an ICANN-­‐specified ICANN-specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenon-exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's’s) Zone File hosting server, and to transfer a copy of the top-­‐level top-level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTPSFTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level top-level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>-yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP SFTP (or other Registry supported) service for an ICANN-­‐specified ICANN-specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenon‐exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level top-level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTPSFTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level top-level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>- yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP SFTP (or other Registry supported) service for an ICANN-­‐specified ICANN-specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenon‐exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level top-level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTPSFTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level top-level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>-yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP (or other Registry supported) service for an ICANN-­‐specified ICANN‐specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenon‐exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level top‐level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level top‐level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>‐yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP FTPSFTP (or other Registry supported) service for an ICANN-­‐specified ICANN-specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenon-exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level top-level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTPFTPSFTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level top-level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>-yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP SFTP (or other Registry supported) service for an ICANN-­‐specified ICANN-specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenon-exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level top-level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTPSFTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level top-level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>- yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP (or other Registry supported) service for an ICANN-­‐specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the RegistryRegistry Operator’s zone data archives. Registry Operator will grant the user a non-­‐exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator XxXXX (optionally through the CZDA Provider) will provide the Zone File FTP (or other Registry supported) service for an ICANN-­‐specified cxDA- specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx TLD>.xxx.xxXX.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator XxXXX will grant xxxxx the user a non-­‐exclusivenon-exclusive, nontransferable, limited right to access Registry OperatorXxXXX ’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level top-level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTP, or other data transport and access protocols that may be prescribed by ICANNcxDA. For every zone file access server, the zone files are in the top-­‐level top-level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator XxXXX (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>- yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP (or other Registry supported) service for an ICANN-­‐specified ICANN-specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenon-exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level top-level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level top-level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>- yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP FTPSFTP (or other Registry supported) service for an ICANN-­‐specified ICANN-specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenon-exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's’s) Zone File hosting server, and to transfer a copy of the top-­‐level top-level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTPFTPSFTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level top-level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>- yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP (or other Registry supported) service for an ICANN-­‐specified ICANN--‐specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenon--‐exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level top--‐level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level top--‐level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>--‐- yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP SFTP (or other Registry supported) service for an ICANN-­‐specified ICANN-specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenon-exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level top-level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTPSFTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level top- level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>-yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator XxXXX (optionally through the CZDA Provider) will provide the Zone File FTP (or other Registry supported) service for an ICANN-­‐specified cxDA- specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx TLD>.xxx.xxXX.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator XxXXX will grant the user a non-­‐exclusivenon-exclusive, nontransferable, limited right to access Registry OperatorXxXXX ’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level top-level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTP, or other data transport and access protocols that may be prescribed by ICANNcxDA. For every zone file access server, the zone files are in the top-­‐level top-level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator XxXXX (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>- yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP (or other Registry supported) service for an ICANN-­‐specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>-­‐ yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP (or other Registry supported) service for an ICANN-­‐specified ICANNLspecified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenonLexclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level topLlevel domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level topLlevel directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>Lyyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the throughthe CZDA Provider) will provide the Zone File FTP (or other Registry otherRegistry supported) service for an ICANN-­‐specified ICANN-specified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenon-exclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level top-level domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level top-level directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>-yyyymmdd.zone.gz, etc.

Grant of Access. Each Registry Operator (optionally through the CZDA Provider) will provide the Zone File FTP (or other Registry supported) service for an ICANN-­‐specified ICANNMspecified and managed URL (specifically, <TLD>.xxx.xxxxx.xxx where <TLD> is the TLD for which the registry is responsible) for the user to access the Registry’s zone data archives. Registry Operator will grant the user a non-­‐exclusivenonMexclusive, nontransferable, limited right to access Registry Operator’s (optionally CZDA Provider's) Zone File hosting server, and to transfer a copy of the top-­‐level topMlevel domain zone files, and any associated cryptographic checksum files no more than once per 24 hour period using FTP, or other data transport and access protocols that may be prescribed by ICANN. For every zone file access server, the zone files are in the top-­‐level topMlevel directory called <zone>.zone.gz, with <zone>.zone.gz.md5 and <zone>.zone.gz.sig to verify downloads. If the Registry Operator (or the CZDA Provider) also provides historical data, it will use the naming pattern <zone>-­‐yyyymmdd.zone.gzzone>Myyyymmdd.zone.gz, etc.