August 2017 - Idngwg - lists.icann.org

Summary of IDNGWG meeting on 24 August 2017
by Sarmad Hussain Aug. 31, 2017

Aug. 31, 2017

Dear IDNGWG members, Please find attached the summary of the meeting of the IDNGWG held on 24 August 2017. Please let us know if you would like to suggest any edits or additions. Please also find attached the updated version 1.6 of the document based on the discussions so far. Action Items S. No. Action Items Owner 1 Break recommendation 13 into sub-recommendations (a), (b) and (c) using the languages in comments. In addition, append the 13(b) with the text with 'should' or a 'must' to highlight a conservative requirement for automatic activation. SH 2 Draft the initial public comment response report to be reviewed and finalized in the next one or two meetings. SH The recording and this summary are also posted at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Regards, Sarmad

1 0

Re: [Idngwg] Report on Public Comments
by Tan Tanaka, Dennis Aug. 30, 2017

Aug. 30, 2017

Suggested edits/comments enclosed. Thank you, Dennis From: <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Saturday, August 26, 2017 at 5:46 AM To: "idngwg(a)icann.org" <idngwg(a)icann.org> Subject: [EXTERNAL] [Idngwg] Report on Public Comments Dear All, We discussed to share the report on public comments through the Google Document. However, unfortunately I am unable to do that using ICANN email. I am attaching a docx version of the initial tentative response for everybody’s review and feedback. If you would like to create a Google Document, I could do it using a non-ICANN email account. Please let me know. Regards, Sarmad

1 0

Re: [Idngwg] IDN Impl. Guidelines session during ICANN 60
by Mats Dufberg Aug. 30, 2017

Aug. 30, 2017

I do not know if I will be able to participate in person. Else I will participate remotely. 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: Wednesday 30 August 2017 at 16:10 To: idngwg <idngwg(a)icann.org> Subject: Re: [Idngwg] IDN Impl. Guidelines session during ICANN 60 Dear All, Following the earlier email, kindly note that we are proposing the following two sessions for IDN Implementation Guidelines WG. 1. Please confirm IDNGWG to hold these sessions: * 75 minute session: IDN Implementation Guidelines WG Update Sun, 29 Oct., 1515-1645 * 5-7 minute update to the community during: IDN Program Update Wed, 1 Nov, 0900-1015 1. Please nominate who will present on behalf of IDNGWG in each of these sessions Regards, Sarmad From: Sarmad Hussain Sent: Monday, August 07, 2017 12:52 PM To: idngwg(a)icann.org Subject: IDN Impl. Guidelines session during ICANN 60 Dear All, I am suggesting an update by the IDNGWG session during ICANN 60. The suggested time is on Sunday 29 October from 315pm till 445pm. Please let me know if this would work, or suggest any alternate day/time. Best if we can finalize this during our meeting this week. Regards, Sarmad

1 0

IDN Impl. Guidelines session during ICANN 60
by Sarmad Hussain Aug. 30, 2017

Aug. 30, 2017

Dear All, I am suggesting an update by the IDNGWG session during ICANN 60. The suggested time is on Sunday 29 October from 315pm till 445pm. Please let me know if this would work, or suggest any alternate day/time. Best if we can finalize this during our meeting this week. Regards, Sarmad

1 1

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

Aug. 30, 2017

Dear All, A gentle reminder for the call tomorrow. Kindly review and send feedback to the public comment report emailed last week (attached here as well). 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

Report on Public Comments
by Sarmad Hussain Aug. 26, 2017

Aug. 26, 2017

Dear All, We discussed to share the report on public comments through the Google Document. However, unfortunately I am unable to do that using ICANN email. I am attaching a docx version of the initial tentative response for everybody's review and feedback. If you would like to create a Google Document, I could do it using a non-ICANN email account. Please let me know. Regards, Sarmad

1 0

aug 24th meeting
by Feher, Kal Aug. 23, 2017

Aug. 23, 2017

Please accept my apologies for tomorrow's meeting. I will be travelling to my ski vacation. Kal Feher

2 1

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

Aug. 23, 2017

Dear All, A gentle reminder for tomorrow 24 August, 11am UTC. 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

Summary of IDNGWG meeting on 17 August 2017
by Sarmad Hussain Aug. 18, 2017

Aug. 18, 2017

Dear IDNGWG members, Please find attached the summary of the meeting of the IDNGWG held on 17 August 2017. Please let us know if you would like to suggest any edits or additions. Please also find attached the updated version 1.5 of the document based on the discussions so far. I have cleaned and accepted the changes which have been agreed. Action Items S. No. Action Items Owner 1 Update recommendation 5 to add the expected Registry action when a domain name label becomes invalid due to an update in IDN table. Also restructure the last sentence of the first paragraph to complete it, with a "should". MD The recording and this summary are also posted at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Regards, Sarmad

1 0

tonight's meeting
by Feher, Kal Aug. 17, 2017

Aug. 17, 2017

Please accept my apologies for tonight's meeting. I have work commitments that will prevent me from attending. Note that a revised section 5 was sent last week and I've also made some suggestions regarding sections around it in my word draft. 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.

1 0