ICANN testing registrar Sample Clauses

ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. SPECIFICATION 11 PUBLIC INTEREST COMMITMENTS
Sample 1Sample 2Sample 3See All (2k)
AutoNDA by SimpleDocs
ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. Registry Operator shall identify these transactions using Xxxxxxxxx XX 0000. SPECIFICATION 11 PUBLIC INTEREST COMMITMENTS 1. Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website.
Sample 1Sample 2Sample 3See All (8)
ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. SPECIFICATION 11 PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator will operate the registry for the TLD in compliance with allhas not included commitments, statements of intent andor business plans stated in the following sections of Registry Operator’sprovided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments, statements of intent and business plans are hereby incorporated by reference into this Agreement. Registry Operator’s obligations pursuant to this paragraph shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at [url to be inserted when final procedure is adopted]xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination [Registry Operator to insert specific application sections here, if applicable]3. Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the PICDRP. Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance o...
Sample 1Sample 2Sample 3See All (5)

Related to ICANN testing registrar

  • Registrar The term “

  • Transfer Agent and Registrar The Trustees shall have power to employ a transfer agent or transfer agents, and a registrar or registrars, with respect to the Shares. The transfer agent or transfer agents may keep the applicable register and record therein, the original issues and transfers, if any, of the said Shares. Any such transfer agents and/or registrars shall perform the duties usually performed by transfer agents and registrars of certificates of stock in a corporation, as modified by the Trustees.

  • Registrar and Paying Agent The Company shall maintain an office or agency where Notes may be presented for registration of transfer or for exchange ("Registrar") and an office or agency where Notes may be presented for payment ("Paying Agent"). The Registrar shall keep a register of the Notes and of their transfer and exchange. The Company may appoint one or more co-registrars and one or more additional paying agents. The term "

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, 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 Specification 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).

  • Registrar; Transfer Agent The Company will maintain a registrar and transfer agent for the Securities.

  • Registrar Data 1.6.1 Query format: whois “registrar Example Registrar, Inc.”

  • Paying Agent 6 Person..........................................................6

  • Per-­‐Registrar Transactions Report 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) 9999 should be used, 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.

  • Registrars (a) All domain name registrations in the TLD must be registered through an ICANN accredited registrar; provided, that Registry Operator need not use a registrar if it registers names in its own name in order to withhold such names from delegation or use in accordance with Section 2.6. Subject to the requirements of Specification 11, Registry Operator must provide non-­‐discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-­‐registrar agreement for the TLD; provided that Registry Operator may establish non-­‐discriminatory criteria for qualification to register names in the TLD that are reasonably related to the proper functioning of the TLD. Registry Operator must use a uniform non-­‐discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-­‐Registrar Agreement”). Registry Operator may amend the Registry-­‐Registrar Agreement from time to time; provided, however, that any material revisions thereto must be approved by ICANN before any such revisions become effective and binding on any registrar. Registry Operator will provide ICANN and all registrars authorized to register names in the TLD at least fifteen (15) calendar days written notice of any revisions to the Registry-­‐Registrar Agreement before any such revisions become effective and binding on any registrar. During such period, ICANN will determine whether such proposed revisions are immaterial, potentially material or material in nature. If ICANN has not provided Registry Operator with notice of its determination within such fifteen (15) calendar-­‐day period, ICANN shall be deemed to have determined that such proposed revisions are immaterial in nature. If ICANN determines, or is deemed to have determined under this Section 2.9(a), that such revisions are immaterial, then Registry Operator may adopt and implement such revisions. If ICANN determines such revisions are either material or potentially material, ICANN will thereafter follow its procedure regarding review and approval of changes to Registry-­‐Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-­‐amendment-­‐procedure>, and such revisions may not be adopted and implemented until approved by ICANN.

  • Information from Paying Agents The Paying Agents shall make available to the Fiscal Agent and the Registrar such information as may reasonably be required for:

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