October 2017 - Idngwg - lists.icann.org

FW: [Ext] ICANN News Alert -- Internationalized Domain Name (IDN) Implementation Guidelines – Second Public Comment
by Sarmad Hussain Oct. 22, 2017

Oct. 22, 2017

Dear all, The following ICANN news alert went out recently announcing the posting of IDN Guidelines for the second public comment. Here are the relevant links for your record. - Announcement: https://www.icann.org/news/announcement-2017-10-19-en - Public Comment: https://www.icann.org/public-comments/idn-guidelines-2017-10-19-en - Draft IDN Guidelines: https://www.icann.org/en/system/files/files/draft-final-idn-guidelines-18oc… Please help circulate to the relevant individuals and community lists. I will also forward to the individuals who have provided the feedback in the first round. Thank you all for your continued contribution to this effort. Regards, Sarmad News Alert https://www.icann.org/news/announcement-2017-10-19-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ Internationalized Domain Name (IDN) Implementation Guidelines – Second Public Comment 19 October 2017 Open Date: 19 October 2017 Close Date: 10 December 2017 Originating Organization: Global Domains Division Categories/Tags: Second-Level Domains Brief Overview: The Internationalized Domain Name (IDN) Implementation Guidelines relate to the IDN registration policies and practices, designed to minimize the risk of cybersquatting and consumer confusion, to cater to the interests of communities using local languages and scripts. Following the Call for Community Experts[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…>, a Working Group (WG) was formed in October 2015 to review the current version (3.0[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>) of the IDN Implementation Guidelines[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, last updated in 2011. The WG updated the Guidelines and conducted the first public comment[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> on them in March 2017. Based on the feedback received from the community, the WG has further updated the draft guidelines. The WG is releasing the latest draft version of the IDN Implementation Guidelines 4.0[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 316 KB] to get general feedback as well as response to some specific queries highlighted in this draft. Based on responses, the WG will finalize the Guidelines. Link: https://www.icann.org/public-comments/idn-guidelines-2017-10-19-en[icann.or…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…>

1 0

Final Draft of Guidelines for Second Public Comment - for your record
by Sarmad Hussain Oct. 19, 2017

Oct. 19, 2017

