May 2023 - Gnso-epdp-idn-team

Notes and action items - IDNs EPDP Meeting #83 - 25 May 2023
by Steve Chan May 31, 2023

May 31, 2023

Dear all, With apologies for the late delivery, please find below the notes and action items from Thursday’s meeting on 25 May 2023 at 12:00 UTC. Kind regards, Ariel, Emily, and Steve Notes and Action Items - IDNs EPDP Call – 25 May 2023 Action Items * None Notes Roll Call and SOI Updates * None Welcome and Chair Updates * Reminder that the Phase 1 Initial Report is out for public comment and there have been a couple of requests to extend the public comment period. Leadership is willing to extend to 19 June. No concerns expressed. * Update from GNSO Council meeting – presented timeline for Phase 2 work which shows this team concluding in Oct 2025. No concerns expressed from Council. Noted that Phase 2 work has already started and making significant progress, which was not planned to start until the end of 2023. * However, unknown what the comments will look like for Phase 1. Depending on the comments received, it could impact timelines for delivering the Phase 1 Final Report by Nov 2023. * Also requested Council consider a F2F meeting for this EPDP Team, which requires a 6-month lead time. Looking at Nov-Dec timeframe. Same-entity charter questions (C1, C2, C3, C3a) * Slide 3: Reminder of what the charter questions are about. * C1 – extending the same entity principle to existing second-level labels. * C2 – Consider what the definition should be for same-entity (e.g., registrant). Also asks what the impact might be for ROs that already have a contractual provision that allows them to allocate second-level variants. * C3 – Assumes that the answers to C1 and C2 are yes, what object should be used to identify entities as being the same? * There is also C3a, but that is dependent upon the group agreeing that ROID is the right mechanism. C1 * Slide 4: There are existing recommendations from SubPro that require second-level labels, in their various permutations (s1.t1, s1.t1v1 & s1, s1v1, … under t1, t1v1, …) must all be allocated only to the same entity. These two recommendations have already been adopted by the ICANN Board and are currently in implementation. The question is essentially, should these recommendations be extended to existing second-level labels that already exist in the DNS? * What might be helpful is to understand if registry/registrar colleagues can share their experiences. How easy is it to identify when there are variants and set them aside? * Clarification that for this question, we only need to consider variants at the second-level, since top-level variants do not exist. So, we only need to consider example.tld, examplev1.tld, … * For the instances where example.tld, examplev1.tld are both already registered but to different registrants, suggestion that these should be grandfathered and not be forced to take one of them away from one of the entities. * However, if only one of them is registered, do not see an issue with enforcing the same entity requirement going forward. * Question about how difficult it is to set aside variants for second-level domains. Response is that it should not be difficult and that currently, many registries are likely already withholding variants. * Support for grandfathering as removing rights from an existing registrant in favor of another may lead to legal issues. Not sure how easy it will be to identify all existing variants and maintain a database. * Question about further actions registrars could take where second-level variants are registered by different registrants. One response is that registrars often just follow policies and the law, and would not do anything additional. * Another question about grandfathering instances where there are two or more registrants for variants of each other. What happens on an ongoing basis? * Suggestion that grandfathering should be a temporary situation that should be rectified as soon as possible. And that for any other allocatable variants, they should remain withheld so as to avoid making the grandfathering issue worse. Some others agree with this approach as allowing additional variants to be registered will perpetuate the conflict with the policy. * Only when the grandfathering situation is removed should the variants become available again. C2 * Slide 6 – reviewed existing contractual language that allows for the activation of variants. These requirements state that it must be the sponsoring registrar of the canonical name requesting activation and they must have the same NS resource records, but do not require the same entity. * The question here is whether the same entity principle should apply to existing second-level domains where variants are held by more than one registrant. The question is directly related to much of the EPDP Team’s discussions so far in this meeting. * Suggestion that allowing additional variants to continue to be registered doesn’t make the problem worse (where there are two or more registrants for variants of each other). Concerns about to withhold until the issue is resolved creates uncertainty. * Noted that allowing additional variants makes resolving the grandfathering issue more difficult to resolve. * There is no data available about how many instances there are of variants being held my 2 or more registrants. * Registrants are potentially being disadvantaged by not being allowed to register additional variants. The grandfathering can still be unwound if the set of variants is reduced to a single registrant. * Example shared for clarification: There are 4 labels that are variants of each other with two of them registered to two separate registrants. The suggestion from some is that the two unregistered variants should remain unregistered until the grandfathering need is removed. * Allowing variants in this situation doesn’t change the scenario, there are 2 or more registrants for variants of each other. * Grandfathering is to take account of the existing state. It should not be considered forward looking to create more grandfathering complexities. It also seems to allow for the violation of the same-entity principles. * Not sure the same entity principle is broken by allowing additional variants to be registered in a grandfathering situation. Summary of discussions to date: it seems like agreement that the same entity principle should be extended to existing registrations. And it seems like agreement that there should be grandfathering. The remaining questions are around the grandfathering rules. * Good stopping point for this first discussion and pursue next meeting. * There is a second piece of C2 to consider which is the impact of the same entity requirement for existing registries that already have the contractual allowance to activate variants. That contractual allowance is different than the same entity requirement. * Initial thought is that since this consensus policy, ROs will need to comply with it. The existing requirements and new consensus policy will need to be consistent. * Further, there is a feeling that the existing requirements are compatible – could therefore add an additional provision that requires the same registrant. * Discussion whether it should be registrant or legal entity, or both. Comes back to what is commonly understood as what is a registrant. Same entity is same registrant, is the same applicant. Need to define what we mean by same registrant or same entity. Details that need to be included. * A registrant (contact) can also represent a legal body or person or both. * The requirement could be for the same entity, but do not specify the method to ensure the same entity. * Should existing Ros that already have this contractual amendment be required to rely on the same entity principle to allocate or withhold for allocation second-level variants int the future? – answer is yes. Will discuss during leadership team where to go next. Dialogue with SSAC SMEs * Lyman Chapin, John Levine, Jim Galvin, Jiankang Yao and Jaap Akkerhuis from SSAC joined the conversation * Purpose of reaching out to SSAC is following publication of the Initial Report to see if there are any security and stability concerns. Getting a heads up may facilitate reconciling public comment input. * General feedback from SSAC SMEs: Although as individuals have strongly held opinions on some of these topics, as variants do not exist at the DNS level, it is not likely one where SSAC will have specific comments on many of the recommendations as these are mainly focused on the user experience and not the technical level. * SSAC SME feedback: Re. Preliminary Recommendation 8.1 - SSAC60 and the follow up comments is to advocate the conservatism approach because there may be permutation effects at the top level and then the second and third level. Understanding from the GNSO deliberation where that conservatism will be achieved will be what the SSAC would be interested in seeing. Need to assess whether the measures in place will result in conservative activation of variants. Economic factor may determine number of variants that will allocated. For second level they could be sold as a package? Maybe for this a ceiling value should be considered to ensure conservatism? * Chair confirmed that the IDN EPDP team has taken a conservative approach recognizing that variants have not been introduced before. Anticipate that reality will be fairly conservative as only Arabic doesn’t have a limit on the variant labels that can be available at the top-level. Have reached out to the Arabic script level to see if they could assist with what would be a reasonable ceiling. * SSAC SME feedback re. Preliminary recommendation 3.7: In relation to 3.7, the SSAC comments on SubPro essentially said the same as preliminary rec 3.7 so there does seem to be consistency. * Response: no upper bound on total number of TLDs is in line with the variant approach. If someone wants to pay for 1,000 variant TLDs they can do so similar to how someone can apply for 1,000 TLDs that are not variants. * SSAC SME feedback re. preliminary recommendation 8.7: there needs to be a transparent process to update the LZ-LGR. * SSAC will take question about providing feedback back. SSAC 60 and SAC120 did already provide input, but review if further input is deemed necessary. Domain name itself consists of top level and second level so permutations are a potential concern for SSAC. Appreciate that the GNSO has reached out in good faith to engage with SSAC on this topic. * Reminder that public comment period is still open – if SSAC has further input, will try to submit by the deadline. * SAC120 highlights importance of ensuring usage of variants. Preliminary recommendation 3.5 provides for explanation for why variants are needed. Others may come into play as well, for example delegation within a certain period of time. 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

