April 2018 - Idngwg - lists.icann.org

Re: [Idngwg] IMPORTANT: FINAL CALL for IDN Guidelines version 4.0
by Tan Tanaka, Dennis April 28, 2018

April 28, 2018

Some minor edits/comments enclosed. Thanks, Dennis From: Idngwg <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Friday, April 27, 2018 at 8:17 AM To: "idngwg(a)icann.org" <idngwg(a)icann.org> Subject: [EXTERNAL] [Idngwg] IMPORTANT: FINAL CALL for IDN Guidelines version 4.0 Dear IDNGWG members, Following the agreement of IDNGWG members on 26 April 2018 on the draft IDN Guidelines, this is the FINAL CALL announcement for any feedback before confirming the “Final Draft of IDN Implementation Guidelines ver. 4.0”. You are all requested to please review the attached document in detail and provide any final feedback by 4 May 2018. As next steps, unless there are substantive changes proposed which are not addressed online, ICANN staff will proceed to finalize the guidelines document and share it with RySG, RrSG, and ccNSO. ICANN staff will also formally send the document to ICANN org for publication and for further processing to implement these guidelines. We look forward to your feedback. Regards, Sarmad

2 1

IMPORTANT: FINAL CALL for IDN Guidelines version 4.0
by Sarmad Hussain April 27, 2018

April 27, 2018

Dear IDNGWG members, Following the agreement of IDNGWG members on 26 April 2018 on the draft IDN Guidelines, this is the FINAL CALL announcement for any feedback before confirming the "Final Draft of IDN Implementation Guidelines ver. 4.0". You are all requested to please review the attached document in detail and provide any final feedback by 4 May 2018. As next steps, unless there are substantive changes proposed which are not addressed online, ICANN staff will proceed to finalize the guidelines document and share it with RySG, RrSG, and ccNSO. ICANN staff will also formally send the document to ICANN org for publication and for further processing to implement these guidelines. We look forward to your feedback. Regards, Sarmad

1 1

Cover notes for sharing IDN Guidelines - please respond by 3 May
by Sarmad Hussain April 27, 2018

April 27, 2018

