February 2017 - Idngwg - lists.icann.org

Action requested: Final Draft of IDN Guidelines 4.0 - last chance to comment before release for Public Comments
by Sarmad Hussain March 2, 2017

March 2, 2017

Dear All, Based on our discussion during the call this week, please find attached the final draft of the IDN Guidelines 4.0. The comments received by WG members will be considered during the WG call in the coming week, after which the document will be finalized - to be released for public comments soon after (and before ICANN 58). All changes agreed during the calls have been accepted in this draft. The redlined text indicates some suggested edits. All the "will" occurrences which have been changed to "must" have been highlighted. Please let us know if any of these should be changed to "should" or other phrases. We also agreed to use either a "label" (to represent a part of a domain name) or a "domain name" to represent a domain with multiple labels - and not use just "domain" or just "name". Thus, all occurrences of the latter two terms have been replaced with "domain name". Changes are in redline and should also be verified. The glossary section still needs input. I have tried to include definitions from various document which require your review. There are some terms which still need to be defined. Thank you all for the significant effort put in to finalize the work. We will be presenting these guidelines at two sessions during ICANN 58: 1. Full 75 minute session: https://schedule.icann.org/event/9nmh/icann-gdd-idn-implementation-guidelin… 2. Short 7 minute update: https://schedule.icann.org/event/9nqW/idn-program-update Please add these sessions to your calendars and hope to see many of you there. regards, Sarmad

3 4

ICANN 58 Presentations on IDN Implementation Guidelines
by Sarmad Hussain Feb. 25, 2017

Feb. 25, 2017

?Dear All, Please find attached the long and the short presentations for the two sessions at ICANN 58, for your review. For the long presentation, I have included the exact wording of the recommendations. Where there are explanations, these have been pushed to the next page of the recommendation (starting with "continued" so that these can be easily skipped, if needed). I will update the guidelines in these presentations, once these are finalized after our meeting next week. Currently the reflect what is in the document circulated yesterday. Please let us know your feedback. regards, Sarmad

1 0

Re: [Idngwg] Summary of Meeting on 16 Feb. 2017
by Tan Tanaka, Dennis Feb. 23, 2017

Feb. 23, 2017

Dear All, My comments and proposed edits are enclosed. Thanks, Dennis From: <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Tuesday, February 21, 2017 at 9:38 AM To: "idngwg(a)icann.org" <idngwg(a)icann.org> Subject: [EXTERNAL] Re: [Idngwg] Summary of Meeting on 16 Feb. 2017 Dear All, A gentle reminder on Action Item 2 below. You are all requested to please review the report attached, based on the most recent call. I have done an initial pass and identified some items to discuss. I have also tried to add some definitions from various sources and added some terms (but have not deleted any yet). I have also marked the use of "will" to discuss how we want to address these instances. Please let us know your feedback. We aim to finalize this report (with some more changes noted in AIs below) in the next call to circulate to the community for discussion during ICANN 58. regards, Sarmad ________________________________ From: Sarmad Hussain Sent: Friday, February 17, 2017 1:14 AM To: idngwg(a)icann.org Subject: Summary of Meeting on 16 Feb. 2017 Dear All, Please find attached the summary of the meeting of the WG on 16 Feb. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Update recommendation on automatic activation of labels in Section 2.6.based on the discussion in the call. EC 2 Review the entire document by next call for any suggestions and feedback on the text All WG members 3 Update the glossary and fill in the definitions MD (and SH) The next meeting is scheduled for Thursday 23 Feb. 2017 11am UTC. We will continue following a weekly meeting schedule. The attached notes of the meeting and the recording of the meeting are available at the IDNGWG 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

4 3

Summary of Meeting on 16 Feb. 2017
by Sarmad Hussain Feb. 21, 2017

Feb. 21, 2017

Dear All, Please find attached the summary of the meeting of the WG on 16 Feb. Please let me know if there are any changes or suggestions.? The meeting has the following AIs: S. No. Action Items Owner 1? Update recommendation on automatic activation of labels in Section 2.6.based on the discussion in the call. EC 2 Review the entire document by next call for any suggestions and feedback on the text All WG members 3 Update the glossary and fill in the definitions MD (and SH) The next meeting is scheduled for Thursday 23 Feb. 2017 11am UTC. We will continue following a weekly meeting schedule. The attached notes of the meeting and the recording of the meeting are available at the IDNGWG 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 1

Summary of meeting on 2 Feb. 2017
by Sarmad Hussain Feb. 16, 2017

Feb. 16, 2017