REMINDER | Meeting Invitation | IDNs EPDP Team | Thursday, 01 June 2023 at 12:00 UTC
by Terri Agnew May 31, 2023

May 31, 2023

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 01 June 2023 at 12:00 UTC for 2 hours. 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/YoZXDg * Check your time zone: https://tinyurl.com/3vh2hsm7 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3vh2hsm7__;!!PtGJab4!-rlJcnZ…> 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

ICANN77 GNSO Policy Briefing Available for Download!
by Julie Bisland May 30, 2023

May 30, 2023

Dear All, On behalf of the GNSO Team, I am happy to report that the GNSO Policy Briefing for ICANN77 is now available for download at http://go.icann.org/gnsobriefing [go.icann.org]<https://urldefense.com/v3/__http:/go.icann.org/gnsobriefing__;!!PtGJab4!9ZW…>. Happy reading! Best 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

Meeting Invitation | IDNs EPDP Team | Thursday, 01 June 2023 at 12:00 UTC
by Julie Bisland May 25, 2023

May 25, 2023

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 01 June 2023 at 12:00 UTC for 2 hours. 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/YoZXDg * Check your time zone: https://tinyurl.com/3vh2hsm7 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

Post Call | IDNs EPDP Team call | Thursday, 25 May 2023
by Julie Bisland May 25, 2023

May 25, 2023

Dear all, All recordings for the IDNs EPDP Team call held on Thursday, 25 May 2023 can be found on the agenda wiki page <https://community.icann.org/x/YIZXDg> (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 * Agenda & Notes/Action Items (if applicable) 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, Julie

1 0

ICANN77 GNSO Sessions - How to Get Organized / Remote Participation Details
by Julie Bisland May 25, 2023

May 25, 2023

