December 2016 - Idngwg - lists.icann.org

IDN Guidelines WG meeting - weekly on Thursdays 11am UTC - 5Jan-9Mar 2017
by Sarmad Hussain Dec. 27, 2016

Dec. 27, 2016

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 meeting and AIs from 22 Dec.
by Sarmad Hussain Dec. 23, 2016

Dec. 23, 2016

Dear All, Please find attached the summary of the meeting of the WG on 22 Dec. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Re-write the recommendation on automatic activation based on the current input for further discussion EC 2 Recommendation on grandfathering current registrations should be updated per the current discussion KF 3 Update recommendation 5 from version 3.0 to include in the current version, to address the discussion on mingling scripts and removing the last sentence MD 4 Update the recommendation on harmonization of LGRs/IDN tables for the registries, addressing the two use cases identified DT The next meeting is schedule for 5 Jan. 2017 11am UTC. We will continue following a weekly meeting schedule from next year. 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. Hope you all have a great holiday season. Regards, Sarmad

1 0

Re: [Idngwg] Summary of meeting and AIs from 15 Dec.
by Tan Tanaka, Dennis Dec. 22, 2016

Dec. 22, 2016

Mats, Please correct me if I’m wrong. I thought the goal of our work on this topic was to focus on two use cases: 1) harmonize variant rules across IDN tables using the same script to make sure all variants within a registry are accounted for, and 2) prevent whole-label homoglyphs such as “ѕсоре” in Cyrilic and “scope” in Latin. Help me understand how your proposed recommendations address these two cases. Also, I’m concern about the usage of confusables.txt, where Latin o and 0, 1 and l are confusables. Are we suggesting that labels like “numero1”, “numer0l”, “numerol” or “numer01” be treated as variants? Thank you, Dennis From: <idngwg-bounces(a)icann.org> on behalf of Mats Dufberg <mats.dufberg(a)iis.se> Date: Wednesday, December 21, 2016 at 3:35 PM To: Sarmad Hussain <sarmad.hussain(a)icann.org>, "idngwg(a)icann.org" <idngwg(a)icann.org> Subject: [EXTERNAL] Re: [Idngwg] Summary of meeting and AIs from 15 Dec. Dear all, My home work was action item 1. Here is my update, based on the discussions during the two last meetings, of the text I submitted two weeks ago. <S1> //Revised text by MD 2016-12-21: BACKGROUND It is a well-known fact that within the Unicode repertoire it is possible to find two or more code points that have identical or confusingly similar glyphs, i.e. visual appearance. If two codepoints have identical glyphs they are called homoglyphs, or else they could be called confusable variants. Sometimes the number of code points are more than two, i.e. it is a group of code points with identical or confusingly similar glyphs. IDNA2008, which is the target for this document, only accepts a subset of the Unicode repertoire, which in this case means that the number of possible confusing code points is reduced. Confusables and homoglyphs can be found both within the same Unicode script, and between different Unicode scripts. Well-known homoglyphs of the latter type are found in Armenian, Cyrillic, Greek, and Latin scripts (but are also found between several other Unicode scripts). RISK If there are no restrictions on the registration of domain names only differing on homoglyphs of confusingly similar glyphs, then the risk of attacks on domain names increases. This can lead to an increase of fraud and reduced trust in the domain name system. SOURCES The Unicode provides two documents "intentional.txt" (3) and "confusables.txt" (4) with true homoglyphs and all confusingly similar glyphs, respectively. During the work with variants for the root zone, i.e. for existing and future IDN TLDs, work has been done to identify such pairs or group of such glyphs (6). MITIGATION To mitigate the risk of visually identical or confusingly similar IDN labels under the same TLD, a process of harmonization must take place, i.e. a process whereby contextual rules or variant rules make it impossible that two such labels are registered under the same TLD by two different registrars. Which code points to involve is partly a question of policy. It is important to point out that the harmonization process must work both within and between the IDN tables for the TLD. RECOMMENDATIONS The registry of a TLD MUST prevent only differing on homoglyphs from "intentional.txt" (3) to be registred by different registrars. The registry of a TLD MUST prevent only differing on homoglyphs that are considered to variants by the root zone work (6) to be registred by different registrars. The registry of a TLD SHOULD prevent only differing on confusingly similar glyphs from "confusables.txt" (4) to be registred by different registrars. REFERENCES 1. "Homoglyph", <https://en.wikipedia.org/wiki/Homoglyph> 2. "Unicode Security Mechanisms", Technical Standard #39, http://unicode.org/reports/tr39/ 3. "intentional.txt" (see TS#39), ftp://ftp.unicode.org/Public/security/revision-02/intentional.txt 4. "confusables.txt", (see TS#39), ftp://ftp.unicode.org/Public/security/revision-02/confusables.txt 5. "Internationalized Domain Names Registration and Administration Guidelines for European Languages Using Cyrillic", appendix A, https://tools.ietf.org/html/rfc5992 6. "Proposals for Root Zone Label Generation Ruleset (LGR)", https://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en </S1> Yours, 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: Sunday 18 December 2016 at 03:31 To: idngwg <idngwg(a)icann.org> Subject: [Idngwg] Summary of meeting and AIs from 15 Dec. Dear All, Please find attached the summary of the meeting of the WG on 15 Dec. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Update the recommendation on harmonization for the registries adhering to data from intentional.txt and root zone LGR as a “must” and also encourage registries to look at confusables.txt (but latter not as a “must”) MD 2 Re-write the recommendation on automatic activation based on the current input for further discussion EC 3 Add recommendation 5 from version 3.0 of the guidelines for further discussion and inclusion in the current version SH The next meeting is schedule for 22 Dec. 11am UTC. 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. Regards, Sarmad

