November 2021 - Gnso-epdp-idn-team

Proposed Agenda - IDN EPDP Meeting #14 - 2 December 2021 at 13:30 UTC for 90 minutes
by Emily Barabas Nov. 30, 2021

Nov. 30, 2021

Dear all, Please find below the proposed agenda for our meeting on 2 December 2021 at 13:30 UTC. Kind regards, Ariel, Steve, and Emily IDN EPDP Meeting #14 Proposed Agenda 1. Roll Call & SOI Updates 2. Welcome & Chair Updates 3. Written Early Input<https://community.icann.org/display/epdpidn/Community+Input> from SO/AC/SG/Cs 4. Continued Deliberations on Topic A: Consistent Definition and Technical Utilization of RZ-LGR (Topic A working document: live version [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1I9dSd7alSvz9…> in Google Docs, archived versions in MS Word on wiki<https://community.icann.org/display/epdpidn/Working+Documents>) * Focus on charter question A4 * Introduce charter question A5 1. AOB

1 0

Draft Outcome: Charter Questions A1)-A3)
by Ariel Liang Nov. 29, 2021

Nov. 29, 2021

Dear EPDP Team, Per action item for staff to formulate the outcome based on the EPDP Team deliberation of questions a1)-a3), please see the “Draft Outcome” google doc for Topic A here: https://docs.google.com/document/d/1Bt0LT45UaLynFNverh1nJhyvq6q6NxgSFAOnOp2… (it also resides on the wiki page here: https://community.icann.org/x/XwyHCg) This document captures the draft language to be incorporated in the EPDP Initial Report, which includes but not limited to the following components: * Answer to charter question * Recommendations and implementation guidance * Rationale for recommendations and implementation guidance These components are modeled after those in the SubPro Final Report and reports of other (E)PDPs. There is an “Open Item” section under question a3), which will likely be removed after EPDP Team’s discussion is closed for that item; additional recommendation and/or implementation guidance may be developed as a result of the discussion. Staff will update this google doc as the EPDP Team works through the Topic A charter questions and develops draft outcome. For the current text under questions a1)-a3), please provide any input/suggestion on the mailing list by Monday, 13 December. Any substantive comments will be discussed during the EPDP Team meeting on Thursday, 16 December. Thank you for your review. Best Regards, Steve, Emily, Ariel Ariel Xinyue Liang Policy Sr. Specialist Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

For Review - Early Written Input Received on IDN EPDP Charter Topics
by Emily Barabas Nov. 22, 2021

Nov. 22, 2021

Dear all, As you will recall, the EPDP Team sent requests at the end of September to SO/AC/SG/Cs seeking early written input on the topics within the EPDP’s Charter. Groups were requested to provide feedback by 10 November. Three groups have responded. Please find attached the input received from the RySG, SSAC, and ccNSO (note: ccNSO input was drafted by the ccPDP4 Variant Management SubGroup). You can also find copies of the written input on the wiki here: https://community.icann.org/display/epdpidn/Community+Input. Please take the time to review these documents. Comments that specifically address charter questions under Topic A have been added to the relevant sections of the working document here<https://docs.google.com/document/d/1I9dSd7alSvz9ZFo0SRxEJdbvTXuYKxfZpxcKVhi…>. As deliberations progress to the other Charter Topics, the relevant comments from the written input will also be included in the applicable working documents. If you have any questions, please feel free to share them on list. Kind regards, Ariel, Steve, and Emily Emily Barabas Policy Development Support Senior Manager Internet Corporation for Assigned Names and Numbers (ICANN) Phone: +31 (0)6 84507976 www.icann.org<http://www.icann.org/>

1 0

Post Call | IDNs EPDP Team call | Thursday, 18 November 2021 at 13:30 UTC
by Devan Reed Nov. 18, 2021

Nov. 18, 2021

Dear all, All recordings for the IDNs EPDP Team call held on Thursday, 18 November 2021 can be found on the agenda wiki page <https://community.icann.org/x/hwO7Cg> (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

