Internationalized Domain Names (IDNs). Registry Operator may offer registration of IDNs at the second and lower levels provided that Registry Operator complies with the following requirements:
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):
Internationalized Domain Names (IDNs). Registry Operator may offer registration of IDNs at the second and lower levels provided that Registry Operator complies with the following requirements:
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). Registry Operator may offer registration of IDNs at the second and lower levels provided that Registry Operator complies with the following requirements:
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). In the case of internationalized domain names, the ASCII-compatible form (A-Label) of the IDN string shall be referenced in the domain name field (e.g. - "xn-11b5bs1di.tld"), not the Unicode label (U-Label).
Internationalized Domain Names (IDNs). Registry Operator may offer registration of IDNs at the second and lower levels provided that Registry Operator complies with the following requirements:
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. Belarusian language 4.3.2. Bosnian language 4.3.3. Bulgarian language 4.3.4. Chinese (Simplified) language
Internationalized Domain Names (IDNs). Registry Operator may offer registration of IDNs at the second and lower levels provided that Registry Operator complies with the following requirements:
5.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP.
5.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration.
5.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.
5.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.
Internationalized Domain Names (IDNs). Indicates a file type " DOMIDN". If an IDN has a corresponding entry in the “DOMAIN” file, the handle for that entry shall be provided in the “Domain Handle” field. If this IDN is a variant of another IDN (the canonical domain name), the handle for the canonical domain name shall be provided in the “Canonical Domain Handle” field. For IDNs that are canonical domain names, the “Canonical Domain Handle” field shall be left blank.
Internationalized Domain Names (IDNs). Indicates a file type " DOMIDN". If an IDN has a corresponding entry in the “DOMAIN” file, the handle for that entry shall be provided in the “Domain Handle” field. If this IDN is a variant of another IDN (the canonical domain name), the handle for the canonical domain name shall be provided in the “Canonical Domain Handle” field. For IDNs that are canonical domain names, the “Canonical Domain Handle” field shall be left blank. The field “Variant Tag” indicates the tag of the IDN variant and shall be any of: “registered”, “reserved” or “blocked”; see section Error! Reference source not found.. For canonical domain names it shall be left blank. The “IDN Table ID” field shall contain the internal ID (see Error! Reference source not found.) of the IDN Table corresponding to the IDN. If the Registrar provided the U-Label for the IDN to the Registry, both U-label and A-label shall be escrowed; if not, only the A-Label shall be escrowed. The following fields shall be stored in the DOMIDN file:
(1) {domainHandle}, Domain Handle;
(2) {canonicalDomainHandle}, Canonical Domain Handle;
(3) {variantTag}, Variant Tag; (4) {idnTableId}, IDN Table ID; (5) {aLabel}, A-Label; and
Internationalized Domain Names (IDNs). Registry Operator may offer registration of IDNs at the second and lower levels provided that Registry Operator complies with the following requirements:
4.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP.
4.2. Registry Operator will not offer variant IDNs.
4.3. 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
Internationalized Domain Names (IDNs). Registry Operator may offer registration of IDNs at the second and lower levels provided that Registry Operator complies with the following requirements:
5.1. Registry Operator must offer Registrars support for handling IDN registrations in EPP.
5.2. Registry Operator must handle variant IDNs as follows:
5.2.1. By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration.
5.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.
5.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.
5.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): 5.3.1. Arabic language 5.3.2. Chinese language 5.3.3. Cyrillic script 5.3.4. French language 5.3.5. Greek script 5.3.6. Hebrew language 5.3.7. Japanese language 5.3.8. Korean language 5.3.9. Lao language 5.3.10. Latin script 5.3.11. Myanmar script 5.3.12. Polish language 5.3.13. Russian language 5.3.14. Spanish language 5.3.15. Swedish language 5.3.16. Thai language CONSENSUS POLICIES AND TEMPORARY POLICIES SPECIFICATION