Dear all, With ICANN77<https://meetings.icann.org/en/icann77> just around the corner, please take a moment to read the information below for a seamless and successful meeting. REGISTER NOW! DEADLINE TO REGISTER IS 07 June 2023! * Sign into Your ICANN Account or create an account here<https://account.icann.org/login>. * Register by selecting the Meeting Registration tile. * Click on the Registration link. Before creating your schedule, please read this page carefully: https://meetings.icann.org/en/remote-participation. If participating on-site, please read the Health and Safety page<https://meetings.icann.org/en/77healthandsafety>. CREATE YOUR MEETING SCHEDULE * Access the ICANN77 schedule here<https://icann77.sched.com/>. The schedule shows up with blank circular radial buttons to the left of each session. Hover over the radial button and click “ADD TO MY SCHEDULE” or just click to add the checkmark. * Once you’ve selected all sessions, click the My Schedule link in the lower left corner or hover over your profile and select My Schedule. * Click the Phone icon * In the bottom section, “Export Calendar”, click the link next to “My Schedule”. When the .ics is exported, add it to the appropriate calendar. OR, after exporting, drag and drop the .ics file into your calendar. * Please remember, for security purposes, participation links will be posted 24-hours prior to the session start times. There will be no calendar invitations sent, as the meeting schedule allows you to download all sessions of interest to your individual calendars Review the Participation Tools and update Zoom * All sessions will use Zoom rooms. Access details are available 24hrs prior. * Visit the Participation Tools page<https://meetings.icann.org/en/remote-participation> for links to download the latest version of Zoom for access to the ICANN Meeting sessions. * Please see the ICANN Meeting Virtual Participation How-To Guide for more information on how to get the most out of the virtual meeting tools. Links to Bookmark ICANN77 Meeting Schedule<https://icann77.sched.com/> GNSO ICANN77 Wiki Page<https://community.icann.org/x/_oZXDg> GNSO Session agendas<https://community.icann.org/x/nIJXDg> For all GNSO meeting-related queries (RP or others), please email us at: gnso-secs(a)icann.org<mailto:gnso-secs@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

**ON IN 5 MINUTES** Meeting Invitation | IDNs EPDP Team | Thursday, 25 May 2023 at 12:00 UTC
by Julie Bisland May 25, 2023

May 25, 2023

**ON IN 5 MINUTES** Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 25 May 2023 at 12:00 UTC for 2 hours. 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/YIZXDg * Check your time zone: https://tinyurl.com/5e9ksvtm [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/5e9ksvtm__;!!PtGJab4!-Yi_LQ-…> 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

**AT THE TOP OF THE HOUR** Meeting Invitation | IDNs EPDP Team | Thursday, 25 May 2023 at 12:00 UTC
by Julie Bisland May 25, 2023

May 25, 2023

**AT THE TOP OF THE HOUR** Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 25 May 2023 at 12:00 UTC for 2 hours. 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/YIZXDg * Check your time zone: https://tinyurl.com/5e9ksvtm [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/5e9ksvtm__;!!PtGJab4!-Yi_LQ-…> 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

ICANN77 Policy Outlook Report is now available for download!
by Julie Bisland May 24, 2023

May 24, 2023

Dear all, The ICANN77 Policy Outlook Report is now available: https://go.icann.org/outlook77 Thank you! Kind regards, Julie

1 0

REMINDER | Meeting Invitation | IDNs EPDP Team | Thursday, 25 May 2023 at 12:00 UTC
by Terri Agnew May 24, 2023

May 24, 2023

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 25 May 2023 at 12:00 UTC for 2 hours. 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/YIZXDg * Check your time zone: https://tinyurl.com/5e9ksvtm [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/5e9ksvtm__;!!PtGJab4!-Yi_LQ-…> 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 #83 - Thursday 25 May 2023 at 12:00 UTC
by Emily Barabas May 24, 2023

May 24, 2023

Dear all, Please find below the proposed agenda for our meeting on Thursday 25 May 2023 at 12:00 UTC (2 hour call). Kind regards, Ariel, Steve, and Emily IDN EPDP Meeting #83 Proposed Agenda 1. Roll Call and SOI Updates (2 mins) 2. Welcome and Chair Updates (5 minutes) 3. Same-entity charter questions (C1, C2, C3, C3a) (50 mins) 4. Dialogue with SSAC SMEs (60 mins) 5. AOB (3 mins) 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

Meeting Invitation | IDNs EPDP Team | Thursday, 25 May 2023 at 12:00 UTC
by Devan Reed May 18, 2023

May 18, 2023

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 25 May 2023 at 12:00 UTC for 2 hours. 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/YIZXDg * Check your time zone: https://tinyurl.com/5e9ksvtm 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

Post Call | IDNs EPDP Team call | Thursday, 18 May 2023
by Devan Reed May 18, 2023

May 18, 2023

Dear all, All recordings for the IDNs EPDP Team call held on Thursday, 18 May 2023 can be found on the agenda wiki page <https://community.icann.org/x/XoZXDg> (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 #82 - 18 May 2023
by Emily Barabas May 18, 2023

May 18, 2023