2 1

Re: [Idngwg] Summary of meeting and AIs from 15 Dec.
by Mats Dufberg Dec. 21, 2016

Dec. 21, 2016

Dear all, My home work was action item 1. Here is my update, based on the discussions during the two last meetings, of the text I submitted two weeks ago. <S1> //Revised text by MD 2016-12-21: BACKGROUND It is a well-known fact that within the Unicode repertoire it is possible to find two or more code points that have identical or confusingly similar glyphs, i.e. visual appearance. If two codepoints have identical glyphs they are called homoglyphs, or else they could be called confusable variants. Sometimes the number of code points are more than two, i.e. it is a group of code points with identical or confusingly similar glyphs. IDNA2008, which is the target for this document, only accepts a subset of the Unicode repertoire, which in this case means that the number of possible confusing code points is reduced. Confusables and homoglyphs can be found both within the same Unicode script, and between different Unicode scripts. Well-known homoglyphs of the latter type are found in Armenian, Cyrillic, Greek, and Latin scripts (but are also found between several other Unicode scripts). RISK If there are no restrictions on the registration of domain names only differing on homoglyphs of confusingly similar glyphs, then the risk of attacks on domain names increases. This can lead to an increase of fraud and reduced trust in the domain name system. SOURCES The Unicode provides two documents "intentional.txt" (3) and "confusables.txt" (4) with true homoglyphs and all confusingly similar glyphs, respectively. During the work with variants for the root zone, i.e. for existing and future IDN TLDs, work has been done to identify such pairs or group of such glyphs (6). MITIGATION To mitigate the risk of visually identical or confusingly similar IDN labels under the same TLD, a process of harmonization must take place, i.e. a process whereby contextual rules or variant rules make it impossible that two such labels are registered under the same TLD by two different registrars. Which code points to involve is partly a question of policy. It is important to point out that the harmonization process must work both within and between the IDN tables for the TLD. RECOMMENDATIONS The registry of a TLD MUST prevent only differing on homoglyphs from "intentional.txt" (3) to be registred by different registrars. The registry of a TLD MUST prevent only differing on homoglyphs that are considered to variants by the root zone work (6) to be registred by different registrars. The registry of a TLD SHOULD prevent only differing on confusingly similar glyphs from "confusables.txt" (4) to be registred by different registrars. REFERENCES 1. "Homoglyph", <https://en.wikipedia.org/wiki/Homoglyph> 2. "Unicode Security Mechanisms", Technical Standard #39, http://unicode.org/reports/tr39/ 3. "intentional.txt" (see TS#39), ftp://ftp.unicode.org/Public/security/revision-02/intentional.txt 4. "confusables.txt", (see TS#39), ftp://ftp.unicode.org/Public/security/revision-02/confusables.txt 5. "Internationalized Domain Names Registration and Administration Guidelines for European Languages Using Cyrillic", appendix A, https://tools.ietf.org/html/rfc5992 6. "Proposals for Root Zone Label Generation Ruleset (LGR)", https://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en </S1> Yours, 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: Sunday 18 December 2016 at 03:31 To: idngwg <idngwg(a)icann.org> Subject: [Idngwg] Summary of meeting and AIs from 15 Dec. Dear All, Please find attached the summary of the meeting of the WG on 15 Dec. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Update the recommendation on harmonization for the registries adhering to data from intentional.txt and root zone LGR as a “must” and also encourage registries to look at confusables.txt (but latter not as a “must”) MD 2 Re-write the recommendation on automatic activation based on the current input for further discussion EC 3 Add recommendation 5 from version 3.0 of the guidelines for further discussion and inclusion in the current version SH The next meeting is schedule for 22 Dec. 11am UTC. 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. Regards, Sarmad