Thank you all for responding. I have also received and “ok to proceed” from Edmon. The attached clean version is being forwarded to public comment today. Regards, Sarmad From: sb.inapp(a)gmail.com [mailto:sb.inapp@gmail.com] On Behalf Of Satish Babu Sent: Thursday, October 19, 2017 8:04 AM To: Feher, Kal <Kalman.Feher(a)team.neustar> Cc: Sarmad Hussain <sarmad.hussain(a)icann.org>; Tan Tanaka, Dennis <dtantanaka(a)verisign.com>; idngwg(a)icann.org Subject: Re: [Idngwg] [EXTERNAL] Re: [Ext] Re: Update draft + PC2 call + ICANN 60 presentations I am ok with the latest version. satish On Thu, Oct 19, 2017 at 3:26 AM, Feher, Kal via Idngwg <idngwg(a)icann.org<mailto:idngwg@icann.org>> wrote: I'm fine with the latest version. Kal Feher Neustar Inc. Level 8, 10 Queens Road, Melbourne, Australia VIC 3004 Office +61 3 9866 3710 / kal.feher(a)team.neustar<mailto:kal.feher@team.neustar> / www.neustar.biz[neustar.biz]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.neustar.biz_&d=DwMF…> Follow Neustar: [http://neunet.neustar.biz/sites/default/files/295/New%20Picture.png] Facebook[facebook.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_neusta…> [http://neunet.neustar.biz/sites/default/files/295/New%20Picture%20(1)(1).png] LinkedIn[linkedin.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_compan…> [http://neunet.neustar.biz/sites/default/files/295/New%20Picture%20(2).png] Twitter[twitter.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_neustar…> ________________________________ The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message. From: <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, 19 October 2017 at 07:56 To: "Tan Tanaka, Dennis" <dtantanaka(a)verisign.com<mailto:dtantanaka@verisign.com>>, "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: [EXTERNAL] Re: [Idngwg] [Ext] Re: Update draft + PC2 call + ICANN 60 presentations Dear WG members, We have not heard back from other members. Please advise if we are ready to proceed with the public comment announcement or you would need more time for review. Regards, Sarmad From: idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Wednesday, October 18, 2017 12:45 AM To: Tan Tanaka, Dennis <dtantanaka(a)verisign.com<mailto:dtantanaka@verisign.com>>; idngwg(a)icann.org<mailto:idngwg@icann.org> Subject: Re: [Idngwg] [Ext] Re: Update draft + PC2 call + ICANN 60 presentations Thank you Dennis and sorry for the confusion caused due to the two versions. I have taken the version with your feedback and added the PC2 paragraph in the beginning to represent the complete document. I am attaching the latest version which we will take forward. I will incorporate any feedback sent in by others on this or any of the earlier versions circulated. Looking forward to any final feedback. Regards, Sarmad From: Tan Tanaka, Dennis [mailto:dtantanaka@verisign.com] Sent: Wednesday, October 18, 2017 12:17 AM To: Sarmad Hussain <sarmad.hussain(a)icann.org<mailto:sarmad.hussain@icann.org>>; idngwg(a)icann.org<mailto:idngwg@icann.org> Subject: [Ext] Re: [Idngwg] Update draft + PC2 call + ICANN 60 presentations Sarmad, I did minor edits to the version enclosed, then I noticed there was another version with the added PC2 paragraph (i.e. nic chile and “x” question). I’m good with this addition. Thank you, Dennis From: <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: Monday, October 16, 2017 at 4:44 AM To: "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: [EXTERNAL] Re: [Idngwg] Update draft + PC2 call + ICANN 60 presentations Dear All, In drafting the explanation for “uniform” in Guideline 13 in the Additional Note II, we should consider another scenario not yet captured but needed in the uniform treatment of variants across the IDN Tables. Thus, I have suggested additional text in the Additional Note II (ii) in the updated version 2.9-redline attached. As an explanation, consider the scenario: Suppose a registry creates two IDN Tables, one exclusively for Traditional Chinese and other exclusively for Simplified Chinese. If the additional text is not there the registry could potentially allocate the TC and SC versions of labels to different registrants. With the proposed text, the variant code points will need to be reviewed for both SC and TC together so even with such IDN Tables, the variant labels for SC and TC will go to the same registrant. The same case can occur in Arabic script. If we have Arabic Kaf (‘k’ كU+0643) in Arabic language table and Persian Kaf (‘k’ کU+06A9) in Persian language table, then the identical labels کتابandكتاب (kitab – book) could be allocated to different registrants. If these are harmonized to be uniform, as described, such cases will be prevented. This case does not seem to be captured elsewhere in the guidelines. I think this was originally intended, but when we specified the definition of “uniform”, we did not capture this part. Kindly see if this version 2.9 is agreeable to proceed (with any further edits suggested) or should we take version 2.8 further. Regards, Sarmad From:idngwg-bounces@icann.org<mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Sunday, October 15, 2017 1:11 PM To: idngwg(a)icann.org<mailto:idngwg@icann.org> Subject: [Idngwg] Update draft + PC2 call + ICANN 60 presentations Dear All, Thank you for the amazing work all of you have done in finalizing the Guidelines document! As discussed, we will conduct a second public comment on this document. Following the IDNGWG meeting on 12 October, please find attached the following: 1. Call for second public comment (PC2) 2. Updated draft of the guidelines (updated redline version + PC2 clean version) 3. Updated ICANN 60 presentations (detailed for 90 min session on 29 Oct. + short for 7 minute update on 1 Nov.) (corresponding PDF versions also attached on request) I have added only two specific questions at the top of the guidelines document: one on scope and other on value of X. Kindly confirm that these are Ok, and please share if you would like to add any additional specific questions? As discussed, second public comment call and corresponding document will be sent in for publication on 18 October, so please share any feedback before 0500 UTC 18 Oct (please make changes directly in the documents). It will be useful to get your confirmation even if you do not have any suggested changes. As usual, the recording of the call is available at the wiki page https://community.icann.org/display/IDN/IDN+Implementation+Guidelines[commu…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> and the notes will also be available there soon. Regards, Sarmad _______________________________________________ Idngwg mailing list Idngwg(a)icann.org<mailto:Idngwg@icann.org> https://mm.icann.org/mailman/listinfo/idngwg

2 1

Re: [Idngwg] Update draft + PC2 call + ICANN 60 presentations
by Tan Tanaka, Dennis Oct. 19, 2017

Oct. 19, 2017

