- Latingp - lists.icann.org

Agenda for the call on 23rd of January, 2018
by Mirjana Tasić Jan. 22, 2018

Jan. 22, 2018

Dear GP members. Please find enclosed the proposal of Agenda for our next telephone conference. After agenda for the call you could find in this mail also the proposal for the Agenda for F2F meeting in Brussels. Regards Mirjana __________________________________________ AGENDA for the GP call on 23rd of January 2018, 16:00UTC 1. Roll call 2. Agenda for F2F meeting in Brussels 3. Short report from Repertoire Group 4. Short report from Variant group 5. Short report from Drafting Team 6. AOB ______________________________________________ Second Face-to-Face Meeting of the Latin GP Brussels, Belgium 29 - 31 January 2018 Day 1 - 29 January 2018 0900 – 1030 Welcome and Introductions Review of Current Status of Latin GP * Current Plan of Work * Review of Status by Repertoire WG * Review of Status by Variants WG All Mirjana Tasic Mats Dufberg Dennis Tan Tanaka 1030 – 1050 Tea and Coffee Break 1050 – 1230 Repertoire Discussion 1 * Open Issues Mats Dufberg 1230 – 1400 Lunch Break 1400 – 1530 Repertoire Discussion 2 * Final Draft of Repertoire Table * Conclusions and Next Steps Mats Dufberg 1530 – 1550 Tea and Coffee Break 1550 – 1730 Variants Discussion 1 * Latin * Cyrillic * Armenian * Greek Dennis Tan Tanaka Day 2 - 30 January 2018 0900 – 1030 Variant Discussion 2 * Final Draft of Variant Tables * Conclusions and Next Steps Dennis Tan Tanaka 1030 – 1050 Tea and Coffee Break 1050 – 1230 Variant Discussion 3 * Similarity of Code Points * Latin * Armenian, Cyrillic and Greek Dennis Tan Tanaka 1230 – 1400 Lunch Break 1400 – 1530 Review of Current Latin LGR Proposal Draft * Introduction sections including scope of work, principles and methodology of analysis * Repertoire section Drafting Team? 1530 – 1550 Tea and Coffee Break 1550 – 1730 Review of Current Latin LGR Proposal Draft * Variant section * WLE section * References and Appendices Drafting Team? Day 3 - 31 January 2018 0900 – 1030 LGR XML Tool Sarmad Hussain 1030 – 1050 Tea and Coffee Break 1050 – 1230 Conclusion and Next Steps Mirjana Tasic 1230 – 1400 Lunch Break 1400 – 1530 1530 – 1550 Tea and Coffee Break 1550 – 1730

1 0

Summary of Latin GP on 9 January 2018
by Pitinan Kooarmornpatana Jan. 22, 2018

Jan. 22, 2018

Dear Latin GP members, Please find attached the summary of the meeting of Latin GP on 9 January 2018. Please let us know if you would like to suggest any edits or additions. Action Items S. No. Action Items Owner 1 Summarize the instruction for reducing the number of references and inform the GP members. MD 2 Update the MSR-3 letter and sent to Sarmad for forwarding to the IP MJ 3 Review Mats' analysis on the code point google sheet and give feedback All This summary and the previous meeting notes are also posted at the Latin GP wiki page at https://community.icann.org/display/croscomlgrprocedure/Latin+GP[community.…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> Regards, Pitinan

1 0

Re: [Latingp] New version of Proposal for inclusion Latin script letters in next version of MSR
by Meikal Mumin Jan. 19, 2018

Jan. 19, 2018

