DOCUMENT TYPE NOTES SESSION ccPDP4 IDN Confusing Similarities SG teleconference (#17) DATE 21 February 2023 TIME 14:00 UTC 1. Welcome Welcome by Anil 2. Admin matters Bart: very low participation today. Do you wish to continue? Anil: yes. Others might join later 2 action items: * Katrina and Patricio appointed as board liaisons. They both joined today’s meeting. * Following discussions 4 weeks ago, the base for comparison had to be adjusted, to be used for CS review. 1 major item still to discuss: the base for comparison. Other items have been agreed upon. The section on CS will be included in the base doc, for discussion and adoption by the full group. If the CS subgroup finalises its work on 7 March, the full group will meet every week, to have the initial report ready for public comment by end April. Update EPDP effort: No fresh update from Anil. deferred to next week, when the full group meets. Ariel: In general the EPDP Team is wrapping up its phase 1 deliberation, still aiming to publish Initial Report in April 2023 Anil: will the meeting on 7 March happen? Close to ICANN76 Bart: let’s discuss at the end of the meeting today 3. Update base document 1. Review section 4.1.2 (3) Page 28 Does the procedural approach address your concerns? Mirjana: it does Jaap: yes, good to see Mirjana is happy. Bart: noted the typos and formatting. Do you agree with including the likelihood of misconnection? No red marks Mirjana: what is “likelihood”? Bart: probable, but not possible. Expending similarity evaluation panel Do you agree? No red marks 2. Review deleting section 5.5.2.1.4 (now included in 4.1.2 (3) Page 41. Similarity evaluation Group agrees to include section in yello 3. What if section (2) added notes and observations (page 43) Page 43. Question by Sarmad. What would happen if a selected IDN ccTLD string is considered not valid, but a delegatable string would be valid, and the applicant needs to apply again. Restart process is an administrative burden. Delegatable variant will become the preferred string. Notes & observations: not part of the policy itself. Help with the interpretation. Do you agree? No red marks Bart: second reading online only 4. Next meeting 1. 28 February – Full Group 2. 7 March – CS subgroup TBD Not needed, 2nd reading online 5. Closure Thank you all. Bye Joke Braeken joke.braeken@icann.org<mailto:joke.braeken@icann.org> = = = ICANN76 LINKS TO BOOKMARK NOW • ccNSO Schedule https://community.icann.org/x/8IMFDQ • ccNSO Session Highlights https://community.icann.org/x/kYYFDQ • Tech Day https://community.icann.org/x/WIQ-DQ From: CCPDP4-CS-SG <ccpdp4-cs-sg-bounces@icann.org> on behalf of Kimberly Carlson <kimberly.carlson@icann.org> Date: Friday, 17 February 2023 at 18:10 To: "ccpdp4-cs-sg@icann.org" <ccpdp4-cs-sg@icann.org> Subject: [CCPDP4-CS-SG] REMINDER: ccPDP4 IDN Confusing Similarities SG teleconference (#17) | 21 February at 14:00 UTC Dear all, As a reminder, the next ccPDP4 IDN Confusing Similarities SG teleconference (#17) is scheduled for 21 February at 14:00 UTC. Agenda: 1. Welcome 2. Admin matters 3. Update base document 1. Review section 4.1.2 (3) 2. Review deleting section 5.5.2.1.4 (now included in 4.1.2 (3) 3. What if section (2) added notes and observations (page 43) 1. Next meeting 1. 27 February – Full Group 2. 7 March – CS subgroup TBD 1. Closure Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/91528741726?pwd=ZmRTRGhLSWsxVldNa0NQZHdldTNsZz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/91528741726?pwd=ZmRTRGhLS...> Meeting ID: 915 2874 1726 Passcode: PDP4-CS#17 Wiki: https://community.icann.org/x/aIDKDQ