Dear all, Please find below the notes and action items from today’s meeting on Thursday, 18 May 2023 at 12:00 UTC. Kind regards, Ariel, Steve, and Emily Notes and Action Items - IDNs EPDP Call – 18 May 2023 Action Items Action Item 1: Leadership to draft text reflecting discussion with suggested recommendations for C4, C5, and C6. The EPDP Team’s next conversation can focus on that draft text. Action Item 2: Staff to forward to the EPDP Team the communication to the SSAC regarding next Thursday’s call. Action Item 3: Staff to check on status of ICANN77 meeting schedule and when it will be posted publicly. Notes Welcome and Chair Updates * Thanks to those who joined the webinar yesterday. Attendance was somewhat light, possibly explained by the APAC-friendly time. * No requests yet to extend public comment deadline. Deadline is currently 5 June. * The GNSO has approved a tool and process for working groups to conduct self assessments during the life of the E/PDP. A self-assessment survey will be opened on Monday next week and remain open for three weeks. Members, alternates, and participants will receive an email with details and a link to the survey. Continued IDN table harmonization (charter questions C4, C5, C6) Recap from previous meeting * Slide 3: Charter Questions: C4, C5, C6 * Last week, the EPDP team went over what harmonization is and why it matters * C4 in brief: Should harmonization be required * C5 in brief: If harmonization is needed how should it be accomplished * C6 in brief: Focuses on how IDN Tables should be effectuated * Slide 4: Focus on Charter Question C4 * Slide 5: Recap of Deliberations for Future Applications – C4 * The Team understands what Harmonization is and why it is important (i.e., avoid inconsistent identification of variants). * Members need to check with their groups, but from a principles level, most seem to support the conservative approach of requiring that applicants/Registry Operators must harmonize their IDN tables for a given gTLD and any variant gTLD(s). * Question: Have EPDP Team members had a chance to speak to their groups to confirm what was heard on last week’s call? * Comment: RySG has not yet reached a conclusion, but is leaning towards being conservative and supporting harmonization. * Comment: ALAC has not yet had a chance to discuss. * Slide 6: Focus on Charter Questions C5-C6 * Slide 7: Recap of Deliberations for Future Applicants – C5/C6 * The Team considered the proposals from the staff paper (i.e., Extend Each IDN Table, Extend Label Check Process) and the anecdote from Michael. * However, while the Team recognized these as viable options, initial reactions seemed to indicate a preference for allowing Registry Operators to determine how to achieve harmonization. * The Team reviewed the evolution of IDN Table Format RFCs (RFCs 3743, 4290, and 7940) and what was shared is that at least some registries do not take IDN tables as inputs into their systems. Rather, they export the IDN tables to meet ICANN requirements. If XML were required, it would mean that registries would have to change how they export the table; wouldn’t change system inputs. * Anecdote from Zuan Zhang re: how Chinese Domain Name Consortium (CDNC) coordinates/manages Chinese IDN table * Concerns expressed about considering adoption of 7940 or Reference LGR - both appear outside scope of C6. * Comment: For 7940, it was suggested that the group examine with respect to other CQs. Continued deliberations * It was noted that the way that registries implement the system is based on the system/software they use. The question is whether tables should be in a machine readable format when shared through IANA. RFC 7940 was suggested as a requirement because that format allows those using IANA tables (ICANN during review, other registry operators while designing their own tables) to process tables less manually and through machines. The advantage is that the LGR format the rules are formally specified, leaving a smaller chance of misinterpretation. It allows for more automatic operations. One could do harmonization in automated manner. * Comment: Perhaps discussion of RFC 7940 does not belong under C6, but it might be appropriate to discuss under other charter questions. Note that the resources required to do the shift to a requirement that ROs move to be consistent with RFC 7940. * Comment: It’s not just time to make the change. It also takes money because engineers will need to do the work. The return on investment is not worth it. * Comment: As reviewed last week, many IDN tables are in TXT. It would be a significant undertaking for ROs. * Question: With RFCs, is there a point in time that RFCs become a technical requirement? * Comment: RFC are of multiple types. The early ones (RFC 3743 and 4290) are informal. The later one (RFC 7940) is standards track, meaning it has been recognized as a standard by the IETF. * Comment: If the RFC is in a contract or a policy, the contracted party has to follow it. Otherwise CPs don’t have to follow. * Comment: In general, all IETF outputs are recommendations for standards. It is up to the businesses and organization to make a judgment call to make them “requirements." In our industry, we adopt IETF standards via consensus policies or contract obligations * Comment: In the context of IDN tables format, this is the current IANA procedure where RFC 7940 is the recommended format https://www.iana.org/help/idn-repository-procedure * Slide 8 – Discussion Questions – Existing ROs * For existing IDN Tables already implemented by existing ROs Should harmonization be a requirement? * For existing IDN Tables already implemented by existing ROs, if the answer to question 1 is yes, should any specific harmonization mechanism be recommended? * For existing IDN Tables already implemented by existing ROs, should the XML format, as recommended by RFC 7940, be required retroactively for already implemented IDN Tables? * One way to look at it is two divide it into two parts. Harmonization seeks to address a security challenge. The first part of the question is should harmonization be done going forward to avoid registration issues. The second part is to deal with existing registrations. * When we are talking about existing ROs we are talking about single TLD, not variant sets. But if variants are part of consensus policy, it would be inconsistent not to require harmonization in existing TLDs. Harmonization needs to be consistent across the name space. Regarding existing registrations, barring significant security concerns, perhaps we can provide the opportunity for grandfathering, which is common practice in certain types of situations. * Clarification: For existing ROs going forward, harmonization would be a requirement. Grandfathering would only apply to existing registrations. * Question: Have there been security challenges with IDN registrations at the second level using IDN tables that are not harmonized? * Response: There has been anecdotal evidence that has been published. The .epic/.epic example was published a few years back. Org has not done an analysis of how many cases of issues exist. * Question: Do we have data or how many ROs currently harmonize IDN tables? * Response: This is not tracked because it is not currently a requirement. * Comment: A suggested data point mentioned in the charter is how many ROs use the LGR format, but that doesn’t necessarily mean that they do harmonization. * Comment: The idea is that the existing registrations could be grandfathered – if the registered domain is dropped, the RO would have to enforce harmonization going forward. * Comment: Grandfathering is a pretty common practice. The alternative is to force harmonization, meaning that a registration is not renewed. * Comment: In the Verisign case, renewal is different from deletion and re-registration. Typically, renewal will just extend the existing registration. When re-registered, it is subject to the registration rules at that time. * Question: should it be a limited period for grandfathering? Does grandfathering appliy to registered names prior to a nominated date? In other words, what are the parameters for grandfathering? * No additional comments. * Comment: It would be useful to have some research on second level domains that currently exist but would be denied under harmonization rules, with counts of affected domains grouped by script or language, so we have an idea of how many domains would be grandfathered, and how much of a security issue it might be. * Response: While it resources might not be available for this data set, there are anecdotal examples that can be reviewed, * Question: 1. For new IDN Tables to be submitted by existing ROs (e.g., as part of the variant gTLD application), should harmonization be a requirement? 2. If the answer to question 1 is yes, how to manage any potential inconsistency with any of the ROs’ already implemented IDN Tables? * Response: It makes sense to have a consistent approach. When we talk about harmonization it should apply to all ROs, existing and new. * Question: One of the aims of harmonization is to make sure that the registries are using tables consistently. There are different levels of consistency. If we have one practice for existing domain names and a different rule for new ones, does that make sense from a consistency perspective? * Response: We are not talking about all ROs being consistent and having identical implementation. We are talking about having a consistent approach to variants that the RO applies in a single name spaces. This type of consistency will address security concerns. But the ROs will be able to adopt their own policy while following the contractual and other obligations. Action Item 1: Leadership to draft text reflecting discussion with suggested recommendations for C4, C5, and C6. The EPDP Team’s next conversation can focus on that draft text. AOB * Next week’s call: Charter Questions C1, C2, C3 and discussion with SSAC subject matter experts about Phase 1 recommendations. * A communication was sent to staff supporting the SSAC mapping CQs and recommendations that touch on early input from the SSAC as well as relevant SSAC advice. This enables them to prepare for the conversation in advance. Action Item 2: Staff to forward to the EPDP Team the communication to the SSAC regarding next Thursday’s call. * Donna will present the revised timeline to the GNSO Council next Thursday, in the context of the Board request for information on efforts that have a dependency on the next round. * Leadership has previously raised the idea of dedicated face-to-face time during Phase 2 work. That will be included in the slides for the Council presentation. Exact timing and location are to be determined, but a 6-month lead time is anticipated. Leadership team would like the meeting to take place in the APAC region. Action Item 3: Staff to check on status of ICANN77 meeting schedule and when it will be posted publicly. 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

