February 2022 - Gnso-epdp-idn-team

Draft Outcome: Charter Questions A5 & A6
by Ariel Liang March 2, 2022

March 2, 2022

Dear All, Please find the draft outcome language for charter questions A5 and A6 on this google doc, pp.6-11: https://docs.google.com/document/d/1Bt0LT45UaLynFNverh1nJhyvq6q6NxgSFAOnOp2… (it is also posted on the wiki page here: https://community.icann.org/x/XwyHCg) Following the agreed format, the draft outcome language includes the following components: * Brief answer to the charter question * Recommendations and implementation guidance * Rationale for recommendations and implementation guidance We would like to highlight the following elements: * Recommendation 1.5 under A5 (p.6): this proposed recommendation may be revisited after the EPDP Team tackles other charter questions; additional details may need to be fleshed out. * Recommendation 1.6 under A6 (p.9): please pay particular attention to the proposed definition of “grandfathering” and provide input, if any. Please provide any input/suggestion for the draft outcome language on the mailing list by Tuesday, 22 January. Any substantive comments will be discussed during the EPDP Team meeting in about two weeks. Best Regards, Steve, Emily, Ariel

6 6

REMINDER: Draft Outcome: Charter Questions A5 & A6
by Ariel Liang March 2, 2022

March 2, 2022

Dear All, This is a friendly reminder to review the draft outcome language for charter questions A5 and A6, and provide your comment/suggestion (if any) by AOB today (22 Feb 2022). Thanks to Michael for the input. Best, Ariel From: "Donna(a)registry.godaddy" <Donna(a)registry.godaddy> Date: Tuesday, February 8, 2022 at 7:28 PM To: Ariel Liang <ariel.liang(a)icann.org>, "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Subject: [Ext] RE: [Gnso-epdp-idn-team] Draft Outcome: Charter Questions A5 & A6 Hi All Just to follow on from Ariel’s email: consideration and input on the language drafted for A5 and A6 by the represented groups of this EPDP Team is really important to our work. Rather than rely on the assumption that no comment means agreement, I’d prefer to have each represented group actively confirm their agreement if that is indeed the case and if not, provide comments/input so that we can discuss areas of contention and find agreeable language for all to the extent possible. Thanks Donna From: Gnso-epdp-idn-team <gnso-epdp-idn-team-bounces(a)icann.org> On Behalf Of Ariel Liang Sent: Wednesday, February 9, 2022 2:22 AM To: gnso-epdp-idn-team(a)icann.org Subject: [Gnso-epdp-idn-team] Draft Outcome: Charter Questions A5 & A6 Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Dear All, Please find the draft outcome language for charter questions A5 and A6 on this google doc, pp.6-11: https://docs.google.com/document/d/1Bt0LT45UaLynFNverh1nJhyvq6q6NxgSFAOnOp2… [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> (it is also posted on the wiki page here: https://community.icann.org/x/XwyHCg [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…>). Following the agreed format, the draft outcome language includes the following components: * Brief answer to the charter question * Recommendations and implementation guidance * Rationale for recommendations and implementation guidance We would like to highlight the following elements: * Recommendation 1.5 under A5 (p.6): this proposed recommendation may be revisited after the EPDP Team tackles other charter questions; additional details may need to be fleshed out. * Recommendation 1.6 under A6 (p.9): please pay particular attention to the proposed definition of “grandfathering” and provide input, if any. Please provide any input/suggestion for the draft outcome language on the mailing list by Tuesday, 22 January. Any substantive comments will be discussed during the EPDP Team meeting in about two weeks. Best Regards, Steve, Emily, Ariel

2 4

Notes and action items - IDNs EPDP Meeting #25 - 25 February 2022
by Steve Chan Feb. 25, 2022

Feb. 25, 2022

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(a)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=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> 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_grou…>

1 0

Post Call | IDNs EPDP Team call | Friday, 25 February 2022 at 13:30 UTC
by Devan Reed Feb. 25, 2022

Feb. 25, 2022

