August 2018 - Latingp - lists.icann.org

From IP: Diacritics below a security risk?
by Sarmad Hussain Aug. 29, 2018

Aug. 29, 2018

Dear Latin GP members Kindly find below some feedback from IP for your consideration. Regards Sarmad TO: LatinGP FROM: IP There are recent and widely published examples of phishing attacks using Latin IDNs in which the key features involved were diacritics below the letter. Here is an example: [cid:part1.E6E9F88C.32B00687@ix.netcom.com] Of all diacritics, diacritics below can be difficult to distinguish or be prone to clipping -- there is less space below the baseline than between the typical lowercase glyph and the top of the line. The example given above shows a further interaction with URL underlining - and not all display engines actually do as nice a job interrupting the underline as in the screen shot above. For example, here is how one system will render this (using a designated UI font - Segoe UI): [cid:part2.59964F92.16B1BC0B@ix.netcom.com] Note, this code point (U+1E33) is in the MSR as is (U+1E35 LATIN SMALL K WITH LINE BELOW). [cid:part3.99B9649E.C3C335FC@ix.netcom.com] The second example contains U+1E35 -- while the effect does not show equally at all type sizes, from 12pt and below the LINE BELOW is reliably hidden. Here are the two examples at 10pt [cid:part4.B43CE3FD.8C84EACF@ix.netcom.com] The issue is not limited to "K". We see "B", "D", "L" and "N" with both DOT and LINE BELOW and "M" and "H" with DOT BELOW, all on the same page in the MSR. It can be argued users have no working understanding of typography and would not reliably interpret small gaps or bulges in the underline as being related to an unfamiliar code point. This appears to make all diacritics below security-sensitive, however, the initial determination belongs to the relevant GPs. Note by the way that the Devanagari LGR treats sequences containing NUKTA (a dot below) as variants in at least some cases and recent community comments for that script are calling for more variant sequences. However, while the feature is graphically analog (dot below), each script works differently and there is no single a-priori solution. The IP would like to encourage the LatinGP (and any other GP facing cases like this) to explicitly examine this example and other cases like it, where code points can become indistinguishable in common usage scenarios for IDNs, and formally conclude whether and how to take these into account when designing their LGR. At this point, the IP would expect the GP to: * explicitly discuss this and other scenarios like it * evaluate whether they constitute a security risk to the Root Zone * come up with a reasoned decision as to whether and how to address them in the design of the Latin GP; and finally * document both the decision and its rationale. In coming to a decision, the GP may resolve: 1) to make them variants 2) to list them for attention as confusable 3) to take no action, because the GP feels that they do not represent a special security risk. As part of the review of the Latin LGR, the IP will look at the background and rationale offered by the Latin GP in coming to its conclusion; note that if the IP feels that the facts considered and rationale documented do not support the conclusion reached by the GP it may raise objections at that time.

1 0

Draft in-script variants
by Tan Tanaka, Dennis Aug. 28, 2018

Aug. 28, 2018

Dear Latin GP, Here is the compilation of current in-script variant candidates for our review during tomorrow’s call. https://docs.google.com/document/d/1bKKFHxbjgBd9CIPRiuOsej_3x670yTytUMM32Ou… Talk to you all soon. Best, -Dennis

3 11

Section numbering in Final report
by Mirjana Tasić Aug. 22, 2018

Aug. 22, 2018

Dear GP members, During upload of the new version of the report, Google docs used its own logic, and numbered our Table of content as section one. I have corrected this, now sections has right numbers as it is stated in Table of contents. Regards Mirjana

1 0

Summary of Latin GP Meeting on 16 August 2018
by Pitinan Kooarmornpatana Aug. 22, 2018

Aug. 22, 2018

Dear Latin GP Members, Please find attached the summary of the meeting of Latin GP Meeting on 16 August 2018. Please let us know if you would like to suggest any edits or additions. Action Items S. No. Action Items Owner 1 Review additional references for EGIDS5 languages ALL 2 Share the text which needs revision to Bill MT 3 Prepare the short list of in-script variant analysis DT This summary and the recording will be posted at the Latin GP wiki page shortly at https://community.icann.org/display/croscomlgrprocedure/Latin+GP Regards, Pitinan

1 0

Handwriting Letters
by Bill Jouris Aug. 20, 2018

Aug. 20, 2018

