- ChineseGP - lists.icann.org

reference to SAC 60 during coordination call between KoreanGP and ChineseGP
by Sarmad Hussain Jan. 21, 2015

Jan. 21, 2015

Dear Prof. Kim, All, Here is the relevant text from SSAC's SAC 60 report (https://www.icann.org/en/system/files/files/sac-060-en.pdf) as mentioned during the call today: Recommendation 7: Should ICANN decide to implement safeguards it should seek to distinguish the following two types of failure modes when a user expects a variant to work but it is not implemented: . Denial of service: the user attempts to visit http://example.Y, reading it as being the same Uniform Resource Identifier (URI) as the http://example.X that, for example, he or she saw in an advertisement, but the connection does not work (lookup fails) because Y is either blocked, withheld, or X has no variant at all, and example.Y is not registered. . Misconnection: the user attempts to visit http://example.Y, reading it as being the same URI as the http://example.X that, for example, he or she saw in an advertisement, but arrives at a site controlled by a registrant different to that of example.X. The second case is much more dangerous than the first one. In the first case, the user is frustrated and may conclude that "the Internet does not work," but no serious harm has arisen. The second case is problematic even if this effect is not the result of malicious work on the part of Y's operator or example.Y registrant. Misconnections to a perfectly legitimate site operating at example.Y present issues of possible credential compromise or other accidental disclosure of information in addition to user confusion and frustration. Regards, Sarmad

2 1

CGP meeting
by Sarmad Hussain Jan. 20, 2015

Jan. 20, 2015