Dear all, I see numerous inconsistencies rather than consistencies in those choices made, and holding on to such choices in the end serves to reinforce pre-existing biases without any supporting data (as Mats pointed out), rather than improving the safety of the zone. So let's argue against it strongly as a GP and ask for a change of policy, if a majority of the GP is in favor! Processes were made to adopt to reality, not the other way around. I'm already working on some text regarding these issues for the proposal. Please feel free to chime in. Best, Meikal On 19 January 2018 at 17:59, Bill Jouris <bill.jouris(a)insidethestack.com> wrote: > Hi Meikal, > > I'd be fine with including something along these lines in the main text, > if the panel is OK with that. What I sent out needs serious editing, but > it's a start. > > My best guess (and it is only a guess) on why is that the IP decided that, > since they were excluding the click symbols that are homoglyphs of > punctuation marks, consistency would indicate that they exclude also those > click symbols which are not. On the other hand, that would have meant > excluding U0294 (ʔ), which would have to be considered at least a near > homoglyph of a question mark (?). But as Mats notes they have accepted > that. So perhaps not. > > Bill Jouris > Inside Products > bill.jouris(a)insidethestack.com > 831-659-8360 > 925-855-9512 (direct) > > > ------------------------------ > *From:* Meikal Mumin <meikal.mumin(a)uni-koeln.de> > *To:* Bill Jouris <bill.jouris(a)insidethestack.com> > *Cc:* Latin GP <latingp(a)icann.org> > *Sent:* Friday, January 19, 2018 6:40 AM > > *Subject:* Re: [Latingp] New version of Proposal for inclusion Latin > script letters in next version of MSR > > Dear colleagues, > > I was trying to look for a specific reason why those code points > representing click sounds have been excluded. Looking at the text of MSR-3, > I was able to find only the following line of argumentation on page 23: > > "In general, where code points are homoglyphs or near homoglyphs of code > points that are not PVALID, > usually punctuation characters, the Integration Panel has not included > such code points in the MSR. > In particular, the following code points are highly confusable with or > outright homoglyphs of code > points, such as common punctuation characters like apostrophe or > exclamation mark, that are not > PVALID in IDNA2008 or excluded for other reasons:" > > I don't see however how the main argument that the code points we > suggested are homogylphs or near homogylphs of such characters they > consider punctuation characters. That argument may be valid in the case of > U01C3 or U0242, but not the three code points we suggested. I think that > this stance taken by IP is overly conservative and reinforces certain > systemic biases in the DNS as part of the internet and that the entire > point of our task is precisely to put and end to such biases and therefore > I would like to raise this issue again. > > I would suggest we submit a comment asking what their specific rationale > for excluding these three code points is, and that clearly U01C2 for > example is NOT a homogylph or near homoglyph of any punctuation > character, just as U01C0 and U01C1. Otherwise, I would like to argue that > following their approach 0069 (i.e. i) as well as any "near homoglyph" of > it is a near homogylph of the exclamation mark and should be excluded > equally. > > Also, I have started working on the proposal, Bill, and I would like to > add your text to it and I don't think it should be an appendix. > > Best, > > Meikal > > On 19 January 2018 at 00:50, Bill Jouris <bill.jouris(a)insidethestack.com> > wrote: > > Hello all, > > Earlier this week, I had been drafting a possible Appendix D for our final > report, to discuss the overall issue of clicks and stops. (And it is a > VERY rough draft. Note, for example, that the various RFCs and other > documents are not yet identified.) > > With this reply from the IP, it seems like the question may be better > addressed in comments on MSR-3. But I have attached what I had for those > who may be interested. > > Bill Jouris > Inside Products > bill.jouris(a)insidethestack.com > 831-659-8360 > 925-855-9512 (direct) > > > ------------------------------ > *From:* Sarmad Hussain <sarmad.hussain(a)icann.org> > *To:* Mirjana Tasić <Mirjana.Tasic(a)rnids.rs>; Latin GP <latingp(a)icann.org> > > *Cc:* "integrationpanel(a)icann.org" <integrationpanel(a)icann.org> > *Sent:* Wednesday, January 17, 2018 10:00 PM > *Subject:* Re: [Latingp] New version of Proposal for inclusion Latin > script letters in next version of MSR > > Dear Mirjana, Latin GP members, > > Please find below the message from the Integration Panel. > > Regards, > Sarmad > > ========= > > The IP is pleased to acknowledge the input from the Chinese, Japanese and > Latin GPs to the MSR-3 update of the Maximal Starting Repertoire. MSR-3 has > just been released for public comment > <https://www.icann.org/public-comments/msr-3-2018-01-17-en> and contains > an updated listing of code points as well as the rationale for including or > excluding particular code points. Based on the input received, the IP has > extended the list of source sets for the Han ideographs with the net effect > of adding three code points. The IP has added three Latin code points > because new evidence provided invalidated the original rationale for their > exclusion. An additional three Latin code points representing clicks were > not included because the original rationale for their exclusion remains > valid. For details see the overview document of MSR-3. > > Integration Panel > > > 1. MSR-3 (HTML > <https://www.icann.org/sites/default/files/packages/lgr/msr/msr-3-wle-rules-…> > , XML > <https://www.icann.org/sites/default/files/packages/lgr/msr/msr-3-wle-rules-…> > ) > 2. MSR-3-Annotated-Hangul-Tables > <https://www.icann.org/en/system/files/files/msr-3-hangul-15jan18-en.pdf> > [PDF, 1.12 MB] > 3. MSR-3-Annotated-Han-Tables > <https://www.icann.org/en/system/files/files/msr-3-han-15jan18-en.pdf> [ > PDF, 39 MB] > 4. MSR-3-Annotated-non-CJK-Tables > <https://www.icann.org/en/system/files/files/msr-3-non-cjk-15jan18-en.pdf> > [PDF, 2.16 MB] > 5. MSR-3-Overview and Rationale > <https://www.icann.org/en/system/files/files/msr-3-overview-15jan18-en.pdf> [PDF, > 1.1 MB] > > > *From:* Mirjana Tasić [mailto:Mirjana.Tasic@rnids.rs ] > *Sent:* Tuesday, January 09, 2018 11:07 PM > *To:* Sarmad Hussain <sarmad.hussain(a)icann.org> > *Cc:* Latin GP <latingp(a)icann.org> > *Subject:* [Ext] New version of Proposal for inclusion Latin script > letters in next version of MSR > > Dear Sarmad, > > After further investigation of Latin Repertoire, Latin GP has found one > additional code point which is not included in our previous proposal for > inclusion in the new version of MSR. > > Please find enclosed the new version of our Proposal for inclusion Latin > script letters in the next version of MSR. > > Regards Mirjana > > > ______________________________ _________________ > Latingp mailing list > Latingp(a)icann.org > https://mm.icann.org/mailman/ listinfo/latingp > <https://mm.icann.org/mailman/listinfo/latingp> > > > > ______________________________ _________________ > Latingp mailing list > Latingp(a)icann.org > https://mm.icann.org/mailman/ listinfo/latingp > <https://mm.icann.org/mailman/listinfo/latingp> > > > > >

