Common use of Internationalized Domain Names Clause in Contracts

Internationalized Domain Names. (IDNs) 4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.2. Registry Operator must handle variant IDNs as follows: 4.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 4.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. 4.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. 4.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): 4.3.1. Chinese language 4.3.2. Danish language

Internationalized Domain Names. (IDNs) 4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.2. Registry Operator must handle variant IDNs as follows: 4.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 4.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. 4.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. 4.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): 4.3.1. Chinese language (Simplified) language 4.3.2. Danish Chinese (Traditional) language

Internationalized Domain Names. (IDNs) 4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.2. Registry Operator must handle variant IDNs as follows: 4.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 4.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. 4.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. 4.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): 4.3.1. Chinese (Simplified) language 4.3.2. Danish Chinese (Traditional) language

Internationalized Domain Names. (IDNs) 4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.2. Registry Operator must handle variant IDNs as follows: 4.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 4.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. 4.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. 4.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): 4.3.1. Chinese language 4.3.2. Danish languageRussian language CONSENSUS POLICIES AND TEMPORARY POLICIES SPECIFICATION

Internationalized Domain Names. (IDNs) 4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.2. Registry Operator must handle variant IDNs as follows: 4.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 4.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. 4.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. 4.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): 4.3.1. Chinese language 4.3.2. Danish German language 4.3.3. Japanese language 4.3.4. Korean language 4.3.5. Russian language

Internationalized Domain Names. (IDNs) 4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.2. Registry Operator must handle variant IDNs as follows: 4.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 4.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. 4.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. 4.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): 4.3.1. Chinese Arabic language 4.3.2. Chinese language 4.3.3. Danish language

Internationalized Domain Names. (IDNs) 4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.2. Registry Operator must handle variant IDNs as follows: 4.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 4.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. 4.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. 4.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): 4.3.1. Chinese Arabic language 4.3.2. Danish Chinese language 4.3.3. Greek script 4.3.4. Hebrew language 4.3.5. Japanese language 4.3.6. Korean language 4.3.7. Lao language 4.3.8. Latin script 4.3.9. Russian language

Internationalized Domain Names. (IDNs) 4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.2. Registry Operator must handle variant IDNs as follows: 4.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 4.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. 4.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. 4.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): 4.3.1. Chinese Arabic language 4.3.2. Danish Chinese language 4.3.3. Greek script 4.3.4. Hebrew language 4.3.5. Japanese language 4.3.6. Korean language 4.3.7. Lao language 4.3.8. Latin script 4.3.9. Russian language 4.3.10. Spanish language

Internationalized Domain Names. (IDNs) 4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.2. Registry Operator must handle variant IDNs as follows: 4.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 4.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. 4.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. 4.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): 4.3.1. Chinese language 4.3.2. Danish Russian language

Internationalized Domain Names. (IDNs) 4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.2. Registry Operator must handle variant IDNs as follows: 4.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 4.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. 4.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. 4.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): 4.3.1. Chinese language 4.3.2. Danish German language 4.3.3. Japanese language

Internationalized Domain Names. (IDNs) 4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.2. Registry Operator must handle variant IDNs as follows: 4.2.1. 4.2.1 By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 4.2.2. 4.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. 4.2.3. 4.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. 4.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): 4.3.1. 4.3.1 Arabic language 4.3.2 Chinese language 4.3.2. 4.3.3 Danish language

Internationalized Domain Names. (IDNs) 4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. . 4.2. Registry Operator must handle variant IDNs as follows: 4.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 4.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. 4.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. 4.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): 4.3.1. Chinese language 4.3.2. Danish German language 4.3.3. Portuguese language 4.3.4. Spanish language

Internationalized Domain Names. (IDNs) 4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.2. Registry Operator must handle variant IDNs as follows: 4.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 4.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. 4.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. 4.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): 4.3.1. Chinese Arabic language 4.3.2. Danish Chinese language 4.3.3. Greek script 4.3.4. Hebrew language 4.3.5. Japanese language 4.3.6. Korean language 4.3.7. Lao language 4.3.8. Latin script 4.3.9. Russian language 4.3.10. Thai language

Internationalized Domain Names. (IDNs) 4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.2. Registry Operator must handle variant IDNs as follows: 4.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 4.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. 4.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. 4.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): 4.3.1. Chinese language 4.3.2. Danish German language 4.3.3. Portuguese language

Internationalized Domain Names. (IDNs) 4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.2. Registry Operator must handle variant IDNs as follows: 4.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. 4.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. 4.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. 4.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): 4.3.1. Chinese language 4.3.2. Danish languageJapanese language 4.3.3. Korean language CONSENSUS POLICIES AND TEMPORARY POLICIES SPECIFICATION