Sarmad, I did minor edits to the version enclosed, then I noticed there was another version with the added PC2 paragraph (i.e. nic chile and “x” question). I’m good with this addition. Thank you, Dennis From: <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Monday, October 16, 2017 at 4:44 AM To: "idngwg(a)icann.org" <idngwg(a)icann.org> Subject: [EXTERNAL] Re: [Idngwg] Update draft + PC2 call + ICANN 60 presentations Dear All, In drafting the explanation for “uniform” in Guideline 13 in the Additional Note II, we should consider another scenario not yet captured but needed in the uniform treatment of variants across the IDN Tables. Thus, I have suggested additional text in the Additional Note II (ii) in the updated version 2.9-redline attached. As an explanation, consider the scenario: Suppose a registry creates two IDN Tables, one exclusively for Traditional Chinese and other exclusively for Simplified Chinese. If the additional text is not there the registry could potentially allocate the TC and SC versions of labels to different registrants. With the proposed text, the variant code points will need to be reviewed for both SC and TC together so even with such IDN Tables, the variant labels for SC and TC will go to the same registrant. The same case can occur in Arabic script. If we have Arabic Kaf (‘k’ ك U+0643) in Arabic language table and Persian Kaf (‘k’ ک U+06A9) in Persian language table, then the identical labels کتاب and كتاب (kitab – book) could be allocated to different registrants. If these are harmonized to be uniform, as described, such cases will be prevented. This case does not seem to be captured elsewhere in the guidelines. I think this was originally intended, but when we specified the definition of “uniform”, we did not capture this part. Kindly see if this version 2.9 is agreeable to proceed (with any further edits suggested) or should we take version 2.8 further. Regards, Sarmad From: idngwg-bounces(a)icann.org [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Sunday, October 15, 2017 1:11 PM To: idngwg(a)icann.org Subject: [Idngwg] Update draft + PC2 call + ICANN 60 presentations Dear All, Thank you for the amazing work all of you have done in finalizing the Guidelines document! As discussed, we will conduct a second public comment on this document. Following the IDNGWG meeting on 12 October, please find attached the following: 1. Call for second public comment (PC2) 2. Updated draft of the guidelines (updated redline version + PC2 clean version) 3. Updated ICANN 60 presentations (detailed for 90 min session on 29 Oct. + short for 7 minute update on 1 Nov.) (corresponding PDF versions also attached on request) I have added only two specific questions at the top of the guidelines document: one on scope and other on value of X. Kindly confirm that these are Ok, and please share if you would like to add any additional specific questions? As discussed, second public comment call and corresponding document will be sent in for publication on 18 October, so please share any feedback before 0500 UTC 18 Oct (please make changes directly in the documents). It will be useful to get your confirmation even if you do not have any suggested changes. As usual, the recording of the call is available at the wiki page https://community.icann.org/display/IDN/IDN+Implementation+Guidelines[commu…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> and the notes will also be available there soon. Regards, Sarmad

4 4

Update draft + PC2 call + ICANN 60 presentations
by Sarmad Hussain Oct. 17, 2017

Oct. 17, 2017

Dear All, Thank you for the amazing work all of you have done in finalizing the Guidelines document! As discussed, we will conduct a second public comment on this document. Following the IDNGWG meeting on 12 October, please find attached the following: 1. Call for second public comment (PC2) 2. Updated draft of the guidelines (updated redline version + PC2 clean version) 3. Updated ICANN 60 presentations (detailed for 90 min session on 29 Oct. + short for 7 minute update on 1 Nov.) (corresponding PDF versions also attached on request) I have added only two specific questions at the top of the guidelines document: one on scope and other on value of X. Kindly confirm that these are Ok, and please share if you would like to add any additional specific questions? As discussed, second public comment call and corresponding document will be sent in for publication on 18 October, so please share any feedback before 0500 UTC 18 Oct (please make changes directly in the documents). It will be useful to get your confirmation even if you do not have any suggested changes. As usual, the recording of the call is available at the wiki page https://community.icann.org/display/IDN/IDN+Implementation+Guidelines and the notes will also be available there soon. Regards, Sarmad

1 2

Canceled: IDN Guidelines WG meeting - weekly on Thursdays 11am UTC -18 May onwards till the Guidelines are finalized
by Sarmad Hussain Oct. 16, 2017

Oct. 16, 2017

(extending IDNGWG meetings till ICANN 60) IDN Meeting room: 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-… Participant Passcode: 1064158692

1 0

Summary of IDNGWG meeting on 12 October 2017
by Pitinan Kooarmornpatana Oct. 15, 2017

Oct. 15, 2017

Dear IDNGWG members, Please find attached the summary of the meeting of the IDNGWG held on 12 October 2017. Please let us know if you would like to suggest any edits or additions. Action Items S. No. Action Items Owner 1 Update the Guidelines and the presentations for ICANN 60 as discussed by the WG. SH 2 Draft the Public Comment call and circulate via mailing list before 16 Oct. 2017. SH 3 Review revised materials by 18 Oct. 2017 All Members 4 Publish updated version for Public Comment on 18 Oct. 2017 SH The recording and this summary are also posted at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> Please be noted that the summary of the meeting of the IDNGWG held on 5 October 2017 was updated and posted in the wiki page. Regards, Pitinan

1 0

IDN Guidelines WG meeting - weekly on Thursdays 11am UTC -18 May onwards till the Guidelines are finalized
by Sarmad Hussain Oct. 12, 2017

Oct. 12, 2017

Dear All, A gentle reminder for today's meeting to finalize the guidelines. Regards, Sarmad IDN Meeting room: 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-… Participant Passcode: 1064158692

1 0

Today's meeting 2017-10-12
by Mats Dufberg Oct. 12, 2017

Oct. 12, 2017

I am sorry, I cannot attend today's meeting. Yours, Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/

1 0

Updated draft of Guidelines following the call on 5 October 2017
by Sarmad Hussain Oct. 9, 2017

Oct. 9, 2017

Dear All, Thank you to those who attended the three-hour long call on 5 October. We were able to complete the first pass and do a whole second pass on the guidelines, to finalize the document. The call recording is available at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. (please note that because we deleted guideline 5, the guideline numbers are readjusted accordingly in the updated version attached and will not match with those called out in the recording) As discussed, please find attached an updated redline version of the document, in which older changes and comments have been accepted and only changes in the recent meeting are now reflected for easier review. In addition a clean version of the same version is also generated. Both versions are attached in docx and pdf formats. Please read through these changes and share any final feedback over email. We will finalize these revisions in the next call and then share the updated version with the community before ICANN 60. Thank you again for all the hard work over the past many months. This work will be really beneficial in the implementation of IDNs. Regards, Sarmad From: idngwg-bounces(a)icann.org [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Thursday, October 05, 2017 7:13 PM To: idngwg(a)icann.org Subject: [Idngwg] Chat log from today's call Dear All, Here is the chat log from today's call. Regards, Sarmad ----------------- (10/05/2017 16:04) ----------------- Kal Feher: yes Mats Dufberg: Satish, do you access to Adobe and can see the document? Satish Babu: Yes, I can see the document. ----------------- (10/05/2017 16:06) ----------------- Satish Babu: I can do two hours... Kal Feher: yes. I should. I may need to step away briefly Kal Feher: yes Satish Babu: Ok ----------------- (10/05/2017 16:36) ----------------- Dennis Tan: I'm not connected from my desk. Sorry I couldn't speak earlier. It was difficult to find a safe time to unmute my phone. Dennis Tan: I mean to say "I am connected" :) Pitinan Kooarmornpatana: :) ----------------- (10/05/2017 16:49) ----------------- Satish Babu: Yes, let's park it for now. Sarmad Hussain: I can suggest during the break Dennis Tan: Thanks Sarmad ----------------- (10/05/2017 16:56) ----------------- Dennis Tan: Have to step away for a few min ----------------- (10/05/2017 17:00) ----------------- Satish Babu: No comments for now... Dennis Tan: I'm back Satish Babu: (yes, ok with the suggested additions) ----------------- (10/05/2017 17:08) ----------------- Kal Feher: yes. they are all optional ----------------- (10/05/2017 17:10) ----------------- Kal Feher: it is ok if the information is not relevant ----------------- (10/05/2017 17:13) ----------------- Satish Babu: In my opinion, 'should' is slightly stronger than optional Dennis Tan: should = used to give or ask advice or suggestions Dennis Tan: other definition = indicating a desirable or expected state ----------------- (10/05/2017 17:19) ----------------- Kal Feher: yes Satish Babu: Agree. ----------------- (10/05/2017 17:29) ----------------- Satish Babu: Ok Mats Dufberg: Back again at 12:44 UTC. ----------------- (10/05/2017 17:44) ----------------- Mats Dufberg: I am back. Dennis Tan: I'm here Satish Babu: I'm back too Sarmad Hussain: Within-script homoglyphsTLD registries are encouraged to consider policies to minimize confusion of IDN labels with other labels within the same script, especially arising due to homoglyphic characters. Also see Additonal Note IV. Sarmad Hussain: should we start? ----------------- (10/05/2017 17:48) ----------------- Dennis Tan: I would change "especially" with "specifically" ----------------- (10/05/2017 17:49) ----------------- Kal Feher: Agree with Dennis and I'm ok with the text ----------------- (10/05/2017 17:54) ----------------- Satish Babu: This looks fine. Kal Feher: it should remain a note. ----------------- (10/05/2017 18:03) ----------------- Kal Feher: agree with Sarmad. the RA uses "allocate" to mean domains which can be registered Satish Babu: Yes, it does make sense. ----------------- (10/05/2017 18:06) ----------------- Mats Dufberg: 1.2 Scope Mats Dufberg: These Guidelines only concerns registred names. ----------------- (10/05/2017 18:08) ----------------- Kal Feher: could you clarify the section pls? ----------------- (10/05/2017 18:11) ----------------- Satish Babu: Apologies...I have to leave now because of another call coming up shortly. Bye, and see you at Abu Dhabi! Mats Dufberg: Bye Satish! Sarmad Hussain: Thank you Satish. Bye. ----------------- (10/05/2017 18:12) ----------------- Dennis Tan: excepted registration = pre-existing registration Kal Feher: suggested text: "With regards to the contents of the TLD zone file, the scope of this document is limited to only the owner-name of the DNS records which are added to the zone file by the registration system. Excluded from scope are any glue records and right-hand or target names." ----------------- (10/05/2017 18:24) ----------------- Kal Feher: this agreement also impacts ccTLDs ----------------- (10/05/2017 18:25) ----------------- Kal Feher: it is binding for ccTLDs on the idn fast track Dennis Tan: that's true Kal Sarmad Hussain: Regisry Agreement: it shall comply with RFCs 5890, 5891, 5892, 5893 and their successors. ----------------- (10/05/2017 18:37) ----------------- Mats Dufberg: When a pre-existing domain name requires a registry to make transitional exception to any of these Guidelines, the terms of that action must also be made readily available online, including the timeline for the resolution of such transitional matters Mats Dufberg: Remove: "The excepted registrations themselves are, however, not part of this documentation. At the end of the transitional period, code points that are prohibited by IDNA 2008 must not be permitted even by exception." Kal Feher: I am ok with the change Dennis Tan: When a pre-existing domain name requires a registry to make transitional exception to any of these Guidelines, the terms of that action must also be made readily available online, including the timeline for the resolution of such transitional matters" +1 ----------------- (10/05/2017 18:46) ----------------- Kal Feher: yes. keep 3 ----------------- (10/05/2017 18:48) ----------------- Kal Feher: I think that is out of scope of these guidelines ----------------- (10/05/2017 18:50) ----------------- Kal Feher: if the table change occurs for any reason other than a specific requirement from these guidelines, then the transition is entirely up to the operator ----------------- (10/05/2017 18:51) ----------------- Kal Feher: I think that last sentence is no loger relevant Kal Feher: no longer relevant Dennis Tan: +1 ----------------- (10/05/2017 18:54) ----------------- Dennis Tan: Do you hear a beep on your earphones or is it just me? Dennis Tan: oh. might be my batteries dying Mats Dufberg: (a) The IDN table must include the complete repertoire of code points, any variant code points, any variant rules and any contextual rules which the registry uses to determine if a label is acceptable for registration. ----------------- (10/05/2017 19:06) ----------------- Kal Feher: I'm fine with 13 ----------------- (10/05/2017 19:08) ----------------- Kal Feher: I think it is readable. ----------------- (10/05/2017 19:09) ----------------- Pitinan Kooarmornpatana: Hi i'm here ----------------- (10/05/2017 19:11) ----------------- Kal Feher: thank you. bye Pitinan Kooarmornpatana: Thanks all ,bye