2 1

New version of Proposal for inclusion Latin script letters in next version of MSR
by Mirjana Tasić Jan. 19, 2018

Jan. 19, 2018

Dear Sarmad, After further investigation of Latin Repertoire, Latin GP has found one additional code point which is not included in our previous proposal for inclusion in the new version of MSR. Please find enclosed the new version of our Proposal for inclusion Latin script letters in the next version of MSR. Regards Mirjana

5 7

[lgr] FW: ICANN News Alert -- Maximal Starting Repertoire version 3 (MSR-3) for Root Zone Label Generation Rules (RZ-LGR)
by Sarmad Hussain Jan. 18, 2018

Jan. 18, 2018

Dear All, MSR-3 has been released for public comment. Please see the announcement and links below. We look forward to your feedback. Regards, Sarmad News Alert https://www.icann.org/news/announcement-2018-01-17-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 Root Zone Label Generation Rules (RZ-LGR) 17 January 2018 Open Date: 17 January 2018 Close Date: 26 February 2018 Originating Organization: Global Domains Division Categories/Tags: Top-Level Domains Brief Overview: ICANN is releasing for public comment version 3 of the Maximal Starting Repertoire (MSR-3: HTML[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.org_sites_defaul…>, XML[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.org_sites_defaul…>). This version is upwardly compatible with MSR-2[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.org_news_announc…> 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__icann.org_en_resources…> [PDF, 772 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__icann.org_resources_pa…> 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__icann.org_resources_pa…>). 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__icann.org_en_system_fi…> [PDF, 1.1 MB]. Link: https://www.icann.org/public-comments/msr-3-2018-01-17-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.org_public-2Dcom…> ICANN News Alert ICANN 12025 Waterfront Drive Suite 300 Los Angeles, CA 90094-2536 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

Repertoire
by Mats Dufberg Jan. 17, 2018

Jan. 17, 2018

I have made a backup of the repertoire file to our dropbox. I have also done an editorial update of the file to make it easier for you to review my work. Column B was previous called "final review". Jag have now split that information into two columns: * Column B, "Candidate for inclusion?", which as either of three values "yes", "no" or "needs review". * Column C, "Comments on inclusion" * If column B has "no" then column C has a short motivation why the code point (or sequence) is not included, or, in some cases, why that language is not a support for that code point (or sequence). * If column B has "needs review", then we need people to read and suggest if it should be "yes" or "no". In column C the problem is described. * If column B has "yes", then usually column C is empty, but sometimes there is a comment. Please review before we reduce by removing languages beyond three per code point or sequence. Yours, Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/

1 0

Re: [Latingp] Variant analysis Latin Armenian
by Tan Tanaka, Dennis Jan. 17, 2018

Jan. 17, 2018

