October 2022 - Gnso-epdp-idn-team

Your Availability for Meetings on 1 Dec & 22 Dec
by Ariel Liang Oct. 31, 2022

Oct. 31, 2022

Dear All, As mentioned during yesterday’s EPDP Team meeting, there may be conflict for some members due to upcoming events and holidays. We would like to check members’ availability for the following two dates: 1. Thursday 1 December – UN IGF will be held during that week and may impact attendance 2. Thursday 22 December – last meeting before the ICANN Holiday Closure If you will not be able to attend either or both of meetings on the two dates above, please respond on list. Based on response, the leadership team will decide whether cancellation and/or rescheduling is necessary. As a reminder, meetings on the following dates will be cancelled: * 3 November – Contracted Parties Summit * 24 November – US Thanksgiving * 29 November – ICANN Holiday Closure Best Regards, Ariel Ariel Xinyue Liang Policy Sr. Specialist Internet Corporation for Assigned Names and Numbers (ICANN)

6 6

Notes and action items - IDNs EPDP Meeting #56 - 27 October 2022
by Emily Barabas Oct. 27, 2022

Oct. 27, 2022

Dear all, Please find below the notes and action items from today’s meeting on Thursday, 27 October 2022 at 13:30 UTC. Kind regards, Ariel, Steve, and Emily Notes and Action Items - IDNs EPDP Call – 27 October 2022 Action Items Action Item 1: Staff to follow up about which EPDP Team meetings may need to be cancelled in November and December. Action Item 2: EPDP members to provide input via mailing list on Charter Question E2 regarding the Legal Rights Objection. Staff to summarize key points for this discussion and Leadership to suggest a path forward. Action Item 3: Leadership team to consider additional framing for the question at hand regarding Charter Question E2 for Community Objections and bring this back to the EPDP Team. Notes Welcome and Chair Updates * Donna provided an update about the EPDP work plan to Council during the GNSO Council meeting on Thursday last week. Councilors appreciated the update and some questions were raised about the possible impact of the revised timeline and work plan on SubPro work. The leadership team will submit a Project Change Request to Council for its consideration at the November Council meeting. * EPDP Team meeting schedule: Proposal to keep meeting at 13:30 UTC on Thursdays and not make any changes with respect to daylight savings. * Additional scheduling items: Meetings will be cancelled on 24 November and 29 December for holidays. Next Thursday, 3 November will be the CP Summit. Many will be attending, so the meeting next will be cancelled. Feedback is welcome about whether to meet on 22 December, as well as whether EPDP Team members will be impacted by the IGF, which clashes with the EPDP Team meeting on 1 December. Action Item 1: Staff to follow up about which EPDP Team meetings may need to be cancelled in November and December. * Donna is relocating permanently to Australia at the end of the year. The group may revisit the timing of calls beginning in January. Continue Discussion of Charter Question B4 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1LlorzuwJlZ1j…>, Discussion Question 2: Based on the observations, is there a compelling reason to allow applications for variant gTLDs of existing gTLDs between application rounds? * Slide 4 – Closed discussion questions on D1b and B4 and open discussion question on B4: Based on the observations, is there a compelling reason to allow applications for variant gTLDs of existing gTLDs between application rounds? * Slide 5 – Strawman Process Flow – Observations * Slide 6 – Additional Observations – Conclusion of D1b Deliberations * Slide 7 – Question for EPDP Team * As a reminder, for the 2012 round, there wasn’t an option for IDN applicants to apply for variants. Question – is there really a need to apply for a variant between rounds following the first round, because that opportunity will exist within rounds going forward? * Comment: In the 2012 round, applicants expressed their interest in variants with the knowledge that they wouldn’t be available yet. Now some users are impacted daily by the lack of availability of variants. Rectifying this is important because there is dilution of trust in the DNS system. The cost of certain processes such as geo names and brands will need to be considered. This does not mean that it will have a direct impact on fees for all. Objections processes, comment processes, etc will be applicable to variants. * Clarification: Are these comments about a standalone IDN round before the next round or also applicable to the question at hand about opportunities between rounds? * Response: The comment is not specific to creating round(s) for variants, but about creating a process for activation that does not happen within a round, just as name servers are changed. There may be feasibility considerations but the group should think it through. * Comment: If the SubPro recommendations are adopted, there should be determinable, short periods between rounds, with regular intervals the offer application opportunities, known in advance. In this world, there would not need to be an opportunity to apply between rounds. If ICANN chooses not to go this route, then this group can give further consideration to the issue of allowing applications for variants between rounds. As a reminder, this is about application for variants. The discussion question is not about delegation or activation, which is more like changing a name server. Comment periods, objections, etc will be applicable for variants. There are good reasons to keep these in rounds because it provides defined windows for observers to monitor applications. * Comment: There is not harm in applying between rounds. ICANN can evaluate costs based on those who are expected to want to apply. If applicants are willing to pay the price they should be able to do so. * Comment: We should assume that there will not be extended intervals between rounds. Some have expressed the disadvantage to Chinese language communities about not having variants available. The next round will be the moment in which existing ROs can first apply for their variants. What is the chance that and RO doesn’t apply for the variants it wants in that first round, resulting in a continued disadvantage? The answer is not known. * Response: Support for an opportunity for ROs from the 2012 round to activate the variants before the next round, after that they can apply for variants as part of rounds. You could focus on those variants that 2012 applicants expressed interest in applying for, which could essentially be considered an application. * Reminder that Section 1.3.3 of the AGB says: “Declaring variant strings is informative only and will not imply any right or claim to the declared variant strings.” “When a variant delegation process is established, applicants may be required to submit additional information such as implementation details for the variant TLD management mechanism, and may need to participate in a subsequent evaluation process, which could contain additional fees and review steps.” * Comment: If someone did list variants for informational purposes, they were not run through string sim or other evaluation elements. Objections would not have been taken with respect to the information provided in that section. This should be taken into account. * Reminder that in last week’s discussion, the EPDP Team concluded that the quickest path forward for IDN applicants for variants is to apply as part of the next round. From a process perspective it is a lot of work and from a timing perspective, it wouldn’t be that much quicker. Last week, the EPDP Team talked about giving prioritization through application queuing procedures in the next round to applications for variants of TLDs that were delegated in the 2012 round. * Comment: It would be helpful to identify reasons why it should not be possible to apply for variants between rounds. * Comment: If IDN variant labels are applied for in rounds, cost recovery takes into account all of the applications in the pool for that round, so costs will be lower. If IDN variant labels are applied for between rounds, the costs will only take into account the cost associated with that few applications. The costs will be very high which creates a potential political issue. * Comment: Last week, we discussed that once the next round is set up from an operational perspective, moving forward if there was an ability to apply for variants between rounds, the costs won’t be as high. * Comment: The share of IDNs is still very low and many users don’t know about IDN gTLDs. UA issues are still significant. Maybe the end users will accept IDN gTLDs in the future, which may make ROs realize that they need to apply for variants. We need to provide for this possibility without such long periods between application opportunities. If a business in China wants to extend their business to Hong Kong or Macau, it may be costly, but you shouldn’t forbid them from doing so. * Comment: The work of this EPDP should not delay the next round. If this EPDP does not conclude in time, the next round goes ahead without variants. If this is the case, then we should have a way to make sure that activation can happen between rounds once the EPDP recommendations can be implemented. * Comment: The EPDP should have a backup plan in case variants are not included in the next round that does allow applicants to include variants in the application and application processes such as string similarity that take into account phase 1 recs. Elements related to phase 2 recs might need to wait. * Summary: Agreements from last week stand. For 2012 applicants, the next opportunity to apply for variants will be the next round and there will be some prioritization. Continue Discussion of Charter Question E2 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1glGuJwSoYlYF…> – Options for Legal Rights and Community Objections · Slide 9 – Legal Rights Objection Recommendation options · Slide 10 – Legal Rights Objection: Option 2 Rationale and Example · The IPC opposes the hybrid model for string similarity review, but if the model is adopted, option 2 will allow for some mitigation. If there is an exception process, option 1 is possible, but option 2 is preferred. Trademark holders should not be prevented from applying for their mark because it is confusingly similar to the blocked variant of another IDN. · Clarification: The IPC believes that if B2 and A1 are applied for in the same round they shouldn’t be a contention set. If A1 is delegated and B2 is applied for in the next round, that is allowed. If that exception process is not put into place, there needs to be a way for B2 to object to A1. · Additional clarification: IPC wants it to be possible for B2 and A1 to coexist. If there is no exception process, the Option 2 won’t be satisfactory. Presumably A1 and B2 will have different meaning and can therefore coexist without confusion. · Response: It is possible that the outcome of a successful objection by B2 could be that A1 could be delegated but A2 could not be requested in the future. · Question: How does the same entity principle come into play here? · Response: The same entity principle is not a problem because it only applies to variants and confusables. · Comment: Just because we allow an objection, it doesn’t mean that the objector will prevail. Different outcomes are possible if B2 objects: * If B2 is successful, A1 can’t be delegated but B2 can be applied for in the future. * If B2 does not prevail, similarity is not strong enough. A1 proceeds and B2 can proceed in a future round. · Comment: If B2 objected to A2 and B2 and A1 are being used for different things, then it’s likely that B2 wouldn’t prevail under the standards of the Legal Rights Objection. Action Item 2: EPDP members to provide input via mailing list on Charter Question E2 regarding the Legal Rights Objection. Staff to summarize key points for this discussion and Leadership to suggest a path forward. * Slide 11 – Community Objection Recommendation – Options * Slide 12 – Community Objection: Option 2 – Rationale and Example * Comment: We are asking the wrong question. We should be asking, “Do we need to create additional standards that would allow a community to prevail?” Action Item 3: Leadership team to consider additional framing for the question at hand regarding Charter Question E2 for Community Objections and bring this back to the EPDP Team. Begin Discussion of Charter Question E6 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1glGuJwSoYlYF…> * Slide 14 – Charter Question E6 * Is there any reason to permit the registration of gTLDs consisting of decorated two-character Latin labels which are not variant labels of any two-letter ASCII labels? If so, rationale must be clearly stated. * What is the question asking: 1. Can a two-letter gTLD label in the Latin script be applied for? 2. Can a two-character IDN gTLD label in the Latin script be applied for? 3. Can a two-character IDN gTLD label in the Latin script that is not a variant of any two-letter ASCII label be applied for? * Slide 15 – ccTLD context * Slide 16 – What Happened in the 2012 Round * Slide 17 – Analyze the Question