ON NOW | Meeting Invitation | IDNs EPDP Team | Thursday, 18 May 2023 at 12:00 UTC
by Devan Reed May 18, 2023

May 18, 2023

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 18 May 2023 at 12:00 UTC for 2 hours. 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/XoZXDg * Check your time zone: https://tinyurl.com/4u4p4uzt [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4u4p4uzt__;!!PtGJab4!841LB4e…> 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

2 1

REMINDER | Meeting Invitation | IDNs EPDP Team | Thursday, 18 May 2023 at 12:00 UTC
by Terri Agnew May 18, 2023

May 18, 2023

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 18 May 2023 at 12:00 UTC for 2 hours. 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/XoZXDg * Check your time zone: https://tinyurl.com/4u4p4uzt [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4u4p4uzt__;!!PtGJab4!841LB4e…> 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 3

15 MINUTES REMINDER | Meeting Invitation | IDNs EPDP Team | Thursday, 18 May 2023 at 12:00 UTC
by Devan Reed May 18, 2023

May 18, 2023

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 18 May 2023 at 12:00 UTC for 2 hours. 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/XoZXDg * Check your time zone: https://tinyurl.com/4u4p4uzt [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4u4p4uzt__;!!PtGJab4!841LB4e…> 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

**starting in 15 minutes | IDNs EPDP Community Webinar Invitation | Wednesday, 17 May 2023 at 11:00 UTC
by Terri Agnew May 17, 2023

May 17, 2023

**Starting in 15 minutes Dear all, The IDNs EPDP Community Webinar is scheduled on Wednesday, 17 May 2023 at 11:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/91235574824?pwd=ZXo0WVV0bERxc2M2aVVVdlZsdGxRdz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/91235574824?pwd=ZXo0WVV0…> Passcode: gW%ag=s30c Or One tap mobile : +13126266799,,91235574824#,,,,*7119325728# US (Chicago) +13017158592,,91235574824#,,,,*7119325728# US (Washington DC) Webinar ID: 912 3557 4824 Passcode: 7119325728 International numbers available: https://icann.zoom.us/u/ac3c2072qs [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/ac3c2072qs__;!!PtGJab4!5…> Interpretation Service: ADIGO LANGUAGE BRIDGES: English 9001 Arabic 9001 Chinese 9001 General International Toll: 2132333193 (this phone number works in every country) Find other phone numbers here: https://www.adigo.com/icann/ [adigo.com]<https://urldefense.com/v3/__https:/www.adigo.com/icann/__;!!PtGJab4!7HFCWx_…> To check your time zone: https://tinyurl.com/bdcwfz4d [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/bdcwfz4d__;!!PtGJab4!5fsJAQF…> Wiki page: https://community.icann.org/x/HIdXDg Thank you. Kind regards, Julie

