Common use of SCHEDULE OF RESERVED NAMES Clause in Contracts

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 1122 contracts

Sources: 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 1031 contracts

Sources: 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 69 contracts

Sources: Registry Agreement, TLD Sponsorship Registry Agreement, Sponsored TLD 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

Sources: 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 14 contracts

Sources: 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

Sources: 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

Sources: 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

Sources: Registry Agreement, Sponsored TLD 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

Sources: Sponsored TLD 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

Sources: 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

Sources: TLD 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-­‐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

Sources: Registry Agreement