- Gnso-epdp-idn-team - lists.icann.org

Updated Language for Rec 12, Rec 14 & "Variant"
by Ariel Liang 20 Feb '24

20 Feb '24

Hello everyone, Following last week’s call, leadership and staff worked together to update recommendation 12 pertaining to RDAP and recommendation 14 regarding IDN Implementation Guidelines. Please note that there are some substantive changes to the recommendation language, and additional implementation guidance has been developed to complement them. You may focus on the new redlines on pp.32-42 for these recommendations and implementation guidance. In particular, on p.37, we kept the old recommendation 14 for the ease of reference, and included the new recommendation 14 and implementation guidance 18 with blue highlight: https://docs.google.com/document/d/1UrrckzbPNL1Z8fUtH5Q5WqUWglxbD-SbihX8o8V… In addition, you may find the new entry of “variant” on the glossary document, pp.16-17: https://docs.google.com/document/d/1NaDttdqEdrNeWPxZVWm2JA565zN3beFx7ZGbYlQ… Thank you for the preview. We will plan to close these remaining loops on Thursday, including the IDN Table harmonization discussion. Thank you, Ariel

1 0

Notes and Action Items from IDN EPDP Meeting #106 and Proposed Agenda - IDN EPDP Meeting #107 - Thursday, 22 February 2024 at 12:00 UTC
by Daniel Gluck 20 Feb '24

20 Feb '24

