Hello all, here is a Press release that's interesting for our region, as I believe some of our ALSes were involved with the work. It is great to see that another script now has its Label Generation Rules defined. Kindest regards, Olivier -------- Forwarded Message -------- Subject: ICANN News Alert -- Proposal for Cyrillic Script Root Zone‬ Label Generation Rules Date: Wed, 18 Oct 2017 15:14:46 -0400 From: ICANN News Alert <no-reply@external.icann.org> Reply-To: no-reply@external.icann.org To: ocl@gih.com ICANN News Alert ICANN <http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2017-10-17-en ------------------------------------------------------------------------ Proposal for Cyrillic Script Root Zone‬ Label Generation Rules 17 October 2017 *Open Date:* 17 October 2017 *Close Date:* 6 December 2017 *Originating Organization:* Global Domains Division *Categories/Tags:* Top-Level Domains *Brief Overview:* The Cyrillic script community has formed the Cyrillic script Generation Panel (GP), which in turn has developed a /Proposal for the Cyrillic Script Root Zone Label Generation Rules/ (Proposal <https://www.icann.org/en/system/files/files/proposal-cyrillic-lgr-17oct17-en...> [XML, 19 KB] and Proposal Documentation <https://www.icann.org/en/system/files/files/proposal-cyrillic-lgr-17oct17-en...> [PDF, 1.23 MB]). As per the LGR Procedure <https://www.icann.org/en/system/files/files/lgr-procedure-20mar13-en.pdf> [PDF, 772 KB], this proposal is being posted for public comments to allow those who have not participated in the Cyrillic script GP to make their views known to the GP. Based on the feedback, the Cyrillic script GP will finalize the proposal for submission for integration into the Label Generation Rules for the Root Zone. *Link:* https://www.icann.org/public-comments/cyrillic-lgr-2017-10-17-en This message was sent to *ocl@gih.com* from *no-reply@external.icann.org* ICANN News Alert ICANN 12025 Waterfront Drive Suite 300 Los Angeles, CA 90094-2536 <https://www.icontact.com/signup-trial?utm_medium=poweredby&utm_source=footer...>