AT-LARGE GATEWAY

At-Large Website

ALAC

RALOs

At-Large Regional Policy Engagement Program (ARPEP)

At-Large Governance

At-Large Reports

Policy Comments & Advice

Working Groups

ICANN Meetings

At-Large Summit (ATLAS III)

At-Large Review Implementation Plan Development

ALAC and RALO Elections, Selections, and Appointments

At-Large Priority Activities - 2021

Public Comment CloseStatement
Name 

Status

Assigned Working Group

Assignee(s)

Call for
Comments Open		Call for
Comments
Close 		Vote OpenVote CloseDate of SubmissionStaff Contact and EmailStatement Number

05 May 2022

Root Zone Label Generation Rules Version 5 (RZ-LGR-5)

No Statement

CPWG

TBC

pitinan.koo@icann.org, sarmad.hussain@icann.org

Hide the information below, please click here 

CategoryTechnical
RequestersICANN org
ICANN org Contact(s)pitinan.koo@icann.org, sarmad.hussain@icann.org

What We Need Your Input On


Recently the Generation Panels (GPs) for Greek, Latin, Japanese, Korean, and Myanmar scripts have finalized their RZ-LGR proposals after Public Comment. In addition, the Armenian and Cyrillic script GPs have also finalized their proposals, which were deferred from integration into RZ-LGR by the Integration Panel (IP) because they were related to Greek and Latin scripts.

The IP has successfully evaluated the RZ-LGR proposals for these scripts and integrated the proposals, along with other scripts in the current RZ-LGR version, to develop the fifth version (RZ-LGR-5). As per the LGR Procedure, RZ-LGR-5 is being released for Public Comment to gather community feedback for its finalization. Proposals for additional scripts will be integrated in future versions of RZ-LGR.


Proposals For Your Input
Repertoire Tables (PDF, 131.94 KB)
Overview and Summary
XML Versions (normative) (PDF, 143.36 KB)
HTML Versions of the XML Files (non-normative, for easier readability) (PDF, 146.23 KB)


Provide Your Input

Background


Community-based GPs organize and develop proposals for the RZ-LGR for their respective scripts or writing systems as per the LGR Procedure. In doing so, the GPs may need to coordinate efforts with other GPs whenever their repertoires either overlap or are closely related. Script proposals are finalized after Public Comment proceedings and then are submitted to the Integration Panel (IP) for evaluation. The successfully evaluated proposals are integrated into the next version of RZ-LGR. 

In the LGR Procedure it states that the IP creates a set of recommended rules that integrates all the approved proposals from the GPs. When the IP has created such a set, it is posted for Public Comment using the prevailing ICANN procedures. At the end of the Public Comment period, the IP receives and reviews the Public Comment to finalize the LGR. The resulting rules become the RZ-LGR. RZ-LGR-5 covers the following scripts: Arabic, Armenian, Bangla, Chinese (Han), Cyrillic, Devanagari, Ethiopic, Georgian, Greek, Gujarati, Gurmukhi, Hebrew, Japanese (Hiragana, Katakana, and Kanji [Han]), Kannada, Khmer, Korean (Hangul and Hanja [Han]), Lao, Latin, Malayalam, Myanmar, Oriya, Sinhala, Tamil, Telugu, and Thai.


Next Steps


As per the LGR Procedure, RZ-LGR-5 is being released for Public Comment to gather community feedback for its finalization. Proposals for additional scripts will be integrated in future versions of RZ-LGR.


Supporting Information

This additional information from ICANN org provides more context for this Public Comment Proceeding and may help you review the proposals for input and publish a submission.

Supporting Information
Repository of Guidelines and other relevant documents
LGR proposals already received
Guidance on Designing LGRs Supporting Variant Labels
LGR Toolset
Machine readable specification for Label Generation Rules
RZ-LGR-4
Root Zone Label Generation Rules
Maximal Starting Repertoire
Procedure to Develop and Maintain the Label Generation Rules for the Root Zone in Respect of IDNA Labels (LGR Procedure)

FINAL VERSION SUBMITTED (IF RATIFIED)

The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote. 


FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC

The final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.


DRAFT SUBMITTED FOR DISCUSSION

The first draft submitted will be placed here before the call for comments begins. The Draft should be preceded by the name of the person submitting the draft and the date/time. If, during the discussion, the draft is revised, the older version(S) should be left in place and the new version along with a header line identifying the drafter and date/time should be placed above the older version(s), separated by a Horizontal Rule (available + Insert More Content control).

1 Comment

  1. Justine Chew

    By way of background,

    •  A set of label generation rules ("LGR") for a zone governs the set of labels that may be allocated and eventually delegated in a given Zone. The Root Zone LGR (RZ-LGR) provides this determination with respect to IDN labels for the Root.
    • Each script community, which in some cases encompasses many languages, has its own script-specific LGR which is developed by the relevant script Generation Panel ("GP"). The GP process is a bottom-up process with community participation. Examples of such script LGRs are those for Arabic, Bengali, Chinese, Devanagari, etc, 
    • In very simple terms, IDNs are represented by / translated into a series of Unicode code points for them to be machine-readable.
    • Logically, any LGR contains four parts: “the rules that define allowable Unicode code points (the repertoire), any code point variants that can be substituted to form a variant (the variant rules), the disposition of any resulting label (whether it may be allocated, or is automatically blocked), and a set of optional whole-label evaluation rules that determine whether the output of the previous three portions is still an acceptable label in the root zone.” – In other words, by using an LGR, one is able to determine which "strings" are valid, and which variant labels for valid "strings" are allocatable or blocked;  "allocatable" here in means capable of being delegated into the root and "blocked" means not allowed to be delegated into the root.
    • Because the Root Zone caters to many scripts, each of which will have script-specific rules, a Common LGR is needed to manage interaction of labels across scripts (such as blocked cross-script variants). The process of creating this Common LGR is called “integration”. The Procedure defines a two-stage process, in which the community-based GPs propose LGRs specific to a given script, which are then reviewed and integrated by the Integration Panel ("IP"), following a set procedure. 
    • A Common LGR has existed for some time now, with version 1 (i.e. RZ-LGR-1) having been issued back in 2015.
    • The present prevailing Common LGR is version 4 (i.e. RZ-LGR-4) which builds on RZ-LGR-1, RZ-LGR-2 and RZ-LGR-3, each version incorporating more scripts for the IDN Program. A total of 18 scripts is available in RZ-LGR-4.


    Subject matter of this Public Comment Proceeding

    • The Overview and Summary document is essentially the proposed version 5 of the Common LGR (i.e. RZ-LGR-5) and is the result of the IP, having following the set procedures, proposing to incorporate 7 new script LGRs (for Armenian, Cyrillic, Greek, Japanese, Korean, Latin and Myanmar) to the 18 scripts in RZ-LGR-4, making a total of 25 scripts available for the IDN program moving forward.
    • Since, the Latin LGR is one of the 7 new script LGRs being proposed to be incorporate, I also reviewed the report of the Latin LGR 2021 public comment proceedings and the Latin GP's responses to comments from that public comment, since the ALAC and 2 other members of the At-Large community (Bill Jouris and Eduardo Diaz) had submitted comments to the said Latin LGR public comment proceedings. 
    • My conclusion is that:-
      • (a) the Latin GP had considered all the comments it received through the said Latin LGR public comment proceedings, providing responses and explanations and has taken requisite action where it deemed appropriate; and
      • (b) there was nothing that compelled the ALAC to make a comment to this Public Comment Proceeding on the proposed RZ-LGR-5.