Dear All, Please find attached the summary of the meeting of the WG on 2 Feb. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Update recommendation on Harmonization of variant rules by (i) changing "will" to "must", etc. according to RFC 2119, and (ii) updating it to note how registries could use the existing work by ICANN community to implement these guidelines, by referring to root zone LGR and other relevant work. DT The next meeting is scheduled for Thursday 9 Feb. 2017 11am UTC. We will continue following a weekly meeting schedule. The attached notes of the meeting and the recording of the meeting are available at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines[commun ity.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di splay_IDN_IDN-26-2343-3BImplementation-26-2343-3BGuidelines&d=DgMGaQ&c=FmY1u 3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm- mxd028M4&m=iHyLVWg5XYYYMyRqhLrWLRT-0Iuh0o5-T_cl8G4x7nY&s=_HPo9va0P1o27gRKByc MzrAZTgn8xXAy86zJg9CEjjI&e=> . Regards, Sarmad

2 2

Re: [Idngwg] Summary of meeting on 2 Feb. 2017
by Tan Tanaka, Dennis Feb. 9, 2017

Feb. 9, 2017

Revised version per below action item. From: <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Saturday, February 4, 2017 at 4:49 AM To: "idngwg(a)icann.org" <idngwg(a)icann.org> Subject: [EXTERNAL] [Idngwg] Summary of meeting on 2 Feb. 2017 Dear All, Please find attached the summary of the meeting of the WG on 2 Feb. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Update recommendation on Harmonization of variant rules by (i) changing “will” to “must”, etc. according to RFC 2119, and (ii) updating it to note how registries could use the existing work by ICANN community to implement these guidelines, by referring to root zone LGR and other relevant work. DT The next meeting is scheduled for Thursday 9 Feb. 2017 11am UTC. We will continue following a weekly meeting schedule. The attached notes of the meeting and the recording of the meeting are available at the IDNGWG 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

4 3

Cannot attend next meeting 2017-02-09
by Mats Dufberg Feb. 5, 2017

Feb. 5, 2017

Friends, I cannot attend the meeting on Thursday. Yours, Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/

1 0

Re: [Idngwg] call today - 2 Feb. 2017
by Feher, Kal Feb. 2, 2017

Feb. 2, 2017

I've updated the grandfathering suggestions using the language in rfc 7940 as a guide. It's hard to determine if a deliberate choice of terms was made in writing that document, because label and domain are used in a few cases interchangeably. However, when referring to the string being evaluated or generated, label (or variant label) is always used. When referring to the registered object, "domain name" is mostly used. So I have sought to match that in the text. Kal Feher Neustar Inc. / Enterprise Architect Level 8, 10 Queens Road, Melbourne, Australia VIC 3004 Office +61 3 9866 3710 / kal.feher(a)neustar.biz<mailto:kal.feher@neustar.biz> / www.neustar.biz<http://www.neustar.biz/> Follow Neustar: [http://neunet.neustar.biz/sites/default/files/295/New%20Picture.png] Facebook<http://www.facebook.com/neustarinc> [http://neunet.neustar.biz/sites/default/files/295/New%20Picture%20(1)(1).png] LinkedIn<http://www.linkedin.com/company/5349> [http://neunet.neustar.biz/sites/default/files/295/New%20Picture%20(2).png] Twitter<http://www.twitter.com/neustarinc> ________________________________ 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, 2 February 2017 at 20:26 To: Edmon Chung <edmon(a)registry.asia<mailto:edmon@registry.asia>>, "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: [Idngwg] call today - 2 Feb. 2017 Thanks Edmon. The changes have been incorporated in the attached document. We will use this version for our call today. Regards, Sarmad From: Edmon Chung [mailto:edmon@registry.asia] Sent: Thursday, February 02, 2017 2:02 PM 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] Summary of meeting on 26 Jan. 2017 Hi Everyone, please find a rough draft for 4th part (with minor edits to part 1) as discussed from last meeting: ====================================================== 2.7 Similarity and Confusability of Labels ... Commingling of cross-script code points in a single IDN label (recommendation 5, version 3) All code points in a single label must be taken from the same script as determined by the Unicode Standard Annex #24: Script Names http://www.unicode.org/reports/tr24[unicode.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.unicode.org_reports…>. Exceptions to this guideline are permissible for languages with established orthographies and conventions that require the commingled use of multiple scripts. .... Harmonization of variant rules across same-script IDN tables ... Cross-script homoglyph labels ... Limitations of IDN tables and policies In the case of any exceptions made allowing mixing of scripts, visually confusable characters from different scripts will not be allowed to co-exist in a single set of permissible code points unless a corresponding policy and character table is clearly defined. TLD registries should also consider policies for visually confusable characters within a same script. Nevertheless, it is important to understand that not all visual confusing similarity issues can be addressed by IDN tables, LGRs and policies. Other policies such as dispute resolution policies may be necessary to mitigate against abusive registrations exploiting visually similar characters. For example, even for Latin LDH repertoire, whereas the digit "0" and letter "O", or the capital letter "I", small letter "l" and digit "1", may be considered visually confusable characters the mitigation policy for abuse is often addressed by dispute resolution policies, leveraging other bodies of knowledge (e.g. Trademark Law) to evaluate whether similarities between names causes confusion and abuse. ====================================================== Also, my apologies, I will not be able to join the call today. Edmon From: idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Wednesday, 1 February 2017 01:28 AM To: idngwg(a)icann.org<mailto:idngwg@icann.org> Subject: [Idngwg] Summary of meeting on 26 Jan. 2017 Dear All, Please find attached the summary of the meeting of the WG on 26 Jan. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Draft the additional fourth part of the recommendation by splitting the first recommendation on comingling cross-script code points on addressing similarity cases EC 2 >From 20170119 - Update recommendation on grandfathering current registrations based on the discussion KF The next meeting is scheduled for Thursday 2 Feb. 2017 11am UTC. We will continue following a weekly meeting schedule. The attached notes of the meeting and the recording of the meeting are available at the IDNGWG 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

call today - 2 Feb. 2017
by Sarmad Hussain Feb. 2, 2017

Feb. 2, 2017

Thanks Edmon. The changes have been incorporated in the attached document. We will use this version for our call today. Regards, Sarmad From: Edmon Chung [mailto:edmon@registry.asia] Sent: Thursday, February 02, 2017 2:02 PM To: Sarmad Hussain <sarmad.hussain(a)icann.org>; idngwg(a)icann.org Subject: [Ext] RE: [Idngwg] Summary of meeting on 26 Jan. 2017 Hi Everyone, please find a rough draft for 4th part (with minor edits to part 1) as discussed from last meeting: ====================================================== 2.7 Similarity and Confusability of Labels ... Commingling of cross-script code points in a single IDN label (recommendation 5, version 3) All code points in a single label must be taken from the same script as determined by the Unicode Standard Annex #24: Script Names http://www.unicode.org/reports/tr24[unicode.org] <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.unicode.org_reports _tr24&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPca wI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=vs67oSzdoKg1I8yXSeEulH7Yxcufd2VTpR6oqGOVaIM &s=ztaPF-opuZl1GG3Qr6GxanJ3or_kOwASxeQsoWC6ca4&e=> . Exceptions to this guideline are permissible for languages with established orthographies and conventions that require the commingled use of multiple scripts. .... Harmonization of variant rules across same-script IDN tables ... Cross-script homoglyph labels ... Limitations of IDN tables and policies In the case of any exceptions made allowing mixing of scripts, visually confusable characters from different scripts will not be allowed to co-exist in a single set of permissible code points unless a corresponding policy and character table is clearly defined. TLD registries should also consider policies for visually confusable characters within a same script. Nevertheless, it is important to understand that not all visual confusing similarity issues can be addressed by IDN tables, LGRs and policies. Other policies such as dispute resolution policies may be necessary to mitigate against abusive registrations exploiting visually similar characters. For example, even for Latin LDH repertoire, whereas the digit "0" and letter "O", or the capital letter "I", small letter "l" and digit "1", may be considered visually confusable characters the mitigation policy for abuse is often addressed by dispute resolution policies, leveraging other bodies of knowledge (e.g. Trademark Law) to evaluate whether similarities between names causes confusion and abuse. ====================================================== Also, my apologies, I will not be able to join the call today. Edmon From: idngwg-bounces(a)icann.org <mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Wednesday, 1 February 2017 01:28 AM To: idngwg(a)icann.org <mailto:idngwg@icann.org> Subject: [Idngwg] Summary of meeting on 26 Jan. 2017 Dear All, Please find attached the summary of the meeting of the WG on 26 Jan. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Draft the additional fourth part of the recommendation by splitting the first recommendation on comingling cross-script code points on addressing similarity cases EC 2 >From 20170119 - Update recommendation on grandfathering current registrations based on the discussion KF The next meeting is scheduled for Thursday 2 Feb. 2017 11am UTC. We will continue following a weekly meeting schedule. The attached notes of the meeting and the recording of the meeting are available at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines[commun ity.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di splay_IDN_IDN-26-2343-3BImplementation-26-2343-3BGuidelines&d=DgMGaQ&c=FmY1u 3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm- mxd028M4&m=iHyLVWg5XYYYMyRqhLrWLRT-0Iuh0o5-T_cl8G4x7nY&s=_HPo9va0P1o27gRKByc MzrAZTgn8xXAy86zJg9CEjjI&e=> . Regards, Sarmad

1 0

Summary of meeting on 26 Jan. 2017
by Sarmad Hussain Feb. 2, 2017

Feb. 2, 2017

Dear All, Please find attached the summary of the meeting of the WG on 26 Jan. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Draft the additional fourth part of the recommendation by splitting the first recommendation on comingling cross-script code points on addressing similarity cases EC 2 >From 20170119 - Update recommendation on grandfathering current registrations based on the discussion KF The next meeting is scheduled for Thursday 2 Feb. 2017 11am UTC. We will continue following a weekly meeting schedule. The attached notes of the meeting and the recording of the meeting are available at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines[commun ity.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di splay_IDN_IDN-26-2343-3BImplementation-26-2343-3BGuidelines&d=DgMGaQ&c=FmY1u 3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm- mxd028M4&m=iHyLVWg5XYYYMyRqhLrWLRT-0Iuh0o5-T_cl8G4x7nY&s=_HPo9va0P1o27gRKByc MzrAZTgn8xXAy86zJg9CEjjI&e=> . Regards, Sarmad

2 1