2 2

Summary of IDNGWG meeting on 5 October 2017
by Pitinan Kooarmornpatana Oct. 9, 2017

Oct. 9, 2017

Dear IDNGWG members, Please find attached the summary of the meeting of the IDNGWG held on 5 October 2017. Please let us know if you would like to suggest any edits or additions. Action Items S. No. Action Items Owner 1 Update the Guidelines document and email the clean and updated redline versions SH 2 Based on the updated Guidelines, share the presentations for ICANN 60 SH The recording and this summary are also posted at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> Regards, Pitinan

1 0

ICANN 60 Presentations for IDNGWG
by Sarmad Hussain Oct. 7, 2017

Oct. 7, 2017

Dear All, Please find the presentations for ICANN 60 for your review and feedback. i. Long version for the 90 minute session (Sun, 29 Oct.; 1515-1645; Capital Suite 06; IDN Implementation Guidelines WG Update) ii. Short version for 7 minute update during the IDN Program Update session (Wed, 1 Nov; 0900-1015; Capital Suite 05; IDN Program Update) We will aim to finalize these during our call next week. We also need to finalize who will present each one on behalf of IDNGWG. Finally, for those of you who are attending ICANN60, let's celebrate the completion of these guidelines. Should we plan for a dinner on 29 Oct.? Regards, Sarmad From: idngwg-bounces(a)icann.org [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Saturday, October 07, 2017 2:49 PM To: idngwg(a)icann.org Subject: [Idngwg] Updated draft of Guidelines following the call on 5 October 2017 Dear All, Thank you to those who attended the three-hour long call on 5 October. We were able to complete the first pass and do a whole second pass on the guidelines, to finalize the document. The call recording is available at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines[commu…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>. (please note that because we deleted guideline 5, the guideline numbers are readjusted accordingly in the updated version attached and will not match with those called out in the recording) As discussed, please find attached an updated redline version of the document, in which older changes and comments have been accepted and only changes in the recent meeting are now reflected for easier review. In addition a clean version of the same version is also generated. Both versions are attached in docx and pdf formats. Please read through these changes and share any final feedback over email. We will finalize these revisions in the next call and then share the updated version with the community before ICANN 60. Thank you again for all the hard work over the past many months. This work will be really beneficial in the implementation of IDNs. Regards, Sarmad From: idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Thursday, October 05, 2017 7:13 PM To: idngwg(a)icann.org<mailto:idngwg@icann.org> Subject: [Idngwg] Chat log from today's call Dear All, Here is the chat log from today's call. Regards, Sarmad ----------------- (10/05/2017 16:04) ----------------- Kal Feher: yes Mats Dufberg: Satish, do you access to Adobe and can see the document? Satish Babu: Yes, I can see the document. ----------------- (10/05/2017 16:06) ----------------- Satish Babu: I can do two hours... Kal Feher: yes. I should. I may need to step away briefly Kal Feher: yes Satish Babu: Ok ----------------- (10/05/2017 16:36) ----------------- Dennis Tan: I'm not connected from my desk. Sorry I couldn't speak earlier. It was difficult to find a safe time to unmute my phone. Dennis Tan: I mean to say "I am connected" :) Pitinan Kooarmornpatana: :) ----------------- (10/05/2017 16:49) ----------------- Satish Babu: Yes, let's park it for now. Sarmad Hussain: I can suggest during the break Dennis Tan: Thanks Sarmad ----------------- (10/05/2017 16:56) ----------------- Dennis Tan: Have to step away for a few min ----------------- (10/05/2017 17:00) ----------------- Satish Babu: No comments for now... Dennis Tan: I'm back Satish Babu: (yes, ok with the suggested additions) ----------------- (10/05/2017 17:08) ----------------- Kal Feher: yes. they are all optional ----------------- (10/05/2017 17:10) ----------------- Kal Feher: it is ok if the information is not relevant ----------------- (10/05/2017 17:13) ----------------- Satish Babu: In my opinion, 'should' is slightly stronger than optional Dennis Tan: should = used to give or ask advice or suggestions Dennis Tan: other definition = indicating a desirable or expected state ----------------- (10/05/2017 17:19) ----------------- Kal Feher: yes Satish Babu: Agree. ----------------- (10/05/2017 17:29) ----------------- Satish Babu: Ok Mats Dufberg: Back again at 12:44 UTC. ----------------- (10/05/2017 17:44) ----------------- Mats Dufberg: I am back. Dennis Tan: I'm here Satish Babu: I'm back too Sarmad Hussain: Within-script homoglyphsTLD registries are encouraged to consider policies to minimize confusion of IDN labels with other labels within the same script, especially arising due to homoglyphic characters. Also see Additonal Note IV. Sarmad Hussain: should we start? ----------------- (10/05/2017 17:48) ----------------- Dennis Tan: I would change "especially" with "specifically" ----------------- (10/05/2017 17:49) ----------------- Kal Feher: Agree with Dennis and I'm ok with the text ----------------- (10/05/2017 17:54) ----------------- Satish Babu: This looks fine. Kal Feher: it should remain a note. ----------------- (10/05/2017 18:03) ----------------- Kal Feher: agree with Sarmad. the RA uses "allocate" to mean domains which can be registered Satish Babu: Yes, it does make sense. ----------------- (10/05/2017 18:06) ----------------- Mats Dufberg: 1.2 Scope Mats Dufberg: These Guidelines only concerns registred names. ----------------- (10/05/2017 18:08) ----------------- Kal Feher: could you clarify the section pls? ----------------- (10/05/2017 18:11) ----------------- Satish Babu: Apologies...I have to leave now because of another call coming up shortly. Bye, and see you at Abu Dhabi! Mats Dufberg: Bye Satish! Sarmad Hussain: Thank you Satish. Bye. ----------------- (10/05/2017 18:12) ----------------- Dennis Tan: excepted registration = pre-existing registration Kal Feher: suggested text: "With regards to the contents of the TLD zone file, the scope of this document is limited to only the owner-name of the DNS records which are added to the zone file by the registration system. Excluded from scope are any glue records and right-hand or target names." ----------------- (10/05/2017 18:24) ----------------- Kal Feher: this agreement also impacts ccTLDs ----------------- (10/05/2017 18:25) ----------------- Kal Feher: it is binding for ccTLDs on the idn fast track Dennis Tan: that's true Kal Sarmad Hussain: Regisry Agreement: it shall comply with RFCs 5890, 5891, 5892, 5893 and their successors. ----------------- (10/05/2017 18:37) ----------------- Mats Dufberg: When a pre-existing domain name requires a registry to make transitional exception to any of these Guidelines, the terms of that action must also be made readily available online, including the timeline for the resolution of such transitional matters Mats Dufberg: Remove: "The excepted registrations themselves are, however, not part of this documentation. At the end of the transitional period, code points that are prohibited by IDNA 2008 must not be permitted even by exception." Kal Feher: I am ok with the change Dennis Tan: When a pre-existing domain name requires a registry to make transitional exception to any of these Guidelines, the terms of that action must also be made readily available online, including the timeline for the resolution of such transitional matters" +1 ----------------- (10/05/2017 18:46) ----------------- Kal Feher: yes. keep 3 ----------------- (10/05/2017 18:48) ----------------- Kal Feher: I think that is out of scope of these guidelines ----------------- (10/05/2017 18:50) ----------------- Kal Feher: if the table change occurs for any reason other than a specific requirement from these guidelines, then the transition is entirely up to the operator ----------------- (10/05/2017 18:51) ----------------- Kal Feher: I think that last sentence is no loger relevant Kal Feher: no longer relevant Dennis Tan: +1 ----------------- (10/05/2017 18:54) ----------------- Dennis Tan: Do you hear a beep on your earphones or is it just me? Dennis Tan: oh. might be my batteries dying Mats Dufberg: (a) The IDN table must include the complete repertoire of code points, any variant code points, any variant rules and any contextual rules which the registry uses to determine if a label is acceptable for registration. ----------------- (10/05/2017 19:06) ----------------- Kal Feher: I'm fine with 13 ----------------- (10/05/2017 19:08) ----------------- Kal Feher: I think it is readable. ----------------- (10/05/2017 19:09) ----------------- Pitinan Kooarmornpatana: Hi i'm here ----------------- (10/05/2017 19:11) ----------------- Kal Feher: thank you. bye Pitinan Kooarmornpatana: Thanks all ,bye