1 0

IDNGWG Meeting 22 Dec. @ 11am UTC
by Sarmad Hussain Dec. 18, 2016

Dec. 18, 2016

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 meeting and AIs from 15 Dec.
by Sarmad Hussain Dec. 18, 2016

Dec. 18, 2016

Dear All, Please find attached the summary of the meeting of the WG on 15 Dec. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Update the recommendation on harmonization for the registries adhering to data from intentional.txt and root zone LGR as a “must” and also encourage registries to look at confusables.txt (but latter not as a “must”) MD 2 Re-write the recommendation on automatic activation based on the current input for further discussion EC 3 Add recommendation 5 from version 3.0 of the guidelines for further discussion and inclusion in the current version SH The next meeting is schedule for 22 Dec. 11am UTC. 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. Regards, Sarmad

1 0

Re: [Idngwg] documents for discussion for IDNGWG meeting today
by Sarmad Hussain Dec. 15, 2016

Dec. 15, 2016

P.S. for the HTML files, please scroll down to the variant sets to see relevant the confusable code points (or code point sequences) being identified. From: Sarmad Hussain Sent: Thursday, December 15, 2016 1:39 PM To: idngwg(a)icann.org Subject: documents for discussion for IDNGWG meeting today Thanks Kal. Dear All, Please find attached the updated version of the document for discussion during our call today. In addition we will also discuss confusables.txt and intentional.txt data given in the HTML files attached. Regards, Sarmad From: idngwg-bounces(a)icann.org <mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Feher, Kal Sent: Thursday, December 15, 2016 12:17 PM To: idngwg(a)icann.org <mailto:idngwg@icann.org> Subject: Re: [Idngwg] Minutes of meeting and AIs from 8 Dec. I've attached an updated version of recommendation 13 which hopefully addresses the feedback from the last meeting. Kal Feher Neustar Inc. / Enterprise Architect Level 8, 10 Queens Road, Melbourne, Australia VIC 3004 Office +61 3 9866 3710 / <mailto:kal.feher@neustar.biz> kal.feher(a)neustar.biz / <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.neustar.biz_&d=DgMF -Q&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv- ZBvdgyyLm-mxd028M4&m=LGQO_Efesqhjhx1eaRO7eMUoBoqYjDPl5qv8zlmB58M&s=GueMwdUxS spsyUKa9St2V_B5esariD8OXh3OY38G1uo&e=> www.neustar.biz[neustar.biz] Follow Neustar: <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_neusta rinc&d=DgMF-Q&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcaw I-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=LGQO_Efesqhjhx1eaRO7eMUoBoqYjDPl5qv8zlmB58M& s=pplJIaLThTWgusavn99x6zEN-KhFkREwvyNL7_kpZP4&e=> Facebook[facebook.com] <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_compan y_5349&d=DgMF-Q&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPc awI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=LGQO_Efesqhjhx1eaRO7eMUoBoqYjDPl5qv8zlmB58 M&s=JfXTgUc90DeMQFNZpL6acPHUqNl9zYkxjytcVT7JcVk&e=> LinkedIn[linkedin.com] <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_neustar inc&d=DgMF-Q&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI -QmNa-kiv-ZBvdgyyLm-mxd028M4&m=LGQO_Efesqhjhx1eaRO7eMUoBoqYjDPl5qv8zlmB58M&s =tAG3l32fMgTdoOXgaTCHwxLYAExODkx6J6brE3YOCf4&e=> Twitter[twitter.com] _____ 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 Kal Feher <kalman.feher(a)neustar.biz <mailto:kalman.feher@neustar.biz> > Date: Wednesday, 14 December 2016 at 18:12 To: "idngwg(a)icann.org <mailto:idngwg@icann.org> " <idngwg(a)icann.org <mailto:idngwg@icann.org> > Subject: Re: [Idngwg] Minutes of meeting and AIs from 8 Dec. Hello Sarmad and IDNGWGers, Unfortunately I will not be able to attend the 22nd. I will be attending the 15th however and will endeavour to have Action item no. 3 ready beforehand. Kal Feher 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: Sunday, 11 December 2016 at 10:47 To: "idngwg(a)icann.org <mailto:idngwg@icann.org> " <idngwg(a)icann.org <mailto:idngwg@icann.org> > Subject: [Idngwg] Minutes of meeting and AIs from 8 Dec. Dear All, Please find attached summary of the meeting of the WG on 8 Dec. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Filter the confusables.txt and intentional.txt to derive a list which does not include code points disallowed in IDNA 2008 for further analysis by the WG SH 2 Update the recommendation on harmonization based on the current discussion MD 3 Update the recommendation on impact of harmonization on existing registrations based on the current discussion KF 4 Review the current discussion on harmonization and continue this discussion further ALL Re-write the recommendation on automatic activation based on the current input for further discussion EC The next meeting is schedule for 15 Dec. 11am UTC. The WG members present in the meeting also suggested a meeting on 22 Dec. 11am UTC. Please let me now if this is not feasible for you. 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 <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di splay_IDN_IDN-26-2343-3BImplementation-26-2343-3BGuidelines&d=DgMF-Q&c=MOptN lVtIETeDALC_lULrw&r=_-v0M-gLiqWrtaHtP66hjSPyu3ePgw9YIihGxxybjqU&m=YCP1sJjzxZ lFIDLtUzl3Uq8XZEXX3a8hLdaT-1H5s_Q&s=8i1v7KJJpqJULJA5s909vnG4i5B1ICGPnNxQRc8L tgU&e=> . Regards, Sarmad

