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.
initiated by Registrars Registry Operator will maintain an emergency operations department prepared to handle emergency requests from registrars. In the event that a registrar is unable to conduct EPP transactions with the registry for the TLD because of a fault with the Registry Service and is unable to either contact (through ICANN mandated methods of communication) the Registry Operator, or the Registry Operator is unable or unwilling to address the fault, the registrar may initiate an emergency escalation to the emergency operations department of ICANN. ICANN then may initiate an emergency escalation with the Registry Operator as explained above.
ROLE OF THE PRIMARY AND SECONDARY CONTACTS 5.01 Primary and Secondary Contact(s). The Resident, in executing this Agreement, is required to identify a “Primary Contact” and a “Secondary Contact”. It is strongly recommended that these contacts are parents or legal guardians of the Resident. The Primary Contact serves as the individual that is contacted by the Manager if concerns or problems arise with the Resident, as detailed in section 5.02 below. If the Primary Contact is not available, the Secondary Contact will be contacted.
Rates for Unbranding and Custom Branding via OLNS software for Directory Assistance and for Operator Call Processing are as set forth in Exhibit E of this Attachment. Notwithstanding anything to the contrary in this Agreement, to the extent BellSouth is unable to xxxx Comm South applicable charges currently, BellSouth shall track such charges and will xxxx the same retroactively at such time as a billing process is implemented. In addition to the charges for Unbranding and Custom Branding via OLNS software, Comm South shall continue to pay BellSouth applicable labor and other charges for the use of BellSouth's Directory Assistance and Operator Call Processing platforms as set forth in Exhibit E of this Attachment.
Representative of the Recipient; Addresses Section 7.01. The Minister of Finance of the Recipient is designated as representative of the Recipient for the purposes of Section 11.03 of the General Conditions.
Promotion and Protection of Investments 1. Each Contracting Party shall encourage and create favourable conditions for investors of the other Contracting Party to make investments in its territory and shall admit such investments in accordance with its laws and regulations.
Authorized Affiliates The parties agree that, by executing the DPA, the Customer enters into the DPA on behalf of itself and, as applicable, in the name and on behalf of its Authorized Affiliate(s), thereby establishing a separate DPA between Okta and each such Authorized Affiliate, subject to the provisions of the Agreement. Each Authorized Affiliate agrees to be bound by the obligations under this DPA and, to the extent applicable, the Agreement. An Authorized Affiliate is not and does not become a party to the Agreement, and is only a party to the DPA. All access to and use of the Service by Authorized Affiliate(s) must comply with the terms and conditions of the Agreement and any violation thereof by an Authorized Affiliate shall be deemed a violation by Customer.
Emergency Escalation initiated by Registrars Registry Operator will maintain an emergency operations department prepared to handle emergency requests from registrars. In the event that a registrar is unable to conduct EPP transactions with the registry for the TLD because of a fault with the Registry Service and is unable to either contact (through ICANN mandated methods of communication) the Registry Operator, or the Registry Operator is unable or unwilling to address the fault, the registrar may initiate an emergency escalation to the emergency operations department of ICANN. ICANN then may initiate an emergency escalation with the Registry Operator as explained above.
Contact a. In accordance with section 215.971(2), Florida Statutes, the Division’s Grant Manager shall be responsible for enforcing performance of this Agreement’s terms and conditions and shall serve as the Division’s liaison with the Sub-Recipient. As part of his/her duties, the Grant Manager for the Division shall: payment.
Promotion and Protection of Investment (1) Each Contracting Party shall encourage and create favourable conditions for investors of the other Contracting Party to make investments in its territory, and admit such investments in accordance with its laws and policy.
