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)
AutoNDA by SimpleDocs
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. .NET Registry Agreement Appendix 4 Format and Content for Registry Operator Monthly Reporting Registry Operator shall provide the following monthly reports, each as described in greater detail in this Appendix, 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 <xxxxxxxx-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 July 1, 2023. Registry Operator may at its election use newer versions of the Registry Interfaces Specification after July 1, 2023. 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 1Sample 2See All (7)
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.
Sample 1Sample 2Sample 3
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. APPENDIX 4 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 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. .name Registry Agreement Appendix 4A FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING (Effective as of January 21, 2022) Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-xxxxxx-icann-registry-interfaces, see Appendix 1A, 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 4A, 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 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. xmlns:whoisdb="urn:musedoma:whoisdb" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:host="urn:ietf:params:xml:ns:host-1.0" elementFormDefault="qualified"> <!--Import EPP Element Types--> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" schemaLocation="eppcom-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:epp-1.0" schemaLocation="epp- 1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:contact-1.0" schemaLocation="contact-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:domain-1.0" schemaLocation="domain-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:host-1.0" schemaLocation="host- 1.0.xsd"/> <annotation> <documentation>XML Schema for Whois Data Escrow From MuseDoma </documentation> </annotation> <!--Child Element--> <element name="whois-data" type="whoisdb:whoisDbType"/> <complexType name="whoisDbType"> <choice> <element name="full" type="whoisdb:fullsetType"/> <element name="incremental" type="whoisdb:partialType"/> </choice> <attribute name="tld" type="whoisdb:tldType" use="required"/> <attribute name="date" type="dateTime" use="required"/> </complexType> <simpleType name="tldType"> <restriction base="string"> <enumeration value="museum"/> </restriction> </simpleType> <complexType name="fullsetType"> <sequence minOccurs="1"> <element name="contact" type="ContactType" minOccurs="0" maxOccurs="unbounded"/> <element name="domain" type="DomainType" minOccurs="0" maxOccurs="unbounded"/> <element name="host" type="host:infDataType" minOccurs="0" maxOccurs="unbounded"/> <element name="registrar" type="whoisdb:registrarType" minOccurs="0" maxOccurs="unbounded"/> </sequence> </complexType> <complexType name="partialType"> <sequence minOccurs="1"> <element name="contact" type="ContactType" minOccurs="0" maxOccurs="unbounded"/> <element name="domain" type="DomainType" minOccurs="0" maxOccurs="unbounded"/> <element name="host" type="host:infDataType" minOccurs="0" maxOccurs="unbounded"/> <element name="registrar" type="whoisdb:registrarType" minOccurs="0" maxOccurs="unbounded"/> <element name="del-...
Sample 1

Related to ICANN Access

  • Internet Access Data and information may be made electronically accessible to the Company through Internet access to one or more links provided by the Administrator or a sub-administrator (“Web Link”). All rights in Web Link (including text and “look and feel” attributes) are owned by the sub-administrator. Any commercial use of the content or any other aspect of Web Link requires the written permission of the sub-administrator. Use of the Web Link by the Company will be subject to any terms of use set forth on the web site. Web Link and the information (including text, graphics and functionality) in the Web Link is presented “As Is” and “As Available” without express or implied warranties including, but not limited to, implied warranties of non-infringement, merchantability and fitness for a particular purpose. The sub-administrator neither warrants that the Web Link will be uninterrupted or error free, nor guarantees the accessibility, reliability, performance, timeliness, sequence, or completeness of information provided on the Web Link.

  • Data Access Access to Contract and State Data The Contractor shall provide to the Client Agency access to any data, as defined in Conn. Gen Stat. Sec. 4e-1, concerning the Contract and the Client Agency that are in the possession or control of the Contractor upon demand and shall provide the data to the Client Agency in a format prescribed by the Client Agency and the State Auditors of Public Accounts at no additional cost.

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