Dear All, Please find attached the cover notes for RySG, RrSG and ccNSO chairs, to share the final draft of the IDN Guidelines with them. Please also find attached the note to be sent to ICANN org. As suggested, these will go from Edmon and Mats, on behalf of IDNGWG. I will send these notes out, with cc: to the IDNGWG, after IDNGWG has concluded the FINAL CALL - likely on 7 May 2018. Please let us know if you would like to send this to any other recipients or would like to suggest any edits to these communications. Please respond by 3 May 2018 for us to finalize any edits in time for 7 May. Regards, Sarmad From: Idngwg [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Friday, April 27, 2018 3:18 PM To: idngwg(a)icann.org Subject: [Idngwg] IDN Guidelines WG meeting on 20180426 Dear IDNGWG Members, Please find attached the notes from the meeting on 26 April 2018. Please let us know if you have any feedback. Please also find attached the latest version of the document with redline, incorporating the changes suggested during the call. Based on the action items, I will shortly circulate the clean version of this document for the final call, along with the cover letters for the SGs/SO and ICANN org. Action items: S. No. Action Items Owner 1 Update the Additional Note VI based on feedback SH 2 Circulate the final version for FINAL CALL on email list for one week as planned SH 3 Circulate the cover notes for RrSG, RySG and ccNSO based on the cover note agreed for ICANN org, noting this is for information and no further action is needed at this time SH 4 After the final call, proceed with further steps for the guidelines, including their publication as the final draft to be approved by the Board. No additional IDNGWG meeting is needed unless there are substantive comments during FINAL CALL which are not addressed online SH The recording of the call and its summary are also available at the IDN Guidelines wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines[commu…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>. Regards, Sarmad

1 0

IDN Guidelines WG meeting on 20180426
by Sarmad Hussain April 27, 2018

April 27, 2018

Dear IDNGWG Members, Please find attached the notes from the meeting on 26 April 2018. Please let us know if you have any feedback. Please also find attached the latest version of the document with redline, incorporating the changes suggested during the call. Based on the action items, I will shortly circulate the clean version of this document for the final call, along with the cover letters for the SGs/SO and ICANN org. Action items: S. No. Action Items Owner 1 Update the Additional Note VI based on feedback SH 2 Circulate the final version for FINAL CALL on email list for one week as planned SH 3 Circulate the cover notes for RrSG, RySG and ccNSO based on the cover note agreed for ICANN org, noting this is for information and no further action is needed at this time SH 4 After the final call, proceed with further steps for the guidelines, including their publication as the final draft to be approved by the Board. No additional IDNGWG meeting is needed unless there are substantive comments during FINAL CALL which are not addressed online SH The recording of the call and its summary are also available at the IDN Guidelines wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Regards, Sarmad

1 0

Today's meeting
by Mats Dufberg April 26, 2018

April 26, 2018

I'm sorry, I cannot attend today's meeting. Yours Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899<tel:+46%2073%20065%203899> https://www.iis.se/en/<http://www.iis.se/en>

1 0

IDN Guideline WG meeting
by Sarmad Hussain April 26, 2018

April 26, 2018

Hi All, A gentle reminder that we will meet today to aim to finalize the IDN Guidelines document during the meeting today, so your participation is requested. We will use the Zoom account today, with the following details: Join from PC, Mac, Linux, iOS or Android: https://icann.zoom.us/j/946639309?pwd=f1w5IRUdJXg Password: IDNGWG Or iPhone one-tap : US: +19294362866,,946639309# or +16699006833,,946639309# 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) Hong Kong: +852 5808 6088 or 800 906 780 (Toll Free) India: +91 22 48 798 004 or 1 800 102 9182 (Toll Free) Australia: +61 (0) 2 8015 2088 or +61 18 0089 3423 (Toll Free) Pakistan: +92 21 3879 9843 Sweden: +46 (0) 8 4468 2488 or +46 20 889 860 (Toll Free) Meeting ID: 946 639 309 International numbers available: https://zoom.us/u/DsJ8t18H Regards, Sarmad

1 0

IDN Guidelines WG meeting on 20180419
by Sarmad Hussain April 21, 2018

April 21, 2018

Please find attached the notes from the meeting on 19 April 2018. Please let us know if you have any feedback. Please also find attached the latest version of the document. I have accepted all the changes from before, except those still not discussed and those newly added, for our discussion in the call. Kindly review the newly added Additional Notes and share any edits you would like to propose. Action items: S. No. Action Items Owner 1 Draft a note for including Chinese language having a practice of automatic activation. SH 2 Draft a note stating that relevant "common" and "inherited" script code point are not prevented from use due to the restriction on script mixing SH 3 Include a note for listing Chinese Japanese and Korean languages as examples which mix scripts with Latin "a-z". In addition, Japanese included as it mixes Hiragana, Katakana and Han scripts SH The recording of the call and its summary are also available at the IDN Guidelines wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Regards, Sarmad

1 1

Re: [Idngwg] latest draft of the IDN Guidelines 4.0
by Mats Dufberg April 19, 2018

April 19, 2018

Friends, I am sorry for my absense on last meeting and in communication. I have looked at guidelines 12, 15 and 16. I think it is hard to add references to specific languages in a good way, so I suggest that 12 and 16 are kept as-is. When it comes to 15 the sentence "All code points in a single label must be taken from the same Unicode script" is problematic since it is very common to combine letter with European numbers or hyphen, and they come from another script (COMMON). I suggest that we add the following sentence at the end of 15: "This guideline also accepts the use of selected codepoints of Unicode script Common or Inherited when such code points are suitable for the language or Unicode script of the IDN table." The enclosed word file contains that update to draft 3.4. Talk to you in a while. Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/ From: Idngwg <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Thursday 19 April 2018 at 08:00 To: idngwg <idngwg(a)icann.org> Subject: [Idngwg] latest draft of the IDN Guidelines 4.0 Dear All, Please find the updated version 3.4 of the document, with the suggested changes incorporated. Regards, Sarmad From: Idngwg [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Wednesday, April 18, 2018 8:27 PM To: Feher, Kal <Kalman.Feher(a)team.neustar>; Tan Tanaka, Dennis <dtantanaka(a)verisign.com>; idngwg(a)icann.org Subject: Re: [Idngwg] [EXTERNAL] Re: Harmonization of Variant Sets Thank you Dennis and Kal. If there is no further feedback on this, I will update the guidelines by removing the yellow highlighted portions shared earlier, removing the same-script requirement. We can finalize during the call tomorrow. Regards, Sarmad From: Feher, Kal [mailto:Kalman.Feher@team.neustar] Sent: Wednesday, April 18, 2018 6:20 AM To: Tan Tanaka, Dennis <dtantanaka(a)verisign.com<mailto:dtantanaka@verisign.com>>; Sarmad Hussain <sarmad.hussain(a)icann.org<mailto:sarmad.hussain@icann.org>>; idngwg(a)icann.org<mailto:idngwg@icann.org> Subject: [Ext] Re: [EXTERNAL] Re: [Idngwg] Harmonization of Variant Sets I agree that removing the "same script|particular script" qualifiers will correctly convey the intent for guideline 13. I think that guideline 17 complements the harmonisation advice by ensuring that confusables, including pre-composed/decomposed representations, are considered across scripts. My reading of TR39 suggests that the two cases described would be covered in principle. -- Kal Feher Melbourne, Australia Neustar From: Idngwg <idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org>> on behalf of "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Reply-To: "Tan Tanaka, Dennis" <dtantanaka(a)verisign.com<mailto:dtantanaka@verisign.com>> Date: Wednesday, 18 April 2018 at 05:27 To: Sarmad Hussain <sarmad.hussain(a)icann.org<mailto:sarmad.hussain@icann.org>>, "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: [EXTERNAL] Re: [Idngwg] Harmonization of Variant Sets Another way to look at this (at least I do) is to consider two uses cases: -use case 1: two (or more) IDN tables, same script -use case 2: two (or more) IDN tables, different scripts The core of the guideline is to harmonize variant rules (i.e. ensure symmetry and transitivity) across all IDN tables under a TLD. I think we were thinking Japanese and Chinese (at least I was) when we discussed the detail and final language. I don’t think it was our intention to discriminate same script vs cross-script. In this sense, it make sense to remove the “same script” qualifier. -Dennis From: Idngwg <idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org>> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org<mailto:sarmad.hussain@icann.org>> Date: Thursday, April 12, 2018 at 8:46 AM To: "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: [EXTERNAL] [Idngwg] Harmonization of Variant Sets Dear All, As discussed in the call today, here is a brief document discussing the harmonization of variant sets. The “same-script IDN tables” in the guidelines allows for the examples in the document. Additional guidelines on cross-script labels would prevent cross-script issues implicitly. However, if the WG considers to make it explicit, it could be done by, for example, removing the yellow highlighted text in the attached document. Regards, Sarmad

1 0

latest draft of the IDN Guidelines 4.0
by Sarmad Hussain April 19, 2018

April 19, 2018

Dear All, Please find the updated version 3.4 of the document, with the suggested changes incorporated. Regards, Sarmad From: Idngwg [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Wednesday, April 18, 2018 8:27 PM To: Feher, Kal <Kalman.Feher(a)team.neustar>; Tan Tanaka, Dennis <dtantanaka(a)verisign.com>; idngwg(a)icann.org Subject: Re: [Idngwg] [EXTERNAL] Re: Harmonization of Variant Sets Thank you Dennis and Kal. If there is no further feedback on this, I will update the guidelines by removing the yellow highlighted portions shared earlier, removing the same-script requirement. We can finalize during the call tomorrow. Regards, Sarmad From: Feher, Kal [mailto:Kalman.Feher@team.neustar] Sent: Wednesday, April 18, 2018 6:20 AM To: Tan Tanaka, Dennis <dtantanaka(a)verisign.com<mailto:dtantanaka@verisign.com>>; Sarmad Hussain <sarmad.hussain(a)icann.org<mailto:sarmad.hussain@icann.org>>; idngwg(a)icann.org<mailto:idngwg@icann.org> Subject: [Ext] Re: [EXTERNAL] Re: [Idngwg] Harmonization of Variant Sets I agree that removing the "same script|particular script" qualifiers will correctly convey the intent for guideline 13. I think that guideline 17 complements the harmonisation advice by ensuring that confusables, including pre-composed/decomposed representations, are considered across scripts. My reading of TR39 suggests that the two cases described would be covered in principle. -- Kal Feher Melbourne, Australia Neustar From: Idngwg <idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org>> on behalf of "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Reply-To: "Tan Tanaka, Dennis" <dtantanaka(a)verisign.com<mailto:dtantanaka@verisign.com>> Date: Wednesday, 18 April 2018 at 05:27 To: Sarmad Hussain <sarmad.hussain(a)icann.org<mailto:sarmad.hussain@icann.org>>, "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: [EXTERNAL] Re: [Idngwg] Harmonization of Variant Sets Another way to look at this (at least I do) is to consider two uses cases: -use case 1: two (or more) IDN tables, same script -use case 2: two (or more) IDN tables, different scripts The core of the guideline is to harmonize variant rules (i.e. ensure symmetry and transitivity) across all IDN tables under a TLD. I think we were thinking Japanese and Chinese (at least I was) when we discussed the detail and final language. I don’t think it was our intention to discriminate same script vs cross-script. In this sense, it make sense to remove the “same script” qualifier. -Dennis From: Idngwg <idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org>> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org<mailto:sarmad.hussain@icann.org>> Date: Thursday, April 12, 2018 at 8:46 AM To: "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: [EXTERNAL] [Idngwg] Harmonization of Variant Sets Dear All, As discussed in the call today, here is a brief document discussing the harmonization of variant sets. The “same-script IDN tables” in the guidelines allows for the examples in the document. Additional guidelines on cross-script labels would prevent cross-script issues implicitly. However, if the WG considers to make it explicit, it could be done by, for example, removing the yellow highlighted text in the attached document. Regards, Sarmad

1 0

Re: [Idngwg] Harmonization of Variant Sets
by Tan Tanaka, Dennis April 18, 2018

April 18, 2018

Another way to look at this (at least I do) is to consider two uses cases: -use case 1: two (or more) IDN tables, same script -use case 2: two (or more) IDN tables, different scripts The core of the guideline is to harmonize variant rules (i.e. ensure symmetry and transitivity) across all IDN tables under a TLD. I think we were thinking Japanese and Chinese (at least I was) when we discussed the detail and final language. I don’t think it was our intention to discriminate same script vs cross-script. In this sense, it make sense to remove the “same script” qualifier. -Dennis From: Idngwg <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Thursday, April 12, 2018 at 8:46 AM To: "idngwg(a)icann.org" <idngwg(a)icann.org> Subject: [EXTERNAL] [Idngwg] Harmonization of Variant Sets Dear All, As discussed in the call today, here is a brief document discussing the harmonization of variant sets. The “same-script IDN tables” in the guidelines allows for the examples in the document. Additional guidelines on cross-script labels would prevent cross-script issues implicitly. However, if the WG considers to make it explicit, it could be done by, for example, removing the yellow highlighted text in the attached document. Regards, Sarmad

3 2