July 2015 - Koreangp - lists.icann.org

Characters likely to cause offence
by Dillon, Chris Oct. 18, 2015

Oct. 18, 2015

Dear Yoneya-san, I mentioned in my last email that one of the things I found in J-LGR-2.xlsx was of a more serious nature. I suspect there may be other characters in there that could cause offence, but 卐 5350 could be horribly abused. I realize that the character it represents is used innocently in temples. It is not our responsibility to make decisions about cases such as this and as far as I know, no part of the existing system deals with them. However, having observed long discussion over cases such as .xxx and .sucks, alarm bells do go off and one feels one should draw 5350 to the attention of colleagues. Regards, Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon

8 17

[lgr] FW: ICANN News Alert -- Proposal for Armenian Script Root Zone‬ Label Generation Rules (LGR)
by Sarmad Hussain July 23, 2015

July 23, 2015

Dear All, The Armenian script Generation Panel has completed their proposal for the Root Zone LGR and submitted it for public review. Kindly find the announcement below. You can visit https://www.icann.org/public-comments/proposal-armenian-lgr-2015-07-22-en for details and for submitting your comments. Regards, Sarmad From: ICANN News Alert [mailto:communications@icann.org] Sent: Thursday, July 23, 2015 10:23 AM Subject: ICANN News Alert -- Proposal for Armenian Script Root Zone Label Generation Rules (LGR) <http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2015-07-22-en _____ Proposal for Armenian Script Root Zone Label Generation Rules (LGR) 22 July 2015 Forum Announcement: Comment Period Opens on Date: 22 July 2015 Categories/Tags: Top-Level Domains Purpose (Brief): The Armenian script community has formed the Armenian Generation Panel (GP), which in turn has developed a Proposal for the Armenian Script Root Zone Label Generation Rules (Proposal <https://www.icann.org/en/system/files/files/proposed-armenian-lgr-04jun15-e…> [XML, 8 KB] and Proposal Documentation <https://www.icann.org/en/system/files/files/proposal-armenian-script-root-z…> [PDF, 1.28 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 Armenian GP to make their views known to the Armenian Generation Panel so it can finalize the proposal for submission for integration into the Label Generation Rules for the Root Zone. Public Comment Box Link: https://www.icann.org/public-comments/proposal-armenian-lgr-2015-07-22-en _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

[lgr] FW: Call for Community Experts to Review the IDN Implementation Guidelines
by Fahd Batayneh July 21, 2015

July 21, 2015

