Dear Team, Please find below the revised language for PR6 (still to combine PR6 and IG7), related to Charter question C5 on IDN table harmonization, from leadership/staff for discussion on Thursday, 1st August 2024, at 12:00 UTC: “Preliminary Recommendation 6: The baseline criteria for implementing IDNs at the second-level must be security and stability of the DNS. ICANN org and gTLD registry operators shall be responsible for reaching mutual agreement on a minimum set of IDN variant deployment requirements, including variant sets, at the second-level. In developing the minimum set of IDN variant deployment requirements, ICANN org and the gTLD registry operators shall consult with other relevant stakeholders, including ICANN-accredited registrars and script communities.” Once again, this will be discussed at the NEXT WEEK’S MEETING on 1st August NOT this week’s meeting on 25th July. Thank you for your kind consideration. Best regards, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org> Reply-To: Saewon Lee <saewon.lee@icann.org> Date: Wednesday, July 17, 2024 at 12:19 PM To: Daniel Gluck <daniel.gluck@icann.org>, "gnso-epdp-idn-team@icann.org" <gnso-epdp-idn-team@icann.org> Subject: [Gnso-epdp-idn-team] Re: Proposed Agenda - IDN EPDP Meeting #110 - WEDNESDAY 17 July 2024 at 12:00 UTC + Notes from Meeting #109 Dear Team, Please find below the proposed language for PR6 (which is to combine PR6 and IG7), related to Charter question C5 on IDN table harmonization, from leadership for discussion on Wednesday, 17 July at 12:00 UTC: “Preliminary Recommendation 6: The baseline criteria for implementing IDNs at the second-level must be security and stability of the DNS. ICANN org and gTLD registry operators, in consultation with other relevant stakeholders including ICANN-accredited registrars, are responsible for developing and reaching full consensus agreement on a minimum set of IDN variant deployment requirements, including variant sets, at the second-level that will satisfy the baseline criteria of security and stability of the DNS.” Also, please refer to the amended agenda below: 1. Roll Call and SOI Updates (2 min) 2. Welcome and Chair Updates (5 min) 3. Discuss ICANN org Request: Stabilize Outputs PR6 and IG7 (30 mins) 4. Continue Reviewing Phase 2 Initial Report Public Comments (80 mins) * Start Discussions from PR17 * Discussions on “Other” (Glossary, General, Charter Questions without the Team’s Responses) 5. AOB (3 min) Thank you for your kind consideration. Best regards, Steve, Dan, and Saewon. From: Daniel Gluck via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org> Reply-To: Daniel Gluck <daniel.gluck@icann.org> Date: Wednesday, July 17, 2024 at 6:44 AM To: "gnso-epdp-idn-team@icann.org" <gnso-epdp-idn-team@icann.org> Subject: [Gnso-epdp-idn-team] Proposed Agenda - IDN EPDP Meeting #110 - WEDNESDAY 17 July 2024 at 12:00 UTC + Notes from Meeting #109 Hi All! Please find below our proposed agenda for WEDNESDAY, 17 July’s team call at 12:00 UTC. IDNs EPDP Meeting #110<https://community.icann.org/x/FIBFF> Proposed Agenda 1. Roll Call and SOI Updates (2 min) 2. Welcome and Chair Updates (5 min) 3. Discuss ICANN org request (30 min) 4. Stabilize Outputs; PR6 and IG7 (30 mins) 5. Continue Reviewing Phase 2 Initial Report Public Comments (50 mins) * Start Discussions from PR17 * Discussions on “Other” (Glossary, General, Charter Questions without the Team’s Responses) 6. AOB (3 min) IDNs EPDP Meeting #109<https://community.icann.org/x/lYBFF> Action Items * The EPDP Team will review the proposed updates to PR14 * The NCSG will discuss and report back with rationale for their PR14 / IG15 comment Notes 1. Roll Call and SOI Updates (2 min) 2. Welcome and Chair Updates (5 min) 3. Continue Reviewing Phase 2 Initial Report Public Comments (50 min) 4. Start Discussions from PR14, IG15 * For PR14, there was discussion regarding the RySG comment that was Supported with a wording change * Consistent with the ICANN org input on the need for a consistent operational process the RySG notes there is no requirement for the service to be public. There are some things that differ from ICANN org. * The ALAC generally supports this but would request a public service to be made available * RySG pushed back on there being a public service component, among other comments made for PR14. * ACTION ITEM: The EPDP Team will review the proposed updates to PR14. * Regarding the NCSG Comment for PR14, there was not push back to the proposed deletion of IG 15, but there was a request to get more information to back up their comment with rationale. * ACTION ITEM: The NCSG will discuss and report back with rationale for their PR14 / IG15 comment 5. AOB (3 min) Thanks! Saewon, Steve, Ariel, and Dan