Dear all, All recordings for the IDNs EPDP Team call held on Friday, 25 February 2022 can be found on the agenda wiki<https://community.icann.org/x/sIH3Cg> page (attendance included) and the GNSO Master Calendar. <https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) * Transcript For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-epdp-idn-team/> and the main wiki page<https://community.icann.org/x/uAPpCQ>. Thank you! Kind Regards, Devan

1 0

**REMINDER** Meeting Invitation | IDNs EPDP Team | Friday, 25 February 2022 at 13:30 UTC
by Julie Bisland Feb. 25, 2022

Feb. 25, 2022

Dear all, The IDNs EPDP Team meeting is scheduled on Friday, 25 February 2022 at 13:30 UTC for 90 minutes. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/sIH3Cg * Check your time zone: https://tinyurl.com/3eazuhrf [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3eazuhrf__;!!PtGJab4!r04us97…> ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan

4 4

Meeting Invitation | IDNs EPDP Team | Thursday, 03 March 2022 at 13:30 UTC
by Devan Reed Feb. 25, 2022

Feb. 25, 2022

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 03 March 2022 at 13:30 UTC for 90 minutes. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/toH3Cg * Check your time zone: https://tinyurl.com/2p9ak8f ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan

1 0

12 MINTUES**REMINDER** Meeting Invitation | IDNs EPDP Team | Friday, 25 February 2022 at 13:30 UTC
by Devan Reed Feb. 25, 2022

Feb. 25, 2022

Dear all, The IDNs EPDP Team meeting is scheduled on Friday, 25 February 2022 at 13:30 UTC for 90 minutes. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/sIH3Cg * Check your time zone: https://tinyurl.com/3eazuhrf [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3eazuhrf__;!!PtGJab4!r04us97…> ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan

1 0

Proposed Agenda - IDN EPDP Meeting #25 - Friday 25 February 2022 at 13:30 UTC for 90 minutes
by Emily Barabas Feb. 23, 2022

Feb. 23, 2022

Dear all, Please find below the proposed agenda for our meeting on Friday 25 February 2022 at 13:30 UTC. Kind regards, Ariel, Steve, and Emily IDN EPDP Meeting #25 Proposed Agenda 1. Roll Call & SOI Updates (2 minutes) 2. Welcome & Chair Updates (5 minutes) 3. Continue discussion on Charter Questions A7, A9, D1b, and B4 (80 minutes) * Working documents<https://community.icann.org/pages/viewpage.action?pageId=176622687> 4. AOB (3 minutes)

1 0

Request for extension of deadline for comments on CQ A5/A6
by Satish Babu Feb. 22, 2022

Feb. 22, 2022

Dear Donna The ALAC team for EPDP on IDNs has been working on our submission on Charter Questions A5 and A6. While most of our response is ready, there are still a few points that need resolution. We would therefore request for an extension of the submission deadline until end-of-day next Wednesday (02 Mar 2022), as this would give us an opportunity to discuss among ourselves, and, if required, also enable us to consult the ALAC Consolidated Policy Working Group (CPWG), which meets every Wednesday. With kind regards satish

2 1

Please read! | ICANN73 GNSO Policy Briefing & ICANN73 Policy Outlook Report Available for Download
by Julie Bisland Feb. 17, 2022

Feb. 17, 2022

Dear All, Please find the GNSO Policy Briefing and Policy Outlook Report links below for ICANN73. GNSO Policy Briefing ICANN73 Edition: http://go.icann.org/gnsobriefing [go.icann.org]<https://urldefense.com/v3/__http:/go.icann.org/gnsobriefing__;!!PtGJab4!uV0…> ICANN73 Policy Outlook Report: https://go.icann.org/outlook73 [go.icann.org]<https://urldefense.com/v3/__https:/go.icann.org/outlook73__;!!PtGJab4!uV0zw…> Thank you. With kind regards, Julie -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 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=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> 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_grou…>

1 0

Notes and action items - IDNs EPDP Meeting #24 - 17 February 2022
by Emily Barabas Feb. 17, 2022