As requested by the chair, the CGP meeting will be held on Wednesday 21 Jan. 4pm Beijing time (see http://www.timeanddate.com/worldclock/converter.html for other time zones). How to connect: Link to Adobe Connect: https://icann.adobeconnect.com/r72wznoryti/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. If you are Unable to log into Adobe Connect and can only join via phone: List of International Dial In Numbers: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=4054049491&num=1-719-… Participant Passcode: 4054049491

1 0

proposal to eliminate the divergence between us
by Wang Wei Jan. 19, 2015

Jan. 19, 2015

Dear Yoneya San and Hotta San Please kindly accept my belated but best wishes for the Christmas and new year. Recently, we carried out the following works and I outlined them here for your comments: For any Hanzi in CGP repertoire, it belong to a variant mapping set (minimum set size is 1 which means there is no variant for the code point) under the current rules borrowed from CDNC; and for any Kanji code point in JGP repertoire, it may also belong to some variant mapping set (we acknowledge that there is no variant in JPRS practice so far, but we assume that there will be a kind of variant mapping definition in JGP repertoire). All the variant mapping sets can be divided into FIVE scenarios: 1) the variant mapping set in JPRS �� variant mapping set in CDNC In CGP �� 611B (0);��(86),��(886);��(0),��(0); �� 7231 (0);��(86),��(886);��(0),��(0); In JGP ��611B(2,3);611B(2,3); 2) the variant mapping set in CDNC �� the variant mapping set in JPRS In CGP: ��520A (0);��520A(86),��520A(886);��(0),�X(0); �X520B (0);��520A(86),��520A(886);��(0),�X(0); In JGP: �� 520A(2,3);520A(2,3); �X 520B(2,3);520B(2,3); �� 681E(2,3);681E(2,3); *: this example is ONLY an assumption 3) the variant mapping set in CDNC = the variant mapping set in JPRS In CGP һ4E00 (0); һ4E00(86),һ4E00(886); һ(0),��(0),Ҽ(0),�o(0); ��58F1 (0); Ҽ58F9(86),Ҽ58F9(886); һ(0),��(0),Ҽ(0),�o(0); Ҽ58F9 (0); Ҽ58F9(86),Ҽ58F9(886); һ(0),��(0),Ҽ(0),�o(0); �o5F0C (0); һ4E00(86),һ4E00(886); һ(0),��(0),Ҽ(0),�o(0); In JGP: һ 4E00(2,3);4E00(2,3); �� 58F1(2,3);58F1(2,3); Ҽ 58F9(2,3);58F9(2,3); �o 5F0C(2,3);5F0C(2,3); *: this example is ONLY an assumption 4) the variant mapping set in CDNC �� the variant mapping set in JPRS = 0 The code point UNIQUELY exists in JGP table �y8FBB(2,3);8FBB(2,3); 5) the variant mapping set in CDNC �� the variant mapping set in JPRS �� 0 and the variant mapping set in CDNC �� the variant mapping set in JPRS No specified example so far \ In the past, we discussed the variants problem for many times, but mainly based on the two types: allocatable and blocked. However, we think another type ("out-of- repertoire") in the XML draft, may help the conflicted issue between JGP and CGP, which was recommended by Asmus' mail. The basic principle is "any variant label with a code point out-of-repertoire is invalid". We think this ��out-of-repertoire�� type and consequent ��invalid�� action will tremendously decrease the complexity of variant mapping coordination between us. For scenario 1: In CGP �� 611B (0);��(86),��(886);��(0),��(0); �� 7231 (0);��(86),��(886);��(0),��(0); In JGP �� 611B(2,3);611B(2,3); JGP take�� 7231 into variant mapping set, but mark it as ��out-of-repertoire�� and take ��invalid�� action for WLG process, which means, �� 7231 will never be generated into the labels. JGP LGR: <language>und-Jpan</language> <char cp="611B" tag="sc:Hani"> <var cp="611B" type="alloc" comment="identity" /> <var cp="7231" type="out-of-repertoire-var" />  </char> WLE rules: <action disposition="invalid" any-variant="out-of-repertoire-var" comment="any variant label with a code point out of repertoire is invalid"/> <action disp="allocatable" all-variant="alloc" /> CGP LGR: <language>und-Hani</language> <char cp="611B" tag="sc:Hani"> <var cp="611B" type="trad" comment="identity" />  <var cp="7231" type="simp" /> </char> <char cp="7231" tag="sc:Hani"> <var cp="611B" type="trad" />  <var cp="7231" type="simp" comment="identity" /> </char> WLE rules: <action disp="blocked" any-variant="block" /> <action disp="allocatable" only-variants="simp both" /> <action disp="allocatable" only-variants="trad both" /> <action disp="blocked" any-variant="simp trad" /> <action disp="allocatable" comment="catch-all" /> For scenario 2: In CGP: ��520A (0);��520A(86),��520A(886);��(0),�X(0); �X520B (0);��520A(86),��520A(886);��(0),�X(0); In JGP: �� 520A(2,3);520A(2,3); �X 520B(2,3);520B(2,3); �� 681E(2,3);681E(2,3); Now it is CGP��s turn to take�� 681E into variant mapping set, but mark it as ��out-of-repertoire�� and take ��invalid�� action for WLG process, which means, �� 681E will never be generated into the labels. CGP LGR <language>und-Hani</language> <char cp="520A" tag="sc:Hani"> <var cp="520A" type="both" comment="identity" /> <var cp="520B" type="block" /> <var cp="681E" type="out-of-repertoire-var" />  </char> <char cp="520B" tag="sc:Hani"> <var cp="520A" type="both" /> <var cp="520B" type="block" comment="identity" /> <var cp="681E" type="out-of-repertoire-var" />  </char> <char cp="681E" tag="sc:Hani">  <var cp="520A" type="block" /> <var cp="520B" type="block" /> <var cp="681E" type="out-of-repertoire-var" comment="identity"/> </char> WLE rules: <action disp="invalid" any-variant="out-of-repertoire-var" comment="any variant label with a code point out of repertoire is invalid"/> <action disp="blocked" any-variant="block" /> <action disp="allocatable" only-variants="simp both" /> <action disp="allocatable" only-variants="trad both" /> <action disp="blocked" any-variant="simp trad" /> <action disp="allocatable" comment="catch-all" /> JGP LGR: <language>und-Jpan</language> <char cp="520A" tag="sc:Hani"> <var cp="520A" type="alloc" comment="identity" /> <var cp="520B" type="block" /> <var cp="681E" type="block" /> </char> <char cp="520B" tag="sc:Hani"> <var cp="520A" type="block" /> <var cp="520B" type="alloc" comment="identity" /> <var cp="681E" type="block" /> </char> <char cp="681E" tag="sc:Hani"> <var cp="520A" type="block" /> <var cp="520B" type="block" /> <var cp="681E" type="alloc" comment="identity"/> </char> WLE rules: <action disp="blocked" any-variant="block" /> <action disp="allocatable" all-variant="alloc" /> For Scenario 3: In CGP һ4E00 (0); һ4E00(86),һ4E00(886); һ(0),��(0),Ҽ(0),�o(0); ��58F1 (0); Ҽ58F9(86),Ҽ58F9(886); һ(0),��(0),Ҽ(0),�o(0); Ҽ58F9 (0); Ҽ58F9(86),Ҽ58F9(886); һ(0),��(0),Ҽ(0),�o(0); �o5F0C (0); һ4E00(86),һ4E00(886); һ(0),��(0),Ҽ(0),�o(0); In JGP: һ 4E00(2,3);4E00(2,3); �� 58F1(2,3);58F1(2,3); Ҽ 58F9(2,3);58F9(2,3); �o 5F0C(2,3);5F0C(2,3); JGP needs to create its own mapping set including all above 4 code points and corresponding rules, otherwise, it will fall into scenario 1.. For Scenario 4: Like UNIQUE code point ONLY exists in JGP table �y8FBB(2,3);8FBB(2,3); CGP probably will not include this code point into its repertoire. No extra work or rule are needed. For Scenario 5: Actually, we have not find the code points which fit into this scenario. But the solution will refer to scenario 1 or 2, like: For JGP, ��C�� will be included but marked as ��out-of-repertoire�� For CGP, ��A�� will be included but marked as ��out-of-repertoire�� In conclusion, ��out-of �Crepertoire type�� and ��invalid action�� provide us a conservative and simple way to reach a consensus for the variant mapping and rules. According to our analysis on CGP table and JPRS table There are 4983 code points fit for Scenario 1 There are 840 code points fit for Scenario 3 There are 170 code points fit for Scenario 4 Since JGP has not decided yet if variant relationship exist in JGP repertoire, we don��t have analytical number about scenario 3 and scenario 5. But what we believe is that the above solution can also be applied for scenario 3 and 5 no matter what kind of variant mapping JGP will produce. All above is our proposal for settle the divergence at minimum cost for both of us. What do you think about it? Looking forward for your reply. Best Regards, Wei Wang

