Common use of Internationalized Domain Names Clause in Contracts

Internationalized Domain Names. (IDNs) 2.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 2.2. Registry Operator must handle variant IDNs as follows: 2.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 2.2.2. Variant IDNs may be activated when requested by the sponsoring Registrar of the canonical name as described in the IDN Tables and IDN Registration Rules. 2.2.3. Active variant IDNs must be provisioned in the TLD’s DNS zone file as zone cuts using the same NS resource records as the canonical name. 2.3. Registry Operator may offer registration of IDNs in the following languages/scripts (IDN Tables and IDN Registration Rules will be published by the Registry Operator as specified in the ICANN IDN Implementation Guidelines):

Internationalized Domain Names. (IDNs) 2.14.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 2.2. 4.2. Registry Operator must handle variant IDNs as follows: 2.2.14.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 2.2.24.2.2. Variant IDNs may be activated when requested by the sponsoring Registrar of the canonical name as described in the IDN Tables and IDN Registration Rules. 2.2.34.2.3. Active variant IDNs must be provisioned in the TLD’s DNS zone file as zone cuts using the same NS resource records as the canonical name. 2.3. Registry Operator may offer registration of IDNs in the following languages/scripts (IDN Tables and IDN Registration Rules will be published by the Registry Operator as specified in the ICANN IDN Implementation Guidelines):

Internationalized Domain Names. (IDNs) 2.13.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 2.2. 3.2. Registry Operator must handle variant IDNs as follows: 2.2.13.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 2.2.23.2.2. Variant IDNs may be activated when requested by the sponsoring Registrar of the canonical name as described in the IDN Tables and IDN Registration Rules. 2.2.33.2.3. Active variant IDNs must be provisioned in the TLD’s DNS zone file as zone cuts using the same NS resource records as the canonical name. 2.3. Registry Operator may offer registration of IDNs in the following languages/scripts (IDN Tables and IDN Registration Rules will be published by the Registry Operator as specified in the ICANN IDN Implementation Guidelines):

Internationalized Domain Names. (IDNs) 2.14.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 2.24.2. Registry Operator must handle variant IDNs as follows: 2.2.14.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration IDNRegistration Rules) must be blocked from registration. 2.2.24.2.2. Variant IDNs may be activated when requested by the sponsoring Registrar of the canonical thecanonical name as described in the IDN Tables and IDN Registration Rules. 2.2.34.2.3. Active variant IDNs must be provisioned in the TLD’s DNS zone file as zone cuts using the usingthe same NS resource records as the canonical name. 2.34.3. Registry Operator may offer registration of IDNs in the following languages/scripts (IDN Tables and Tablesand IDN Registration Rules will be published by the Registry Operator as specified in the ICANN IDN ICANNIDN Implementation Guidelines):