- Koreangp - lists.icann.org

[lgr] Fwd: [Ext] Fwd: ICANN News Alert -- Proposals for Kannada, Oriya and Telugu Scripts' Root Zone Label Generation Rules
by Pitinan Kooarmornpatana Aug. 8, 2018

Aug. 8, 2018

Dear All, We are pleased to announce that the Neo-Brahmi GP has finalized and published Root Zone LGR proposals for three scripts: Kannada, Telugu and Oriya. See below for further details (see the complete list of proposals published here<https://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en>). We look forward to the comments and feedback from the community. Regards, Sarmad [ICANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> News Alert https://www.icann.org/news/announcement-2018-08-08-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ Proposals for Kannada, Oriya and Telugu Scripts' Root Zone Label Generation Rules 8 August 2018 Open Date: 8 August 2018 Close Date: 20 September 2018 Originating Organization: Global Domains Division Categories/Tags: Top-Level Domains Brief Overview: The Neo-Brahmi Script Generation Panel (NBGP) was formed by nine communities that use scripts derived from the Brahmi script. NBGP is developing Root Zone Label Generation Rules (LGR) for Bengali, Devanagari, Gujarati, Gurmukhi, Kannada, Malayalam, Oriya, Tamil and Telugu scripts. The GP is publishing the proposals for the LGRs of these nine scripts in three sets, releasing proposals for the scripts which share cross-script variant code points together to the extent possible. The first set is already undergoing public comment and the second set, being released now, includes the following proposals: (1) Proposal for the Kannada Script Label Generation Rules for the Root Zone, (2) Proposal for the Oriya Script Label Generation Rules for the Root Zone, and (3) Proposal for the Telugu Script Label Generation Rules for the Root Zone. As per the LGR Procedure [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>, these proposals are being posted for public comments to allow those who have not participated in the NBGP to make their views known. Based on the feedback, the NBGP will finalize each proposal for its evaluation and integration into the Label Generation Rules for the Root Zone. Link: https://www.icann.org/public-comments/kannada-oriya-telugu-lgr-2018-08-08-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] FW: ICANN News Alert -- Study on Technical Use of Root Zone Label Generation Rules
by Sarmad Hussain Aug. 2, 2018

Aug. 2, 2018

Dear All, The scope of an ongoing study on technical use of RZ-LGR has been published for public comment. We look forward to your input on the proposed scope. See below for further details. Regards, Sarmad News Alert https://www.icann.org/news/announcement-2018-08-02-en [icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> _____ Study on Technical Use of Root Zone Label Generation Rules 2 August 2018 Open Date: 2 August 2018 Close Date: 11 September 2018 Originating Organization: Global Domains Division Categories/Tags: Top-Level Domains Brief Overview: Second version of the Root Zone Label Generation Rules (RZ-LGR-2) was released in August 2017, integrating six script proposals, as other LGR script proposals are being finalized. The Root Zone Label Generation Rules Study Group (RZ-LGR-SG) has been constituted to study and make recommendations for the technical use of RZ-LGR in a harmonized way across Internationalized Domain Name (IDN) Top-Level Domains (TLDs). RZ-LGR-SG has identified its scope of work [icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 128 KB], which is being shared with the community. The SG seeks feedback from the community on whether the questions identified are all relevant for this study and whether there are any other issues it should also consider. RZ-LGR-SG will take into account the community input to finalize the scope of its work, develop the related recommendations and share these recommendations with the community before finalization. Link: https://www.icann.org/public-comments/technical-rz-lgr-2018-08-02-en [icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] FW: ICANN News Alert -- Proposals for Devanagari, Gurmukhi, and Gujarati Scripts' Root Zone‬ Label Generation Rules
by Sarmad Hussain July 27, 2018

July 27, 2018

Dear All, We are pleased to announce that the Neo-Brahmi GP has finalized and published Root Zone LGR proposals for three scripts: Devanagari, Gurmukhi and Gujarati. See below for further details (see the complete list of proposals published here <https://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en> ). We look forward to the comments and feedback from the community. Regards, Sarmad News Alert https://www.icann.org/news/announcement-2018-07-27-en [icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> _____ Proposals for Devanagari, Gurmukhi, and Gujarati Scripts' Root Zone Label Generation Rules 27 July 2018 Open Date: 27 July 2018 Close Date: 10 September 2018 Originating Organization: Global Domains Division Categories/Tags: Top-Level Domains Brief Overview: The Neo-Brahmi Script Generation Panel (NBGP) was formed by nine communities that use scripts derived from the Brahmi script. NBGP is developing Root Zone Label Generation Rules (LGR) for Bengali, Devanagari, Gujarati, Gurmukhi, Kannada, Malayalam, Oriya, Tamil and Telugu scripts. The GP intends to publish the proposals for the LGRs of these nine scripts in three sets, releasing proposals for the scripts which share cross-script variant code points together to the extent possible. The first set includes the following: (1) Proposal for the Devanagari Script Label Generation Rules for the Root Zone, (2) Proposal for the Gurmukhi Script Label Generation Rules for the Root Zone, and (3) Proposal for the Gujarati Script Label Generation Rules for the Root Zone. As per the LGR Procedure [icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> , these proposals are being posted for public comments to allow those who have not participated in the NBGP to make their views known. Based on the feedback, the NBGP will finalize each proposal for its evaluation and integration into the Label Generation Rules for the Root Zone. Link: https://www.icann.org/public-comments/devanagari-gurmukhi-gujarati-scripts-… [icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] FW: ICANN News Alert -- Recommendations for Managing IDN Variant Top-Level Domains
by Sarmad Hussain July 25, 2018

July 25, 2018

Dear All, Recommendations for Managing IDN Variant Top-Level Domains <https://www.icann.org/public-comments/managing-idn-variant-tlds-2018-07-25-…> have been announced for public comment. We look forward to your input. Regards, Sarmad News Alert https://www.icann.org/news/announcement-2018-07-25-en [icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> _____ Recommendations for Managing IDN Variant Top-Level Domains 25 July 2018 Open Date: 25 July 2018 Close Date: 3 September 2018 Originating Organization: Global Domains Division Categories/Tags: Top-Level Domains Brief Overview: Recommendations for managing Internationalized Domain Name (IDN) variant labels for top level domains (TLDs) have been developed by ICANN organization. The relevant materials along with these proposed recommendations are being published to seek community feedback. The community has identified a need for IDN variant TLDs; however, 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 ICANN organization and the community led to the identification of two issues: (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 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 has been developed for six scripts, and other scripts are being added as their proposals are finalized by the relevant script communities. For the second issue, ICANN organization has undertaken a detailed examination to propose a set of recommendations for variant management mechanisms for TLDs, which will be finalized based on the community input. The finalized recommendations will be presented to the ICANN Board, anticipated in March 2019. At that time, the ICANN Board will be requested to consider these recommendations to allow for implementing IDN variant TLDs. Link: https://www.icann.org/public-comments/managing-idn-variant-tlds-2018-07-25-… [icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] FW: CANN News Alert -- ICANN Board to Hold Four Public Sessions - Including One on IDN Variant TLD Implementation
by Sarmad Hussain June 11, 2018

June 11, 2018

Dear Generation Panel Members, As per the news below, ICANN Board will hold a public session on IDN Variant TLD Implementation Recommendations on 22 June 2018. As a background, the work following the board resolution in 2010 (see under IDN Variant TLD Implementation here <https://www.icann.org/resources/pages/idn-relevant-board-resolutions-2017-1…> ) led to the development of the Integrated Issues Report <https://www.icann.org/resources/pages/idn-relevant-board-resolutions-2017-1…> (IIR) by the community and ICANN org. IIR identified two gaps in implementing IDN variant TLDs: (i) There was no definition of IDN Variant TLDs (ii) There was no management mechanism for IDN Variant TLDs To address the first item, LGR Procedure was developed and was adopted by the ICANN Board in 2013, which has led to the development of RZ-LGR. Now, through the RZ-LGR, there is a clear definition of IDN Variant TLDs. With its availability, the RZ-LGR Study group has been formed to address the technical aspects of using the RZ-LGR for this purpose. However, RZ-LGR only addresses part of the issue, as identified by IIR. To address the second item, ICANN org has also been looking into the challenges of variant management mechanism to implement IDN Variant TLDs based on current IDN (g and cc) TLD procedures. This particular presentation to the ICANN Board focuses on that part of the work. Naturally, defining variant labels is a pre-requisite of managing them. So our focus has remained the RZ-LGR definition. With the RZ-LGR now available and remaining script communities well underway to finalize their LGR proposals, it is a good time to start the conversation about their management mechanism. Regards, Sarmad <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> [icann.org] News Alert <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> https://www.icann.org/news/announcement-2018-06-07-en [icann.org] _____ ICANN Board to Hold Four Public Sessions and Board Meeting During Panama Workshop 7 June 2018 LOS ANGELES – 7 June 2018 – The ICANN Board will be holding four public sessions and a public Board meeting during its upcoming workshop in Panama City, Panama, which will be taking place from 22-24 June 2018, ahead of ICANN62. The agenda of the sessions is provided below. Date Time (UTC) Session 22 June 18:15 – 19:15 IDN Variant TLD Implementation Recommendations 23 June 14:00 – 15:00 Public Board Meeting 23 June 18:00 – 18:15 Board FY18 Priorities – Status of Deliverables 23 June 18:15 – 18:45 Long-Term and Short-Term Options for Streamlining the Reviews 23 June 22:00 – 23:00 Internet Governance Strategic Discussion Progress The sessions will be in English only. The format for each will be a listen-only session via Adobe Connect. Adobe Connect Link: https://participate.icann.org/opencommunity/ Participant Code: 5542211258 Additional access numbers: https://www.myrcplus.com/cnums.asp?bwebid=8369444 <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.myrcplus.com_cnums…> &ppc=5542211258&num=1-605-475-5606 [myrcplus.com] For more information about the Panama workshop and other upcoming ICANN Board meetings, please go to https://www.icann.org/resources/pages/2018-board-meetings [icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> . About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

Fw: Possible OBF question -- I18n
by Yoshiro YONEYA June 6, 2018

June 6, 2018

FYI Threads can be obtained from IETF mail archive. <https://www.ietf.org/mail-archive/web/ietf/current/msg108021.html> Begin forwarded message: Date: Wed, 30 May 2018 15:55:24 -0400 From: John C Klensin <john-ietf(a)jck.com> To: ietf(a)ietf.org Subject: Possible OBF question -- I18n Hi. I want to share a question and possible an idea and see if it gets any traction before Thursday's BOF application cutoff. Many people seem to think that what has come to be called "internationalization" ("i18n") of the Internet is important, both to serving existing users for whom English may not be a comfortable language or Lain script a comfortable writing system and to making the Internet accessible to much larger populations ("the next billion"). Some of the issues are related to identifiers, with examples including IDNA, IRIs, PRECIS, and the recent work on non-ASCII identifiers in certificates. Others are more connected to actual protocol design, such as the SMTPUTF8 work in the EAI WG. Still others are related to content, language selection ins various applications, and so on. I think there is general recognition that the problems are difficult. Human languages have evolved, and evolved differently, over more centuries than anyone can count, making extrapolations from one language or writing system to another difficult and error-prone. Conventions that evolved to permit use of typewriters (with mechanically-limited numbers of keys) with writing systems with more than that many characters haunt contemporary comparison and matching issues. Even changes as recent as the divergence of American from British English, French as spoken and written in France from French as used in Quebec, and efforts to simplify the representations of a few thousand commonly-used Chinese characters can pose serious problems for computer system designers and implementers who just want do do something quick, obvious, and straightforward but still correct (or at least acceptable enough to not be culturally insulting). At the same time, the IETF has a problem with expertise, real energy, and support for internationalization work. The last WGs directly focused on the issues have essentially run out of steam, with a very small number of participants able and willing to do late-stage analysis and reviews. Other WGs whose work has involved important I18n issues have recognized that they don't have the needed expertise and had some trouble recruiting it or, when we are less lucky, have not recognized the problem. The latter poses a special challenge because, if the work is specialized, there may be little or no review of the I18n impact during IETF Last Call unless someone happens to notice, a sitaution that might pose a real threat to interoperability when the protocols are actually used. In addition, pressing problems do show up about which decisions need to be made if the IETF is going to fulfill its responsibilities in this area and, because of concerns about reviews (and probably more), it seems impossible to process work that is necessarily standards track without a WG and impossible to create a WG given the absence of manifestations of broad interest and knowledge and the history, mentioned above, of WGs running out of steam. It also probably doesn't help that several of the acknowledged experts and critically interested parties have little or no reliable support for attending IETF meetings so, if a group is to be judged by counting the number of people in the room for a discussion, it is easy to conclude that there is less interest than might actually exist. Some of us have been waiting for the IESG and/or IAB to sort the situation out and tell us what to do. That hasn't happened, possibly because flying pigs are in short supply but more likely because they understand the problems and don't have any solutions either. The IAB's concluding almost a year ago that its I18n Program was unsustainable and closing it was probably a benchmark, especially when one notices that no substitute has emerged, but, even had that not happened, an IAB Program can't process standards track documents under our current rules (or any rules I see anyone rushing to propose). So I'm wondering whether there is sufficient interest to hold a BOF to discuss how to deal with this situation. I don't want to get into the many substantive issues that have been hanging around, but rather to address the question of how, if there were drafts, what the review and approval process should be in an IETF where there will probably never be a huge number of experts around with time on their hands. Could we devise something Directorate-like or even Area-like? Could that group be counted on for substantive/ technical reviews to the extent to which, even if no other reviews addressed the substantive subject matter and no one on the IESG had special expertise, they could be approved anyway? Should we be reaching out to other groups with general internationalization expertise (not just, or a focus on, character coding) to see if we would work out joint review efforts or even if we could comfortably export the topic? Or have we actually come to the conclusion that the IETF had best stop claiming any responsibility or authority in this area and that we are willing to let whatever emerges fill the vacuum? If this sounds useful and you have anything to contribute, especially procedural or "where do we find the experts" advice, please speak up within the next 24-48 hours. IMO, if we should give give up, I think it would be better to do that as the result of a formal discussion than as a decision of a handful of people meeting more or less in private and without an explicit opportunity for community input. john p.s. before someone asks, I'm thinking actual BOF because don't think there is any point in this unless it has someone from the IESG willing to take at least some responsibility, produces minutes, has meetecho coverage, etc. I don't think dancing around with Bar BOFs, non-bar Bar BOFs, informal meetings, etc., meet those criteria. I don't thing a presentation in an area meeting or two would do it either -- we've tried that with no success and, more important, I'm seeing an increasing number of WGs being created with i18n implications or necessary involvement that are not in the ART area.

2 4

Re: [Koreangp] [lgr] [Ext] BENGALI LGR updated
by Pitinan Kooarmornpatana May 3, 2018

May 3, 2018

Thank you, Dr. Atiur. We will update the XML accordingly and send back to you for your finalization. Regards, Pitinan From: atiurk <atiurk(a)cdac.in> Reply-To: atiurk <atiurk(a)cdac.in> Date: Friday, May 4, 2018 at 14:50 To: "LGR(a)icann.org" <LGR(a)icann.org>, "unciil(a)yahoo.com" <unciil(a)yahoo.com>, Ajay Data <ajay(a)data.in>, Sarmad Hussain <sarmad.hussain(a)icann.org>, Pitinan Kooarmornpatana <pitinan.koo(a)icann.org> Subject: [Ext] BENGALI LGR updated Dear All, Please find the Bengali (Bangla) LGR Document revised post- F2F Meeting in Delhi for your perusal and for the IP also. The google link is below: https://docs.google.com/document/d/1kCB9xuvAhRKtX3P9WfDYXUC_pQPPM4kSaWMFxyl… regards Dr. Atiur Rahman Khan Principal Technical Officer (PTO) NLP Research Lab, GIST Group 5th Floor, CDAC Innovation Park / 5 वीं मंजिल, सी-डैक इनोवैशन पार्क Panchavati, Pashan, Pune / पंचवटी, पाषाण, पुणे Pin: 411 008 / पिन: 411 008 ------------------------------------------------------------------------------------------------------------------------------- [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------------------------- _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] FW: ICANN News Alert -- Maximal Starting Repertoire Version 3 (MSR-3) for the Development of Label Generation Rules for the Root Zone
by Sarmad Hussain March 29, 2018

March 29, 2018

Dear All, We are pleased to inform you that MSR-3 has been released. Please see below for details. Regards, Sarmad News Alert https://www.icann.org/news/announcement-2-2018-03-29-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ Maximal Starting Repertoire Version 3 (MSR-3) for the Development of Label Generation Rules for the Root Zone 29 March 2018 LOS ANGELES – 29 March 2018 - The Internet Corporation for Assigned Names and Numbers (lCANN) today announced the release of the third version of the Maximal Starting Repertoire (MSR-3[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>). This version is upwardly compatible with MSR-2 and adds three code points each to the repertoires of Han and Latin scripts. Under the Procedure to Develop and Maintain Label Generation Rules for the Root Zone with Respect to IDN Labels[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_resou…> [PDF, 72 KB] , the MSR is the starting point for the work by community based Generation Panels[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> which are developing the proposals for relevant scripts for the Root Zone Label Generation Rules (RZ-LGR[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>). The contents of MSR-3 and the detailed rationale behind its development are described in MSR-3-Overview and Rationale[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 242 KB]. The RZ-LGR is a mechanism for determining valid IDN top-level domain labels and their variant labels. MSR-3 covers the following 28 scripts: Arabic, Armenian, Bengali, Cyrillic, Devanagari, Ethiopic, Georgian, Greek, Gujarati, Gurmukhi, Han, Hangul, Hebrew, Hiragana, Kannada, Katakana, Khmer, Lao, Latin, Malayalam, Myanmar, Oriya, Sinhala, Tamil, Telugu, Thaana, Tibetan, and Thai. For these scripts, MSR-3 contains 33,496 code points short-listed from 97,973 PVALID/CONTEXT code points of Unicode version 6.3. In addition to selecting their repertoire from within the MSR for developing the RZ-LGR proposals, Generation Panels will also evaluate whether any such code points are variant code points and if any rules are needed to further constrain the labels generated using these code points. The resulting RZ-LGR proposals by the Generation Panels will be released for public comment before they are reviewed by the Integration Panel for integration into the RZ-LGR. MSR-3 defers code points that are already encoded in later releases of Unicode. In addition, the Integration Panel monitors any scripts not included in the MSR for indications change in the MSR is warranted. Until such a change of the MSR, MSR-3 will be the foundation for any RZ-LGR versions developed. All future versions of the MSR and all versions of the RZ-LGR must retain full backwards compatibility. About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] ICANN61 IDN Open Sessions on WED 14 Mar
by Pitinan Kooarmornpatana March 13, 2018

March 13, 2018

Dear all, This is a gentle reminder for the IDN Open Sessions tomorrow (Wed, 14 Mar) * IDN RZ-LGR Workshop 15:15 - 16:45, Wed, Mar 14, 2018 209-A https://61.schedule.icann.org/meetings/647605 * IDN Program Update 17:00 - 18:15, Wed, Mar 14, 2018 209-A https://61.schedule.icann.org/meetings/647604 Regards, Pitinan _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[FYI] KGP status update @ ICANN 61, SJU
by KIM Kyongsok March 11, 2018

March 11, 2018

-- 김 경석 KIM, Kyongsok

1 0