5 13

Chinese, Japanese and Korean GP Coordination meeting 2:30-3:30pm Monday 9 Feb. at ICANN 52, Singapore
by Sarmad Hussain Jan. 19, 2015

Jan. 19, 2015

Dear All, We will be organizing a coordination meeting between Chinese, Japanese and Korean Generation Panel members during the Singapore meeting as per the following schedule. IP members will be present. We will also arrange remote participation during this session. Time: 14:30 - 15:30 Date: Monday, 9 February 2015 Room: To be announced If this is insufficient time, please let us know details and we can organize an additional session. We will share further details as soon as they are available. Regards, Sarmad -----Original Message----- From: hotta(a)jprs.co.jp [mailto:hotta@jprs.co.jp] Sent: Sunday, January 18, 2015 8:19 PM To: Dillon, Chris Cc: ?超; Sarmad Hussain; Yoshiro YONEYA; ChineseGP(a)icann.org Subject: Re: [ChineseGP] proposal to eliminate the divergence between us > I’m also looking forward to discussing these things in Singapore! Yes, definitely. Is there a plan for CJK & IP & ICANN to meet in Singapore already? Hiro

4 5

Chinese and Korean Generation Panels: Coordination Call
by Sarmad Hussain Jan. 6, 2015

Jan. 6, 2015