1 0

Chat log from today's call
by Sarmad Hussain Oct. 5, 2017

Oct. 5, 2017

Dear All, Here is the chat log from today's call. Regards, Sarmad ----------------- (10/05/2017 16:04) ----------------- Kal Feher: yes Mats Dufberg: Satish, do you access to Adobe and can see the document? Satish Babu: Yes, I can see the document. ----------------- (10/05/2017 16:06) ----------------- Satish Babu: I can do two hours... Kal Feher: yes. I should. I may need to step away briefly Kal Feher: yes Satish Babu: Ok ----------------- (10/05/2017 16:36) ----------------- Dennis Tan: I'm not connected from my desk. Sorry I couldn't speak earlier. It was difficult to find a safe time to unmute my phone. Dennis Tan: I mean to say "I am connected" :) Pitinan Kooarmornpatana: :) ----------------- (10/05/2017 16:49) ----------------- Satish Babu: Yes, let's park it for now. Sarmad Hussain: I can suggest during the break Dennis Tan: Thanks Sarmad ----------------- (10/05/2017 16:56) ----------------- Dennis Tan: Have to step away for a few min ----------------- (10/05/2017 17:00) ----------------- Satish Babu: No comments for now... Dennis Tan: I'm back Satish Babu: (yes, ok with the suggested additions) ----------------- (10/05/2017 17:08) ----------------- Kal Feher: yes. they are all optional ----------------- (10/05/2017 17:10) ----------------- Kal Feher: it is ok if the information is not relevant ----------------- (10/05/2017 17:13) ----------------- Satish Babu: In my opinion, 'should' is slightly stronger than optional Dennis Tan: should = used to give or ask advice or suggestions Dennis Tan: other definition = indicating a desirable or expected state ----------------- (10/05/2017 17:19) ----------------- Kal Feher: yes Satish Babu: Agree. ----------------- (10/05/2017 17:29) ----------------- Satish Babu: Ok Mats Dufberg: Back again at 12:44 UTC. ----------------- (10/05/2017 17:44) ----------------- Mats Dufberg: I am back. Dennis Tan: I'm here Satish Babu: I'm back too Sarmad Hussain: Within-script homoglyphsTLD registries are encouraged to consider policies to minimize confusion of IDN labels with other labels within the same script, especially arising due to homoglyphic characters. Also see Additonal Note IV. Sarmad Hussain: should we start? ----------------- (10/05/2017 17:48) ----------------- Dennis Tan: I would change "especially" with "specifically" ----------------- (10/05/2017 17:49) ----------------- Kal Feher: Agree with Dennis and I'm ok with the text ----------------- (10/05/2017 17:54) ----------------- Satish Babu: This looks fine. Kal Feher: it should remain a note. ----------------- (10/05/2017 18:03) ----------------- Kal Feher: agree with Sarmad. the RA uses "allocate" to mean domains which can be registered Satish Babu: Yes, it does make sense. ----------------- (10/05/2017 18:06) ----------------- Mats Dufberg: 1.2 Scope Mats Dufberg: These Guidelines only concerns registred names. ----------------- (10/05/2017 18:08) ----------------- Kal Feher: could you clarify the section pls? ----------------- (10/05/2017 18:11) ----------------- Satish Babu: Apologies...I have to leave now because of another call coming up shortly. Bye, and see you at Abu Dhabi! Mats Dufberg: Bye Satish! Sarmad Hussain: Thank you Satish. Bye. ----------------- (10/05/2017 18:12) ----------------- Dennis Tan: excepted registration = pre-existing registration Kal Feher: suggested text: "With regards to the contents of the TLD zone file, the scope of this document is limited to only the owner-name of the DNS records which are added to the zone file by the registration system. Excluded from scope are any glue records and right-hand or target names." ----------------- (10/05/2017 18:24) ----------------- Kal Feher: this agreement also impacts ccTLDs ----------------- (10/05/2017 18:25) ----------------- Kal Feher: it is binding for ccTLDs on the idn fast track Dennis Tan: that's true Kal Sarmad Hussain: Regisry Agreement: it shall comply with RFCs 5890, 5891, 5892, 5893 and their successors. ----------------- (10/05/2017 18:37) ----------------- Mats Dufberg: When a pre-existing domain name requires a registry to make transitional exception to any of these Guidelines, the terms of that action must also be made readily available online, including the timeline for the resolution of such transitional matters Mats Dufberg: Remove: "The excepted registrations themselves are, however, not part of this documentation. At the end of the transitional period, code points that are prohibited by IDNA 2008 must not be permitted even by exception." Kal Feher: I am ok with the change Dennis Tan: When a pre-existing domain name requires a registry to make transitional exception to any of these Guidelines, the terms of that action must also be made readily available online, including the timeline for the resolution of such transitional matters" +1 ----------------- (10/05/2017 18:46) ----------------- Kal Feher: yes. keep 3 ----------------- (10/05/2017 18:48) ----------------- Kal Feher: I think that is out of scope of these guidelines ----------------- (10/05/2017 18:50) ----------------- Kal Feher: if the table change occurs for any reason other than a specific requirement from these guidelines, then the transition is entirely up to the operator ----------------- (10/05/2017 18:51) ----------------- Kal Feher: I think that last sentence is no loger relevant Kal Feher: no longer relevant Dennis Tan: +1 ----------------- (10/05/2017 18:54) ----------------- Dennis Tan: Do you hear a beep on your earphones or is it just me? Dennis Tan: oh. might be my batteries dying Mats Dufberg: (a) The IDN table must include the complete repertoire of code points, any variant code points, any variant rules and any contextual rules which the registry uses to determine if a label is acceptable for registration. ----------------- (10/05/2017 19:06) ----------------- Kal Feher: I'm fine with 13 ----------------- (10/05/2017 19:08) ----------------- Kal Feher: I think it is readable. ----------------- (10/05/2017 19:09) ----------------- Pitinan Kooarmornpatana: Hi i'm here ----------------- (10/05/2017 19:11) ----------------- Kal Feher: thank you. bye Pitinan Kooarmornpatana: Thanks all ,bye

