April 2018 - Latingp - lists.icann.org

Variant cross-script analysis worksheets
by Tan Tanaka, Dennis May 31, 2018

May 31, 2018

Dear Latin GP, The worksheets for cross-script analysis are ready, as follows: * Cyrillic: https://docs.google.com/spreadsheets/d/1_AvaG3vgNsozyNs1Cj68HivcWmV7HRwwXz4… * Greek: https://docs.google.com/spreadsheets/d/1EK9HdI64HXvhGP8XkV9ZSZhePVRWPBxBDXI… * Armenian: https://docs.google.com/spreadsheets/d/1SpC8hHecvohEeBveFBQz0Fw7wQAxE9HG9Bu… I recommend we start with Cyrillic and Greek, as these can be worked on Google Docs directly. Armenian script support is limited to one font, so we need to decide whether to continue doing the analysis in Google Docs (preferred method because of collaboration features) or do it offline in Excel and then merge the different inputs (more work but doable, I think). CALL TO ACTION: Please respond to this email if you can help do the cross-script analysis. You can sign-up for one or for all, let me know. The mechanics is very simple: 1. Each code point needs to be inspected twice by different people. A score needs to be assigned for each font type (Times, Arial and Courier). At the end of each inspection there should be 3 distinct score inputs (Column J for first inspection or Column L for second inspection). 2. The Scoring System is defined as follows: * 1 = Identical = the two glyphs are identical in design * 2 = Nearly Identical = the two glyphs are not exactly identical, but the difference may be attributed to font design (Example: Latin “r” and Cyrillic “г”) * 3 = Distinguishable = the two glyphs are similar but distinguishable from each other * 4 = Different = self-explanatory * 5 = N/A = this means there is no variant candidate found in Latin LGR If you want to volunteer for this work please answer to this email by no later than noon Friday 27 Easter Time. I will do my best to leave the assignments before I go offline for a few days. Thank you, Dennis

6 22

AGENDA for the GP call on May, the 3rd, 2018, 16:00UTC
by Mirjana Tasić April 30, 2018

April 30, 2018

Dear GP members. Please find enclosed the proposal of Agenda for our next telephone conference. Please, give a look to the documents pointed by links in the proposed Agenda. We should try to finalize first draft of the report. Regards Mirjana AGENDA for the GP call on May, the 3rd, 2018, 16:00UTC 1. Roll call 2. Discussion about tables with code points excluded from Repertoire · ALL-CodePointsNotIncluded https://drive.google.com/open?id=1REbgfWyaAB9XeYn-MfwNZ4dXpc0OCgnYS7Mzs6J7u… * CodePointsNotIncluded-OutsideMSR https://drive.google.com/open?id=1lEvneyV9ZzkAE42FvNIHswatnndTDsIWPtYtsM4kx… · CodePointsNotIncluded-FoundInMSR2 https://docs.google.com/document/d/1oU2E-Jtq5-HF-V_idDjE2bbthFGg9afznp67zm4… 1. Discussion on further development of Final report https://docs.google.com/document/d/1Dy1zxy2vH6c-xaBMt4nqw4hfUuMN6wNAwDNPDxp… 1. AOB

1 0

Kazakhstan Is Changing Its Alphabet From Cyrillic To Latin-Based Style Favored By the West
by Tan Tanaka, Dennis April 26, 2018

April 26, 2018

I found this article interesting … do you think it is worth assessing whether our LGR proposal would serve Kazakhstan’s new alphabet? https://news.slashdot.org/story/18/04/25/2223207/kazakhstan-is-changing-its…

2 1

CALL FOR HELP: Native speakers of Latin script-based languages
by Mirjana Tasić April 20, 2018

April 20, 2018

