BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:UTC BEGIN:STANDARD DTSTART:16010101T000000 TZOFFSETFROM:+0000 TZOFFSETTO:+0000 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T000000 TZOFFSETFROM:+0000 TZOFFSETTO:+0000 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT ORGANIZER;CN=Pitinan Kooarmornpatana:MAILTO:pitinan.koo@icann.org ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Latin GP:M AILTO:latingp@icann.org ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Sarmad Hus sain:MAILTO:sarmad.hussain@icann.org ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Mirjana Ta sić:MAILTO:Mirjana.Tasic@rnids.rs ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Tran Canh Toan:MAILTO:toantc@VNNIC.VN ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Fahd Batay neh:MAILTO:fahd.batayneh@icann.org DESCRIPTION;LANGUAGE=en-US:Dear Latin GP members\,\n\n\nThis is a gentle re minder for the Latin GP meeting on 7 May 2020\, 16.00UTC.\nPlease join th e meeting at the updated link: https://icann.zoom.us/j/95395839226?pwd=ZGx pYmRqV2E2NjloWTFHZWNGbkJWZz09\nPassword: 096517\n\n\n--------------\nTo jo in via phone\, please find your local number at https://icann.zoom.us/u/aw 6COk4xD\nMeeting ID: 953 9583 9226\nPassword: 096517\n\n\nPlease find the Agenda and the note from the chair below.\n\n\nRegards\,\nPitinan\n\n\nDea r GP members\,\n\n\n\nPlease find enclosed the proposal of Agenda for our call. Any comments\, corrections and suggestions are welcome.\n\n\n\n\n\nR egards Mirjana\n\n\n\n____________________________________________________ ___________________________________________\n\nAGENDA for the GP call on M ay the 7th 2020\, 16:00UTC\n\n\n\n 1. Latin Small Letter I () and L atin Small Letter Dotless I () the analysis is already documented\, it onl y requires the final conclusion. Please find the relevant section in the p roposal below.\n\n 2. Next tasks- discuss the priorities:\n\n * Thorough reading and finalization of In-Script variant analysis\n\n * Review proposed confusables for Similarity review\n\n * Rep ort finalization\n\n * XML production and correction of possible errors\n\n * Test data production\n\n 3. Next meeting May the 14th 2020\, 16:00 UTC\n\n 4. AOB\n\n\n\n\n\n\n\nD.5.2 Latin Small Lett er Dotless I (Äą) 0131\n\n\n\nThere are four Latin code points that have a special case (upper case/lower case) relationship:\n\n ¡ U +0069 Latin Small Letter I ("i")\n\n ¡ U+0049 Latin Capital L etter I ("I")\n\n ¡ U+0131 Latin Small Letter Dotless I ("Ä ą")\n\n ¡ U+0130 Latin Capital Letter I with Dot Above ("Ä °")\n\n\n\nIn most locales Latin Small Letter I is lower case of Latin Ca pital Letter I\, and reverse Latin Capital Letter I (U+0069) is upper case of Latin Small Letter I (U+0069). In those locales\, Latin Capital Letter I (U+0049) is also upper case of Latin Small Letter Dotless I. It could b e described as in the following chart:\n\n\n\nTable D.8. Case Relationship s for 0069\, 0049\, 0130\, and 0131\n\nCharacter\n Process\n Resulting Character\n Process\n Resulting Character\n\nLati n Small Letter I\n\nU+0069\n up case →\n Latin Capita l Letter I\n\nU+0049\n down case →\n Latin Small Lett er I\n\nU+0069\n\nLatin Small Letter Dotless I\n\nU+0131\n up case →\n Latin Capital Letter I\n\nU+0049\n down case â †’\n Latin Small Letter I\n\nU+0069\n\nLatin Capital Letter I w ith Dot Above\n\nU+0130\n down case →\n Latin Small L etter I\n\nU+0069\n up case →\n Latin Capital Letter I\n\nU+0049\n\n\n\nIn two locales\, Turkish and Azeri\, respectively\, the case relationship is different. In those two\, Latin Small Letter I and L atin Capital Letter I with Dot Above are in mutual upcase/downcase relatio nship to each other\, as well as Latin Small Letter Dotless I and Latin Ca pital Letter I\, which could be described as in the following chart:\n\n\n \nTable D.9. Case Relationships in Turkish and Azeri Locales\n\nCharacter\ n Process\n Resulting Character\n Process\n Re sulting Character\n\nLatin Small Letter I\n up case →\n Latin Capital Letter I with Dot Above\n down case →\n Latin Small Letter I\n\nLatin Small Letter Dotless I\n up case →\n Latin Capital Letter I\n down case →\n Latin Small Letter Dotless I\n\n\n\nIf we look at the repertoire of La tin code points for the root zone\, as proposed by the Latin Generation Pa nel\, Latin Small Letter I and Latin Small Letter Dotless I are included\, whereas the capital letters are excluded. Capital letters are not even va lid in IDNA2008\, so the question is\, is the case relationship described here a problem or even relevant?\n\n\n\nBefore IDNA2008\, there was IDNA20 03. Even though IDNA2003 has been replaced by IDNA2008 it is still impleme nted. For example\, the web browser Google Chrome to date remains IDNA2003 compliant but not fully IDNA 2008 compliant. In IDNA2003 there is a pre-p rocess\, normalization\, of domain names before conversion to Punycode. Th at normalization includes down casing of Latin characters. For ASCII label s there is already an equivalence between upper case and lower case letter s. And this is what users\, based on decades of experience\, expect to hap pen.\n\n\n\nIn an IDNA2003-compliant web browser it is expected that "EXĂ „MPEL" and "EXAMPLE" are equivalent to "exämpel" and "example"\, resp ectively. In an IDNA2008 browser "EXAMPLE" must be accepted\, but "EXĂ„ MPLE" could be rejected since "Ă„" is not valid\, but that is not how e .g. Mozilla Firefox and Apple Safari have been designed to handle the prob lem. They also do down case before the formal IDNA2008 process.\n\n\n\nEve n though down casing is not part of the formal IDNA2008 process\, one of t he IDNA2008 documents\, RFC 5894\, states that the user interface of an ap plication\, before IDNA2008 processing\, can do normalization. The down ca sing in IDNA2008 browsers should probably be seen in that light.\n\n\n\nWh ile "TĂ„T" will probably be down cased to "tät" in the browser\, wha t should the browser do with "TIT"? Depending on the locale that the brows er is running in\, it may be down cased to either "tit" or "tÄąt" (with or without the dot).\n\n\n\nThe casing\, in an application\, is expected t o go in one direction\, from upper case to lower case. When domain names a re presented in text\, however\, it is common that domain names are presen ted in upper or mixed case. So "ice" might become "Ice" or "Ä°ce".\n\n\n \nIt is quite obvious from the text above that case shift of dotted or dot less I could create erroneous lookup\, but the question is how large threa t it would be to the users. Since the applications are expected to go from upper case to lower case\, when they handle domain names\, we should cons ider a situation where down casing could result in different lower case le tters\, i.e. when CAPITAL LETTER I is down cased.\n\n\n\nWith a non-Turkis h and non-Azeri locale\, a Latin CAPITAL LETTER I in a domain name is eith er down cased to Latin Small Letter I (IDN label) or equivalent to Latin S mall Letter I (ASCII label).\n\n\n\nWith a Turkish or Azeri locale\, a Lat in Capital Letter I is expected to be down cased to Latin Small Letter Dot less I\, but in an ASCII label in a domain name\, it is still expected to be equivalent with Latin Small Letter I\, because that is what the DNS sta ndards says.\n\n\n\nThere is an obvious risk that\, in a Turkish or Azeri locale that the two letters are confused or mistreated due to the case fol ding\, and this confusion could be misused. To be on the safe side Latin S mall Letter I and Latin Small Letter Dotless I should be variants. Accordi ngly\, the following variant set could be the optimal solution:\n\n\n\nTab le D.10. Possible Variant Relationships for 0069 and 0131\n\n\n\nGroup\n Dotless i vs. i\n\nTarget\n Source\n Variant Candidate [Yes/No]\n Disposition [Allocatable/\n\nBlocked]\n Rational e\n\nCode Point\n Glyph\n Name\n Code Point\n Glyph\n Name\n\n0069\n i\n Latin Small Letter I\n 0131\n Äą\n Latin Small Letter Dotless I\n YES\ n Blocked\n Risk of confusion due to inconsistent case foldi ng\n\n0131\n Äą\n Latin Small Letter Dotless I\n 00 69\n i\n Latin Small Letter I\n YES\n Blocked\ n Risk of confusion due to inconsistent case folding\n\n\n\n\n\n\n\ n\n\n\n\n\n\n\n\n SUMMARY;LANGUAGE=en-US:Latin GP Meeting DTSTART;TZID=UTC:20200507T160000 DTEND;TZID=UTC:20200507T170000 UID:9B8DE6EB-D66B-4527-903D-3C0FACAFBFBE RECURRENCE-ID;TZID=UTC:20200507T160000 CLASS:PUBLIC PRIORITY:5 DTSTAMP:20200507T044526Z TRANSP:OPAQUE STATUS:CONFIRMED SEQUENCE:8 LOCATION;LANGUAGE=en-US:https://icann.zoom.us/j/95395839226?pwd=ZGxpYmRqV2E 2NjloWTFHZWNGbkJWZz09 X-MICROSOFT-CDO-APPT-SEQUENCE:8 X-MICROSOFT-CDO-OWNERAPPTID:2118355385 X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY X-MICROSOFT-CDO-ALLDAYEVENT:FALSE X-MICROSOFT-CDO-IMPORTANCE:1 X-MICROSOFT-CDO-INSTTYPE:3 X-MICROSOFT-DISALLOW-COUNTER:FALSE BEGIN:VALARM DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT15M ACTION:DISPLAY END:VALARM END:VEVENT END:VCALENDAR