Hi All, Please find below the notes and action items from last Thursday’s (15 Feb 2024) IDN EPDP Meeting #106<https://community.icann.org/pages/viewpage.action?pageId=302350604> as well as a proposed agenda for this Thursday’s (22 Feb 2024) IDN EPDP Meeting #107.<https://community.icann.org/x/DoEFEg> Thanks! Ariel, Steve, Saewon, and Dan IDNs EPDP Meeting #106 ACTION ITEMS * IDN Table Harmonization: The RySG will deliberate this week and staff will request proposed language to be circulated ahead of the next meeting for a more efficient discussion/conclusion * Recommendation 12 (RDAP profile): Leadership to develop language that is an overarching/general recommendation * Recommendation 14: Staff to revise language and rationale (to refer to CSC Charter). Merging 14.2 and 14.3 and then reordering the items was suggested. * Glossary: Staff to draft “variants” in the context of IDN EPDP while Leadership finalizes review * Implementation Guidance 15 (Automatic activation): This was not covered during Team meeting and will be discussed in upcoming meetings or on the email list NOTES * Roll Call and SOI Updates (2 min) * Welcome and Chair Updates (5 min) * The chair welcomed everyone to the call * Timeline Overview & Public Comment Approach (15 min) * The chair then briefed the team on the timeline, including a meeting (#107) next week on 22 February, leading all the way through the public comment break, and all the way until mid-May when meetings pick back up (#108 on 16 May) * Glossary Review (30 min) * Without substantive comments, the glossary entries will be accepted. Staff will make any grammatical or formatting changes that have been recommended. * One comment received was regarding the word “variant” and it was suggested that there could be an entry added to “variant” to clarify that this document always refers to IDN Variants when “variant” is mentioned. * In phase 1, “IDN” was specifically divorced from “variant” to allow for separation to occur but now there are suggestions for phase 2 to bring them back together? * ACTION ITEM: Staff to draft “variants” in the context of IDN EPDP while Leadership finalizes review for the glossary * Close Loop on Draft Recommendations (50 min) * Preliminary Recommendation 12: RDAP Query * The RySG Reported back on their discussions * There was a sense that RDAP might not be the right protocol to be used to identify variants * The volume might be overwhelming, per a team member. * It may be out of scope for the EPDP team to prescribe specific RDAP changes, including potential contractual issues * A different team member disagreed with this evaluation * This should not be a major issue to performance of RDAP as the work already has to be done by the Registry, per that team member. * It was suggested that the actions of the RDDS contract are specified (stemming from the Registration Data Policy EPDP) and this would change that * A team member recommended that the specificity of the PR12 should be changed to a recommendation for registries to review /update RDAP profile documents * Potentially the chair thought that specifics could be added to implementation guidance while the recommendation could stay general like in the suggestion. * Another team member talked about the difference between policy changes and contractual changes. While PDPs may change contracts, the specific language to the contracts are different from the language in the PDPs. If updates to the RDAP lead to megabytes of information included on each query, then there will need to be significant structural changes to RDAP and its SLAs. * If the result of such changes leads to significant increases in volume for output, than the SLAs should be reviewed * The Chair suggested the creation of a general recommendation that does not prescribe contractual changes but says the RDAP profile needs to account for variants, with specific context in the implementation guidance. * Another team member described the potential need for specific tasks within the policies * Registries should be much more amenable to this situation * ACTION ITEM: Leadership will look at creating a general recommendation with specifics in implementation guidance for PR 12 * There is a need to update RDAP profile in response to a query to see variants and this needs to be clear why the recommendation is being made but then “should” statements like what to display when a query is received could be in the implementation guidance * Implementation Guidance 15: Automatic Activation * This was not covered during Team meeting and will be discussed in upcoming meetings or on the email list * Initial Feedback from ccPDP4 on Preliminary Recommendation 14: IDN Implementation Guidelines * The ccPDP4 team does not have significant concerns about the recommendation. There were some reservations on the specific language, which they allege may be a bit confusing. * “Working group” is mentioned twice but regarding different groups. Could there be modifiers to resolve confusion? * In terms of 14.1, who develops the process and what goes into the process of establishing the working group. This is well defined for the ccNSO processes, but not as clear here. Who is responsible for the actions in this recommendation? * Additional confusion on who would approve the Implementation Guidelines? GNSO? ccNSO? ICANN Board? * Regarding 14.2, there was confusion on the order of establishing the working group and establishing a charter. * The charter must be formalized before the working group is created and text should be updated to clearly define this. * 14.3 may be combined with 14.2 for additional clarity * This was supported by multiple members of the team * ACTION ITEM: Leadership and staff will review PR 14 to revise language and rationale (to refer to CSC Charter) - Merging 14.2 and 14.3 and then reordering the items was suggested. * Other Comments * IDN Table Harmonization Update (15 min) * PR1 received a detailed discussion in the past, but there are still outstanding issues * There is a key component of harmonization not reflected in PR1. In Implementation Guidelines 4.0 there is a prescription to identify additional variant codepoints. Currently IDN variant tables don’t look at cross script codepoints and it would be beneficial to reference these points in the recommendation. * Recommendations from team members included referencing community work from the RZ-LGR. * There have been multiple meetings between the Registries and ICANN Org experts on this topic * Discussions are still ongoing and there is another call between the two on the 20th. * The recommendation language in C4 and C5 is generally okay per a member of the RySG, but the conversations center around how these changes could be implemented. * It was recommended by the chair that additional text should supplement the implementation guidance but not the recommendation language itself. * Draft text will be circulated internally within the RySG members to review before going out to the larger EPDP team * ACTION ITEM: The RySG will deliberate this week and staff will request proposed language to be circulated ahead of the next meeting for a more efficient discussion/conclusion * AOB (3 min) * IG 25.3 of the Sub Pro PDP says applicants can apply for labels in scripts not in RZ-LGR (it will not be delegated if the script is not in the RZ-LGR). The Phase 1 IDN EPDP report says that variants can be applied for if the script is in the RZ-LGR. It could be considered that IG 25.3 could be an overarching recommendation, while the IDNs recommendation could be a subset of the IDN labels and variants. * The chair stated that this EPDP was grounded in the principles of the RZ-LGR. It's possible that someone could apply for a variant that was not involved in the RZ-LGR process, but it may not be an inconsistency. * A team member echoed this latter argument. They can work in conjunction, but it is possible to view them as incongruent. * Staff reminded the team to review the documents that have been circulated for a final review before implementation into the initial report. * Staff also walked through the table of content for the P2 Initial Report. * For the P2 initial report public comment, a guided input form will be used. IDNs EPDP Meeting #107 Proposed Agenda 1. Roll Call and SOI Updates (2 min) 2. Welcome and Chair Updates (5 min) 3. IDN Table Harmonization Update (40 min) 4. Close Loop on Draft Recommendations (70min) * Updated Preliminary Recommendations 12 and 14 * Glossary: Variant 5. AOB (3 min)