Dear GP members, It is very important that every member of the Latin Generation Panel read and act t to our call.. Regards Mirjana Tasic Call for help: Native speakers of Latin script-based languages The Latin Generation Panel (LGP) is looking for individuals with good knowledge in languages written in Latin script, to help identify cases where the same letter could be written in two or more forms in printed text in any given language. Example Language: Marshallese Reference: https://en.m.wikipedia.org/wiki/Marshallese_language#Display_issues Evidence: https://www.dropbox.com/s/mm5rn8upi57ecwz/Marshallese%20language%20-%20Wiki… Wikipedia says (somewhat updated): In the most polished printed text, the letters Ļ ļ M̧ m̧ Ņ ņ O̧ o̧ always appear with cedillas directly beneath, and the letters Ā ā N̄ n̄ Ō ō Ū ū always appear with macrons directly above. Regardless, the diacritics are often replaced by ad hoc spellings using more common or more easily displayable characters. In particular, the Marshallese-English Online Dictionary (MOD) uses the following characters: Standard MOD Ļ M̧ Ņ N̄ O̧ Ḷ Ṃ Ṇ Ñ Ọ ļ m̧ ņ n̄ o̧ ḷ ṃ ṇ ñ ọ This means that versions of letters with diacritics (cedilla and dot below) are used interchangeably in this example: * ļ = ḷ * m̧ = ṃ * ņ = ṇ * o̧ = ọ Printed versions of the dictionary do not use letters with dots below. MOD uses letters with dots below because characters with cedilla have no precomposed form, and sometimes these characters are not displayed correctly. If you have examples in your language (i.e. two or more letters are used interchangeably in every day writing) please write to Mirjana Tasic, Chair of the Latin Generation Panel at mirjana.tasic(a)rnids.rs<mailto:mirjana.tasic@rnids.rs> or latingp(a)icann.org<mailto:latingp@icann.org>, describing your specific case along with documentation that provides evidence of use. The deadline for your submission is May 25th, 2018. More about the Latin Generation Panel here<https://community.icann.org/display/croscomlgrprocedure/Latin+GP>.

1 0

ACTION NEEDED: Last comments on mockup proposed by Denis until the end of Friday, April 20
by Mirjana Tasić April 20, 2018

April 20, 2018

Dear Latin GP, On our call of April 19 we reviewed the draft worksheet that Latin GP intends to use to capture cross-script analysis and to determine the variants with Latin script. Please kindly review the proposed draft and provide feedback no later than April, Friday 20. https://docs.google.com/spreadsheets/d/1EEDl7WruMcTxZkLJWa05PRGhw4Nc46yr-W2… Regards Mirjana

2 1

Re: [Latingp] ACTION NEEDED: Last comments on mockup proposed by Denis until the end of Friday, April 20
by Mats Dufberg April 19, 2018

April 19, 2018

Proposal is fine. Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/ From: Latingp <latingp-bounces(a)icann.org> on behalf of Mirjana Tasić <Mirjana.Tasic(a)rnids.rs> Date: Thursday 19 April 2018 at 19:23 To: ICANN Latin GP <latingp(a)icann.org> Subject: [Latingp] ACTION NEEDED: Last comments on mockup proposed by Denis until the end of Friday, April 20 Dear Latin GP, On our call of April 19 we reviewed the draft worksheet that Latin GP intends to use to capture cross-script analysis and to determine the variants with Latin script. Please kindly review the proposed draft and provide feedback no later than April, Friday 20. https://docs.google.com/spreadsheets/d/1EEDl7WruMcTxZkLJWa05PRGhw4Nc46yr-W2… Regards Mirjana

1 0

AGENDA for the GP call on April, the 19th, 2018, 16:00UTC
by Mirjana Tasić April 19, 2018

April 19, 2018

Dear GP members. Please find enclosed the proposal of Agenda for our next telephone conference. Please, give a look to the documents pointed by links in the proposed Agenda. Regards Mirjana AGENDA for the GP call on April, the 19th, 2018, 16:00UTC 1. Roll call 2. Short tutorial on using ZOOM, new communication tool 3. Proposal of the letter to the community to help us find additional in-script variant https://docs.google.com/document/d/1oi0VsAdv9UVkSGiSbFaJy_dtDA0PkRFkaK2lJZx… 1. Discussion on the Mockup document for Cross-script Analysis https://docs.google.com/spreadsheets/d/1EEDl7WruMcTxZkLJWa05PRGhw4Nc46yr-W2… 1. Discussion about tables with code points excluded from Repertoire · ALL-CodePointsNotIncluded https://drive.google.com/open?id=1REbgfWyaAB9XeYn-MfwNZ4dXpc0OCgnYS7Mzs6J7u… * CodePointsNotIncluded-OutsideMSR https://drive.google.com/open?id=1lEvneyV9ZzkAE42FvNIHswatnndTDsIWPtYtsM4kx… · CodePointsNotIncluded-FoundInMSR2 https://docs.google.com/document/d/1oU2E-Jtq5-HF-V_idDjE2bbthFGg9afznp67zm4… 1. Discussion on further development of Final report https://docs.google.com/document/d/1Dy1zxy2vH6c-xaBMt4nqw4hfUuMN6wNAwDNPDxp… 1. AOB

