January 2024 - Gnso-epdp-idn-team

Notes and Action Items from IDN EPDP Meeting #104
by Daniel Gluck Jan. 29, 2024

Jan. 29, 2024

Hi All, Please find below the notes and action items from last Thursday’s IDN EPDP Meeting #104.<https://community.icann.org/x/wQGWEQ> Thanks! Ariel, Steve, Saewon, and Dan ACTION ITEMS * Leadership requests Team’s review and input on the new batch of draft texts (Preliminary Recommendations and Glossary) by Friday, 2 February * Further discussion will take place, but the Chair asked the RySG to have an update by 29 January for the Harmonization of IDN tables. * Leadership and Staff to discuss further on including an individual section covering a brief response to the implementation guidelines regarding the proposed approach for deferred items. * leadership and staff will determine appropriate language for referencing the board/ specific working groups. * Staff to have an informal discussion with ccPDP4 on preliminary recommendation 14, as ccTLDs are the other impacted party of IDN Implementation Guidelines ________________________________ NOTES * Roll Call and SOI Updates (2 min) * Welcome and Chair Updates (5 min) * The Chair welcomed everyone to the call and provided an update on tasks completed over the past two months. * Saewon Lee was introduced as a new member of the ICANN Policy Development Support Team and will be supporting this EPDP. * Harmonization of IDN tables discussion (30 min) * Groups of stakeholders got together to discuss IDN Table Harmonization * There was a discussion where certain registries may be interested in having common IDN tables as an option, but not a mandate. * This could be also for the benefit of registrars to have an open standard to add * ACTION ITEM: Further discussion will take place, but the Chair asked the RySG to have an update during the week of 29 January. * Variant Domain Set Definition (30 min) * A proposed explanation was added to the draft glossary * Per a team member, t1v1 hard to say if they are allocatable or blocked unless the source was determined. It was decided that each of the TLDs needed a source domain in order to determine the disposition of each. For example, s1v1 would be unable to be determined without a source domain for t1v1 stated. * At points in time, it may be hard to see the disposition of a domain (allocatable / blocked). As soon as a source is declared, then the other variants can be determined. * Another team member shared that there may be two use cases for this broader domain set. * One is for a registrant to register other variant TLDs * The other is that while it may not be relevant if a domain is allocatable or blocked, in some cases the disposition value is useful but may not be for others. * A comment in chat said “The entire set is established by the first source / primary domain…. if a registrant is not interested in the other variant domain names, then the registrar or registry do not care about it either. When the registrant decides he/she wants any of the variants in the variant TLD, then the coordination between rt/rr/ry happens.” * If we have a source registered for a given TLD, variant domain names and their disposition values can be calculated for a given TLD, and the set will consist of variant labels at the second level, but the disposition will be unknown. The set will remain the same, but disposition cannot be determined. * Staff presented an unresolved question “IF the second-level label of the source domain name is only valid under T1, but not under T1v1, what does the variant domain set consist of, also factoring in T1v1?” * If the two IDN tables are harmonized, the last code point in each table would be considered variants of each other. * Certain code points are included with certain rules. If code points are “out of repertoire” then there are procedures in the RZ-LGR. For harmonization, it would be good to have certain rules across tables, but you need to be consistent in order to do that. * This relates to Preliminary Rec (PR) 5. * Should the above ideas be listed in the rationale for PR5? Should it be in PR5 itself? * This is an important recommendation for the purpose of understanding the source domain. There may be value in expanding on the second part of the recommendation, potentially in a footnote, but it is important not to devalue the recommendation. * It was asked if the variant domain set changes between the two steps? * The set does not change but the disposition may change * Step 1 defines the set but with underspecified dispositions. Step 2 adds to the missing information on dispositions * There was discussion if this is an edge case or a general case * Should “out of repertoire” be used? * This term is used in the RZ-LGR, so it is appropriate. * Staff will refine the rationale language for PR5 but will not change the recommendation itself. * ACTION ITEM: For Variant Domain Set Definition, Staff to include a rationale and refine the rationale language - but no need to change recommendation 5 * Proposed Approach for Deferred Items from Implementation Guidelines 4.0 (25 min) * Leadership described their proposed approach to tackle the deferred items from the Implementation Guidelines 4.0. * There was a question if the group agreed with this becoming a section in the report? * It was agreed that the second level is out of scope with ccPDP4. Rationale in the report wouldn’t hurt (a brief response in the relevant rationale portion). * There were three potential scenarios mentioned as approaches: * One is that the guidelines as stated are acceptable * Regarding country code policy, there has not been anything flagged in the guidelines as issues of concern. * The second is that they may be acceptable, but with an updated scope to reflect new recommendations * The third is that the guidelines are not consistent with recommendations and need to be redeveloped. * These last two would have documentation of divergence between GNSO and ccNSO recommendations. * ACTION ITEM: Leadership and Staff to discuss further on including an individual section covering a brief response to the implementation guidelines * Proposed Approach for Coordination with ccPDP4 Regarding Implementation Guidelines (25 min) * Preliminary recommendation 14 is related to the charter question of whether the IDN guidelines should stay the same. There were recommendations for the development of future guidelines. * Given that the guidelines impact the ccPDP4, there may be value in working with the ccPDP4 team on coming to a similar conclusion to avoid confusion. * ACTION ITEM: Staff to have an informal discussion with ccPDP4 on preliminary recommendation 14, as ccTLDs are the other impacted party of IDN Implementation Guidelines * There is no current liaison to ccPDP4. * It was mentioned that specific ICANN Board working groups should not be referenced in the recommendation, but leadership would rather not assign tasks to the board as a whole. * ACTION ITEM: leadership and staff will determine appropriate language for referencing the board/ specific working groups. * AOB (3min) * ACTION ITEM: Leadership requests Team’s review and input on the new batch of draft texts (Preliminary Recommendations and Glossary) by Friday, 2 February * No call scheduled next week, but maybe the week afterwards at the usual time (Thursday 8 February at 12:00 UTC)