Feb. 17, 2022

Dear all, Please find below the notes and action items from today’s meeting on Thursday, 17 February 2022 at 13:30 UTC. Kind regards, Ariel, Steve, and Emily Action Items: Action Item #1: Staff to double-check transaction fees listed on slide 11 from today’s call. Notes – IDNs EPDP Call – 17 February 2022 Welcome & Chair Updates * Reminder to provide feedback on draft language for charter questions A5 and A6 by next week Tuesday (22 February). If the groups that members represent are comfortable with the language, please confirm on the mailing list by the deadline. * The leadership team met earlier this week to review the project plan. While the EPDP Team is not moving through the charter questions as quickly as anticipated, we are not going to submit project change request (PCR) yet. The group will focus on progress towards key milestones in the project plan, and in particular the Initial Report target date. The EPDP Team will revisit the project plan in three months when the group has a better sense of the timing for delivery of the Initial Report. * Reminder: Next week’s the meeting is rescheduled to Friday (25 February) to avoid conflicts with ICANN73 Prep Week sessions. Deliberations on Topic D [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1h34xShdFFjRo…>: Charter question D1b * Slides 2-4 – breakdown of the three parts of charter question D1b, including summary of discussions to date and additional elements for the EPDP Team to discuss. The focus of today’s discussion will be Part 2: An existing RO seeks to activate allocatable variant label(s) of its existing gTLD. * Slide 5 – Existing gTLDs with allocatable variants. * Slide 6 – Number of self-identified variants of Arabic and Chinese gTLDs from the 2012 round and the number of allocatable variants among the self-identified ones. * Comment: Information about self-identified variants from the 2012 round was used in the objections process as well as in the evaluation of contention sets. If the variants overlapped, they would be used in the contention set. The EPDP Team should keep in mind that these self-declared variants were not completely unused in the 2012 round. * Comment: All that happened during the last round is historical data. Many TLDs have changed hands since then, so other information will also need to be taken into account in planning for future processes. * Response: We need to marry what has happened in the past with what needs to happen in the future. We will seek to find the best path. * Slide 7 – Review of IDN-specific application questions from the 2012 round. * Comment: Using RZ-LGR would replace the need to request the applicant the IDN table for the top-level label (Q15). * Slide 8-9 – Overview of the application process flow in the 2012 round. * For consideration: what elements of the 2012 application process would still apply in cases where an existing RO seeks to activate allocatable variant label(s) of its existing gTLD? * Comment: While self-identified variants were taken into account to some extent during the 2012 round, with the RZ-LGR there are more variant possibilities now. * Question: which parts of the process did self-identified variants go through in the 2012 round? * Response: RZ-LGR did not exist, but the IDN Tables needed to be included in the application. Self-identified variants were likely identified by the applicant drawing the IDN Tables. Self-identified variants were taken into account in string similarity evaluation and objections processes. They were parts of these elements in relation to the IDN application, but the self-identified variants were not evaluated themselves. * Comment: While we can consider which potential applicants might apply for variants, we don’t know for sure if they will be interested in doing so. One question to consider is whether they can just go ahead and obtain variants between application rounds. If existing gTLD operators do apply for a variant, it’s important to consider staffing needs to be put into place to conduct the evaluation. One possibility is to make sure there is an opportunity for existing gTLD operators to apply for their variants before the next round opens. * Comment: It is important to consider evaluation elements that do not need to be completed repeatedly. There should be a simplified round existing gTLD operators do apply for a variant. * For discussion: Based on the information provided, what process should be used for an existing RO to activate allocatable variant label(s) of its existing gTLD? Could this happen on an ad hoc basis or is a more structured opportunity needed? Would a simplified round make sense? What application questions are appropriate? * Comment: A simplified round might be seen as a workaround for certain applicants. It will be viewed by some as preferential treatment. From one perspective, SubPro did not support special application rounds for specific types of applications. * Comment: The EPDP Team should not use the term “application” in discussing the delegation of variants. It should use the term “activation” of variants because there is some support in the EPDP Team for having single application for a variant set. * Comment: The process for requesting and obtaining variants should be ongoing, whether for the previous round or future rounds. Successful applicants should be able to activate allocatable variants at any time. Since the process operates on a cost recovery basis, when we talk about activation of variants, we should consider principles to take into account in the calculation of fees. * Comment: The terminology of “apply” vs. “activated” is important and may inform how these labels are delegated in the root zone. * Comment: In principle, simple processes are better. ICANN already has processes for evaluating labels in general and IDN labels specifically, including evaluating technical competency for IDN services. We can consider a simple process for existing ROs to obtain variants, with the addition of a few questions regarding management of variants. No one is frontrunning here. The existing ROs are entitled to those variants. * Comment: In addition to the technical evaluations, there were other processes from the 2012 round we need to take into account, for example the EPDP Team should consider whether string similarity is still relevant and if so, how to we incorporate it. * Comment: In general, activation of variant TLDs should not be only possible in a future round, because this may take a lot of time. However, some applicants will be at a disadvantage if this is the case -- specifically, an applicant for a label that the applicant considers to be a variant that is not a variant according to the RZ-LGR. This applicant would have to wait until the next round to apply. Example: .quebec. * Staff Comment: Regarding the framing of deciding between a simple vs. complex process – the core issue is that we need to ensure that the variant is being evaluated to make sure it is being introduced and managed in a safe and secure manner. The EPDP Team needs to make sure that the necessary elements are taken into account in completing the evaluation. There are two elements of the evaluation processes: those involving the applicant vs. those involving the string itself. The EPDP Team may want to take that into account when considering which elements are applicable to evaluating variants. In the 2012 round, the processes involving the string itself allowed the community/public to provide their input on the string. * Comment: If a special process is needed, it might be able to draw on the model of the fast track process for ccTLDs. * Data point presented by staff: There is a considerable difference between the number of self-identified variants from the 2012 round and those generated through the RZ-LGR. There were approximately 170 self-identified variants from the 2012 application round excluding Arabic script, whereas the number of variant labels generated through the RZ-LGR is around 1,000 if you exclude those in the Arabic script. For the numbers including the Arabic script, the number of self-identified variants is still around 200. The variant labels generated through the RZ-LGR is around and 20,000 if you include the Arabic script. * Next Steps: Develop a strawman proposal of a discrete process for further consideration. * Slide 10 – Recap of discussion on fees (part 3 of charter question D1b) * Slide 11 – Overview of fees from the 2012 round * Comment: Applicants from the 2012 round have already paid the application fee of $185.000. This should potentially be considered in the activation of variants. Would applying for a variants set include additional costs, or should it be considered that the applicant has already paid their fees in 2012? The revenue neutral model should be taken into account. * Comment: In the TMCH, each string is treated separately with an associated fee. We should look at this model as we consider the question. Action Item: Staff to double-check transaction fees listed on slide 11 from today’s call. AOB * For further discussion: Consider whether the meeting should be 2 hours every other week.