2 1

Re: [Latingp] Draft variants principles document - Dotless I
by Tan Tanaka, Dennis April 19, 2018

April 19, 2018

Bill, thanks for this. I have to question, though, the relevancy of your experiment. Is a visual test of running test relevant for internet identifiers? And on the subject of visual similarity, I believe this has been discussed extensively and this panel has agreed that visual similarity is outside the scope of our work. The case of the “small dotless I” and “small letter I” is interesting because of the treatment under different locale settings. The focus of our analysis should be on that, taking into account the needs and expectations of different internet users, including the Turkish community. -Dennis From: Bill Jouris <bill.jouris(a)insidethestack.com> Reply-To: Bill Jouris <bill.jouris(a)insidethestack.com> Date: Thursday, April 5, 2018 at 2:05 PM To: Dennis Tan Tanaka <dtantanaka(a)verisign.com>, Mats Dufberg <mats.dufberg(a)iis.se>, Michael Bauland <michael.bauland(a)knipp.de> Cc: Mirjana Tasić <mirjana.tasic(a)rnids.rs> Subject: [EXTERNAL] Re: [Latingp] Draft variants principles document - Dotless I I've given some more thought to the Dotless I question. It occurred to me that there are actually two approaches to the question: analysis and experiment. So I ran an experiment. Here are the results: A dozen subjects were tested. All were well-educated native speakers of English. Approximately 1/3 are involved in IT, but none are network experts and none are involved in ICANN. The subjects were given a paragraph to read (on the subject of variants). In one word, the lower case I was replaced by a dotless I. The number of subjects who noticed when reading the paragraph: Zero. The subjects were then told that the substitution had been made, that it was in the first sentence, and shown the dotless I for information. Half managed to locate the substitution in 1 or 2 re-reads of the sentence; half took 3 or more tries to spot the substitution – even though they knew what the substitution was and knew that it was there to find. In short, misreading is the expected result of a substitution. Accordingly, it is again recommended that U0069 and U0131 be determined to be blocked variants Happily, the results are the same as the analysis. I have updated the document with this information. Bill Jouris Inside Products bill.jouris(a)insidethestack.com 831-659-8360 925-855-9512 (direct) ________________________________ From: "Tan Tanaka, Dennis via Latingp" <latingp(a)icann.org> To: "Tan Tanaka, Dennis via Latingp" <latingp(a)icann.org> Sent: Thursday, April 5, 2018 9:41 AM Subject: [Latingp] Draft variants principles document Need assistance with developing the sections for special cases: https://docs.google.com/document/d/1IrT_kfildf1SumYUqjkaIkMT-TYx9IRqtuPMV4Y… Thanks, Dennis _______________________________________________ Latingp mailing list Latingp(a)icann.org<mailto:Latingp@icann.org> https://mm.icann.org/mailman/listinfo/latingp

3 3

Latin GP Meeting
by Pitinan Kooarmornpatana April 19, 2018

April 19, 2018

Dear Latin GP Members, This is a gentle reminder for the Latin GP meeting today, 19 April 2018. The agenda as follow. Kindly note that we will use Zoom for this meeting. AGENDA for the GP call on April, the 19th, 2018, 16:00UTC 1. Roll call 2. Short tutorial on using ZOOM, new communication tool 3. Proposal of the letter to the community to help us find additional in-script variant https://docs.google.com/document/d/1oi0VsAdv9UVkSGiSbFaJy_dtDA0PkRFkaK2lJZx…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> 4. Discussion on the Mockup document for Cross-script Analysis https://docs.google.com/spreadsheets/d/1EEDl7WruMcTxZkLJWa05PRGhw4Nc46yr-W2…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_spread…> 5. Discussion about tables with code points excluded from Repertoire * ALL-CodePointsNotIncluded https://drive.google.com/open?id=1REbgfWyaAB9XeYn-MfwNZ4dXpc0OCgnYS7Mzs6J7u…<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-…> * CodePointsNotIncluded-OutsideMSR https://drive.google.com/open?id=1lEvneyV9ZzkAE42FvNIHswatnndTDsIWPtYtsM4kx…<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-…> * CodePointsNotIncluded-FoundInMSR2 https://docs.google.com/document/d/1oU2E-Jtq5-HF-V_idDjE2bbthFGg9afznp67zm4…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> 6. Discussion on further development of Final report https://docs.google.com/document/d/1Dy1zxy2vH6c-xaBMt4nqw4hfUuMN6wNAwDNPDxp…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> 7. AOB Regards, Pitinan .............................................. How to connect: Join from PC, Mac, Linux, iOS or Android: https://icann.zoom.us/j/602545847 Or iPhone one-tap : US: +19294362866,,602545847# or +16699006833,,602545847# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 669 900 6833 or +1 877 853 5247 (Toll Free) or +1 877 369 0926 (Toll Free) Meeting ID: 602 545 847 International numbers available: https://zoom.us/u/bY1Dpd8bb