1 0

Post Call | IDNs EPDP Team call | Thursday, 15 February 2024
by Devan Reed 15 Feb '24

15 Feb '24

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

Meeting Invitation | IDNs EPDP Team | Thursday, 22 February 2024 at 12:00 UTC
by Devan Reed 15 Feb '24

15 Feb '24

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 22 February 2024 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 page: https://community.icann.org/x/DoEFEg * Check your time zone: http://tinyurl.com/2s99kbdv 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 #106 - Thursday, 15 February 2024 at 12:00 UTC
by Daniel Gluck 15 Feb '24

15 Feb '24

Hello All, Please find below the proposed agenda for our meeting on Thursday, 15 February 2024 at 12:00 UTC. IDNs EPDP Meeting #106 Proposed Agenda 1. Roll Call and SOI Updates (2 min) 2. Welcome and Chair Updates (5 min) 3. Timeline Overview & Public Comment Approach (15 min) 4. Glossary Review (30 min) 5. Close Loop on Draft Recommendations (50 min) * Preliminary Recommendation 12: RDAP Query * Implementation Guidance 15: Automatic Activation * Initial Feedback from ccPDP4 on Preliminary Recommendation 14: IDN Implementation Guidelines * Other Comments 1. IDN Table Harmonization Update (15 min) 2. AOB (3 min) Thanks! Ariel, Steve, Saewon, and Dan

3 2

15 MINUTES REMINDER | Meeting Invitation | IDNs EPDP Team | Thursday, 15 February 2024 at 12:00 UTC
by Devan Reed 15 Feb '24

15 Feb '24

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

1 0

REMINDER | Meeting Invitation | IDNs EPDP Team | Thursday, 15 February 2024 at 12:00 UTC
by Terri Agnew 14 Feb '24

14 Feb '24

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 15 February 2024 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 page: https://community.icann.org/x/d4D6EQ * Check your time zone: http://tinyurl.com/2p4aj3zp [tinyurl.com]<https://urldefense.com/v3/__http:/tinyurl.com/2p4aj3zp__;!!PtGJab4!6mTSAo3b…> 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

Notes and Action Items from IDN EPDP Meeting #105
by Daniel Gluck 13 Feb '24

13 Feb '24