2 1

documents for discussion for IDNGWG meeting today
by Sarmad Hussain Dec. 15, 2016

Dec. 15, 2016

Thanks Kal. Dear All, Please find attached the updated version of the document for discussion during our call today. In addition we will also discuss confusables.txt and intentional.txt data given in the HTML files attached. Regards, Sarmad From: idngwg-bounces(a)icann.org [mailto:idngwg-bounces@icann.org] On Behalf Of Feher, Kal Sent: Thursday, December 15, 2016 12:17 PM To: idngwg(a)icann.org Subject: Re: [Idngwg] Minutes of meeting and AIs from 8 Dec. I've attached an updated version of recommendation 13 which hopefully addresses the feedback from the last meeting. Kal Feher Neustar Inc. / Enterprise Architect Level 8, 10 Queens Road, Melbourne, Australia VIC 3004 Office +61 3 9866 3710 / <mailto:kal.feher@neustar.biz> kal.feher(a)neustar.biz / <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.neustar.biz_&d=DgMF -Q&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv- ZBvdgyyLm-mxd028M4&m=LGQO_Efesqhjhx1eaRO7eMUoBoqYjDPl5qv8zlmB58M&s=GueMwdUxS spsyUKa9St2V_B5esariD8OXh3OY38G1uo&e=> www.neustar.biz[neustar.biz] Follow Neustar: <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_neusta rinc&d=DgMF-Q&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcaw I-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=LGQO_Efesqhjhx1eaRO7eMUoBoqYjDPl5qv8zlmB58M& s=pplJIaLThTWgusavn99x6zEN-KhFkREwvyNL7_kpZP4&e=> Facebook[facebook.com] <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_compan y_5349&d=DgMF-Q&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPc awI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=LGQO_Efesqhjhx1eaRO7eMUoBoqYjDPl5qv8zlmB58 M&s=JfXTgUc90DeMQFNZpL6acPHUqNl9zYkxjytcVT7JcVk&e=> LinkedIn[linkedin.com] <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_neustar inc&d=DgMF-Q&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI -QmNa-kiv-ZBvdgyyLm-mxd028M4&m=LGQO_Efesqhjhx1eaRO7eMUoBoqYjDPl5qv8zlmB58M&s =tAG3l32fMgTdoOXgaTCHwxLYAExODkx6J6brE3YOCf4&e=> Twitter[twitter.com] _____ 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 Kal Feher <kalman.feher(a)neustar.biz <mailto:kalman.feher@neustar.biz> > Date: Wednesday, 14 December 2016 at 18:12 To: "idngwg(a)icann.org <mailto:idngwg@icann.org> " <idngwg(a)icann.org <mailto:idngwg@icann.org> > Subject: Re: [Idngwg] Minutes of meeting and AIs from 8 Dec. Hello Sarmad and IDNGWGers, Unfortunately I will not be able to attend the 22nd. I will be attending the 15th however and will endeavour to have Action item no. 3 ready beforehand. Kal Feher 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: Sunday, 11 December 2016 at 10:47 To: "idngwg(a)icann.org <mailto:idngwg@icann.org> " <idngwg(a)icann.org <mailto:idngwg@icann.org> > Subject: [Idngwg] Minutes of meeting and AIs from 8 Dec. Dear All, Please find attached summary of the meeting of the WG on 8 Dec. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Filter the confusables.txt and intentional.txt to derive a list which does not include code points disallowed in IDNA 2008 for further analysis by the WG SH 2 Update the recommendation on harmonization based on the current discussion MD 3 Update the recommendation on impact of harmonization on existing registrations based on the current discussion KF 4 Review the current discussion on harmonization and continue this discussion further ALL Re-write the recommendation on automatic activation based on the current input for further discussion EC The next meeting is schedule for 15 Dec. 11am UTC. The WG members present in the meeting also suggested a meeting on 22 Dec. 11am UTC. Please let me now if this is not feasible for you. 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 <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di splay_IDN_IDN-26-2343-3BImplementation-26-2343-3BGuidelines&d=DgMF-Q&c=MOptN lVtIETeDALC_lULrw&r=_-v0M-gLiqWrtaHtP66hjSPyu3ePgw9YIihGxxybjqU&m=YCP1sJjzxZ lFIDLtUzl3Uq8XZEXX3a8hLdaT-1H5s_Q&s=8i1v7KJJpqJULJA5s909vnG4i5B1ICGPnNxQRc8L tgU&e=> . Regards, Sarmad