1 0

Post Call | IDNs EPDP Team call | Thursday, 17 February 2022 at 13:30 UTC
by Devan Reed Feb. 17, 2022

Feb. 17, 2022

Dear all, All recordings for the IDNs EPDP Team call held on Thursday, 17 February 2022 can be found on the agenda wiki page <https://community.icann.org/x/qIH3Cg> (attendance included) and the GNSO Master Calendar. <https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) * Transcript For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-epdp-idn-team/> and the main wiki page<https://community.icann.org/x/uAPpCQ>. Thank you! Kind Regards, Devan

1 0

RESCHEDULED DUE TO ICANN73 PREP WEEK | Meeting Invitation | IDNs EPDP Team | Friday, 25 February 2022 at 13:30 UTC
by Devan Reed Feb. 17, 2022

Feb. 17, 2022

Reminder: Meeting rescheduled due to ICANN73 Prep Week. Please ONLY remove the 24 February meeting and update with the attached .ics for 25 February. Dear all, The IDNs EPDP Team meeting is scheduled on Friday, 25 February 2022 at 13:30 UTC for 90 minutes. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/sIH3Cg * Check your time zone: https://tinyurl.com/3eazuhrf [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3eazuhrf__;!!PtGJab4!r04us97…> ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan

1 0

15 MINUTES **REMINDER** Meeting Invitation | IDNs EPDP Team | Thursday, 17 February 2022 at 13:30 UTC
by Devan Reed Feb. 17, 2022