3 2

Post Call | IDNs EPDP Community Webinar | Wednesday, 17 May 2023
by Devan Reed May 17, 2023

May 17, 2023

Dear all, All recordings for the IDNs EPDP Community Webinar held on Wednesday, 17 May 2023 can be found on the agenda wiki page <https://community.icann.org/x/HIdXDg> (attendance included) and the GNSO Master Calendar<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…>. These include: * 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

Proposed Agenda - IDN EPDP Meeting #82 - Thursday 18 May 2023 at 12:00 UTC
by Emily Barabas May 17, 2023

May 17, 2023

Dear all, Please find below the proposed agenda for our meeting on Thursday 18 May 2023 at 12:00 UTC (2 hour call). Kind regards, Ariel, Steve, and Emily IDN EPDP Meeting #82 Proposed Agenda 1. Roll Call and SOI Updates (2 mins) 2. Welcome and Chair Updates (5 minutes) 3. IDN table harmonization (charter questions C4, C5, C6) (110 mins) * Recap of last week’s discussion * Continued deliberations 1. AOB (3 minutes) 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

REMINDER | IDNs EPDP Community Webinar Invitation | Wednesday, 17 May 2023 at 11:00 UTC
by Devan Reed May 16, 2023

May 16, 2023

Dear all, The IDNs EPDP Community Webinar is scheduled on Wednesday, 17 May 2023 at 11:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/91235574824?pwd=ZXo0WVV0bERxc2M2aVVVdlZsdGxRdz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/91235574824?pwd=ZXo0WVV0…> Passcode: gW%ag=s30c Or One tap mobile : +13126266799,,91235574824#,,,,*7119325728# US (Chicago) +13017158592,,91235574824#,,,,*7119325728# US (Washington DC) Webinar ID: 912 3557 4824 Passcode: 7119325728 International numbers available: https://icann.zoom.us/u/ac3c2072qs [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/ac3c2072qs__;!!PtGJab4!5…> Interpretation Service: ADIGO LANGUAGE BRIDGES: English 9001 Arabic 9001 Chinese 9001 General International Toll: 2132333193 (this phone number works in every country) Find other phone numbers here: https://www.adigo.com/icann/ To check your time zone: https://tinyurl.com/bdcwfz4d [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/bdcwfz4d__;!!PtGJab4!5fsJAQF…> Wiki page: https://community.icann.org/x/HIdXDg Thank you. Kind regards, Julie

1 0

ICANN77 prep week schedule is now published / How to Create your Prep Week Schedule
by Julie Bisland May 16, 2023

May 16, 2023

Dear all, The ICANN77 prep week schedule is now published! Please take a moment to read the information below to help create your prep week schedule and add sessions to your calendar. For the prep week schedule, go here: https://icann77.sched.com/ [icann77.sched.com]<https://urldefense.com/v3/__https:/icann77.sched.com/__;!!PtGJab4!_E5j-hi3y…> * Click Sign up or Log in and enter your information (email address and create password) * Once you “Join Event”, the schedule shows up with blank circular buttons to the left of each session. Hover over each button and click “ADD TO MY SCHEDULE” (see screenshot below) or just click in each circle to add the checkmark. [zH2S7YhPBpH+xAAAAAElFTkSuQmCC] * Once you’ve selected all sessions, click the My Schedule link in the lower left corner or hover over your profile and select My Schedule. [UYF4B+Gah4wAAAAASUVORK5CYII=] Or [iZO0AAAAASUVORK5CYII=] * You will see this message, “A copy of your schedule has been sent to your(a)email.com<mailto:your@email.com>.” To export the schedule, click the Phone icon: [wOqHIHPNJbGoQAAAABJRU5ErkJggg==] * On the page that appears, scroll down to the section Calendar Sync for Google Calendar, Outlook & Apple Calendar -> Export Calendar, and click the link next to “My Schedule”. When the .ics is exported, add it to the appropriate calendar (see screenshots below). Or, after exporting, drag and drop the .ics file directly into your calendar.. [sPtvZbES15QAAAABJRU5ErkJggg==] [wEIEk8JZn0NCQAAAABJRU5ErkJggg==] The ICANN77 Schedule<https://meetings.icann.org/en/icann77> will be posted 22 May 2023. Please email questions to us at: gnso-secs(a)icann.org<mailto:gnso-secs@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

Notes and action items - IDNs EPDP Meeting #81 - 11 May 2023
by Emily Barabas May 11, 2023

May 11, 2023

