SCHEDULE OF RESERVED NAMES. Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve the following labels from initial (i.e., other than renewal) registration within the TLD. If using self-‐allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable.
Appears in 1088 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
SCHEDULE OF RESERVED NAMES. Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve the following labels from initial (i.e., other than renewal) registration within the TLD. If using self-‐allocationself-‐ allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable.
Appears in 989 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
SCHEDULE OF RESERVED NAMES. Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve the following labels from initial (i.e., other than renewal) registration within the TLD. If using self-‐allocationself- allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable.
Appears in 59 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
SCHEDULE OF RESERVED NAMES. Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve the following labels from initial (i.e., other than renewal) registration within the TLD. If using self-‐allocationself-allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable.
Appears in 44 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
SCHEDULE OF RESERVED NAMES. Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve the following labels from initial (i.e., other than renewal) registration within the TLD. If using self-‐allocationself‐allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable.
Appears in 13 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
SCHEDULE OF RESERVED NAMES. Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve the following labels from initial (i.e., other than renewal) registration within the TLD. If using self-‐allocationself‐ allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable.
Appears in 4 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
SCHEDULE OF RESERVED NAMES. Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve the following labels from initial (i.e., other than renewal) registration within the TLD. If using self-‐allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable.:
Appears in 2 contracts
Samples: Registry Agreement, Registry Agreement
SCHEDULE OF RESERVED NAMES. Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve the following labels from initial (i.e., other than renewal) registration within the TLD. If using self-‐allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable.:
Appears in 2 contracts
Samples: Sponsored TLD Registry Agreement, Registry Agreement
SCHEDULE OF RESERVED NAMES. Except to the extent that ICANN otherwise expressly authorizes in writing, and theand subject to the terms and conditions of this Specification, Registry Operator shall reserve names formed with the following labels from initial (i.e., other than renewal) registration within the TLD:. If using self-‐allocationself-allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable.
Appears in 1 contract
SCHEDULE OF RESERVED NAMES. Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve the following labels from initial (i.e., other than renewal) registration within the TLD. If using self-‐allocationselfM allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable.
Appears in 1 contract
Samples: Registry Agreement
SCHEDULE OF RESERVED NAMES. Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve the following labels from initial (i.e., other than renewal) registration within the TLD. If using self-‐allocationselfLallocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable.
Appears in 1 contract
Samples: Registry Agreement
SCHEDULE OF RESERVED NAMES. Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve the following labels from initial (i.e., other than renewal) registration within the TLD. If using self-‐allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable.. registration within the TLD:
Appears in 1 contract
Samples: TLD Registry Agreement