1 0

Post Call | IDNs EPDP Team call | Thursday, 25 January 2024
by Devan Reed Jan. 25, 2024

Jan. 25, 2024

Dear all, All recordings for the IDNs EPDP Team call held on Thursday, 25 January 2043 can be found on the agenda wiki page <https://community.icann.org/x/wQGWEQ> (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 recording (including audio, visual, rough transcript, chat) * 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, Devan

1 0

REMINDER | Meeting Invitation | IDNs EPDP Team | Thursday, 25 January 2024 at 14:00 UTC
by Terri Agnew Jan. 25, 2024

Jan. 25, 2024

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 25 January 2024 at 14: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 page: https://community.icann.org/x/wQGWEQ * Check your time zone: http://tinyurl.com/njteu2d [tinyurl.com]<https://urldefense.com/v3/__http:/tinyurl.com/njteu2d__;!!PtGJab4!8ilEFeHHp…> 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

3 2

ON NOW | Meeting Invitation | IDNs EPDP Team | Thursday, 25 January 2024 at 14:00 UTC
by Devan Reed Jan. 25, 2024

Jan. 25, 2024

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 25 January 2024 at 14: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 page: https://community.icann.org/x/wQGWEQ * Check your time zone: http://tinyurl.com/njteu2d [tinyurl.com]<https://urldefense.com/v3/__http:/tinyurl.com/njteu2d__;!!PtGJab4!8ilEFeHHp…> 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

15 MINUTES REMINDER | Meeting Invitation | IDNs EPDP Team | Thursday, 25 January 2024 at 14:00 UTC
by Devan Reed Jan. 25, 2024

Jan. 25, 2024

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 25 January 2024 at 14: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 page: https://community.icann.org/x/wQGWEQ * Check your time zone: http://tinyurl.com/njteu2d [tinyurl.com]<https://urldefense.com/v3/__http:/tinyurl.com/njteu2d__;!!PtGJab4!8ilEFeHHp…> ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Julie

1 0

Proposed Agenda - IDN EPDP Meeting # 104 - Thursday, 25 January 2024 at 14:00 UTC (UPDATED TIME)
by Daniel Gluck Jan. 23, 2024

Jan. 23, 2024

Hi All, Please find below the proposed agenda for our meeting on Thursday, 25 January 2024 from 14:00 – 16:00 UTC, which is two hours later than our usual start time. IDNs EPDP Meeting #104 Proposed Agenda Hi All, 1. Roll Call and SOI Updates (2 min) 2. Welcome and Chair Updates (5 min) 3. Harmonization of IDN tables discussion (30 min) 4. Variant Domain Set Definition (30 min) 5. Proposed Approach for Deferred Items from Implementation Guidelines 4.0 (25 min) 6. Proposed Approach for Coordination with ccPDP4 Regarding Implementation Guidelines (25 min) 7. AOB (3min) Thanks! Ariel, Steve, Saewon, and Dan

1 0

Meeting Invitation | IDNs EPDP Team | Thursday, 25 January 2024 at 14:00 UTC
by Julie Bisland Jan. 19, 2024

