Dear All, ICANN announced the release of the Recommendations for Managing Internationalized Domain Name (IDN) Variant Top-Level Domains (TLDs)<https://www.icann.org/resources/pages/idn-variant-tld-implementation-2018-07...> as a collection of six documents. https://www.icann.org/news/announcement-2019-02-05-en These recommendations have been developed by the ICANN organization with community feedback received during the Public Comment<https://www.icann.org/public-comments/managing-idn-variant-tlds-2018-07-25-e...> period. A. IDN Variant TLD Implementation – Executive Summary<https://www.icann.org/en/system/files/files/idn-variant-tld-exec-summary-25j...> [PDF, 70 KB] B. IDN Variant TLD Implementation – Motivation, Premises and Framework<https://www.icann.org/en/system/files/files/idn-variant-tld-motivation-premi...> [PDF, 391 KB] C. IDN Variant TLD Implementation – Recommendations and Analysis<https://www.icann.org/en/system/files/files/idn-variant-tld-recommendations-...> [PDF, 382 KB] D. IDN Variant TLD Implementation – Rationale for RZ-LGR<https://www.icann.org/en/system/files/files/idn-variant-tld-rationale-lgr-25...> [PDF, 497 KB] E. IDN Variant TLD Implementation – Risks and their Mitigation<https://www.icann.org/en/system/files/files/idn-variant-tld-risks-mitigation...> [PDF, 230 KB] F. IDN Variant TLD Implementation – Appendices (A: Definitions, B: Use of ROID, C: Limiting Allocated Variant TLDs)<https://www.icann.org/en/system/files/files/idn-variant-tld-appendices-25jan...> [PDF, 530 KB] While the Internet community has often expressed a need for IDN variant TLDs, appropriate technical details and procedures have not been in place to support these. The ICANN Board resolved on 25 September 2010 that "no variants of gTLDs will be delegated ... until appropriate variant management solutions are developed." Subsequent work by the ICANN org and the community on the analysis of issues for Arabic<http://archive.icann.org/en/topics/new-gtlds/arabic-vip-issues-report-07oct1...> [PDF, 1.06 MB], Chinese<http://archive.icann.org/en/topics/new-gtlds/chinese-vip-issues-report-03oct...> [PDF, 2.86 MB], Cyrillic<http://archive.icann.org/en/topics/new-gtlds/cyrillic-vip-issues-report-06oc...> [PDF, 1 MB], Devanagari<http://archive.icann.org/en/topics/new-gtlds/devanagari-vip-issues-report-03...> [PDF, 461 KB], Greek<http://archive.icann.org/en/topics/new-gtlds/greek-vip-issues-report-07oct11...> [PDF, 354 KB], and Latin<http://archive.icann.org/en/topics/new-gtlds/latin-vip-issues-report-07oct11...> [PDF, 425 KB] scripts in 2011, integrated in the Integrated Issues Report (IIR)<https://www.icann.org/en/system/files/files/idn-vip-integrated-issues-final-...> [PDF, 2.14 MB] (2012), identified two challenges: (i) there is no accepted definition for variant TLDs, and (ii) there is no 'variant management' mechanism for TLDs. For the first issue, the Root Zone Label Generation Rules (RZ-LGR) Procedure<https://www.icann.org/en/system/files/files/draft-lgr-procedure-20mar13-en.p...> [PDF, 1.39 MB] was developed with the support of the community and adopted by the ICANN Board on 11 April 2013 for implementation. The Procedure has been implemented and RZ-LGR<https://www.icann.org/resources/pages/root-zone-lgr-2015-06-21-en> has been developed for six scripts, while other scripts are being added as their proposals<https://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en> are finalized by the relevant script communities<https://www.icann.org/resources/pages/generation-panel-2015-06-21-en>. This enables a transparent and predictable mechanism for identification of variant labels going forward For the second issue, the ICANN org has undertaken a detailed examination to develop a set of recommendations on variant management mechanisms for TLDs, which have been finalized based on the community input. The recommendations, in summary, include the following: 1. RZ-LGR must be the only source for valid TLDs and their variant labels. 2. IDN variant TLDs {t1, t1v1, …} must be allocated to same entity. 3. Same label under IDN variant TLDs s1.{t1, t1v1, …} must be registered to the same entity. 4. Second-level variant labels under IDN variant TLDs {s1, s1v1, …}.{t1, t1v1, …} must be registered to the same entity. 5. Second-level IDN tables offered under IDN variant TLDs must be harmonized. 6. IDN variant label allocatable or activated under IDN variant TLDs may not necessarily be the same. 7. The registry service providers must be the same for IDN variant TLDs. 8. Existing policies and associated procedures for TLDs must be updated to accommodate the recommendations for IDN variant TLDs. 9. All remaining existing TLD policies must apply to IDN variant TLDs, unless otherwise identified. These recommendations and associated analysis in the six documents will be presented for further consideration to the ICANN Board, anticipated in March 2019. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken@icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org