Reservations for Registry Operations. 3.1. The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator upon delegation into the root zone at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD (in accordance with the provisions of Exhibit A, the ASCII label NIC must be provisioned in the DNS as a zone cut using NS resource records). None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names 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. Such domains shall be identified by Xxxxxxxxx XX 0000.
Appears in 35 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Reservations for Registry Operations. 3.1. The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator upon delegation into the root zone at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD (in accordance with the provisions of Exhibit A, the ASCII label NIC must be provisioned in the DNS as a zone cut using NS resource records). None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-allocate 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. Such domains shall be identified by Xxxxxxxxx XX 0000.
Appears in 12 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Reservations for Registry Operations. 3.1. The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator upon delegation into the root zone at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD (in accordance with the provisions of Exhibit A, the ASCII label NIC must be provisioned in the DNS as a zone cut using NS resource records). None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names 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. Such domains shall be identified by Xxxxxxxxx XX 0000Registrar ID 9999.
Appears in 11 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Reservations for Registry Operations. 3.1. The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator upon delegation into the root zone at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD (in accordance with the provisions of Exhibit A, the ASCII label NIC must be provisioned in the DNS as a zone cut using NS resource records). None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names 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 7.2(c) of the Agreement. Such domains shall be identified by Xxxxxxxxx XX 0000.
Appears in 6 contracts
Samples: Aero TLD Sponsorship Registry Agreement, Museum Registry Agreement, .Museum Registry Agreement
Reservations for Registry Operations. 3.1. The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator upon delegation into the root zone at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD (in accordance with the provisions of Exhibit A, the ASCII label NIC must be provisioned in the DNS as a zone cut using NS resource records). None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-allocate 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. Such domains shall be identified by Xxxxxxxxx XX 0000Registrar ID 9999.
Appears in 3 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Reservations for Registry Operations. 3.1. 3.1 The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator upon delegation into the root zone at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD (in accordance with the provisions of Exhibit A, the ASCII label NIC must be provisioned in the DNS as a zone cut using NS resource records). None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-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. Such domains shall be identified by Xxxxxxxxx XX 0000Registrar ID 9999.
Appears in 2 contracts
Samples: Registry Agreements, Registry Agreement
Reservations for Registry Operations. 3.1. The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator upon delegation into the root zone at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD (in accordance with the provisions of Exhibit A, the ASCII label NIC must be provisioned in the DNS as a zone cut using NS resource records). None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names 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 7.2(c) of the Agreement. Such domains shall be identified by Xxxxxxxxx XX 0000Registrar ID 9999.
Appears in 1 contract