Internationalized Domain Names. (IDNs)
4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP. 4.2. Registry Operator will not offer variant IDNs.
Internationalized Domain Names. (IDNs)
3.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP.
3.2. Registry Operator must handle variant IDNs as follows:
3.2.1. Variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) will be blocked from registration.
3.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):
3.3.1. French Language
3.3.2. 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 language
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. Variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) will be blocked from registration.
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)
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. Variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) will be blocked from registration.
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. Arabic script 4.3.2. Armenian script 4.3.3. Avestan script 4.3.4. Azerbaijani language 4.3.5. Balinese script 4.3.6. Bamum script 4.3.7. Batak script 4.3.8. Belarusian language 4.3.9. Bengali script 4.3.10. Bopomofo script 4.3.11. Brahmi script 4.3.12. Buginese script 4.3.13. Buhid script 4.3.14. Bulgarian language 4.3.15. Canadian Aboriginal script 4.3.16. Carian script 4.3.17. Cham script 4.3.18. Cherokee script 4.3.19. Chinese language 4.3.20. Coptic script 4.3.21. Croatian language 4.3.22. Cuneiform script 4.3.23. Cyrillic script 4.3.24. Devanagari script 4.3.25. Egyptian Hieroglyphs script 4.3.26. Ethiopic script 4.3.27. Georgian script 4.3.28. Glagolitic script 4.3.29. Greek script 4.3.30. Greek, Modern language 4.3.31. Gujarati script 4.3.32. Gurmukhi script 4.3.33. Han script 4.3.34. Hangul script 4.3.35. Hanunoo script 4.3.36. Hebrew script 4.3.37. Hiragana script 4.3.38. Imperial Aramaic script 4.3.39. Inscriptional Pahlavi script 4.3.40. Inscriptional Parthian script 4.3.41. Japanese language 4.3.42. Javanese script 4.3.43. Kaithi script 4.3.44. Kannada script 4.3.45. Katakana script 4.3.46. Kayah Li script 4.3.47. Kharoshthi script 4.3.48. Khmer script 4.3.49. Korean language 4.3.50. Kurdish language 4.3.51. Lao script 4.3.52. Latin script 4.3.53. Lepcha script 4.3.54. Limbu script 4.3.55. Lisu script 4.3.56. Lycian script 4.3.57. Lydian script 4.3.58. Macedonian language 4.3.59. Malayalam script
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
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. Variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) will be blocked from registration.
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. Japanese Language 4.3.2. Spanish Language 4.3.3. French Language 4.3.4. Korean Language 4.3.5. Polish Language 4.3.6. Portuguese Language CONSENSUS POLICIES AND TEMPORARY POLICIES SPECIFICATION
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.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):
2.3.1. Chinese 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. Latin script
