Dear all, Please find below the notes from today’s meeting on Friday, 27 February 2022 at 13:30 UTC. Best, Ariel, Emily, Steve Action Items: Action Item: leadership and staff to suggest a stripped back version of the question(s) to ask the GP. Will provide to the EPDP to consider. Notes – IDNs EPDP Call – 27 February 2022 Roll Call & SOI Updates * None Welcome & Chair Updates * Extended deadline for A5 and A6 until Wednesday, 2 March * Request to open up draft recommendations Google docs to allow comments. Committed to not redline to document. Continue discussion on Charter Questions A7, A9, D1b, and B4 A7 * Recap on A7 deliberations to date. For part 1, suggestion that 3rd bullet is not needed for drafting recommendation. * For part 2, if the GP is asked to do work, they will need instructions to perform the work. * Staff suggestion for the GP to identify an exclusion list rather than an inclusive task, given the thousands of Han characters. * And further, perhaps the CJK GPs can develop a “hard no” list of disqualified Han characters (e.g., single or two stroke characters). And have that subject to EPDP Team’s review. * Clear instructions needed for GPs and IP for developing additional criteria to be used by DNS stability, string sim, and other areas TBD. Suggested criteria on slide. * Some concern that the criteria is being overcomplicated. Because of the punycode, it does not seem to be a technical and security reason. It just needs to be an ideograph/ideogram and otherwise meet normal requirements of program. * The reason for considering this criteria is because the group agreed that it did not have the expertise to determine allowable characters, or a mechanism to do so. * SAC052 recommends a very conservative approach for single character IDNs. It notes that a shorter string has a higher potential for confusability. * Suggestion that confusability should not matter against undelegated strings. * Suggestion that allowable single HAN characters should have a meaning, represent a word. * Agreement that technically, not a problem. However, notes the confusability issue is more pronounced the shorter the string. If a panel is to perform the evaluation in New gTLD Program, it could not be a GP, as it is not a standing panel. Suggestion that meaning might not be important, since that is not required for ASCII strings. * The idea is to give the GPs instructions to help provide input to the EPDP to consider. * Some support for GPs to consider the confusability question, not to only rely on the panel after submission. * Suggestion that the SSAC Advice will be taken into account via the evaluation processes. * The idea of doing up front analysis helps potential applicants to submit an acceptable character. To that end, SubPro welcomed the clarity of a prescriptive list to make the process more predictable via the Rationale. * Suggestion again that only bullets 1-3 are relevant, and no need to inquire with the GPs. * Question about whether there is an algorithmic way to add predictability. SubPro recommended against that (e.g., SWORD). Clarification that SubPro recommended against SWORD specifically. * GPs have been quite helpful in the past and timing will of course depend upon the task. What the EPDP could do is actually go to the GP with a very high level question to get an estimate of time and willingness to undertake work. * Suggestion to strip the question back to just hard no or disqualified characters. Some support to inquire with the GP, in part because they are linguists and have expertise that is not necessarily present in the EPDP. Action Item: leadership and staff to suggest a stripped back version of the question(s) to ask the GP. Will provide to the EPDP to consider. A9 * Noted that Delegated and Rejected overlap with Application statuses in the 2012 round. * Allocated seems to serve as a precursor to “In Contracting” * No equivalent to Blocked or Withhold-same-entity * Suggestion to accept the Staff Paper proposed label states for now. Rationale is that the label states are not dependent upon the application status and the EPDP team is not asked to expand application statuses. * Label states are used to track the status of variant labels. * That set of variant labels and their respective states will be leveraged in different processes and considered by this group later (e.g., string sim, objections, etc.) * Some support that they can live with it as a preliminary recommendation * Suggestion to ensure that definitions are not inconsistent with what the ODP is working on. And that the recommendation not be prescriptive about the specific words, but recommend that they be consistent with terminology in the new gTLD Program (and ccTLDs to the extent possible). D1b * N/A B4 * N/A AOB * None Steven Chan Senior Director, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 Email: steve.chan@icann.org<mailto:steve.chan@icann.org> Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group...>