Public Comment is a vital part of our multistakeholder model. It provides a mechanism for stakeholders to have their opinions and recommendations formally and publicly documented. It is an opportunity for the ICANN community to effect change and improve policies and operations.
Submissions for this Proceeding
Additional Script-Based Reference Label Generation Rules and Related Updates
View this Proceeding
Search Public Comment Submissions For This Proceeding
To search for keywords within Public Comment submissions documents or pages, type in the keyword and press Enter after each selection.
(personal capacity, not wearing my chair of Hebrew RZ-LGR WG hat or any other hat)
Essentially, I believe the Reference LGR for Hebrew script meets its goals and is ready for implementation.
I would further comment that adding the two ASCII charset blocking variants, under the assumption that they are potential homoglyphs to Hebrew script characters ("i" to "VAV", "o" to "SAMECH") does not solve a real problem. That being said, sin...
For a long time we are trying to raise a concerned issue which is containing atomic versions of three decomposed characters in the LGR document.
So here is few specifications in proposal for Bangla, from our side which is strongly recommended that য় YYA (U+09DF), ড় RRA (U+09DC) and ঢ় RRHA (U+09DD) are to be used in Bangla LGR instead of “য”YA (U+09AF)+”়”Nukta (U+09BC), "ড"DDA (U+09A1)+”়” Nukta (U+09BC) and "ঢ"DDHA (U+09A2)+”়” Nukta...
Despite the provisions in the proposal for Bangla, there is a long-standing concern regarding the incorporation of atomic versions of three decomposed characters in the LGR document, namely য় YYA (U+09DF), ড় RRA (U+09DC), and ঢ় RRHA (U+09DD). It is strongly recommended that these characters be used in the Bangla LGR instead of the decomposed characters, "য"YA (U+09AF)+”়”Nukta (U+09BC), "ড"DDA (U+09A1)+”়” Nukta (U+09BC), and "ঢ"DDHA (U+09A...
As a GAC member, a technical change is suggested to incorporate atomic versions of three decomposed characters in the Reference LGR for Bangla Script.
The RySG supports the process that creates the LGRs .
The RySG would like to understand whether ICANN’s design choice is going to adversely affect the existing approved tables or the existing second level registrations.
The Armenian GP thanks the ICANN IDN program and Pitinan and Sarmad personally for the huge job that resulted in the finalization of the Second-Level Reference Label Generation Rules (Reference LGRs) for Seven additional scripts. We are proud to be a part of the world IDN community.
In our opinion, the Reference LGRs meet their goals and are ready for implementation.
We agree with the proposal about new second-level reference LGRs.
Particularly, for the Japanese Language LGR, it is appreciated that standalone LGR with no interference by LGRs for Chinese or Korean language, presuming the case of only Japanese language as the label.
In addition to the above, we propose a small amendment to make the LGR more secure.
We also thank the ICANN IDN team for their continuous effort.
It is my view that it is inappropriate to use the set of variants used for the Root Zone in the RZ-LRGs for the Second Level.
The Root Zone LGRs were developed under the explicit mandate to ignore any possible implications for the Second Level. This matters because proposed gTLD registrations are subject to manual review, to avoid confusion. Whereas Second Level Domain Name registrations are not, and cannot be, manually...
No modifications needed for Gujarati.
I have gone over the Hindi and Devanagari LGRs and found no reportable problems with them.
My impression is that everything works well with the Devnagari script. Thus, as a member of the NBGP, I came out in support of it and made a proposal to move forward.