Jan. 19, 2024

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 25 January 2024 at 14: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 page: https://community.icann.org/x/wQGWEQ * Check your time zone: http://tinyurl.com/njteu2d 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

IDNs EPDP Team meeting
by ICANN Policy Calendar Jan. 19, 2024

Jan. 19, 2024

Meeting: IDNs EPDP Team Date/time: Thursday, 25 January 2024 at 14: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 page: https://community.icann.org/x/wQGWEQ * Check your time zone: http://tinyurl.com/njteu2d 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

[Review Requested by COB 2 February] New Draft Text Developed Following F2F Workshop
by Ariel Liang Jan. 18, 2024

Jan. 18, 2024

Dear EPDP-Team, Thank you all for your patience! A new batch of draft text is now ready for your review and input. 1. Preliminary Recommendations: https://docs.google.com/document/d/1UrrckzbPNL1Z8fUtH5Q5WqUWglxbD-SbihX8o8V… * Pages 23-41: this section contains the new draft language developed following the team’s deliberations in the F2F workshop. Kindly note that some recommendation language (e.g., Preliminary Recommendation 14) may require input from external parties, such as ccPDP4. In addition, per action items for staff, early input is sought from ICANN org SMEs on some additional draft recommendations (e.g., Preliminary Recommendations 8, 12-13, and Implementation Guidance 9). * Pages 1-22: this section of the draft text has already been reviewed and discussed by the EPDP Team prior to the workshop. Most of the redlines reflect the team’s discussion about terminology. As you may recall, since the harmonization question has not been resolved (charter question C4), further discussion among the EPDP Team is expected and the draft text on pp.1-3 is subject to change. 2. Glossary: https://docs.google.com/document/d/1NaDttdqEdrNeWPxZVWm2JA565zN3beFx7ZGbYlQ… * Items highlighted in yellow: substantive updates have been made to these items following the F2F workshop deliberation * Items highlighted in blue: these are new terms incorporated in the glossary after the workshop (mostly reproduced verbatim from the ICANN website) * Remaining items: agreed updates that were discussed during the F2F workshop have been incorporated, and these items should be straightforward / ‘non-controversial’ Leadership team kindly request your review and input for these two google docs by COB Friday, 2 February. For prioritization purposes, kindly focus on pages 23-41 on the preliminary recommendations document and the yellow items in the glossary. Per our usual practice, second reading and discussion of input received is expected to take place during the upcoming EPDP Team meetings. Thank you for your review! Best Regards, Ariel, Steve, Dan

1 0

Re: [Gnso-epdp-idn-team] Tentative Dates to Resume Calls & Quick Update on Progress
by Nitin Walia Jan. 12, 2024

Jan. 12, 2024

Thanks for the updates dear Ariel, Happy New Year to you and all EPDP Team members, looking forward to resume soon. . Warm Regards Nitin Walia | DirectorData Ingenious Global LimitedTel: +91-141-2554970Fax: +91-141-2554972LinkedIn Twitternitin(a)data.in | नितिन(a)xn--c2bd1gb.xn--h2brj9c | https://dil.inVC: https://bridge01.videomeet.in - room: nitin pwd: 10000Get email id like me in your own language, download DATAMAIL app from your iOS or android play store. भाषाकीआजादी - Bridging the Digital Divide, Getting Next billion online >From: Ariel Liang MailId : [139576921]To: "gnso-epdp-idn-team(a)icann.org" Subject: [Gnso-epdp-idn-team] Tentative Dates to Resume Calls &amp Quick Update on ProgressDate: 12 Jan 2024 03:33:31 AM Dear EPDP Team, Happy New Year! Hope everyone had a wonderful holiday break and a great start in 2024! The leadership team would like to give the team a couple of quick updates on the progress following the workshop: New draft text related to the charter questions the Team finished discussing in KL has been developed and is under leadership review. We aim to circulate it for the EPDP Team&rsquos review soon . Our calls will be resumed on either Thursday, 25 January or Thursday, 1 February. We will keep the group posted. In the meantime, please contact staff if you have any conflict with either or both dates . Please contact staff if you have any questions. We will return to the IDN work in full swing shortly! Best Regards, Ariel _______________________________________________Gnso-epdp-idn-team mailing listGnso-epdp-idn-team@icann.orghttps://mm.icann.org/mailman/listinfo/gnso-epdp-idn-teamDo not Remove:[HID]20240112033331201[-HID] [XGENFOOTER] [-XGENFOOTER]

1 0