Coordination meeting between Chinese and Korean Generation Panels on Thursday 8 January 0700 UTC, 3pm Beijing Time, 4pm Seoul Time (please visit http://www.timeanddate.com/worldclock/converter.html for other time zones). Relevant documents for discussion: Instructions to connect: Link to Adobe Connect: https://icann.adobeconnect.com/r72wznoryti/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. If you are Unable to log into Adobe Connect and can only join via phone: List of International Dial In Numbers: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=4054049491&num=1-719-… Participant Passcode: 4054049491

1 0

[lgr] ICANN News Alert -- IDN TLDs - LGR Procedure Implementation - Maximal Starting Repertoire Version 2 is Now Open for Public Comment
by Sarmad Hussain Dec. 17, 2014

Dec. 17, 2014

Dear All, (Apologies for cross-posting) MSR 2 has been released for public comments and is available at https://www.icann.org/public-comments/msr-2014-12-15-en. We look forward to your feedback. Regards, Sarmad From: ICANN News Alert [mailto:communications@icann.org] Sent: Wednesday, December 17, 2014 1:20 AM To: Sarmad Hussain Subject: ICANN News Alert -- IDN TLDs - LGR Procedure Implementation - Maximal Starting Repertoire Version 2 is Now Open for Public Comment <http://www.icann.org/> News Alert https://www.icann.org/news/announcement-3-2014-12-15-en _____ IDN TLDs - LGR Procedure Implementation - Maximal Starting Repertoire Version 2 is Now Open for Public Comment 15 December 2014 Forum Announcement: Comment Period Opens on Date: 15 December 2014 Categories/Tags: Internationalized Domain Names, IDN, IDN TLD, IDN Variant TLD, new gTLD, IDN ccTLD Purpose (Brief): ICANN is releasing for public comment version 2 of the Maximal Starting Repertoire (MSR-2). This upwardly compatible version of the MSR <https://www.icann.org/news/announcement-2-2014-06-20-en> adds six additional scripts to the repertoire. The MSR is the first deliverable under the "Procedure to Develop and Maintain Label Generation Rules (LGR) for the Root Zone With Respect to IDN Labels <https://www.icann.org/en/resources/idn/variant-tlds/lgr-procedure-20mar13-e…> " [PDF, 772 KB] (the Procedure) and the starting point for the work by community based Generation Panels to develop their LGR proposals. The contents of MSR-2 and the detailed rationale behind its development are described in "Maximal Starting Repertoire - MSR-2-Overview and Rationale <https://www.icann.org/en/system/files/files/msr-overview-04dec14-en.pdf> " [PDF, 1.12 MB]. Community members are invited to provide feedback on the contents of MSR-2. Public Comment Box Link: https://www.icann.org/public-comments/msr-2014-12-15-en This message was sent to sarmad.hussain(a)icann.org <mailto:sarmad.hussain@icann.org> from: ICANN News Alert | communications(a)icann.org <mailto:communications@icann.org> | ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 Email Marketing by <http://www.icontact.com/a.pl/144186> <http://app.icontact.com/icp/mmail-mprofile.pl?r=27296433&l=6333&s=95OV&m=95…>Manage Your Subscription _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

答复: Chinese Generation Panel Meeting
by Wang Wei Dec. 17, 2014

Dec. 17, 2014

Dear All Mr. QI Chao help to prepare a solution draft for mapping between C and J. According to XML RFC Draft and Asmus’ suggestion to JGP, a new type “out-of-repertoire” could be added to the variant table, the corresponding action is “invalid”. Which means, for those Chinese characters which exist in JGP repertoire and will be added into CGP repertoire The most conservative and simplest solution, is mark them as “out of repertoire”, and take no action to them at all. I’d like to hear your suggestions tomorrow. Wang Wei -----约会原件----- 发件人: chinesegp-bounces(a)icann.org [mailto:chinesegp-bounces@icann.org] 代表 Sarmad Hussain 发送时间: 2014年12月12日 8:09 收件人: ChineseGP(a)icann.org 主题: Chinese Generation Panel Meeting 时间: 2014年12月18日星期四 12:00-13:00GMT+0500。地点: Adobe Connect - Details below Meeting time: 7am UTC, 3pm Beijing Time on Thursday 18 Dec. 2014 (see http://www.timeanddate.com/worldclock/converter.html for other time zones). How to connect: Link to Adobe Connect: https://icann.adobeconnect.com/r72wznoryti/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. If you are Unable to log into Adobe Connect and can only join via phone: List of International Dial In Numbers: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=4054049491&num=1-719-4 57-6209 Participant Passcode: 4054049491 << 文件: 未命名的附件 00063.txt >>

2 1

Chinese Generation Panel Meeting
by Sarmad Hussain Dec. 12, 2014

Dec. 12, 2014

Meeting time: 7am UTC, 3pm Beijing Time on Thursday 18 Dec. 2014 (see http://www.timeanddate.com/worldclock/converter.html for other time zones). How to connect: Link to Adobe Connect: https://icann.adobeconnect.com/r72wznoryti/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. If you are Unable to log into Adobe Connect and can only join via phone: List of International Dial In Numbers: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=4054049491&num=1-719-… Participant Passcode: 4054049491

1 0

Chinese Generation Panel Meeting
by Sarmad Hussain Dec. 12, 2014

Dec. 12, 2014

Meeting time: 7am UTC, 3pm Beijing Time on Thursday 18 Dec. 2014 (see http://www.timeanddate.com/worldclock/converter.html for other time zones). How to connect: Link to Adobe Connect: https://icann.adobeconnect.com/r72wznoryti/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. If you are Unable to log into Adobe Connect and can only join via phone: List of International Dial In Numbers: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=4054049491&num=1-719-… Participant Passcode: 4054049491

1 0

Chinese Generation Panel Meeting
by Sarmad Hussain Dec. 11, 2014

Dec. 11, 2014

Meeting time: 7am UTC, 3pm Beijing Time on Thursday 18 Dec. 2014 (see http://www.timeanddate.com/worldclock/converter.html for other time zones). How to connect: Link to Adobe Connect: https://icann.adobeconnect.com/r72wznoryti/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. If you are Unable to log into Adobe Connect and can only join via phone: List of International Dial In Numbers: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=4054049491&num=1-719-… Participant Passcode: 4054049491

1 0