ICANN Access Sample Clauses

ICANN Access. Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC.
Sample 1Sample 2Sample 3See All (2k)
ICANN Access. Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC. Registry Operator shall provide the following monthly reports, each as described in greater detail below, for the TLD: (1) the Service Level Agreement Performance Report; (2) the Per-Registrar Transactions Report; and (3) the Registry Functions Activity Report. The Service Level Agreement Performance Reports shall be submitted to ICANN via email to <registry- xxxxxxx@xxxxx.xxx>. The Per-Registrar Transactions Reports and the Registry Functions Activity Reports shall be submitted to ICANN using the API described in draft-xxxxxx-icann- registry-interfaces, see xxxxx://xxxxxxxxxxx.xxxx.xxx/doc/draft-xxxxxx-icann-registry-interfaces (the “Registry Interfaces Specification”). If not already an RFC, Registry Operator will use the most recent draft version of the Registry Interfaces Specification available as of December 1, 2024. Registry Operator may at its election use newer versions of the Registry Interfaces Specification after December 1, 2024. Once the Registry Interfaces Specification is published as an RFC, Registry Operator will implement the RFC version no later than one hundred eighty (180) calendar days after it is published. ICANN may request in the future that the reports be delivered by other means and using other formats. For each of the reports, ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Appendix 4, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Sample 1See All (5)
ICANN Access. Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC. 1. Per-Registrar Transactions Report for Second-Level and Traditional Third-Level Transactions. This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-transactions-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # Field Name Description 01 registrar-name Registrar’s full corporate name as registered with IANA 02 iana-id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) either 9998 or 9999 should be used depending on registration type (as described in Appendix 6), otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-ids 03 total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-adds-1-yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.
Sample 1Sample 2
ICANN Access. Registry Operator shall provide bulk access to the zone files
Sample 1Sample 2
ICANN Access. Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC. Registry Operator's Monthly Reports Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-xxxxxx-icann-registry-interfaces, , see Appendix see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Appendix 4Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Sample 1
ICANN Access. Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC. Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Appendix 1, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Appendix 4, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Sample 1
ICANN Access. Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC. Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-xxxxxx-icann-registry-interfaces, see Appendix 1, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Appendix 4, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Sample 1

Related to ICANN Access

  • Service Access Access to the clinical parts of our Site is restricted to Users. Users of our Site are provided with unique User IDs by the Clinic with which they are associated and must choose a password of their choice to sign on to our Site. Users must provide personal contact information, and you must ensure that your information is kept up to date at all times. User IDs and passwords constitute an electronic signature and will be used by us to authenticate access to our Site. If a User opts to sign onto Xxxxxx.xxx, the User will be able to take advantage of the non- public sections of our Site. If a User opts not to sign onto our Site, their access to our Site will be restricted to the public sections of our Site only. If you are provided with a User ID, password or any other piece of information as part of our security procedures, you must treat such information as confidential, and you must not disclose it to any third party. We have the right to disable any User ID at any time, if in our opinion, you have failed to comply with any of the provisions of this Agreement. You may only use our Site as set out in this Agreement. Any illegal or unauthorized use of our Site shall constitute a violation of this Agreement. You do not have permission to access our Site in any way that violates this Agreement or breaches any applicable law. You agree to keep your and your Patients’ Data accurate, current and complete. You may print off or download extracts of page(s) from our Site for your use in Patient care or insertion into a Patient’s electronic health records only.

Most Referenced Clauses

Most Referenced Definitions