Hi All, Please find below the notes and action items from last Thursday’s (Feb 8, 2024) IDN EPDP Meeting #105<https://community.icann.org/x/d4D6EQ> Thanks! Ariel, Steve, Saewon, and Dan ACTION ITEMS * Leadership and the registries will review the D8 Team Response comments and get back to the team. * Staff will update D8 EPDP Team response to clarify #3 to “3) The source domain name used to calculate the variant set that the queried domain name is a part of, if applicable" * Staff will look at PR 6 to incorporate “there is some view” instead of “some members * The team will review the glossary before the next call and update the document accordingly * Staff will revise text in Rec 13 to remove the clause about the accuracy between the HTML and TXT versions of the Root Zone Database * Staff will remove IG 9 in response to ICANN org comments. NOTES * Roll call and SOI updates (2 min) * There was an SOI update from Anil Kumar Jain. * Welcome and chair updates (5 min) * The chair welcomed everyone to the call and noted the greater than usual amount of apologies due to the lunar new year. * Second reading of draft recommendation text & glossary – review of input received (60 min) * Leadership and staff are still waiting on Team feedback on harmonization tables * Comments were received for the D8 EPDP Team Response * Does the team want to make any rules regarding querying a domain that is not registered / allocated, but has allocated variants? * This may depend on how registry systems work and it also might already be accounted for. * If non registered domain names should be included, there should be further explanation. When talking about RDAP in other areas it is not explicitly stated that it means * If the team wants to include all allocated variant domain names, then they should include them all and not just a subset of the listing, per a participant and later echoed by another. * Since we are talking about the variant set, then all variants under variant TLDs should be included. The source domain name under the TLD should be included at a minimum, variant TLDs should be included in RDAP. * If RDAP requests are per TLD, what kind of complexities are being added? * This could potentially be too heavy of a lift for registries? * From chat: ”without response to domains that are un"registered" but actually in an existing domain registration set of variants would add a huge burden on registrar systems actually” * Potentially a minimal recommendation that says something along the lines of “it would be good to encapsulate the variant domain set” but the team will not be sure if this is necessary until a better understanding of the concept is achieved. * Does the team have an agreement on a preliminary recommendation? Initial thoughts include potentially keeping the text as is and leadership will discuss a path forward. * Does the context for “domain name” need to change in the first line of the D8 Team Response? * ACTION ITEM: Leadership and the registries will review the D8 Team Response comments and get back to the team. * Comments were also received to improve on subsection 3 in the first bullet on calculating the variant domain set. * "3) The source domain name used to calculate the variant set that the queried domain name is a part of, if applicable" * This suggestion was Accepted by the team * ACTION ITEM: Staff will update D8 EPDP Team response to clarify #3 to “3) The source domain name used to calculate the variant set that the queried domain name is a part of, if applicable" * There was a question about the process about GNSO and ccNSO PDP mechanisms. * The GNSO PDP does not impact the ccNSO. The consequences are different and they do not have to abide by what is made in this group. * There was an edit made to PR 5 during the call to reflect best practices in RFC 2119. * Under the Rationale for PR 5, there were discussions over redline text. There was agreement from the team to accept the redline text under this section. * Under the Rationale for PR 6 there was a discussion about the use of “some members” in the text. This could be tweaked to sound a bit better. * ACTION ITEM: Staff will look at PR 6 to incorporate “there is some view” instead of “some members” * ACTION ITEM: The team will review the glossary before the next call and update the document accordingly. * Review of ICANN org SMEs’ comments for draft recommendations (20 min) * There was additional feedback from SMEs within ICANN that will be considered regarding the TMCH on charter question F1. * The registries that have established variant registration policies essentially concern both ROs that block variants and those that allow activation. There is the possibility that there could be allocation without activation. * Per Section 4.1.3 of the Trademark Clearinghouse Rights Protection Mechanism Requirements, the RO, in both situations (block variants vs. activate variants), needs to check all labels (i.e., allocatable and blocked) in a variant label set against the Domain Name List recorded in the TMCH before any domain names from the set are registered. * There was a question from a team member if this is just for registries that activate variants? * No. * The suggested action for this recommendation is to not make any changes to the text. A footnote could be created for context but that is not necessary. * Agreement from the team was given for this recommendation of no action * Regarding Recommendations 12 and 13, IANA Staff members provided feedback * On Rec 12: There are no plans to implement an RDAP server at the IANA level for variant TLDs. * No concerns about the recommendations but wanted to clarify a comment * From a team member, there are questions about implementation. Will the team have to go back and reinvent the wheel? Is it possible for the EPDP to develop technical standards? Based on the comments from IANA there are different opinions on how to proceed. * From a leadership perspective, there is no action required. Potential benefit to make the recommendation clearer relating to the intent, but not necessary at this time. * The Chair asked the team if somebody was to query a domain through RDAP and it turned out to be an unallocated variant, could someone attempt to register that domain? * The understanding is that the registrant would have to be the person for whom the variant is reserved. Due to the same entity principle, if there is an existing domain in the variant set, it would be reserved for whoever owns the entity. * By adding things onto RDAP that don’t create value, is the team spending its time wisely? * It could add value if you could query non existing domain names. If a set exists, but a variant is unregistered, it would be beneficial to users for them to see that in a query of all of the variant set. * Users can make any query, it's up to the registry / registrar on how to answer. Some TLDs answer that a string cannot be registered or reserved. Some do not because they do not have to. It is up to the contracted party to give the level of detail requested by the Chair. * On Rec 13: There were concerns about a comment in the rationale for Recommendation 13. During the workshop it was discussed the accuracy between the HTML and TXT versions of the Root Zone Database. IANA disagrees with this characterization. * Staff asked if the rationale should be modified in Rec 13 to account for IANA comments? * The chair is in favor of removing the rationale text in Rec 13 as it is not necessary for the text and the team agreed. * ACTION ITEM: Staff will revise text in Rec 13 to remove the part about the accuracy between the HTML and TXT versions of the Root Zone Database. * On Rec 8 and IG 9, There were IANA staff comments that IG 9 would delay Rec 8. Staff asked the team if they would require IG 9? * Leadership is in favor of removing IG 9 as it is unclear if it's beneficial at this time. * The team agreed. Since it is already a “Should” clause and already weak * As it is already written, it can be interpreted that this should be delayed pending the URDP review, but that is not the intent of the team. * ACTION ITEM: Staff will remove IG 9 in response to ICANN org comments. * Update from ccPDP4 on Preliminary Recommendations 14 (10 min) * ccPDP4 welcomed EPDP IDN policy staff to present to their group and provide an introduction to the preliminary recommendation. The ccPDP4 team will present to the ccNSO council and there should be an update from the ccNSO and ccPDP4 team by Friday, 16 Feb. * Draft section to address deferred guidelines from IDN Implementation Guidelines version 4.0 (20 min) * For Implementation Guidance 15, There was a question if automatic activation should be allowed or be only considered for where generally the community agrees with the need? * This was raised because automatic registration poses a challenge for registrants (Someone applies for 1 and gets 4, can be challenging to manage). SAC060 notes this challenge. * Some comments from the team said they could see the reasoning that some automatic activation could be sensible, but also that it should be restricted. * May have an impact, for example, that a registrant applying for Simplified Chinese may want to automatically receive the Traditional Chinese variant automatically. In the IDNs guidelines, this was only applicable to Chinese. * There was a point that the team should not be overly prescriptive, specifically in implementation guidance. We could go further on IG 15.2, but also valid to not expand further. * AOB (3 min) * Next call will take place next week. Looking longer out, there will be two calls before ICANN79, with a meeting still planned for ICANN79.