Feb. 17, 2022

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 17 February 2022 at 13:30 UTC for 90 minutes. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/qIH3Cg * Check your time zone: https://tinyurl.com/y2bv56bt [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/y2bv56bt__;!!PtGJab4!qbmu-7g…> ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan

1 0

Proposed Agenda - IDN EPDP Meeting #24 - 17 February 2022 at 13:30 UTC for 90 minutes
by Emily Barabas Feb. 17, 2022

Feb. 17, 2022

Dear all, Please find below the proposed agenda for our meeting on 17 February 2022 at 13:30 UTC. Kind regards, Ariel, Steve, and Emily IDN EPDP Meeting #24 Proposed Agenda 1. Roll Call & SOI Updates (2 minutes) 2. Welcome & Chair Updates (5 minutes) 3. Deliberations on Topic D<https://docs.google.com/document/d/1h34xShdFFjRoZo9TKkHq1v9IRAiif18066a79uJ…>: Charter questions D1b (80 minutes) 4. AOB (3 minutes)

3 2

**REMINDER** Meeting Invitation | IDNs EPDP Team | Thursday, 17 February 2022 at 13:30 UTC
by Julie Bisland Feb. 16, 2022

Feb. 16, 2022

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 17 February 2022 at 13:30 UTC for 90 minutes. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/qIH3Cg * Check your time zone: https://tinyurl.com/y2bv56bt [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/y2bv56bt__;!!PtGJab4!qbmu-7g…> ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan

1 0

ICANN73 GNSO Sessions - How to Get Organized / Remote Participation Details
by Julie Bisland Feb. 11, 2022

Feb. 11, 2022

Dear all, Now is the moment to prepare your schedules for ICANN73! There will be no calendar invitations sent, as the meeting schedule allows you to download all sessions of interest to you, to your individual calendars. Please read the below points for a seamless ICANN73! YOU MUST REGISTER FOR ICANN73 INFORMATION * Sign into your ICANN Account, or create an account here [account.icann.org]<https://urldefense.com/v3/__https:/account.icann.org/login__;!!PtGJab4!r0Vr…>. * Register for ICANN73 by clicking in the ICANN SERVICES menu and selecting Meeting Registration and click on the ICANN73 Registration link. Click here [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> for detailed instructions. Access the ICANN73 Schedule * ICANN73 schedule: https://73.schedule.icann.org/ [73.schedule.icann.org]<https://urldefense.com/v3/__https:/73.schedule.icann.org/__;!!PtGJab4!r0Vro…> For security purposes, participation links will be posted 24-hours prior to the session start times. * ICANN73 GNSO Sessions have been grouped on the ICANN73 GNSO wiki page<https://community.icann.org/x/Fc0GCw>. Create your own schedule: * The ICANN Meeting website allows you to download all GNSO-related meetings to your inbox calendar in one go. For detailed instructions on how to create your personalized ICANN73 schedule and import your schedule to your calendar, click here [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>. Review the Participation Tools and update Zoom * All sessions will use Zoom rooms. Access details are available 24hrs prior on the ICANN73 Meeting Schedule [73.schedule.icann.org]<https://urldefense.com/v3/__https:/73.schedule.icann.org/__;!!PtGJab4!r0Vro…>. * Visit the Participation Tools page [73.schedule.icann.org]<https://urldefense.com/v3/__https:/73.schedule.icann.org/participation-tool…> for links to download the latest version of Zoom for access to the ICANN73 sessions. * Please see the ICANN Meeting Virtual Participation How-To Guide [73.schedule.icann.org]<https://urldefense.com/v3/__https:/73.schedule.icann.org/attend__;!!PtGJab4…> for more information on how to get the most out of the virtual meeting tools. Links to Bookmark ICANN73 Meeting Schedule [73.schedule.icann.org]<https://urldefense.com/v3/__https:/73.schedule.icann.org/__;!!PtGJab4!r0Vro…> GNSO ICANN73 Wiki Page<https://community.icann.org/x/Fc0GCw> GNSO Session agendas<https://community.icann.org/x/EM0GCw> For all GNSO meeting-related queries (RP or others), please email us at: gnso-secs(a)icann.org and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 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=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> 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_grou…>