Dear all, Please find below the notes and action items from today’s meeting on Thursday, 11 May 2023 at 12:00 UTC. Kind regards, Ariel, Steve, and Emily Notes and Action Items - IDNs EPDP Call – 11 May 2023 Action Items Action Item 1: EPDP members to encourage their community colleagues to attend the webinar on 17 May at 11:00 UTC. Notes Welcome and Chair Updates * Donna is on vacation this week. Justine will be chairing the call. * SOI update – Justine is the ALAC representative to the SubPro IRT. * Thanks to all for remembering to attend the call one hour earlier. Meetings are now taking place at 12:00 UTC. * There is a community webinar scheduled for Wednesday next week (17 May) at 11:00 UTC. The webinar will focus on getting the community up to speed on Initial Report recommendations. Action Item 1: EPDP members to encourage their community colleagues to attend the webinar on 17 May at 11:00 UTC. * The EPDP Team call on 25 May will be a discussion with SSAC. This is the second engagement session held with the SSAC and this EPDP. IDN table harmonization (charter questions C4, C5, C6) Background and presentation on what harmonization is: * Slide 3: Charter Questions C4, C5, C6 * Note: mutually coherent = harmonized * Harmonization Core Question - C4) Should the second-level IDN tables offered under a TLD, including IDN variant TLDs, be required to be mutually coherent? If yes, how should existing registrations which may not meet the “mutually coherent” requirement of second-level IDN tables be addressed? * Harmonization Mechanism - C5) The Staff Paper suggests maintaining a common set of harmonized second-level IDN tables for all IDN variant TLDs and then (a) choosing all these IDN tables to offer for all IDN variant TLDs, or (b) choosing a relevant different subset of IDN tables to offer for each different IDN variant TLD. Are the above suggested methods in the Staff Paper sufficient for IDN table harmonization purposes? Should any additional implementation guidance be provided for a registry? * Harmonization Mechanism - IDN Table Format - C6) Should Registry Operators be required to use the machine readable LGR format as specified in RFC 7940 for their second-level IDN tables? Or should Registry Operators have the flexibility to resolve the harmonization issue so long as it can predictably and consistently produce the same variant labels, albeit with different disposition values, across the same-script IDN tables? * Slide 4: What is an IDN Table * An IDN Table is used by a registry operator to represent second-level rules under a gTLD for validating IDN labels for registration, calculating variant labels, and determining disposition values of variant labels. * Slide 5: What is Harmonization? * Summary: Ensure that the variant relationship between any two given second-level labels is consistently defined across all of the IDN Tables offered by a gTLD and its variant gTLD(s). * Clarification - the purpose is to ensure that the set of labels in a set is consistent throughout the TLD, no matter what table used. Disposition values might be different. * Additional information: How does the RO know which table to use? If a IDN label is being requested, the EPP needs to come up with a language tag parameter which informs the registry of the intended language to use and therefore the associated table. * Slide 6: Example Output * Slide 7: Why is harmonization needed? – Potential consequence of current practice * There is no current requirement for harmonization and no requirement for ICANN org to cross reference the different IDN tables for a gTLD. * As a result, the second-level variant label set produced for a requested second-level label may be inconsistent when different IDN Tables are used. Variant labels may be permitted for registration by different registrants as distinct labels under the same gTLD. * Question: When a registrant wants a SLD, does the registrant choose the IDN Table, and can this be abused? * Response: The registrant is probably not able to choose. The registrar will choose which IDN table to be used. It shouldn’t be possible to misuse. The registry should take care that inconsistent registrations are not possible. * Response: Anecdotally from one registry, there are different ways that registrars select the language. In some cases, the registrar does this on behalf of the registrant. It is up to the registrar to validate the string and the language. * Slide 8: Example Output: Consequences Without Harmonization * Clarification: Harmonization is not a tool that creates variant relationships. If a registry decides to create variant relationship, that is one choice. A second choice is harmonization, which is about making these relationships consistent. * Response: The relationship between 643 and 689 is established by the Arabic script community. The script community had also established the relationship between 629 and 6C3. Unicode has encoded these two letters K and T in Arabic and K and T in Urdu as different code point. As far as the script community is concerned, the two Ks are the same and the two Ts are the same. This is also the same in reference LGRs for the Arabic script. If they are designing an Arabic table, the use the Arabic K and T and when designing the Urdu table, they use the Urdu K and T. If you don’t harmonize, you can end up with two identical strings with two different registrants. * Response: That is a design choice of the reference LGRs. The comment above is implying that the registries need to harmonize with the reference LGR, which is a different issue. Harmonization the context of the current discussion is only about practices within IDN tables. * Response: If there are two variants, the motivation of harmonization is to address a security problem where if two identical strings under a TLD, they should either be registered by the same registrant or be blocked. If they are registered by different registrants there is a security risk. Who identifies what is a variant label? We can take this from the relevant script community. That is based on their understanding about what is the same or not. What we are suggesting is that a variant set is based on a community’s recommendation. * Question: Are there going to be collisions resulting in the process of harmonization? * Response: This question gets into how this should be implemented. There are two ways to implement – data driven or process driven. In one case, one could keep the same IDN tables and change the process. Alternately, you keep the process the same and update the tables. This will be discussed later. * Comment: We are talking about two different things. One is harmonization. The other is on what variant relationships should be included in variant tables at the second level. That is the prerogative of the RO. That is outside the question of C4. * Response: In some ways this is correct. However, there is one more impact of harmonization. Even when registries are doing it, there will be some impact on ICANN’s review of IDN table. When designing the IDN table for Arabic, ICANN would also need to look at other IDN tables using Arabic script. Designing IDN tables may be a separate process, but it will eventually have some influence on the design itself because of the downstream process. * Slide 9 – How are IDN Tables Harmonized * Currently no standard process for harmonizing IDN tables. Staff paper suggested two possible methods: Extend each IDN table or Extend label check process. * Reference to cross-language and cross-script should be removed from this slide. * Ultimately how a registry solves the harmonization requirements will depend on the systems. * These two methods are presented as examples without a suggestion on picking one or another. It could vary from registry to registry. Different methods could lead to the same result, so the requirement could simply be that harmonization is required. * These are possibilities but registry platforms predate harmonization requirements. Registries will need to take the requirements and design architecture to solve for that. How it is achieved can be left to the registries to design. It will be counterproductive to mandate design decisions. * Slide 10 – Anecdote on Harmonization Practice – Shared by Michael Bauland * Clarification: The variants for all labels are stored in a canonical way in a database. At each registration, the canonical form is compared against the database to see if the label should be blocked. * For canonical calculations, the canonical label could even be mixed script. It is not shown to anyone. It’s not used for anything else, only for harmonization on IDN tables. It is not comparable to the primary label. * The EPDP Team is also seeking inputs from other registries and registrars about what they currently do with respect to harmonization. This provides additional context for the group as they consider policy recommendations. * Slide 11 – If Harmonization becomes a policy requirement – potential outcomes: * ICANN org be authorized to review ALL IDN Tables offered by a gTLD and its variant gTLDs in a holistic manner * ICANN org may reject an IDN Table if the variant label set of a given code point is not consistently produced * Slide 12 – IDN Table Formats * Comment: These are ways to represent rules of a table. Up to this point, when published the IDN table is an artifact to represent the rules of the registry but does not inform how the registry logic works. Regardless of format of the output, it is a plain output. Disagree with the text in the slide: “LGR processing tools can be developed to help registries automatically harmonize IDN Tables in XML format.” You still need to parse the XML rules and have to build a machine read it. Some registry databases predate XML. You can’t conclude that using the XML table format is a way to ensure harmonization. * Comment: Agreement with the above comment. The processing tools that exist are helpful for registries that already uses XML format. If you are not using XML format, these tools won’t help. It may not be easy to build the XML format standard in existing software. Some registry platforms may not implement XML format. * Comment: Moving to XML format won’t solve the harmonization per se, but a transition over time may be helpful. If you want to transfer a domain between registries and the registries use different formats, a manual intervention is needed. XML is future looking. * Response: Adoption of RFC 7940 is outside the scope of charter question C6. * Comment: Transferring between registrars might not be a problem as long as the registry remains the same. Registrars look to the registry to use the IDN tables. There is a different charter question focused on transfers. * Additional information about the tools: * option that you feed in a TXT format and get a XML format. * provide a function to show an HTML representation of the XML. * open-source, code is available in GitHub, so it is not necessary to start from scratch. * IDN Tables are a representation, not a reflection of how the system works. Registry systems don’t take IDN Tables as input. * IDN tables don’t drive the logic of the registry platform. In the registry platform, there are specific rules that are applied. There is a hierarchy of rules that need to be represented. The IDN tables themselves are visually independent, but there is logic behind the analysis that takes place. * C6 is not necessarily the impetus for moving things to XML format in service of harmonization. If harmonization is prescribed, efficiency on top of that could be achieved via XML. * Slide 13 – Anecdote on IDN Tables – shared by Zuan Zhang * Slide 14 - Discussion Questions – Future Applicants * Discussion Question 1: Should harmonization be a requirement? In other words, should it be a requirement that the variant relationship between any two given second-level labels is consistently defined across all of the IDN Tables offered by a gTLD and its variant gTLD(s) * Discussion Question 2: If the answer to question 1 is yes, should any specific harmonization mechanism be recommended? Specifically, should the Reference LGR, including the Common LGR, be recommended as a reference for developing IDN Tables by future applicants? * Discussion Question 3: Should the XML format, as recommended by RFC 7940, be required for IDN Tables to be submitted by future applicants? * Question: Does this refer to Charter Question C6? As presented it does not summarize the CQ. Question 3 is presented without the context of the charter question, which explains what we are trying to solve for. * It was agreed that question 3 more accurately a sub-question under question 2. * Comment: Harmonization is seeking to address security concerns. But we can’t think about harmonization in a vacuum. There is also usability, which is connected to the principle that behavior may be different. Registries are leaning towards being conservative, but do not have a definite answer. They are leaning towards making a positive statement on harmonization. Registries feel strongly that it should be left to registries to determine how to solve for harmonization. * Some support expressed for the idea that the WG should recommend harmonization but not how registries do it at a technical level. * Suggestion that the EPDP Team might want to develop an oversight mechanism to address security and stability issues. * Comment: We shouldn’t add to existing requirements for backend testing. 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, 11 May 2023
by Devan Reed May 11, 2023

May 11, 2023

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

Meeting Invitation | IDNs EPDP Team | Thursday, 18 May 2023 at 12:00 UTC
by Devan Reed May 11, 2023

May 11, 2023

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 18 May 2023 at 12:00 UTC for 2 hours. 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/XoZXDg * Check your time zone: https://tinyurl.com/4u4p4uzt 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