August 2016 - Idngwg - lists.icann.org

Re: [Idngwg] meeting notes from 11 August 2016
by Tan Tanaka, Dennis Aug. 25, 2016

Aug. 25, 2016

All, Please find enclosed revised recommendation language related to LGRs. It was difficult to merge the two concepts, so I left recommendation 9 unchanged. Also, this new recommendation does not fit in the “consistency” bucket so it would probably fit best in whatever category recommendation 6 is placed. -Dennis From: <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Thursday, August 11, 2016 at 8:48 AM To: "idngwg(a)icann.org" <idngwg(a)icann.org> Subject: [Idngwg] meeting notes from 11 August 2016 Dear All, Please find attached the summary of our meeting on 11 August 2016. Please let me know in case of any changes. We have the following action items: S. No. Action Items Owner 1 Staff to move Recommendation 6 to a new section as suggested SH 2 In Section 2.4, review and suggest changes to the new proposed recommendation regarding the Reference 2nd Level LGRs and merge with Recommendation 9, which is on more general IDN policy and collaboration in other aspects of IDNs in the future. This may result in one or more revised recommendations. DT The attached notes and the recording of the meeting are available at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Next meeting will be on 25 August, 11am UTC. Regards, Sarmad From: Sarmad Hussain Sent: Thursday, July 28, 2016 7:23 AM To: idngwg(a)icann.org Subject: RE: [Idngwg] meeting notes from 14 July 2016 Dear All Not sufficient members joined the call, therefore the members on the call decided to cancel today’s meeting. Please review the text added in Section 2.4 and let us know your feedback. We will reconvene in two weeks. 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, July 28, 2016 3:30 PM To: idngwg(a)icann.org<mailto:idngwg@icann.org> Subject: Re: [Idngwg] meeting notes from 14 July 2016 Thanks Kal. Dear All, Please find attached the updated version of the document for discussion today. Per the tasks from last meeting, edits include: 1. RFC 7940 for LGR 2. Updated Recommendation 6 by Kal, in Section 2.4 3. Updated Recommendation 9, in Section 2.4 4. New recommendation on reference second level LGRs in Section 2.4 In addition to the wording of the recommendation, we also need to define a section in the guidelines where these recommendations should be listed. 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, July 28, 2016 10:25 AM To: idngwg(a)icann.org<mailto:idngwg@icann.org> Subject: Re: [Idngwg] meeting notes from 14 July 2016 I've attached the revised recommendation 6 for section 2.4. During the last meeting, I think a few of us felt that this recommendation was an awkward fit for 'Section 2.4 Consistency'. This recommendation, if followed, will improve a user's understanding of the language table and how it is implemented in the registry and DNS. So it is more about education than collaboration/consistency. While I think the recommendation has merit and should remain in the guidelines in some form, it should probably be in a section related to user acceptance or Registrant interaction with IDN based registries. 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: [ttp://neunet.neustar.biz/sites/default/files/295/New%20Picture.png] Facebook<http://www.facebook.com/neustarinc> [ttp://neunet.neustar.biz/sites/default/files/295/New%20Picture%20(1)(1).png] LinkedIn<http://www.linkedin.com/company/5349> [ttp://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: Sunday, 24 July 2016 at 21:14 To: "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: Re: [Idngwg] meeting notes from 14 July 2016 Dear All, Wael also attended this meeting. The updated version of the meeting notes has been uploaded at the wiki page. Regards, Sarmad From: idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Sunday, July 24, 2016 1:59 PM To: idngwg(a)icann.org<mailto:idngwg@icann.org> Subject: [Idngwg] meeting notes from 14 July 2016 Dear All, Please find attached the meeting notes from 14 July 2016. Please let me know in case of any edits or suggestions. We have the following action items: S. No. Action Items Owner 1 Staff to share when RFC on LGRs is published and update document appropriately SH 2 Suggest updated text for current Recommendation 6 in section 2.4 KF 3 Break Recommendation 9 in section 2.4 into multiple recommendations covering the various ideas discussed, including Reference 2nd Level LGRs, more general IDN policy and collaboration in other aspects of IDNs in the future SH for first-cut 4 Review the table with text on IDN Variants and come with suggestion for recommendation(s) for next meeting ALL The attached notes and the recording of the meeting are available at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Next meeting will be on 28 July, 11am UTC. Regards, Sarmad

2 1

IDNGWG Meeting - Alternate Thursdays 11am UTC
by Sarmad Hussain Aug. 23, 2016

Aug. 23, 2016

Adobe Connect - IDN Meeting room: How to connect: Link to Adobe Connect: https://icann.adobeconnect.com/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

meeting notes from 11 August 2016
by Sarmad Hussain Aug. 11, 2016

Aug. 11, 2016

Dear All, Please find attached the summary of our meeting on 11 August 2016. Please let me know in case of any changes. We have the following action items: S. No. Action Items Owner 1 Staff to move Recommendation 6 to a new section as suggested SH 2 In Section 2.4, review and suggest changes to the new proposed recommendation regarding the Reference 2nd Level LGRs and merge with Recommendation 9, which is on more general IDN policy and collaboration in other aspects of IDNs in the future. This may result in one or more revised recommendations. DT The attached notes and the recording of the meeting are available at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Next meeting will be on 25 August, 11am UTC. Regards, Sarmad From: Sarmad Hussain Sent: Thursday, July 28, 2016 7:23 AM To: idngwg(a)icann.org Subject: RE: [Idngwg] meeting notes from 14 July 2016 Dear All Not sufficient members joined the call, therefore the members on the call decided to cancel today's meeting. Please review the text added in Section 2.4 and let us know your feedback. We will reconvene in two weeks. 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, July 28, 2016 3:30 PM To: idngwg(a)icann.org <mailto:idngwg@icann.org> Subject: Re: [Idngwg] meeting notes from 14 July 2016 Thanks Kal. Dear All, Please find attached the updated version of the document for discussion today. Per the tasks from last meeting, edits include: 1. RFC 7940 for LGR 2. Updated Recommendation 6 by Kal, in Section 2.4 3. Updated Recommendation 9, in Section 2.4 4. New recommendation on reference second level LGRs in Section 2.4 In addition to the wording of the recommendation, we also need to define a section in the guidelines where these recommendations should be listed. 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, July 28, 2016 10:25 AM To: idngwg(a)icann.org <mailto:idngwg@icann.org> Subject: Re: [Idngwg] meeting notes from 14 July 2016 I've attached the revised recommendation 6 for section 2.4. During the last meeting, I think a few of us felt that this recommendation was an awkward fit for 'Section 2.4 Consistency'. This recommendation, if followed, will improve a user's understanding of the language table and how it is implemented in the registry and DNS. So it is more about education than collaboration/consistency. While I think the recommendation has merit and should remain in the guidelines in some form, it should probably be in a section related to user acceptance or Registrant interaction with IDN based registries. 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 / <http://www.neustar.biz/> www.neustar.biz Follow Neustar: <http://www.facebook.com/neustarinc> Facebook <http://www.linkedin.com/company/5349> LinkedIn <http://www.twitter.com/neustarinc> Twitter _____ 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: Sunday, 24 July 2016 at 21:14 To: "idngwg(a)icann.org <mailto:idngwg@icann.org> " <idngwg(a)icann.org <mailto:idngwg@icann.org> > Subject: Re: [Idngwg] meeting notes from 14 July 2016 Dear All, Wael also attended this meeting. The updated version of the meeting notes has been uploaded at the wiki page. Regards, Sarmad From: idngwg-bounces(a)icann.org <mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Sunday, July 24, 2016 1:59 PM To: idngwg(a)icann.org <mailto:idngwg@icann.org> Subject: [Idngwg] meeting notes from 14 July 2016 Dear All, Please find attached the meeting notes from 14 July 2016. Please let me know in case of any edits or suggestions. We have the following action items: S. No. Action Items Owner 1 Staff to share when RFC on LGRs is published and update document appropriately SH 2 Suggest updated text for current Recommendation 6 in section 2.4 KF 3 Break Recommendation 9 in section 2.4 into multiple recommendations covering the various ideas discussed, including Reference 2nd Level LGRs, more general IDN policy and collaboration in other aspects of IDNs in the future SH for first-cut 4 Review the table with text on IDN Variants and come with suggestion for recommendation(s) for next meeting ALL The attached notes and the recording of the meeting are available at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Next meeting will be on 28 July, 11am UTC. Regards, Sarmad

1 0

Regrets for today's meeting
by Ram Mohan Aug. 11, 2016

Aug. 11, 2016

I won't be able to make today's meeting

1 0

Re: [Idngwg] meeting notes from 14 July 2016
by Feher, Kal Aug. 10, 2016

Aug. 10, 2016

I've attached the revised recommendation 6 for section 2.4. During the last meeting, I think a few of us felt that this recommendation was an awkward fit for 'Section 2.4 Consistency'. This recommendation, if followed, will improve a user's understanding of the language table and how it is implemented in the registry and DNS. So it is more about education than collaboration/consistency. While I think the recommendation has merit and should remain in the guidelines in some form, it should probably be in a section related to user acceptance or Registrant interaction with IDN based registries. 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: Sunday, 24 July 2016 at 21:14 To: "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: Re: [Idngwg] meeting notes from 14 July 2016 Dear All, Wael also attended this meeting. The updated version of the meeting notes has been uploaded at the wiki page. Regards, Sarmad From: idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Sunday, July 24, 2016 1:59 PM To: idngwg(a)icann.org<mailto:idngwg@icann.org> Subject: [Idngwg] meeting notes from 14 July 2016 Dear All, Please find attached the meeting notes from 14 July 2016. Please let me know in case of any edits or suggestions. We have the following action items: S. No. Action Items Owner 1 Staff to share when RFC on LGRs is published and update document appropriately SH 2 Suggest updated text for current Recommendation 6 in section 2.4 KF 3 Break Recommendation 9 in section 2.4 into multiple recommendations covering the various ideas discussed, including Reference 2nd Level LGRs, more general IDN policy and collaboration in other aspects of IDNs in the future SH for first-cut 4 Review the table with text on IDN Variants and come with suggestion for recommendation(s) for next meeting ALL The attached notes and the recording of the meeting are available at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Next meeting will be on 28 July, 11am UTC. Regards, Sarmad

3 5

FW: [Lager] RFC 7940 on Representing Label Generation Rulesets Using XML
by Sarmad Hussain Aug. 10, 2016

Aug. 10, 2016

Dear All, RFC 7940 "Representing Label Generation Rulesets Using XML" is now available. Regards, Sarmad -----Original Message----- From: Lager [mailto:lager-bounces@ietf.org] On Behalf Of rfc-editor(a)rfc-editor.org Sent: Wednesday, August 10, 2016 12:06 PM To: ietf-announce(a)ietf.org; rfc-dist(a)rfc-editor.org Cc: drafts-update-ref(a)iana.org; lager(a)ietf.org; rfc-editor(a)rfc-editor.org Subject: [Lager] RFC 7940 on Representing Label Generation Rulesets Using XML A new Request for Comments is now available in online RFC libraries. RFC 7940 Title: Representing Label Generation Rulesets Using XML Author: K. Davies, A. Freytag Status: Standards Track Stream: IETF Date: August 2016 Mailbox: kim.davies(a)icann.org, asmus(a)unicode.org Pages: 82 Characters: 170416 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-lager-specification-13.txt URL: https://www.rfc-editor.org/info/rfc7940 DOI: http://dx.doi.org/10.17487/RFC7940 This document describes a method of representing rules for validating identifier labels and alternate representations of those labels using Extensible Markup Language (XML). These policies, known as "Label Generation Rulesets" (LGRs), are used for the implementation of Internationalized Domain Names (IDNs), for example. The rulesets are used to implement and share that aspect of policy defining which labels and Unicode code points are permitted for registrations, which alternative code points are considered variants, and what actions may be performed on labels containing those variants. This document is a product of the Label Generation Rules Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor(a)rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ Lager mailing list Lager(a)ietf.org https://www.ietf.org/mailman/listinfo/lager

1 0

should registries be allowed to implement techno-policies that violate these IDN Guidelines
by Edmon Chung Aug. 5, 2016

Aug. 5, 2016

Hi Everyone, It has come to my attention in the recent public comments regarding registry agreement amendment that Google has expressed that it seems they do not wish for these IDN Guidelines to be hard requirements for gTLDs: ====================================== Specification 6, Section 1.4 (IDNs): [Google Registry] expressed concern that the proposed language would permanently prevent registries from being able to predictably negotiate potential changes to the provision of IDNs that conflicted with the IDN Guidelines, as the IDN Guidelines would continue to control even if these services had been reviewed, approved, and reflected in the respective Registry Operator’s Exhibit A. Thus, [Google Registry] recommended that the proposed text be revised to reflect that if there is an approved RSEP allowing the Registry to deviate from the IDN Guidelines, the IDN-related provisions of Exhibit A would control. ====================================== Given our discussion so far, I think we intend for these IDN Guidelines to be overarching requirements that should never be conflicted with. If that is the idea for these IDN Guidelines, then we should alert ICANN not to allow such "exceptions". If there exist a case that such an "exception" is needed, the proper approach maybe to update these IDN Guidelines... Wonder what others think... Edmon

3 2