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. German language 4.3.2. Danish language 4.3.3. Hungarian language 4.3.4. Icelandic language 4.3.5. Korean language 4.3.6. Lithuanian language 4.3.7. Latvian language 4.3.8. Polish language 4.3.9. Swedish language 4.3.10. Spanish language 4.3.11. Chinese (Simplified) language

Appears in 19 contracts

Samples: Registry Agreement, Registry Agreement, Registry Agreement

AutoNDA by SimpleDocs

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. German 4.3.1 Chinese language 4.3.2. 4.3.2 Danish language 4.3.3. 4.3.3 Finnish language 4.3.4 German language 4.3.5 Hungarian language 4.3.4. 4.3.6 Icelandic language 4.3.5. 4.3.7 Japanese language 4.3.8 Korean language 4.3.6. 4.3.9 Latvian language 4.3.10 Lithuanian language 4.3.7. Latvian 4.3.11 Norwegian language 4.3.8. 4.3.12 Polish language 4.3.9. 4.3.13 Portuguese language 4.3.14 Russian language 4.3.15 Spanish language 4.3.16 Swedish language 4.3.10. Spanish language 4.3.11. Chinese (Simplified) languageCONSENSUS POLICIES AND TEMPORARY POLICIES SPECIFICATION

Appears in 1 contract

Samples: Registry Agreement

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. German Chinese language 4.3.2. Danish language 4.3.3. Hungarian Finish language 4.3.4. Icelandic German language 4.3.5. Korean Hungarian language 4.3.6. Lithuanian Icelandic language 4.3.7. Latvian Japanese language 4.3.8. Polish Korean language 4.3.9. Swedish Latvian language 4.3.10. Spanish Lithuanian language 4.3.11. Chinese (Simplified) languageNorwegian language 4.3.12. Polish language 4.3.13. Portuguese language 4.3.14. Russian language 4.3.15. Spanish language 4.3.16. Swedish language CONSENSUS POLICIES AND TEMPORARY POLICIES SPECIFICATION

Appears in 1 contract

Samples: Registry Agreement

Internationalized Domain Names. (IDNs) 4.13.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.23.2. Registry Operator must handle variant IDNs as follows: 4.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. 4.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. 4.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. 4.33.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.13.3.1. German language 4.3.23.3.2. Danish language 4.3.33.3.3. Hungarian language 4.3.4language 3.3.4. Icelandic language 4.3.53.3.5. Korean language 4.3.63.3.6. Lithuanian language 4.3.7. Latvian language 4.3.8. Polish language 4.3.9. Swedish language 4.3.10. Spanish language 4.3.11. Chinese (Simplified) language

Appears in 1 contract

Samples: Registry Agreement

AutoNDA by SimpleDocs

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. German Belarusian language 4.3.2. Bosnian language 4.3.3. Bulgarian language 4.3.2. Danish language 4.3.3. Hungarian language 4.3.4. Icelandic language 4.3.5. Korean language 4.3.6. Lithuanian language 4.3.7. Latvian language 4.3.8. Polish language 4.3.9. Swedish language 4.3.10. Spanish language 4.3.11. Chinese (Simplified) language 4.3.5. Chinese (Traditional) language 4.3.6. Danish language 4.3.7. German language 4.3.8. Hungarian language 4.3.9. Icelandic language 4.3.10. Korean language 4.3.11. Latvian language 4.3.12. Macedonian language 4.3.13. Montenegrin language 4.3.14. Polish language 4.3.15. Russian language 4.3.16. Serbian language 4.3.17. Spanish language 4.3.18. Swedish language 4.3.19. Ukrainian language Consensus Policies.

Appears in 1 contract

Samples: Registry Agreement

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!