1 0

Latin GP Meeting
by Pitinan Kooarmornpatana April 16, 2018

April 16, 2018

Dear Latin GP Members, Please find the agenda for the Latin GP meeting as follow. Kindly note that we will use Zoom for this meeting. AGENDA for the GP call on April, the 19th, 2018, 16:00UTC 1. Roll call 2. Short tutorial on using ZOOM, new communication tool 3. Proposal of the letter to the community to help us find additional in-script variant https://docs.google.com/document/d/1oi0VsAdv9UVkSGiSbFaJy_dtDA0PkRFkaK2lJZx…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> 1. Discussion on the Mockup document for Cross-script Analysis https://docs.google.com/spreadsheets/d/1EEDl7WruMcTxZkLJWa05PRGhw4Nc46yr-W2…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_spread…> 1. Discussion about tables with code points excluded from Repertoire * ALL-CodePointsNotIncluded https://drive.google.com/open?id=1REbgfWyaAB9XeYn-MfwNZ4dXpc0OCgnYS7Mzs6J7u…<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-…> * CodePointsNotIncluded-OutsideMSR https://drive.google.com/open?id=1lEvneyV9ZzkAE42FvNIHswatnndTDsIWPtYtsM4kx…<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-…> * CodePointsNotIncluded-FoundInMSR2 https://docs.google.com/document/d/1oU2E-Jtq5-HF-V_idDjE2bbthFGg9afznp67zm4…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> 1. Discussion on further development of Final report https://docs.google.com/document/d/1Dy1zxy2vH6c-xaBMt4nqw4hfUuMN6wNAwDNPDxp…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> 1. AOB Regards, Pitinan .............................................. How to connect: Join from PC, Mac, Linux, iOS or Android: https://icann.zoom.us/j/602545847 Or iPhone one-tap : US: +19294362866,,602545847# or +16699006833,,602545847# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 669 900 6833 or +1 877 853 5247 (Toll Free) or +1 877 369 0926 (Toll Free) Meeting ID: 602 545 847 International numbers available: https://zoom.us/u/bY1Dpd8bb

1 0

cross-script analysis worksheet mockup
by Tan Tanaka, Dennis April 13, 2018

April 13, 2018

All, This is a preliminary mockup of a worksheet to capture cross-script variant candidates. The worksheet incorporates the elements we discussed in Brussels, with a caveat. I added a new Score value of 5 to denote N/A (not applicable). This is to be used when there is no single Latin candidate to compare against the target script. https://docs.google.com/spreadsheets/d/1EEDl7WruMcTxZkLJWa05PRGhw4Nc46yr-W2… I thought of different layouts but decided on this format to optimize for side-to-side comparison. Let me know your feedback in order to finalize the worksheet template. The next step is to populate the worksheets with the repertoire of the target scripts (i.e. Cyrillic, Greek and Armenian) Thanks, Dennis

1 0

Summary of Latin GP on 5 April 2018
by Pitinan Kooarmornpatana April 7, 2018

April 7, 2018

Dear Latin GP Members, Please find attached the summary of the meeting of Latin GP on 5 April 2018. Please let us know if you would like to suggest any edits or additions. Action Items S. No. Action Items Owner 1 Simplify the letter to the community calling for the information for variant. DT 2 Review the draft Principle for variant analysis and add the special cases section. ALL 3 Adjust the repertoire table in the Unicode code ascending order. SH 4 Complete the first draft of proposal to accompany the repertoire XML. MT 5 Work with the GP chair to decide the tool for the next meeting. PK This summary and the recording are 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] Draft variants principles document - Dotless I
by Tan Tanaka, Dennis April 6, 2018