While thinking about Meikal's comments on the subject in Thursday's meeting, I came across this in an e-mail: ----- Forwarded Message ----- From: Bαnk of Americα <customer(a)bankofamerica-alert.com> To: Sent: Thursday, June 28, 2018 10:26 PM Subject: Notification: Confirm Your Online Banking Details Note the first two instances of a lower case letter A in the From line. Apparently someone has generated a lower case letter A in the handwritten form, and expected it to be recognized easily. The alternative being that American English has acquired a Latin Small Letter Alpha (which, note, isn't in our repertoire currently) . . . and is misspelling both "Bank" and "America" to boot. Just a little more food for thought. Bill Jouris Inside Products bill.jouris(a)insidethestack.com 831-659-8360 925-855-9512 (direct)

3 3

Re: [Latingp] FW: IP response on Latin Repertoire 20180525
by Meikal Mumin Aug. 20, 2018

Aug. 20, 2018

Dear Mirjana, dear colleagues, I reviewed the evidence on the use of Bavarian. I had not look at which characters are used within those publications. 0115 does not occur in those sources and from what I read on the Bavarian wikipedia no standard has emerged and there is a tendency to use the German orthographic repertoire. So my analysis is that Bavarian is used - also on the internet - but that any additional signs are only used for special purposes, such as scientific transliteration. I also was unable to find any substantial evidence for other language's use, so I would suggest removing 0115. Best, Meikal On 16. Aug 2018 at 19:45, Mirjana Tasić <Mirjana.Tasic(a)rnids.rs> wrote: Dear Meikal, Here are the links you provided for Bavarian “Anyhow breve occurs in Bavarian, and there are samples online, such as special editions of newspapers in local varieties: http://www.aichacher-zeitung.de/vorort/dialektwoche/ https://www.tz.de/thema/tz-auf-bairisch-ere108588/ “ Further on you can find your e-mail with responses to IP comments. Regards Mirjana *From: *Latin GP <latingp-bounces(a)icann.org> on behalf of Meikal Mumin < meikal.mumin(a)uni-koeln.de> *Date: *Thursday, June 28, 2018 at 14:13 *To: *Michael Bauland <michael.bauland(a)knipp.de> *Cc: *Latin GP <latingp(a)icann.org> *Subject: *Re: [Latingp] IP response on Latin Repertoire 20180525 Dear colleagues, I agree with Michael's suggestion to remove EGIDS5 evidence, where there is other evidence. Where it is the only source for a code point we should provide specific evidence and sources for contemporary usage. I also added numerous comments to the two documents - I would have done it on an online version preferably, but to avoid version conflicts I added comments to the word files. Several comments of mine contain suggested action items. On the whole, IP's review leaves me with the impression, that we have to work again on the repertoire. Particularly the additional evidence required for African languages will require quite a bit of work, and it is unclear to me why - as a general rule - IP seems to have higher demands towards the supporting evidence for African languages versus other languages. Best, Meikal On 26 June 2018 at 22:02, Michael Bauland <michael.bauland(a)knipp.de> wrote: Hi all, I am a bit confused by the choice of comments from the IP regarding EGIDS 5 languages: * In some occasions (e.g., 0115, Bavarian (5)) they state that the languages should be removed from the refernce (sometimes with the result of eliminating the whole character) * In some occasions (e.g., 015D, Tswa (5)) they require additional comments for those languages. * In some occasions (e.g., 1E5B, Kabyle (5)) the languages are accepted without complaint from IP. I guess, according to our statement "Languages with EGIDS 5 may be included in special cases where there is additional evidence that it is in widespread use" we should alter our table as follows: * remove EGIDS 5 languages, if other at least two other references are available wiht higher score * keep EGIDS 5 languages, if there is one or no other reference available * add a comment to prove its widespread use for all remaining EGIDS 5 langauges Cheers, Michael -- ____________________________________________________________________ | | | knipp | Knipp Medien und Kommunikation GmbH ------- Technologiepark Martin-Schmeisser-Weg 9 44227 Dortmund Germany Dipl.-Informatiker Fon: +49 231 9703-0 Fax: +49 231 9703-200 Dr. Michael Bauland SIP: Michael.Bauland(a)knipp.de Software Development E-mail: Michael.Bauland(a)knipp.de Register Court: Amtsgericht Dortmund, HRB 13728 Chief Executive Officers: Dietmar Knipp, Elmar Knipp _______________________________________________ Latingp mailing list Latingp(a)icann.org https://mm.icann.org/mailman/listinfo/latingp

2 1

Latin In-Script Variants
by Bill Jouris Aug. 19, 2018

Aug. 19, 2018

Hi folks, At our meeting last Thursday, Dennis mentioned in passing that there were “only a few” in-scriptvariants for Latin. I think this isseriously incorrect. You may recallthat, at our face-to-face meeting in Brussels last winter, Sarmad expanded thisspreadsheet https://docs.google.com/spreadsheets/d/1Sj2moWEw4YFLFTcvsiRpjsQRyLZJ7SCnlF7… include atab for each letter of the Latin alphabet, and created tables (in each of ourthree fonts) for the variations of each letter. (I am still in awe that he managed to do the whole thing in under anhour!) I’ve made a few additions to thetables: - I’veadded rows and columns for the code points (e.g. from Esperanto) that have beenadded to our repertoire since then. - I’veput a few codepoints in additional places. For example, ł (0142 Latin Small LetterL with Stroke) is still with the letter L, but it also got added to the tab forthe letter T. My thought being that, forthose who do not know Polish and so are unfamiliar with the codepoint, it wouldautomatically be read as a T. - I’ve added a column giving the Unicode code foreach glyph. That should give us a head start, when we got to create a table of variants. In addition, I’ve taken a stab at rating each pair. (I’m still slogging thru the letter O. But the rest are done.) I have found that it is extremely helpful to highlight theindividual entries: 1 is highlighted in blue, 2 in green, 3 in yellow. That way, it is far easier to find things inthe sea of ratings. So far, I have over 25 Variants that I would rate as a 1, andan additional 140+ that I would rate as a 2. (And, as noted, I've still got the 23 Letter O codepoints to work thru.) Obviously we need a second pair of eyes to look over each case. But it’s a start. Clearly this isn’t something that we are going to just whipthru in a week or two. However,if Mirjana is willing, it occurs to me that we can offer up what I’ve got inthe DRAFT that we are sending to the IP at the end of the month. It won't be our final opinion, of course, but it will at least give them something on which to base feedback – if theydisagree with where I’ve gone, they can tell us, so we can make corrections inour face-to-face meeting. Bill Jouris Inside Products bill.jouris(a)insidethestack.com 831-659-8360 925-855-9512 (direct)

1 0

Latin GP meeting
by Pitinan Kooarmornpatana Aug. 17, 2018

Aug. 17, 2018

Dear Latin GP members , This is a placeholder for the Latin GP meeting on August the 23rd, 2018, 16:00UTC. Regards, Pitinan ---------------------------- 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-… Participant Passcode: 1064158692

1 0

Variant update
by Tan Tanaka, Dennis Aug. 15, 2018

Aug. 15, 2018

Dear Latin GP, I have updated the Latin-Cyrillic Working Document based on the latest conversation (e.g. resolution , new cases, etc), but there are still pending cases based on member’s input. The working documents for Greek and Armenian with pending cases for resolution are also available for comments. Cyrillic: https://docs.google.com/document/d/1Ontc-amdQ_dFCRCc9oHBvotjwIhYc8xEM1OBn5y… Greek: https://docs.google.com/document/d/1jQz-X7wk_Um-vpL2D2PjaTEs2Iq7zGVJd8PCt0A… Armenian: https://docs.google.com/document/d/1FUPNDwJUq9cvHAqgIIzpgAYeaLhmbdDwsr0mgi4… We can review these documents in our call tomorrow. Thanks, -Dennis

1 0

Latin GP meeting
by Pitinan Kooarmornpatana Aug. 13, 2018

Aug. 13, 2018

Dear Latin GP members , Please find the agenda for the next Latin GP meeting as follows: AGENDA for the GP call on Thursday August the 16th, 2018, 16:00UTC 1. Roll call 2. IP comments on repertoire - final discussion * Document with list of tasks to be fulfilled, and some comments https://docs.google.com/document/d/1DhK_YyksaKbNtJ-vN_Q4gsucIpCUt80o2b01Ecc… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> * New version of the Report with almost all comments from IP resolved https://docs.google.com/document/d/1rXd6ffnbD2BQa3HRvtJcNJDqZ58vaCPr5jzj47S… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> 3. Latin/Cyrillic cross-script Variants finalization -STATUS 4. Finalization of the Report with Repertoire and Variants * Finalization of the Repertoire * Checking the final Repertoire * Finalization of all variants table * Updating references * Production of test label file 5. Next telephone conference August the 30th 6. AOB Regards, Pitinan ---------------------------- 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-… Participant Passcode: 1064158692

1 0