2 1

Notes and action items - IDNs EPDP Meeting #13 - 18 November 2021
by Emily Barabas Nov. 18, 2021

Nov. 18, 2021

Dear all, Please find below the notes from today’s meeting on Thursday, 18 November 2021 at 13:30 UTC. Best regards, Ariel, Steve, and Emily Action Items: Action Item #1: Drawing on the high-level agreements, leadership team to draft response to charter question A3 and corresponding recommendations for review by the EPDP. Notes – IDNs EPDP Call – 18 November 2021 Welcome & Chair Updates * The working group is currently running somewhat behind the anticipated schedule. There will be further discussion about whether adjustments will be needed to the call schedule to make up time or whether the work plan needs to be adjusted. Continued Deliberations on Topic A Charter question A3 * First, seek to agree on high-level points, and then the leadership team will draft a response to the charter question. Leadership will share this text on the mailing list and provide members with two weeks to review and provide feedback before we move on. * High-level points for A3: 1. An applicant can challenge an evaluation determined by the DNS Stability Panel that the applied-for TLD label, whose script is supported by the RZ-LGR, is “invalid” 2. Eligibility for filing such a challenge is limited to the applicant’s belief that the DNS Stability Panel has incorrectly assessed the label as “invalid”. 3. The evaluation challenge processes and criteria applicable to the DNS Stability Review recommended in the SubPro Final Report should be used for such a challenge. * Comment: On the second point, should it also include cases where the applicant believes that the algorithm has been applied incorrectly (the application system is believed to be wrong)? * Response: Ultimately it will be the panel that will make the assessment. It may be helpful to add some clarification that the panel will be validating the outcome of the algorithmic check. * Support for the high-level points, although some additional detail is needed about the role of the panel. * Review of applicable recommendations and implementation guidance from SubPro (see slide deck beginning on slide 6). For discussion: 1. Are any or all of the additional SubPro recommendation and implementation guidance applicable? 2. Should any additional implementation guidance be developed? * The only IG item not included in the slides is 32.6, which only applies to appeals (not challenges) and is therefore is not applicable to the scenarios being discussed in this EPDP. * Comment: This group needs to have a good reason to not accept any of the SubPro recs. The SubPro WG reached consensus on their recommendations. * Response: It is still important to review the SubPro outputs to determine if they are applicable to the scenarios we are discussing. To the extent that we believe that they are not, we need to understand the implications and provide a rationale. This is a due diligence step and not intended to manipulate the recommendations from SubPro. * Question: Did SubPro consider cases where an algorithm was part of the evaluation? * Response: SubPro’s discussion focused on the outcomes of the evaluation and not specifically how the evaluations are done. In the end, there is going to be a DNS Stability Panel that validates the results of the algorithmic check. The tools used by the panel is not necessarily a relevant factor. * General support expressed for the framework provided by SubPro. It is up to this EPDP to determine the thresholds for which a challenge can be triggered, but the general framework seems to work. * Question: does there need to potentially be additional implementation guidance with respect to the human element of the evaluation? * Response: We had envisioned that there would be a manual check of the algorithm’s ouput in all cases. Does this address the concern? * Members confirmed that this addresses the concern, as long as it is explained in the EPDP recommendations/response to charter questions. * Reminder: We do not need to adopt SubPro recommendations, we can just include in the charter question that the working group confirms that the SubPro outputs are fit for purpose. Update on data gathering for charter questions A1 and A2 * Data collection task: Use the latest version of the RZ-LGR determine the variant labels of the 2012 New gTLD Round and determine whether the list of calculated variants match those that were identified by the applicant. * For New gTLD applications, there are two cases where there is a difference between self-identified variants and those calculated by the RZ-LGR, one likely related to a spelling variation and the other potentially a typo. There is also one ccTLD case. * For potential further discussion: the definition of “variant” is the one from the RZ-LGR. Outside RZ-LGR a “variant” could be defined as something different e.g. spelling variant. * The purpose of this exercise was to confirm that there is no significant difference between the variants calculated by the RZ-LGR and those self-identified variants from the 2012 round to confirm with the output of the RZ-LGR is consistent with the community’s expectations. * Based on this data, it appears that if we decide that RZ-LGR is the sole source for existing gTLD labels, it won’t have a major impact on existing gTLD operators. * Comment: It was not possible in the 2012 round to self-identify variants in an application for an ASCII TLD. Do we have to consider cases where applicant applied for an ASCII TLD and would have wanted to apply for a variant but were not allowed to do so? Example: . Quebec and .Québec. * Response: This might be an opportunity for .Quebec for submitting a public comment on the Initial Report if they want specific use cases taken into account. * Response: From one perspective, if .Québec is not a variant of .Quebec for the purposes of this group, .Quebec can apply for .Québec as a separate application in the next round. * It would be an interesting exercise but the purpose of the data collection in this case was to inform whether the two sets of variants coincide in order to determine how this should work for applicants who apply for variants in the future. * There is no standard of variants outside of the RZ-LGR. There might be other instances where, since there was no definition, the applicant came up with their own variant, for example a spelling difference. * Comment: RZ-LGR is good to use for the existing applied for TLDs. The few cases where self-identified variants are not in the RZ-LGR, they are alternative spellings and should therefore not be considered variant. * If the RZ-LGR is used for existing gTLDs going forward, some of the self-identified variants would be blocked. Does this impact the WG’s thinking? * Preliminarily, WG members provided feedback that this data should not impact the WG’s conclusion. The WG can return to this on the next call if it requires further discussion. Charter question A2 * There are only a couple of cases in the data where self-identified variants are inconsistent with the list of variants generated by the RZ-LRG. It doesn’t seem that they have been used. Is this correct? * The key here is the legal standing. Former applicants were informed that they would not have legal standing so they would not have claims to the self-identified variants. Those strings were for information purposes. That is the fundamental basis for us making our decision. In drafting the charter questions, it was brought to the group’s attention that these strings were used in some manner, for example in string similarity reviews. Therefore, this group may want to consider whether there is additional implementation guidance that needs to be applied for future processes. One possible assumption: For future processes, the RZ-LGR is used as the sole source, and that determines which variants you have a right to. This is for the working group to consider. * Comment: Data appears to support that no further considerations are needed by this group. * Question: Do we need to investigate if any of these variants that deviate were used in certain processes, such as string contention resolution, in the 2012 round? * Comment: This may not be necessary to investigate further. One of the principles of SubPro is that to the extent that new rules are put in place in the New gTLD Program, those rules apply to the specific round and are not retroactively applied. Therefore, it might not be important how these strings were used in the past. * Agreement that if it is time consuming, the additional data collection may not be necessary. * Comment: To the extent that existing applicants from 2012 round want variants allocated to them going forward, new rules will apply. * If there is a 2012 applicant for an IDN label and they requested variants at that time, there is a question about whether that application is still in the 2012 round or whether it ends up in a future round for the variants. This is something that may become clear as we work through the other questions.