April 6, 2018

During the Brussels workshop we talked about doing visual tests, etc. We asked the IP whether such tests would be acceptable to support the definition of variant sets. They replied, no. Visual confusion if out of scope. We discussed it, accepted that reality and moved on. About the Japanese case. What they told the Japanese GP is consistent what IP told us in Brussels regarding cross-script homoglyphs. So I see no problem here. Dotless I case: we were requested to analyze this case due to compatibility issues vis-à-vis IDNA2003, not on grounds of visual confusion. So, all I’m asking is to focus on the ask. -Dennis From: Mats Dufberg <mats.dufberg(a)iis.se> Date: Friday, April 6, 2018 at 5:21 AM To: Dennis Tan Tanaka <dtantanaka(a)verisign.com>, Bill Jouris <bill.jouris(a)insidethestack.com> Cc: Mirjana Tasić <mirjana.tasic(a)rnids.rs>, Latin GP <latingp(a)icann.org>, Michael Bauland <michael.bauland(a)knipp.de> Subject: [EXTERNAL] Re: [Latingp] Draft variants principles document - Dotless I Dennis, I believe that a visual test of running text is relevant for Internet identifiers. Internet identifiers are often found in running text. What Bills test shows (which is of no surprise to us) is that people have a hard time noticing minute differences of no relevance. I think we all agree that homoglyph pairs should be handled by variant rules. And that is because they are visual similar to the extreme. At the ICANN 61 meeting, the IP actually proposed to the Japanese GP that some pairs of characters from different Unicode scripts (but from a Japanese perspective belonging to the Japanese script) be treated as variants even though those character pairs are not homoglyphs. Yes, SMALL LETTER I and SMALL LETTER DOTLESS I are interesting because of the complexity of up-casing and down-casing in different locales. But if we are allowed to take upper case into consideration, there are other interesting cases. The upper case of LATIN SMALL LETTER D WITH STROKE (U+0111), LATIN SMALL LETTER ETH (U+00F0) and LATIN SMALL LETTER D WITH TAIL (U+0256) are homoglyphs which opens up for injections of "false" domains. 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: Thursday 5 April 2018 at 20:27 To: Bill Jouris <bill.jouris(a)insidethestack.com>, Mats Dufberg <mats.dufberg(a)iis.se>, Michael Bauland <michael.bauland(a)knipp.de> Cc: Mirjana Tasić <mirjana.tasic(a)rnids.rs>, ICANN Latin GP <latingp(a)icann.org> Subject: Re: [Latingp] Draft variants principles document - Dotless I Bill, thanks for this. I have to question, though, the relevancy of your experiment. Is a visual test of running test relevant for internet identifiers? And on the subject of visual similarity, I believe this has been discussed extensively and this panel has agreed that visual similarity is outside the scope of our work. The case of the “small dotless I” and “small letter I” is interesting because of the treatment under different locale settings. The focus of our analysis should be on that, taking into account the needs and expectations of different internet users, including the Turkish community. -Dennis From: Bill Jouris <bill.jouris(a)insidethestack.com> Reply-To: Bill Jouris <bill.jouris(a)insidethestack.com> Date: Thursday, April 5, 2018 at 2:05 PM To: Dennis Tan Tanaka <dtantanaka(a)verisign.com>, Mats Dufberg <mats.dufberg(a)iis.se>, Michael Bauland <michael.bauland(a)knipp.de> Cc: Mirjana Tasić <mirjana.tasic(a)rnids.rs> Subject: [EXTERNAL] Re: [Latingp] Draft variants principles document - Dotless I I've given some more thought to the Dotless I question. It occurred to me that there are actually two approaches to the question: analysis and experiment. So I ran an experiment. Here are the results: A dozen subjects were tested. All were well-educated native speakers of English. Approximately 1/3 are involved in IT, but none are network experts and none are involved in ICANN. The subjects were given a paragraph to read (on the subject of variants). In one word, the lower case I was replaced by a dotless I. The number of subjects who noticed when reading the paragraph: Zero. The subjects were then told that the substitution had been made, that it was in the first sentence, and shown the dotless I for information. Half managed to locate the substitution in 1 or 2 re-reads of the sentence; half took 3 or more tries to spot the substitution – even though they knew what the substitution was and knew that it was there to find. In short, misreading is the expected result of a substitution. Accordingly, it is again recommended that U0069 and U0131 be determined to be blocked variants Happily, the results are the same as the analysis. I have updated the document with this information. Bill Jouris Inside Products bill.jouris(a)insidethestack.com 831-659-8360 925-855-9512 (direct) ________________________________ From: "Tan Tanaka, Dennis via Latingp" <latingp(a)icann.org> To: "Tan Tanaka, Dennis via Latingp" <latingp(a)icann.org> Sent: Thursday, April 5, 2018 9:41 AM Subject: [Latingp] Draft variants principles document Need assistance with developing the sections for special cases: https://docs.google.com/document/d/1IrT_kfildf1SumYUqjkaIkMT-TYx9IRqtuPMV4Y… Thanks, Dennis _______________________________________________ Latingp mailing list Latingp(a)icann.org<mailto:Latingp@icann.org> https://mm.icann.org/mailman/listinfo/latingp