1 0

RESCHEDULING DUE TO ICANN73 PREP WEEK | Meeting Invitation | IDNs EPDP Team | Friday, 25 February 2022 at 13:30 UTC
by Devan Reed Feb. 10, 2022

Feb. 10, 2022

Please note: Sending this invitation two weeks in advance to give everyone the opportunity to update their calendars. Please ONLY remove the 24 February meeting and update with the attached .ics for 25 February. Dear all, The IDNs EPDP Team meeting is scheduled on Friday, 25 February 2022 at 13:30 UTC for 90 minutes. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/sIH3Cg * Check your time zone: https://tinyurl.com/3eazuhrf ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan

1 0

IDNs EPDP Team meeting
by ICANN Policy Calendar Feb. 10, 2022

Feb. 10, 2022

Meeting: IDNs EPDP Team meeting Date/time: Friday, 25 February 2022 at 13:30 UTC for 90 minutes Please click the link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the agenda wiki page: https://community.icann.org/x/h4H3Cg (06 January, see future dates on the left side) * For other places see: https://tinyurl.com/2p88cjd8 ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands.

1 0

Reschedule IDNs EPDP Meeting during ICANN73 Prep Week
by Ariel Liang Feb. 10, 2022

Feb. 10, 2022

Dear EPDP Team, As some of you may be aware, the ICANN73 Prep Week<https://73.schedule.icann.org/prep-week-schedule> Policy Update Webinar is scheduled on Thursday, 24 February at 13:00-14:30 UTC. It will conflict with the IDNs EPDP Team’s meeting that week and affect attendance of members and support staff. Would you be able to meet on Friday, 25 February at 13:30-15:00 UTC instead? In the absence of objections, staff will update the invite following this Thursday’s call. Thank you for your help and understanding. Best Regards, Ariel Ariel Xinyue Liang Policy Sr. Specialist Internet Corporation for Assigned Names and Numbers (ICANN)

3 3

Post Call | IDNs EPDP Team call | Thursday, 10 February 2022 at 13:30 UTC
by Devan Reed Feb. 10, 2022

Feb. 10, 2022

Dear all, All recordings for the IDNs EPDP Team call held on Thursday, 10 February 2022 can be found on the agenda wiki page <https://community.icann.org/x/pIH3Cg> (attendance included) and the GNSO Master Calendar. <https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) * Transcript For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-epdp-idn-team/> and the main wiki page<https://community.icann.org/x/uAPpCQ>. Thank you! Kind Regards, Devan

1 0

Notes and action items - IDNs EPDP Meeting #23 - 10 February 2022
by Emily Barabas Feb. 10, 2022

Feb. 10, 2022