FYI… For those interested in the work undertaken by ICANN on Internationalized Domain Names (IDNs), the below might be of interest to you. Fahd Batayneh ICANN Sent: Tuesday, July 21, 2015 12:50 AM Subject: ICANN News Alert -- Call for Community Experts to Review the IDN Implementation Guidelines <http://www.icann.org/> ICANN News Alert https://www.icann.org/news/announcement-2015-07-20-en _____ Call for Community Experts to Review the IDN Implementation Guidelines 20 July 2015 1. Introduction The IDN Implementation Guidelines address the IDN registration policies and practices, designed to minimize the risk of cybersquatting and consumer confusion, and respect the interests of communities using local languages and scripts. These Guidelines are for registry operators to implement IDNs at the second level. Registry operators that offer IDNs under the new gTLDs, resulting from the 2012 application round, are contractually bound to adhere to the Guidelines per Specification 6 of the Registry Agreement. The IDN ccTLDs are encouraged to follow the Guidelines through the IDN ccTLD Fast Track process, but are not contractually obligated to do so. IDN Implementation Guidelines were last updated in 2011. ICANN is now initiating a revision of these guidelines and soliciting the participation of expert community volunteers to form a working group for this purpose. The working group will comprise of expert volunteer members from GNSO, ccNSO, SSAC and ALAC, as per the details below. Interested experts should be endorsed by their respective SOs/ACs and should send their Resumes and Statements of Interest to IDNProgram(a)icann.org by 3 August, 2015. 2. Background Historically, the IDN Implementation Guidelines have been updated when there was a change to relevant protocols or other demand from the community, but not on a regular basis. As there are contractual obligations associated with the Guidelines, updating them may have a significant impact. To date, there have been five versions of the Guidelines, available through the link: https://www.icann.org/resources/pages/implementation-guidelines-2012-02-25-…. The current Version 3.0 <https://www.icann.org/resources/pages/idn-guidelines-2011-09-02-en> was developed through a community based effort and finalized on 2 September 2011. This was endorsed <https://www.icann.org/resources/board-material/resolutions-2011-10-28-en#1.2> by the ICANN Board of Directors on 28 October 2011. Since publication of the latest version of the Guidelines in 2011, there have been changes in the terminology around IDNs and language tables (e.g. see Appendix 2 of Integrated Issues Report <https://www.icann.org/en/system/files/files/idn-vip-integrated-issues-final…> [PDF, 2.15 MB]), as well as a definition of the formal representation <https://tools.ietf.org/html/draft-davies-idntables-08> of the language tables to make them machine readable. Additional analysis and data are also available, including Maximal Starting Repertoire <https://www.icann.org/news/announcement-2-2014-06-20-en> (MSR), informational RFC 6912 and revised IANA IDNA tables <http://www.iana.org/assignments/idna-tables> for Unicode 6.3.0. Finally there have been recommendations for consistency and manageability of variants across different levels in a domain name, e.g. in the User Experience Study <https://www.icann.org/en/system/files/files/active-ux-21mar13-en.pdf> [PDF, 1.38 MB] and related SSAC comments in SAC 60 <https://www.icann.org/en/system/files/files/sac-060-en.pdf> [PDF, 655 KB] report. Based on the experience with implementing IDNs accumulated since 2011, GNSO Council and its members have asked ICANN to update these guidelines. 3. Working Group Expertise and Composition The working group members should have expertise in one or more of the following areas, as relevant for the second level. * DNS and IDNA protocols * IDN language or script tables, including variants and label level rules * IDN policy * IDN implementation * IDN label registration process and registration data * IDN related SSR issues, including string similarity * IDN usability challenges and universal acceptance The working group is anticipated to have expertise in all these areas, with tentatively seven members: GNSO (3), ccNSO (2), SSAC (1) and ALAC (1). The number of GNSO and ccNSO members are based on membership during previous revisions of IDN Implementation Guidelines. SSAC and ALAC members are being added for additional consideration of SSR and usability issues. 4. Tentative Work Plan The working group will determine its own work plan and deliverables, after its formation. The following are tentative steps and the timeline the working group may undertake to complete its work. The working group is expected to hold regular conference calls to undertake this work. * Formation – August 2015 * Identification of relevant issues * Public comment on issues – ICANN 54 * Finalization of issues * Development of initial recommendations against the issues identified * Public comment on Interim draft – ICANN 55 * Finalization of recommendations * Development of complete draft * Public comment on complete draft– ICANN 56 * Publication of updated IDN Implementation Guidelines – August 2016 _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

回复： [ChineseGP] Terminology for CJK coordination committee and IP (v1.0)
by ZhangJoe July 16, 2015

July 16, 2015

One typo in (3) Disposition: whole level evaluation | V whole label evaluation ? ZHANG 发送自我的三星设备 -------- 原始邮件 -------- 发件人： Yoshiro YONEYA <yoshiro.yoneya(a)jprs.co.jp> 日期: 2015-07-16 13:10 (GMT+08:00) 收件人： IntegrationPanel(a)icann.org, ChineseGP(a)icann.org, JapaneseGP(a)icann.org, KoreanGP(a)icann.org, edmon(a)registry.asia, sarmad.hussain(a)icann.org 主题： [ChineseGP] Terminology for CJK coordination committee and IP (v1.0) Dear IP members, CJK GP members, Edmon and Sarmad, Sorry for my delayed submission. Please find attached final version of Terminology text (v1.0). Regards, -- Yoshiro YONEYA <yoshiro.yoneya(a)jprs.co.jp> _______________________________________________ ChineseGP mailing list ChineseGP(a)icann.org https://mm.icann.org/mailman/listinfo/chinesegp

3 3

Two new English topics on JGP web site
by HiroHOTTA July 16, 2015

July 16, 2015

Dear CGP/JGP/KGP colleagues, JGP posted two new English topics on its web site (http://j-gp.jp/en) which are brief reports about the JGP and CJK activities in ICANN BA and APrIGF Macau. URL links to the topics are shown below for your reference. (1) RootLGR integration algorithm was agreed in CJK Coordination Committee held in June 2015 (16 July, 2015) http://j-gp.jp/en/topics/20150716-01 (2) JGP Chair introduced JGP activities and CJK coordination efforts to global community (16 July, 2015) http://j-gp.jp/en/topics/20150716-02 Regards, Hiro Hotta

1 0

Terminology for CJK coordination committee and IP (v1.0)
by Yoshiro YONEYA July 15, 2015

July 15, 2015

Dear IP members, CJK GP members, Edmon and Sarmad, Sorry for my delayed submission. Please find attached final version of Terminology text (v1.0). Regards, -- Yoshiro YONEYA <yoshiro.yoneya(a)jprs.co.jp>

1 0