1 0

November & December 2022 | IDNs EPDP Team
by Devan Reed Oct. 27, 2022

Oct. 27, 2022

Dear all, Please find the .ics attachments and dates below for the IDNs EPDP Team calls taking place in November and December 2022. Please download them to your calendar. Calls take place every Thursday 13:30 UTC for 90 minutes. The dates are as follows: * Thursday, 03 November 2022 **NO CALL SCHEDULED** * Thursday, 10 November 2022 * Thursday, 17 November 2022 * Thursday, 24 November 2022 **NO CALL SCHEDULED** * Thursday, 01 December 2022 * Thursday, 08 December 2022 * Thursday, 15 December 2022 * Thursday, 22 December 2022 The email invitation for each call will be sent out closer to the date of the meeting. The next call is taking place on 10 November 2022 and the invitation has been sent out. The next call takes place after most daylight savings time changes have occurred. Please check meeting times against the time and date link to ensure the meetings download to your calendar correctly. Nov 10: https://tinyurl.com/mvmhs8bp Thank you. Kind regards, Devan

1 0

Post Call | IDNs EPDP Team call | Thursday, 27 October 2022
by Devan Reed Oct. 27, 2022

Oct. 27, 2022

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

CORRECTED DATE | Meeting Invitation | IDNs EPDP Team | Thursday, 10 November 2022 at 13:30 UTC
by Devan Reed Oct. 27, 2022