1 0

call for help letter
by Tan Tanaka, Dennis April 6, 2018

April 6, 2018

Mirjana, Revised letter https://docs.google.com/document/d/1oi0VsAdv9UVkSGiSbFaJy_dtDA0PkRFkaK2lJZx… This is now a stripped down version as discussed yesterday. The document is open for anyone to edit. -Dennis

1 0

Draft variants principles document
by Tan Tanaka, Dennis April 5, 2018

April 5, 2018

Need assistance with developing the sections for special cases: https://docs.google.com/document/d/1IrT_kfildf1SumYUqjkaIkMT-TYx9IRqtuPMV4Y… Thanks, Dennis

1 0

Latin GP Bi-weekly meeting Thursday 1600UTC
by Pitinan Kooarmornpatana April 5, 2018

April 5, 2018

Dear Latin-GP members, This is a gentle reminder for the Latin GP call on April, the 5th, 2018, 16:00UTC AGENDA 1. Roll call 2. Repertoire tables made by Sarmad's team, comments, additions, adoption 3. Proposal of the letter to the community to help us find additional in-script variant 4. Report from Variant group Draft letter to the community: https://docs.google.com/document/d/1DlGI3gBWpN3sIiY78ldsR48LhcPd6eKAP2D_ELO…<https://docs.google.com/document/d/1DlGI3gBWpN3sIiY78ldsR48LhcPd6eKAP2D_ELO…>] 5. Review and comments of final report https://docs.google.com/document/d/1Dy1zxy2vH6c-xaBMt4nqw4hfUuMN6wNAwDNPDxp…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> 6. AOB Regards, Pitinan ------------------------------ How to connect: [GlobalMeet] [https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] You're invited. You've been invited to a GlobalMeet(r) audio meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me[go.conferencinghub.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__go.conferencinghub.com…> Not at your computer? You can join by dialing one of the access numbers below. Dial in Number USA /Canada (toll free): 1-866-398-2885 Guest Passcode: 599 105 1297 Additional Access: USA: 1-605-475-5604 USA: 1-712-770-4203 USA: 1-719-457-6209 Canada, Calgary: +1 403 407 5793 Canada, Montreal: +1 514 669 5928 Canada, Toronto: +1 647 426 9172 Canada, Vancouver: +1 604 222 7836 Argentina, Buenos Aires: +54 (0) 11 5172 6003 Argentina (toll free): 0800 800 1223 Australia, Sydney: +61 (0) 2 8017 6064 Australia, Melbourne: +61 (0) 3 8687 0553 Australia, Brisbane: +61 (0) 7 3015 0535 Australia (toll free): 1 800 804 786 Austria, Vienna: +43 (0)1 928 2773 Austria (toll free): 0800 070 981 Bahrain, Manama: +973 1619 8739 Bahrain (toll free): 800 04212 Belarus (toll free): 8 820 0011 0341 Belgium, Brussels: +32 (0) 2 400 6928 Belgium (toll free): 0800 39279 Bosnia and Herzegovina: +387 7031 1442 Brazil, Sao Paulo: +55 11 4935 7169 Brazil, Rio de Janeiro: +55 21 4560 0072 Brazil (toll free): 0800 887 0233 Bulgaria, Sofia: +359 (0) 2 491 6045 Bulgaria (toll free): 00800 111 4950 Cambodia, Phnom Penh: +855 23 965 723 Canada (toll free): 1 855 950 3717 Chile, Santiago: +56 (0) 2 2666 0696 Chile (toll free): 171 800 835 783 China (national): +400 613 8103 China, Beijing: +86 10 5667 0003 China, Shanghai: +86 21 2039 7081 Colombia, Bogota: +57 1 508 8137 Colombia (toll free): 01 800 755 0102 Costa Rica (toll free): 800 542 5328 Croatia (toll free): 0800 805 940 Cyprus (toll free): 800 97424 Czech Republic, Prague: +420 225 986 554 Czech Republic (toll free): 800 701 532 Denmark, Copenhagen: +45 32 72 78 10 Denmark (toll free): 80 70 35 86 Egypt (toll free): 0800 000 0593 Estonia, Tallinn: +372 622 6551 Estonia (toll free): 800 011 1589 Fiji (toll free): 00800 3322 Finland, Helsinki: +358 (0) 9 2310 1677 Finland (toll free): 0800 772 236 France, Paris: +33 (0) 1 70 37 16 56 France (toll free): 0800 946 531 France (national): 0811 655 100 France (national): 0821 231 671 Georgia, Tbilisi: +995 32 2 050 778 Germany, Frankfurt: +49 (0) 69 2222 10612 Germany, Munich: +49 (0) 89 2030 31207 Germany (national): 01801 003 899 Germany (toll free): 0800 588 9170 Greece, Athens: +30 211 181 3824 Greece (toll free): 00800 128 913 Hong Kong: +852 3018 9111 Hong Kong (toll free): 800 901 787 Hungary, Budapest: +36 1408 8953 Hungary (toll free): 068 001 9673 Iceland (toll free): 800 9847 India, Delhi: +91 11 6310 0268 India, Mumbai: +91 22 6310 0298 India, Chennai: +91 44 6310 0234 India, Bangalore: +91 80 6760 8755 India (toll free): 1800 3010 1582 Indonesia, Jakarta: +62 21 2188 9084 Indonesia (toll free): 007 803 321 8927 Ireland, Dublin: +353 (0) 1 526 9421 Ireland (national): 0818 270 271 Ireland (toll free): 1800 937 649 Ireland (national): 1890 907 630 Israel, Tel Aviv: +972 (0)3 721 7943 Israel (toll free): 1809 213 168 Italy, Milan: +39 02 3600 8006 Italy, Rome: +39 06 8750 0676 Italy (toll free): 800 146 094 Japan, Tokyo: +81 3 4560 1270 Japan, Osaka: +81 6 4560 2410 Japan (toll free): 0120 305 211 Japan (mobile): 0120 632 611 Japan (national): 0570 085 744 Jordan (toll free): 0800 22172 Kazakhstan (toll free): 8800 333 7554 Kenya, Nairobi: +254 (0)207 643 581 South Korea, Seoul: +82 (0) 2 6007 0079 South Korea (toll free): 00798 6136 1454 Latvia, Riga: +371 6601 3627 Latvia (toll free): 8000 4418 Lithuania, Vilnius: +370 5205 5468 Lithuania (toll free): 8800 31449 Luxembourg: +352 2088 1749 Luxembourg (toll free): 800 28433 Malaysia, Kuala Lumpur: +60 (0) 3 7724 8010 Malaysia (toll free): 1 800 816 152 Mexico, Guadalajara: +52 33 4162 4504 Mexico, Mexico City: +52 55 8421 0326 Mexico, Monterrey: +52 81 4162 5648 Mexico (toll free): 01 800 733 4102 Morocco, Casablanca: +212 (0) 520 48 0022 Morocco (toll free): 0800 091 296 Netherlands, Amsterdam: +31 (0) 20 716 8345 Netherlands (toll free): 0800 020 2597 New Zealand, Christchurch: +64 (0) 3 974 2596 New Zealand, Wellington: +64 (0) 4 909 4674 New Zealand, Auckland: +64 (0) 9 929 1825 New Zealand (toll free): 0800 452 947 Nigeria, Lagos: +234 1 277 3944 Norway, Oslo: +47 21 00 48 15 Norway (toll free): 800 56081 Oman (toll free): 800 77265 Pakistan, Islamabad: +92 5181 08863 Panama, Panama City: +507 8 335 913 Panama (toll free): 00800 223 1390 Peru, Lima: +51 (0) 1 700 9571 Philippines, Manila: +63 (0)2 395 3426 Philippines (toll free): 1 800 111 013 99 Poland, Warsaw: +48 22 295 3570 Poland (toll free): 00 800 121 4356 Portugal, Lisbon: +351 21 316 4093 Portugal (toll free): 800 784 442 Qatar (freephone): 00 800 100 491 Romania, Bucharest: +40 (0) 21 529 3992 Romania (toll free): 0800 801 035 Russia, Moscow: +7 495 646 9181 Russia (toll free): 8 800 500 9241 Saudi Arabia (toll free): 800 844 6641 Saudi Arabia (toll free): 800 850 0219 Serbia (toll free): 0800 190 712 Singapore: +65 6654 9112 Singapore (toll free): 800 616 3192 Slovakia, Bratislava: +421 (0)2 3321 5498 Slovakia (toll free): 0800 002 002 Slovenia, Ljubljana: +386 1600 8695 Slovenia (toll free): 0800 81193 South Africa, Johannesburg: +27 (0)11 589 8321 South Africa (toll free): 0800 999 434 Spain, Madrid: +34 91 114 6653 Spain, Barcelona: +34 93 800 1946 Spain (toll free): 900 828 035 Sri Lanka, Sri Lanka: +94 720 910 333 Sweden, Stockholm: +46 (0) 8 5065 3956 Sweden (toll free): 0200 125 588 Switzerland, Geneva: +41 (0) 22 595 4795 Switzerland, Zurich: +41 (0) 44 580 7207 Switzerland (toll free): 0800 740 360 Taiwan, Taipei: +886 (0) 2 2650 7329 Taiwan (toll free): 0800 666 596 Thailand, Bangkok: +66 (0) 2104 0761 Thailand (toll free): 001 800 6136 1473 Tunisia, Tunis: +216 31 378 101 Turkey, Istanbul: +90 212 375 50 49 Turkey (toll free): 00800 4488 26642 Ukraine (toll free): 0800 500 896 UAE (toll free): 8000 3570 2662 UK (03): +44 (0)330 336 6002 UK (toll free): 0800 358 6385 UK (national): 0844 473 5010 UK (national): 0845 545 0015 USA /Canada (toll free): 1-866-398-2885 Uruguay (toll free): 0004 019 0152 Venezuela, Caracas: +58 212 720 2164 Venezuela (toll free): 0 800 162 7451 Vietnam, Hanoi: +84 24 4458 3312 Vietnam, Ho Chi Minh: +84 28 4458 1322 Vietnam (toll free): 1800 9226