1 0

IDN Guidelines WG meeting - weekly on Thursdays 11am UTC -18 May onwards till the Guidelines are finalized
by Sarmad Hussain Oct. 5, 2017

Oct. 5, 2017

1 0

Re: [Idngwg] Summary of IDNGWG meeting on 28 September 2017
by Mats Dufberg Oct. 5, 2017

Oct. 5, 2017

15. TLD registries are encouraged to consider policies to minimize confusion of IDN labels with other labels arising from visually confusable characters within a same script. Also see Additonal Note IV. Propose: 15. TLD registries are encouraged to consider policies to minimize confusion of IDN labels with other labels (IDN labels or ASCII labels) arising from visually confusable characters within a same script. Also see Additonal Note IV. Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/ From: <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Wednesday 4 October 2017 at 13:19 To: idngwg <idngwg(a)icann.org> Subject: Re: [Idngwg] Summary of IDNGWG meeting on 28 September 2017 Dear IDN Guidelines WG members, Please find attached the updated version of the guidelines document, for our extended meeting tomorrow. Regards, Sarmad From: idngwg-bounces(a)icann.org [mailto:idngwg-bounces@icann.org] On Behalf Of Pitinan Kooarmornpatana Sent: Wednesday, October 04, 2017 4:05 PM To: idngwg(a)icann.org Subject: [Idngwg] Summary of IDNGWG meeting on 28 September 2017 Dear IDNGWG members, Please find attached the summary of the meeting of the IDNGWG held on 28 September 2017. Please let us know if you would like to suggest any edits or additions. Action Items S. No. Action Items Owner 1 Edit guideline15 and 19 and Implementation Notes as discussed by the WG SH 2 Draft suggested edits for guidelines 17 and No. 18 MD 3. Circulate the confirmed attendees’ list for the extended next meeting SH The recording and this summary are also posted at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> Regards, Pitinan

