September 2017 - Idngwg - lists.icann.org

Re: [Idngwg] Updated document based on current discussions
by Tan Tanaka, Dennis Oct. 1, 2017

Oct. 1, 2017

Dear All, I added comments to the latest draft. Thanks, Dennis From: <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Thursday, September 28, 2017 at 6:06 AM To: "idngwg(a)icann.org" <idngwg(a)icann.org> Subject: [EXTERNAL] [Idngwg] Updated document based on current discussions Dear All, Please find attached a clean version of the document for our discussion today, based on the request by WG members in the last meeting. The changes include: 1. Addition of a section on “Implementation Notes” 2. Separating a section/guideline which asks for publishing the IDN policies, with a list of items to be included 3. Re-ordering of some guidelines to the relevant sections and in better sequence (e.g. guideline on within-script homoglyphs before cross-script homoglyphs) 4. Accepting changes and removing comments which have been agreed to, for a cleaner version of the document 5. Updating glossary: a. Removing the definition of security and stability from the Glossary, as the WG intended not to define these terms but inherit them from the respective contracts. b. Adding definition of Whole-Label Confusables, based on UTR 36 Regards, Sarmad

2 2

Extended Meeting Next week
by Sarmad Hussain Sept. 28, 2017

Sept. 28, 2017

Dear All, Just a gentle reminder that we have an extended 3 hrs. long meeting next week, intended to finalize the guidelines document. Following people have confirmed to join: 1. Dennis 2. Kal 3. Mats Others are kindly requested to respond. Regards, Sarmad

1 0

Updated document based on current discussions
by Sarmad Hussain Sept. 28, 2017

Sept. 28, 2017

Dear All, Please find attached a clean version of the document for our discussion today, based on the request by WG members in the last meeting. The changes include: 1. Addition of a section on "Implementation Notes" 2. Separating a section/guideline which asks for publishing the IDN policies, with a list of items to be included 3. Re-ordering of some guidelines to the relevant sections and in better sequence (e.g. guideline on within-script homoglyphs before cross-script homoglyphs) 4. Accepting changes and removing comments which have been agreed to, for a cleaner version of the document 5. Updating glossary: * Removing the definition of security and stability from the Glossary, as the WG intended not to define these terms but inherit them from the respective contracts. * Adding definition of Whole-Label Confusables, based on UTR 36 Regards, Sarmad

1 0

apologies for 28th September
by Feher, Kal Sept. 28, 2017

Sept. 28, 2017

Unfortunately I am unwell and will not be able to attend tonight's meeting. Kal Feher Neustar Inc. Level 8, 10 Queens Road, Melbourne, Australia VIC 3004 Office +61 3 9866 3710 / kal.feher(a)team.neustar / 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.

2 1

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

Sept. 25, 2017

Dear All, Please confirm your availability for the IDNGWG meeting on Thursday this week. Regards, Sarmad

1 0

IDNGWG Meeting extension 2
by Sarmad Hussain Sept. 22, 2017

Sept. 22, 2017

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

IDNGWG Meeting extension 1
by Sarmad Hussain Sept. 22, 2017

Sept. 22, 2017

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

Completing the IDN Impl. Guidelines revision before ICANN 60
by Sarmad Hussain Sept. 22, 2017

Sept. 22, 2017

Dear All During the meeting of the IDNGWG yesterday, it was discussed that the WG should aim to finalize the recommendations before ICANN 60 meeting. To be able to achieve the target, one option considered was to have a longer (2.5 hrs - extendable to 3 hrs) meeting of the WG the week after next (by extending the existing meeting time). I am going to send two additional invitations (breaking it down to hour level). You are all requested to respond to the invitations by 27 September to let us know your availability, for us to finalize the meeting during the call next week. We will still meet for the scheduled one hour during the next week. Regards, Sarmad

1 0

Re: [Idngwg] Summary of IDNGWG meeting on 14 September 2017
by Tan Tanaka, Dennis Sept. 21, 2017

Sept. 21, 2017

Dear colleagues, Please find below the propose changes to guidelines 12 and 13 (a and b). To do this, I reviewed RFCs 3743 and 4290 to find the common language with RFC 7940. My action item was to draft a guideline or guidelines that could use common terminology so that it could be understood by users of all RFCs. Here is a summary of the terms used by the RFCs. RFC 3743, 4290 RFC 7940 Activation, Registration (used interchangeably) Activated Reserved label (in a bundle) Allocatable (as in for potential registration) Block (from registration) Block (from registration) It was difficult for me to use the words “disposition” and “allocatable” since they are very RFC7940 specific. So my approach was to start from a clean slate and come up with a guideline that addresses the following questions, which I believe are the objective of the guidelines on variant management: Who offers variant management? – the registry, defined by registry policy and idn tables. What determine the variant labels? – registry policy and idn tables. Who can activate a variant? – registrar at registrant’s request, or registry per local policy. What triggers activation of a variant? – registrant’s request, or registry policy. What type of variant is allowed to be activated? – per registry policy. Proposed guideline to replace 12, 13(a) and 13(b): TLD Registries may activate an IDN Variant Label, provided that i) such IDN Variant Label is requested by the same registrant or corresponding registrar as the Primary IDN Label, ii) such IDN Variant Label is registered to the registrant of the Primary IDN Label, and iii) such IDN Variant Label conforms with the registry policy. In exceptional cases, where a language and/or script have established conventions, a TLD Registry may automatically activate an IDN Variant Label at its discretion. In such cases, the TLD Registry must ensure that only the necessary IDN Variant Labels are automatically activated and the number of such labels remains as small as possible. Also, we should consider thinking about the implication with the restriction on variant activation required by many RAs. -Dennis From: <idngwg-bounces(a)icann.org> on behalf of Pitinan Kooarmornpatana <pitinan.koo(a)icann.org> Date: Wednesday, September 20, 2017 at 11:30 AM To: "idngwg(a)icann.org" <idngwg(a)icann.org> Subject: [EXTERNAL] Re: [Idngwg] Summary of IDNGWG meeting on 14 September 2017 Dear IDNGWG members, Please use this revised version of the summary as attached. Regards, Pitinan From: idngwg-bounces(a)icann.org [mailto:idngwg-bounces@icann.org] On Behalf Of Pitinan Kooarmornpatana Sent: Wednesday, September 20, 2017 8:15 PM To: idngwg(a)icann.org Subject: [Idngwg] Summary of IDNGWG meeting on 14 September 2017 Dear IDNGWG members, Please find attached the summary of the meeting of the IDNGWG held on 14 September 2017. Please let us know if you would like to suggest any edits or additions. Action Items S. No. Action Items Owner 1 Rephrase the 13(a) and (b) as discussed by the WG DT 2 Create the Implementation Notes Section in the document and move the text as discussed by WG PK The recording and this summary are also posted 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, Pitinan

2 2

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

Sept. 21, 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

2 1