1 0

ICANN79 GNSO Sessions - How to Get Organized / Remote Participation Details
by Julie Bisland 12 Feb '24

12 Feb '24

Dear all, With ICANN79<https://meetings.icann.org/en/icann79> 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 28 February 2024! * Sign into Your ICANN Account or create an account here [account.icann.org]<https://urldefense.com/v3/__https:/account.icann.org/login__;!!PtGJab4!7Ose…>. * Register by selecting the Meeting Registration tile. * Click on the Registration link. NOTE: There will be no onsite registration facilities this year so you must register in advance. In-person, advance registration will close on 28 February 2024. After that point in time, only virtual participation will be open for continued registration. Walk-up and late registrations will not be accepted after the in-person advance registration closes. All walk-up and late registered attendees will only have access to virtual participation. 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/79healthandsafety>. CREATE YOUR MEETING SCHEDULE * Access the schedule here [icann79.sched.com]<https://urldefense.com/v3/__https:/icann79.sched.com/__;!!PtGJab4!7OsehoONe…>. 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, “Mobile app + iCal” (located on the right side of the page) * 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 ICANN79 Meeting Schedule [icann79.sched.com]<https://urldefense.com/v3/__https:/icann79.sched.com/__;!!PtGJab4!7OsehoONe…> ICANN79 GNSO Remote Participation Wiki Page<https://community.icann.org/x/XIMYEQ> GNSO Session agendas<https://community.icann.org/x/WYMYEQ> 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…> [signature_2593744606]

1 0

Reminder: Key Documents for Your Review
by Ariel Liang 12 Feb '24

12 Feb '24

Hello EPDP Team, This is a friendly reminder for you to review the following documents in preparation for the final discussions, which are expected to take place in this week’s and next week’s meetings: 1. Draft recommendation text: https://docs.google.com/document/d/1UrrckzbPNL1Z8fUtH5Q5WqUWglxbD-SbihX8o8V… * Note: please focus on the redlines; the proposed updates for preliminary recommendation 12 (pp.33-34) is pending feedback from the registries members, in particular. 2. Draft Glossary: https://docs.google.com/document/d/1NaDttdqEdrNeWPxZVWm2JA565zN3beFx7ZGbYlQ… * Note: please focus on the items highlighted in yellow 3. Assessment of Deferred Guidelines from IDN IG v4.0: https://docs.google.com/document/d/1bL-b_rM3Da7szcS1Rhm20vk9_5jTMQwmkCHKsxq… * Note: please focus on the “Summary of EPDP-IDNs Output” and “Assessment” in the table Thank you all! Best Regards, Ariel

1 0