1 0

Summary of IDNGWG meeting on 28 September 2017
by Pitinan Kooarmornpatana Oct. 4, 2017

Oct. 4, 2017

Dear IDNGWG members, Please find attached the summary of the meeting of the IDNGWG held on 28 September 2017. Please let us know if you would like to suggest any edits or additions. Action Items S. No. Action Items Owner 1 Edit guideline15 and 19 and Implementation Notes as discussed by the WG SH 2 Draft suggested edits for guidelines 17 and No. 18 MD 3. Circulate the confirmed attendees' list for the extended next meeting SH The recording and this summary are also posted at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> Regards, Pitinan

2 1

Re: [Idngwg] Updated document based on current discussions
by Tan Tanaka, Dennis Oct. 1, 2017

Oct. 1, 2017

Dear All, I added comments to the latest draft. Thanks, Dennis From: <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Thursday, September 28, 2017 at 6:06 AM To: "idngwg(a)icann.org" <idngwg(a)icann.org> Subject: [EXTERNAL] [Idngwg] Updated document based on current discussions Dear All, Please find attached a clean version of the document for our discussion today, based on the request by WG members in the last meeting. The changes include: 1. Addition of a section on “Implementation Notes” 2. Separating a section/guideline which asks for publishing the IDN policies, with a list of items to be included 3. Re-ordering of some guidelines to the relevant sections and in better sequence (e.g. guideline on within-script homoglyphs before cross-script homoglyphs) 4. Accepting changes and removing comments which have been agreed to, for a cleaner version of the document 5. Updating glossary: a. Removing the definition of security and stability from the Glossary, as the WG intended not to define these terms but inherit them from the respective contracts. b. Adding definition of Whole-Label Confusables, based on UTR 36 Regards, Sarmad

2 2