Two-­‐character labels Sample Clauses

Two-­‐character labels. All two-­‐character ASCII labels shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Such labels may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator, provided that such two-­‐character label strings may be released to the extent that Registry Operator reaches agreement with the related government and country-­‐code manager of the string as specified in the ISO 3166-­‐1 alpha-­‐2 standard. The Registry Operator may also propose the release of these reservations based on its implementation of measures to avoid confusion with the corresponding country codes, subject to approval by ICANN. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such labels that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
Sample 1Sample 2Sample 3See All (2k)
Two-­‐character labels. All two-character ASCII labels shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Such labels may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator, provided that such two-character label strings may be released to the extent that Registry Operator reaches agreement with the related government and country-code manager of the string as specified in the ISO 3166-1 alpha-2 standard. The Registry Operator may also propose the release of these reservations based on its implementation of measures to avoid confusion with the corresponding country codes, subject to approval by ICANN. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such labels that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
Sample 1Sample 2Sample 3See All (124)
Two-­‐character labels. Notwithstanding Section 2 of Specification 5 of the Agreement, Registry Operator may offer registrations for and activate in the DNS all two-­‐character ASCII labels listed in Attachment 1 to Exhibit A, which is incorporated herein by this reference.
Sample 1Sample 2Sample 3See All (26)
Two-­‐character labels. All two-character labels shall be initially reserved. The reservation of a two- character label string shall be released to the extent that Registry Operator reaches agreement with the government and country-code manager. The Registry Operator may also propose release of these reservations based on its implementation of measures to avoid confusion with the corresponding country codes.
Sample 1Sample 2Sample 3See All (10)
Two-­‐character labels. All two character labels that were previously reserved by Registry Operator pursuant to prior registry agreements between Registry Operator and ICANN may be allocated through ICANN-accredited registrars, subject to the following:
Sample 1Sample 2
Two-­‐character labels. Notwithstanding Section 2 of Specification 5, and subject specifically to the provisions of Section 3.2 of Specification 5, Registry Operator may activate in the DNS all two-­‐character ASCII labels listed in Attachment 1 to Exhibit A, which is incorporated herein by this reference. Despite the terms of Section 3.2 of Specification 5, Registry Operator may not release any such name for registration to another person or entity. In the event any label listed in Attachment 1 to Exhibit A is changed from "Unassigned" to any other status in the ISO 3166-­‐1 alpha-­‐2 standard, Registry Operator must deactivate all related names that are active in the DNS.
Sample 1

Related to Two-­‐character labels

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Deland Actel has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Deland Actel. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Deland Actel (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Deland Actel, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Deland Actel will then have the option of paying the one-time SC rates to place the Loop.

  • Customer Content As part of the Services provided under this Agreement, Customer Data will be stored and processed in the data center region specified in the applicable Ordering Document. Axway shall not access Customer Content except in response to support or technical issues where Customer provides Axway with prior Customer’s written authorization required to access such Customer Content. Axway is not responsible for unauthorized access, alteration, theft or destruction of Customer Content arising from Customer’s own or its authorized users’ actions or omissions in contravention of the Documentation. Customer’s ability to recover any lost data resulting from Axway’s misconduct is limited to restoration by Axway from the most recent back-up.