Dear all, Please find below the notes from today’s meeting on Thursday, 10 February 2022 at 13:30 UTC. Kind regards, Ariel, Steve, and Emily Action Items: None Notes – IDNs EPDP Call – 10 February 2022 SOI Updates * Satish Babu’s SOI has been updated to reflect that he is now the ALAC Liaison to the UASG. Welcome & Chair Updates * Reminders: * Staff has sent draft language for charter questions A5 and A6 to the mailing list. Members are encouraged to respond on list, even if they approve of the language. * Some of the charter questions have been re-sequenced, the questions we address today reflect this new order. Charter question B3 * Slide 3 – context on charter question B3. * Comment: It may be useful to consider that the backend registry service provider can be different after some time. * Response: The registry should keep using the same RSP. If a change of owner happens, all variant TLDs should be migrated at the same time, so that it is easier to enforce policies that not only cover the top level but the second level as well. * Comment: It is not necessary to enforce that the same nameservers are used for all in a set if the registry operator and backend service provider are the same. The same rules from the registry can be enforced if those policies are in place. * Comment: In case of a backend change, all variants should change to the same backend at the same time. * Comment: Physically, you will not be able to have the same nameservers without damaging the cloud. Support expressed for not requiring the same nameservers. * Summary: There does not appear to be anything new to add for B3. * General support expressed for the idea that if there is a change in the backend, all variants should change to the same backend at the same time. Some support expressed for including this as implementation guidance. * Suggestion to note that this is a matter of implementation rather than something for the IRT to handle. Charter question D1 * Slide 5 – overview of D1. Charter question D1a * Slide 6 – context on D1a. * Comment: There is nothing wrong with having one agreement where there is a new schedule that covers variants. This is important because there is a relationship between the way the operator manages the TLD and variants and it is too confusing if there are separate agreements. It will be inefficient to have multiple agreements. There could be a special agreement when an IDN is delegated and its variants are delegated. Base terms and conditions will apply, but there are special provisions for the variant relationships that should be in a schedule. * Questions: What do separate agreements entail? Would these agreements be associated with registration fees later? * Response: The RAs are posted on ICANN’s website. We have not yet answered the question about fees. * Comment: It seems logical to have one agreement that includes the variants. * Additional support expressed for having one agreement. The agreement is an important part of mapping the label and the variant labels together. In terms of fees, these would be based on billable transactions under the TLD. These would be generally uniform but dependent on the TLD implementation. * Comment: Creating a new agreement will take a significant amount of time. Annex A is an appropriate place to include provisions relating to variants. * Comment: If we agree that a single contract is appropriate, we can leave it to implementation to determine exactly how the contract is adapted for this purpose. * Comment: Having one agreement for multiple TLDs is common practice in the industry (for example in RRAs), so it should be possible in this context. * Comment: Additional support for keeping all labels in a “bundle” under a single contract because they are closely interlinked. EPDP might want to consider using and defining a term, perhaps “bundle”, to refer to such a group. * Comment: We shouldn’t use marketing terms for a technical concept. Bundling is a marketing term, which doesn’t necessarily refer to variants. Using this term will create confusion. We should use “IDN label and its variants.” * Comment: We need to be clear in terms of terminology – for example, the term is “set” in the staff paper. * Comment: We are currently talking about the agreement itself – rights and obligations of contracted parties – this should be separate from the discussion of fees. * Comment: We are talking about the same entity principle. It seems logical and efficient that the legal agreement comes in a single form with a schedule, exhibit, or annex that provides details about the variant set. These TLDs are supposed to behave as a set. The same entity principle will exist throughout the lifecycle. This can be accounted for in a single agreement. * Question: The RA doesn’t currently call out the registry service provider for an registry operator. If we have a requirement that a set has the same RSP, does this need to be included in the RA? * Question: Should the group have a recommendation or implementation guidance to update the RA in line with this discussion? * Comment: Support expressed for a glossary to define label states discussed in A9 and A10, as well as language related to sets, reserved strings, etc. At the same time, it is important to be clear about the different categories of terms and make sure they are not conflated. * Comment: The only thing we need to say for this charter question is that there should be a single RA for a set. The rest can be handled by org implementation. * Comment: The RA has provisions and requirements for the RSP and there are rules for changing the RSP. It is easy to add to the RA that an registry operator can’t change a material subcontractor for one part of the set without changing it for the rest of the set. * Summary: General agreement that it is appropriate to have one shared RA per variant set. * Comment: A separate process for existing IDN TLDs should be developed. * Comment: We have not had variants before. That was not possible from a policy perspective. The NGO-ONG case was an example of a “bundle.” This could be looked at more closely. Charter question D1b * Slide 7 - context on D1b. * Suggestion: First focus on the process by which an applicant applies for a new IDN gTLD and seeks to obtain allocatable variants. * Comment: We should not think about trying to keep the number of applications low by imposing fees. Each variant label should not be a separate complete application. A registry needs to prove to evaluators that it can manage the set. This should be reflected in the application. ICANN and the evaluators need to be able to look at the big picture and it is not manageable to do this with multiple applications. This issue should be considered apart from the fee question. * Additional support for the idea from a technical and security and stability perspective, the applicant should be able to explain how it will manage the set. If the applicant is applying for multiple strings in a set at the same time, this should be one application. If variants in a set are applied for a different times, then there need to be separate applications. * Further support for one application. For applications that involve IDN variants that need to be activated, there need to be additional application questions to address how the set will be handled operationally. The cost should be covered as a separate discussion. The application process is completed on a cost recovery basis per round. This is an important principle. Some applications are more complicated and some are less complicated, but they pay the same fee. We should make sure that IDN applications are not “second class” or required to pay more. In some cases, the TLD is not complete without variants. The variants are part of the TLD experience. We should not penalize the applicant in these cases. * Comment: If you have a set of variants, it will likely have to go through special panel which is not required in the case of a single application for a single string. If the applicant pays the same fee for the set, it is not fair to other IDN applicants that have to pay for each string separately. * Comment: There are three possible scenarios: 1. The RO is applying for a new gTLD and also a variant 2. The RO already has a gTLD and is applying only for a variant. 3. Other scenarios, for example if an RO is applying for more than one variant TLD at the same time against a given gTLD. Each might call for different sub-processes. * Response: For the purposes of the current discussion, we are only talking about scenario 1. * Summary: Some agreement that from a process perspective, for a new application, there is only one application for the label and its variant set. There is a need for the applicant to explain how it will manage the set. * Next topic: Discussion about process by which an existing RO could apply for or be allocated a variant for its existing gTLD. * Does this need to happen during an application round or can it happen outside of a round? Would there need to be the same requirements to demonstrate the ability to manage the set? * Additional considerations: When a TLD string goes through the application process, it there is an opportunity for community review. There is an objection process, string similarity process, etc. A variant, while administratively bound, is still a string that goes into the root zone. From a technical perspective, it may need to go through many of the same steps and reviews as other strings. Would the applicant need to apply for the potential variants to go through the processes or would there be some type of pre-approval process that could take place? * Response: It makes sense that the evaluations and objections processes be done up front. The entire set of variants need to be considered throughout the process, including from the beginning. * Clarification regarding charter questions: Topic E of the charter discusses string similarity, objection, contention sets, reserved strings, and other details. Question B4 covers the timing and sequence aspect of the application process. Charter question B4 * In initial discussions that touch on the fees issue, there appears to be different perspectives. The group will need to return to this topic.

1 0

Meeting Invitation | IDNs EPDP Team | Thursday, 17 February 2022 at 13:30 UTC
by Devan Reed Feb. 10, 2022

Feb. 10, 2022

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 17 February 2022 at 13:30 UTC for 90 minutes. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/qIH3Cg * Check your time zone: https://tinyurl.com/y2bv56bt ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan

1 0

15 MINUTES **REMINDER** Meeting Invitation | IDNs EPDP Team | Thursday, 10 February 2022 at 13:30 UTC
by Devan Reed Feb. 10, 2022

Feb. 10, 2022

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 10 February 2022 at 13:30 UTC for 90 minutes. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/pIH3Cg * Check your time zone: https://tinyurl.com/fwam26t3 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/fwam26t3__;!!PtGJab4!ovVLO3B…> ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan

1 0

**REMINDER** Meeting Invitation | IDNs EPDP Team | Thursday, 10 February 2022 at 13:30 UTC
by Julie Bisland Feb. 9, 2022

Feb. 9, 2022

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 10 February 2022 at 13:30 UTC for 90 minutes. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/pIH3Cg * Check your time zone: https://tinyurl.com/fwam26t3 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/fwam26t3__;!!PtGJab4!ovVLO3B…> ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan

1 0