Oct. 27, 2022

**Please note: There is no scheduled meeting on 03 November to avoid a scheduling conflict with the Contracted Parties Summit. Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 10 November 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/M4YFDQ * Check your time zone: https://tinyurl.com/mvmhs8bp [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/mvmhs8bp__;!!PtGJab4!_IaEWzk…> 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

Meeting Invitation | IDNs EPDP Team | Thursday, 10 November 2022 at 13:30 UTC
by Devan Reed Oct. 27, 2022

Oct. 27, 2022

**Please note: There is no scheduled meeting on 03 November to avoid a scheduling conflict with the Contracted Parties Summit. Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 27 October 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/M4YFDQ * Check your time zone: https://tinyurl.com/mvmhs8bp 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 Oct. 27, 2022

Oct. 27, 2022

Meeting: IDNs EPDP Team meeting Pattern: Weekly on Thursday’s 10 November – 22 December 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 (10 November): https://community.icann.org/x/M4YFDQ * For other places see (10 November): https://tinyurl.com/mvmhs8bp 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

2-character IDNs
by Jeff Neuman Oct. 27, 2022

Oct. 27, 2022

All, At the end of today’s discussion we talked about whether to allow 2 character Latin Script applications given that 2 character ASCII characters are all reserved for ccTLDs. In line with that, I believe this group should adopt a similar recommendation as was adopted by SubPro for Single Characters, namely: Recommendation 25.4: Single character gTLDs [170] may be allowed for limited script/language combinations where a character is an ideograph (or ideogram) and do not introduce confusion risks that rise above commonplace similarities, consistent with SSAC171 [171] and Joint ccNSO-GNSO IDN Workgroup (JIG) [172] reports. 170 Meaning a character in a U-label. 171 See report here: https://www.icann.org/en/system/files/files/sac-052-en.pdf 172 See report here: https://ccnso.icann.org/sites/default/files/filefield_22667/jig-final-repor… * This would prevent 2 character Cyrillic Script applications as well (not just latin) for things like “ав” “ек” “рш” “ћс” * Or from the Malayalam Script: “ଠട” * Or the Hebrew Script: “ע ס” (and being a descendant from Israelis, I would love to apply for that one for so many reasons) * Or the Ethiopic Script: “ሀሃ” or “ጣፐ” * Or from the Gujarati script “ડ વ” I think that illustrates the point, but I am sure there are more examples. Sincerely, Jeff [cid:image001.png@01D8E9F4.FA740870] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com

1 0

05 MINUTES REMINDER | Meeting Invitation | IDNs EPDP Team | Thursday, 27 October 2022 at 13:30 UTC
by Devan Reed Oct. 27, 2022

Oct. 27, 2022

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 27 October 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/QYKkD * Check your time zone: https://tinyurl.com/4hybjh3y <https://urldefense.com/v3/__https:/tinyurl.com/4hybjh3y__;!!PtGJab4!9XpaiFo…> 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, 27 October 2022 at 13:30 UTC
by Devan Reed Oct. 27, 2022

Oct. 27, 2022

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 27 October 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/QYKkD * Check your time zone: https://tinyurl.com/4hybjh3y <https://urldefense.com/v3/__https:/tinyurl.com/4hybjh3y__;!!PtGJab4!9XpaiFo…> 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