1 0

Meeting Invitation | IDNs EPDP Team | Thursday, 02 December 2021 at 13:30 UTC
by Devan Reed Nov. 18, 2021

Nov. 18, 2021

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 02 December 2021 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 [icann.zoom.us]<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 [gnso.icann.org]<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 [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/uQe7Cg * Check your time zone: https://tinyurl.com/muvpkh49 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

**10 Minutes Reminder** | Meeting Invitation | IDNs EPDP Team | Thursday, 18 November 2021 at 13:30 UTC
by Devan Reed Nov. 18, 2021

Nov. 18, 2021

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 18 November 2021 at 13:30 UTC for 90 minutes. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 [icann.zoom.us]<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 [icann.zoom.us]<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 [gnso.icann.org]<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 [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/hwO7Cg * Check your time zone: https://tinyurl.com/ekdp76rh [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/ekdp76rh__;!!PtGJab4!sual_bH…> 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, Julie

1 0

Re: [Gnso-epdp-idn-team] Proposed Agenda - IDN EPDP Meeting #13 - 18 November 2021 at 13:30 UTC for 90 minutes
by Ariel Liang Nov. 17, 2021

Nov. 17, 2021

Dear all, In preparation for tomorrow’s meeting, staff have attached a slide deck jointly developed by the leadership team and staff. The slide deck includes the recap for charter question A3 (i.e., EPDP Team’s agreement so far) as well as the SubPro recommendations and implementation guidance relevant to the limited challenge mechanism. As mentioned in the proposed agenda, tomorrow’s meeting will discuss whether any or all of the relevant SubPro recommendations and implementation guidance are applicable to the A3 challenge. You are welcome to review the slides and familiarize with the content in advance. Best Regards, Steve, Emily, Ariel From: Gnso-epdp-idn-team <gnso-epdp-idn-team-bounces(a)icann.org> on behalf of Emily Barabas <emily.barabas(a)icann.org> Date: Tuesday, November 16, 2021 at 5:42 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Subject: [Gnso-epdp-idn-team] Proposed Agenda - IDN EPDP Meeting #13 - 18 November 2021 at 13:30 UTC for 90 minutes Dear all, Please find below the proposed agenda for our meeting on 18 November 2021 at 13:30 UTC. Please note that following discussion on the mailing list, beginning this Thursday, meetings will be 90 minutes in length and begin at 13:30 UTC. You will receive updated meeting invites shortly. Kind regards, Ariel, Steve, and Emily IDN EPDP Meeting #13 Proposed Agenda 1. Roll Call & SOI Updates 2. Welcome & Chair Updates 3. Continued Deliberations on Topic A: Consistent Definition and Technical Utilization of RZ-LGR (Topic A working document: live version [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1I9dSd7alSvz9…> in Google Docs, archived versions in MS Word on wiki<https://community.icann.org/display/epdpidn/Working+Documents>) * Charter question A3: recap takeaways from discussion so far and consider whether any additional implementation guidance is needed * Update on data gathering for charter questions A1 and A2 * Discussion of charter questions A1 and A2 (time permitting) 1. AOB

1 0

**REMINDER** Meeting Invitation | IDNs EPDP Team | Thursday, 18 November 2021 at 13:30 UTC
by Julie Bisland Nov. 17, 2021

Nov. 17, 2021

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 18 November 2021 at 13:30 UTC for 90 minutes. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 [icann.zoom.us]<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 [icann.zoom.us]<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 [gnso.icann.org]<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 [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/hwO7Cg * Check your time zone: https://tinyurl.com/ekdp76rh [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/ekdp76rh__;!!PtGJab4!t31xok6…> 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, Julie

1 0

Proposed Agenda - IDN EPDP Meeting #13 - 18 November 2021 at 13:30 UTC for 90 minutes
by Emily Barabas Nov. 16, 2021

Nov. 16, 2021

Dear all, Please find below the proposed agenda for our meeting on 18 November 2021 at 13:30 UTC. Please note that following discussion on the mailing list, beginning this Thursday, meetings will be 90 minutes in length and begin at 13:30 UTC. You will receive updated meeting invites shortly. Kind regards, Ariel, Steve, and Emily IDN EPDP Meeting #13 Proposed Agenda 1. Roll Call & SOI Updates 2. Welcome & Chair Updates 3. Continued Deliberations on Topic A: Consistent Definition and Technical Utilization of RZ-LGR (Topic A working document: live version [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1I9dSd7alSvz9…> in Google Docs, archived versions in MS Word on wiki<https://community.icann.org/display/epdpidn/Working+Documents>) * Charter question A3: recap takeaways from discussion so far and consider whether any additional implementation guidance is needed * Update on data gathering for charter questions A1 and A2 * Discussion of charter questions A1 and A2 (time permitting) 1. AOB

1 0