- Idngwg - lists.icann.org

IDN Guidelines WG meeting - Thursdays @ 1100 UTC
by Sarmad Hussain Dec. 25, 2017

Dec. 25, 2017

1 0

Re: [Idngwg] Public Comment extension request
by Tan Tanaka, Dennis Dec. 13, 2017

Dec. 13, 2017

Dear Sarmad, Who is NCSG? Just curious to know. Regardless, I would not be opposed to accept their comments. As far as a meeting, I will be available on most days before year end, but will be absent during Jan 11 through 17. Best, Dennis From: Idngwg <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Tuesday, December 12, 2017 at 12:21 PM To: "idngwg(a)icann.org" <idngwg(a)icann.org> Subject: [EXTERNAL] [Idngwg] Public Comment extension request Dear IDNGWG members, The Public Comment for IDN Guidelines closed on 10 Dec. We have received many comments (see https://www.icann.org/public-comments/idn-guidelines-2017-10-19-en) However, we have also received a request from NCSG requesting the extension till this Friday. I hope it will be ok to extend the PC till then. I will work to summarize the comments in the meantime and share a summary report soon afterwards. Would you like to schedule a call to consider these comments before the holidays, or should I schedule a call in the second week of January onwards? Please advise. Regards, Sarmad

2 1

Public Comment extension request
by Sarmad Hussain Dec. 12, 2017

Dec. 12, 2017

Dear IDNGWG members, The Public Comment for IDN Guidelines closed on 10 Dec. We have received many comments (see https://www.icann.org/public-comments/idn-guidelines-2017-10-19-en) However, we have also received a request from NCSG requesting the extension till this Friday. I hope it will be ok to extend the PC till then. I will work to summarize the comments in the meantime and share a summary report soon afterwards. Would you like to schedule a call to consider these comments before the holidays, or should I schedule a call in the second week of January onwards? Please advise. Regards, Sarmad

1 0

Re: [Idngwg] [EXTERNAL] SAC099: SSAC Response to the ICANN IDN Guidelines WG
by Feher, Kal Nov. 22, 2017

Nov. 22, 2017

Thank you Sarmad, I think this advice aligns well with our scope statement. -- Kal Feher Neustar Inc. Melbourne, Australia 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: Wednesday, 22 November 2017 at 18:07 To: "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: [EXTERNAL] [Idngwg] SAC099: SSAC Response to the ICANN IDN Guidelines WG Dear IDN Guidelines WG members, Attached, please find the SSAC response to IDNGWG question on 27 July 2017. The document SAC099 is also published on the following webpage: https://www.icann.org/groups/ssac/documents<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_groups_s…>. The second public comment is still open. I will get back to all of you soon to schedule our calls after the public comment closes. If you would like to meet before that time, please let me know. Regards, Sarmad

2 1

SAC099: SSAC Response to the ICANN IDN Guidelines WG
by Sarmad Hussain Nov. 22, 2017

Nov. 22, 2017

Dear IDN Guidelines WG members, Attached, please find the SSAC response to IDNGWG question on 27 July 2017. The document SAC099 is also published on the following webpage: https://www.icann.org/groups/ssac/documents. The second public comment is still open. I will get back to all of you soon to schedule our calls after the public comment closes. If you would like to meet before that time, please let me know. Regards, Sarmad

1 0

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