as long as primary and secondary reviews are completed (individually), no further work is necessary after that. We will review the two consolidated files in Brussels. -Dennis From: Mats Dufberg <mats.dufberg(a)iis.se> Date: Wednesday, January 17, 2018 at 3:47 PM To: Dennis Tan Tanaka <dtantanaka(a)verisign.com>, Latin GP <latingp(a)icann.org> Subject: [EXTERNAL] Re: [Latingp] Variant analysis Latin Armenian Until I get some other feedback, I consider my individual work to be completed. But I am not sure how primary and secondary reviewer should finalize. Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/ From: "Tan Tanaka, Dennis" <dtantanaka(a)verisign.com> Date: Wednesday 17 January 2018 at 21:36 To: Mats Dufberg <mats.dufberg(a)iis.se>, Latin GP <latingp(a)icann.org> Subject: Re: [Latingp] Variant analysis Latin Armenian Thanks Mats. I have completed my first inspection for both Armenian and Greek. Files are in corresponding folders. I will look again at all of the files and consolidate our findings before our meeting in Brussels. Please aim to finish or review your work no later than next Wednesday 24. Thank you, Dennis From: Latingp <latingp-bounces(a)icann.org> on behalf of Mats Dufberg <mats.dufberg(a)iis.se> Date: Wednesday, January 17, 2018 at 9:30 AM To: Latin GP <latingp(a)icann.org> Subject: [EXTERNAL] Re: [Latingp] Variant analysis Latin Armenian For the variant group: After some feedback from Michael I have slightly updated my review plus defined how I use MD{+,-,#,*}: · MD#: there is no Latin character to compare with · MD+: the Latin character is a candidate for being a variant, independent if the character is part of MSR or the Latin GP repertoire. · MD-: there is a similar character, but too different to be a candidate. · MD*: unsure if MD+ or MD-. When I have changed the character in what was Bill's original analysis, then I have set the background to be yellow. Yours, Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/ From: Mats Dufberg <mats.dufberg(a)iis.se> Date: Wednesday 17 January 2018 at 13:58 To: Latin GP <latingp(a)icann.org> Subject: Variant analysis Latin Armenian For the variant group: I have completed my analysis, both my primary and my secondary (where Bill's is the primary). I am still confused of the codes. MD+ means that I think they should be variants. MD-, MD# and MD* means that I do not think so but in different situations? In some cases I have updated the data of Bill's analysis (but in a separate file with my tag "MD" and a date on). Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/

1 0

Re: [Latingp] Variant analysis Latin Armenian
by Tan Tanaka, Dennis Jan. 17, 2018

Jan. 17, 2018

Thanks Mats. I have completed my first inspection for both Armenian and Greek. Files are in corresponding folders. I will look again at all of the files and consolidate our findings before our meeting in Brussels. Please aim to finish or review your work no later than next Wednesday 24. Thank you, Dennis From: Latingp <latingp-bounces(a)icann.org> on behalf of Mats Dufberg <mats.dufberg(a)iis.se> Date: Wednesday, January 17, 2018 at 9:30 AM To: Latin GP <latingp(a)icann.org> Subject: [EXTERNAL] Re: [Latingp] Variant analysis Latin Armenian For the variant group: After some feedback from Michael I have slightly updated my review plus defined how I use MD{+,-,#,*}: · MD#: there is no Latin character to compare with · MD+: the Latin character is a candidate for being a variant, independent if the character is part of MSR or the Latin GP repertoire. · MD-: there is a similar character, but too different to be a candidate. · MD*: unsure if MD+ or MD-. When I have changed the character in what was Bill's original analysis, then I have set the background to be yellow. Yours, Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/ From: Mats Dufberg <mats.dufberg(a)iis.se> Date: Wednesday 17 January 2018 at 13:58 To: Latin GP <latingp(a)icann.org> Subject: Variant analysis Latin Armenian For the variant group: I have completed my analysis, both my primary and my secondary (where Bill's is the primary). I am still confused of the codes. MD+ means that I think they should be variants. MD-, MD# and MD* means that I do not think so but in different situations? In some cases I have updated the data of Bill's analysis (but in a separate file with my tag "MD" and a date on). Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/

2 1

Variant analysis Latin Armenian
by Mats Dufberg Jan. 17, 2018

Jan. 17, 2018

For the variant group: I have completed my analysis, both my primary and my secondary (where Bill's is the primary). I am still confused of the codes. MD+ means that I think they should be variants. MD-, MD# and MD* means that I do not think so but in different situations? In some cases I have updated the data of Bill's analysis (but in a separate file with my tag "MD" and a date on). Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/

1 1

Latin GP meeting
by Pitinan Kooarmornpatana Jan. 11, 2018

Jan. 11, 2018

Dear Latin GP Members, This is the place holder for the Latin GP meeting on 23 January 2018 16:00 UTC Regards, Pitinan How to connect: Link to Adobe Connect: https://participate.icann.org/idn/ *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: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=1064158692&num=1-719-…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.myrcplus.com_cnums…> Participant Passcode: 1064158692

1 0