1 0

Re: [Idngwg] Minutes of meeting and AIs from 8 Dec.
by Feher, Kal Dec. 15, 2016

Dec. 15, 2016

Hello Sarmad and IDNGWGers, Unfortunately I will not be able to attend the 22nd. I will be attending the 15th however and will endeavour to have Action item no. 3 ready beforehand. Kal Feher 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: Sunday, 11 December 2016 at 10:47 To: "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: [Idngwg] Minutes of meeting and AIs from 8 Dec. Dear All, Please find attached summary of the meeting of the WG on 8 Dec. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Filter the confusables.txt and intentional.txt to derive a list which does not include code points disallowed in IDNA 2008 for further analysis by the WG SH 2 Update the recommendation on harmonization based on the current discussion MD 3 Update the recommendation on impact of harmonization on existing registrations based on the current discussion KF 4 Review the current discussion on harmonization and continue this discussion further ALL Re-write the recommendation on automatic activation based on the current input for further discussion EC The next meeting is schedule for 15 Dec. 11am UTC. The WG members present in the meeting also suggested a meeting on 22 Dec. 11am UTC. Please let me now if this is not feasible for you. 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. Regards, Sarmad

1 1

Minutes of meeting and AIs from 8 Dec.
by Sarmad Hussain Dec. 12, 2016

Dec. 12, 2016

Dear All, Please find attached summary of the meeting of the WG on 8 Dec. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Filter the confusables.txt and intentional.txt to derive a list which does not include code points disallowed in IDNA 2008 for further analysis by the WG SH 2 Update the recommendation on harmonization based on the current discussion MD 3 Update the recommendation on impact of harmonization on existing registrations based on the current discussion KF 4 Review the current discussion on harmonization and continue this discussion further ALL Re-write the recommendation on automatic activation based on the current input for further discussion EC The next meeting is schedule for 15 Dec. 11am UTC. The WG members present in the meeting also suggested a meeting on 22 Dec. 11am UTC. Please let me now if this is not feasible for you. 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. Regards, Sarmad

1 1