Registrars Sample Clauses

The Registrars clause defines the role and responsibilities of registrars within the context of the agreement. Typically, this clause outlines which party or entity is designated as the registrar, their authority to maintain official records, and the procedures for registering relevant information such as ownership, transfers, or changes. For example, in a share agreement, the registrar may be responsible for updating the register of shareholders. The core function of this clause is to ensure there is a clear, authoritative record-keeper, thereby reducing disputes and ensuring accurate documentation of key information.
POPULAR SAMPLE Copied 1 times
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. (b) If Registry Operator (i) becomes an Affiliate or reseller of an ICANN accredited registrar, or (ii) subcontracts the provision of any Registry Services to an ICANN accredited registrar, registrar r...
Registrars. (i) The ordinary hours of full-time work will be 38 hours plus five reasonable additional hours of Training Time (as defined at subclause 3.1(dd)) equalling 43 hours per week or an average of 43 hours per week over a period of up to four weeks. (ii) The arrangement of hours for Registrars is a long-standing industry arrangement that ensures Registrars have access to Training Time.
Registrars. Indicates a file type "REGISTRAR". This file contains information for every Registrar linked with any domain name included in DOMAIN. The following fields shall be stored in the REGISTRAR file:
Registrars. (a) Registry Operator must use only ICANN accredited registrars in registering domain names. Registry Operator must provide non-discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with Registry Operator’sthe 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. Such agreement may be revised by Registry Operator from time to time; provided, however, that any such revisions must be approved in advance by ICANN. (b) If Registry Operator (i) becomes an Affiliate or reseller of an ICANN accredited registrar, or (ii) subcontracts the provision of any Registry Services to an ICANN accredited registrar, registrar reseller or any of their respective Affiliates, then, in either such case of (i) or (ii) above, Registry Operator will give ICANN prompt notice of the contract, transaction or other arrangement that resulted in such affiliation, reseller relationship or subcontract, as applicable, including, if requested by ICANN, copies of any contract relating thereto; provided, that ICANN will not disclose such contracts to any third party other than relevant competition authorities. ICANN reserves the right, but not the obligation, to refer any such contract, transaction or other arrangement to relevant competition authorities in the event that ICANN determines that such contract, transaction or other arrangement might raise competition issues. (c) For the purposes of this Agreement: (i) “Affiliate” means a person or entity that, directly or indirectly, through one or more intermediaries, controls, is controlled by, or is under common control with, the person or entity specified, and (ii) “control” (including the terms “controlled by” and “under common control with”) means the possession, directly or indirectly, of the power to direct or cause the direction of the management or policies of a person or entity, whether through the ownership of securities, as trustee or executor, by serving as an employee or a member of a board of directors or equivalent governing body, by contract, by credit arrangement or otherwise.
Registrars. All domain name registrations in the TLD must be registered through cxDA accredited registrars; provided, that XxXXX 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 10, XxXXX must provide non-discriminatory access to Registry Services to all cxDA accredited registrars that enter into and are in compliance with the registry access agreement for the TLD; provided that XxXXX may establish non-discriminatory criteria for qualification to register names in the TLD that are reasonably related to the proper functioning of the TLD. XxXXX must use a uniform non-discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry Access Agreement”). XxXXX may amend the registry access agreement from time to time; provided, however, that any material revisions thereto must be approved by cxDA before any such revisions become effective and binding on any registrar. XxXXX will provide cxDA and all registrars authorized to register names in the TLD at least fifteen
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. Within sixty (60) calendar days of the RAA Adoption Date, as that term is defined herein below, Registry Operator will submit to ICANN for approval an amended version of the Registry-­‐Registrar Agreement (“Amended RAA”) in accordance with the provisions
Registrars. Michxxx X. Xxxxxxx J. Bxxxxxxx Xxxr Xxterim President and CEO Assistant Administrator Internet Corporation for Assigned National Telecommunications and Names and Numbers Information Administration
Registrars. Indicates a file type "REGISTRAR" The following fields shall be stored in the REGISTRAR file:
Registrars. The previous Registrar Year 1 (HM24) increment was removed. New incremental levels resulted and are expressed below, together with the classification translation for Doctors employed and classified as Registrars as at 31 January 2011 and translated to the new Registrar incremental rate on 1 February 2011: Current Classification (at 31 January 2011) New Classification (at 1 February 2011) Registrar Year 1 Registrar Year 1 Registrar Year 2 Registrar Year 1 Registrar Year 3 Registrar Year 2 Registrar Year 4 Registrar Year 3 Registrar Year 5 Registrar Year 4 Registrar Year 6 Registrar Year 5 Registrar Year 7 Registrar Year 6 Registrars who as at 31 January 2011 were classified as Registrar Year 1 were translated to the new Registrar Year 1 (HM25) incremental rate on 1 February 2011 and then progressed to the new Registrar Year 2 rate on the anniversary of their commencement (or as otherwise provided for in this Agreement). Incremental advancement for former Registrar Years 2, 3, 4, 5 and 6 classified Doctors will continue to apply on their anniversary date of commencement as a Registrar.
Registrars. Indicates a file type "REGISTRAR" The following fields shall be stored in the REGISTRAR file: (1) Registrar Handle; (2) IANA ID for Registrar as per IANA Registrar IDs [8]; and (3) Registrar Name;