1 0

Re: [Latingp] Agenda for the call on April the 5th, 2018
by Tan Tanaka, Dennis April 4, 2018

April 4, 2018

Mirjana, Draft letter to the community: https://docs.google.com/document/d/1DlGI3gBWpN3sIiY78ldsR48LhcPd6eKAP2D_ELO… -Dennis From: Latingp <latingp-bounces(a)icann.org> on behalf of Mirjana Tasić <Mirjana.Tasic(a)rnids.rs> Date: Tuesday, April 3, 2018 at 5:09 PM To: Latin GP <latingp(a)icann.org> Subject: [EXTERNAL] [Latingp] Agenda for the call on April the 5th, 2018 Dear GP members. Please find enclosed the proposal of Agenda for our next telephone conference. It will be good if all members look at the Repertoire tables made by Sarmad’s team. Regards Mirjana AGENDA for the GP call on April, the 5th, 2018, 16:00UTC 1. Roll call 2. Repertoire tables made by Sarmad’s team, comments, additions, adoption 3. Proposal of the letter to the community to help us find additional in-script variant 4. Report from Variant group 5. Review and comments of final report https://docs.google.com/document/d/1Dy1zxy2vH6c-xaBMt4nqw4hfUuMN6wNAwDNPDxp… 6. AOB

1 0

Agenda for the call on April the 5th, 2018
by Mirjana Tasić April 3, 2018

April 3, 2018

Dear GP members. Please find enclosed the proposal of Agenda for our next telephone conference. It will be good if all members look at the Repertoire tables made by Sarmad’s team. Regards Mirjana AGENDA for the GP call on April, the 5th, 2018, 16:00UTC 1. Roll call 2. Repertoire tables made by Sarmad’s team, comments, additions, adoption 3. Proposal of the letter to the community to help us find additional in-script variant 4. Report from Variant group 5. Review and comments of final report https://docs.google.com/document/d/1Dy1zxy2vH6c-xaBMt4nqw4hfUuMN6wNAwDNPDxp… 6. AOB

1 0