- GNSO-TPR - lists.icann.org

Proposed agenda for meeting #47 on Tuesday 17 May 2022 at 16:00 UTC
by Caitlin Tubergen June 1, 2022

June 1, 2022

Dear Working Group members, Please find below the proposed agenda for the next meeting scheduled to take place on Tuesday, 17 May 2022 at 16:00 UTC. Kind regards, Emily, Julie, Berry, and Caitlin Transfer Policy Review Phase 1 - Meeting #47 Proposed Agenda 17 May 2022 1. Roll Call & SOI updates 2. Welcome and Chair Updates 3. Return to items in the preliminary recommendations flagged for further discussion during last week’s call (see here<https://docs.google.com/document/d/1clAqB1wBeOf9ZC5RMMxKrrUTs3N2WyaVYTIyVy_…>) * Recommendation 7 * Recommendation 9.2 * Recommendation 13.1 * Recommendation 13.2 4. Discussion of Recommendation 19 email thread (please see here<https://mm.icann.org/pipermail/gnso-tpr/2022-May/000449.html>) 5. Begin review of items flagged in Proposed Revisions from Working Group members<https://docs.google.com/document/d/1s9xumJ1XBPdTb7kQmc5sAC2AkszvfAF0freMvnx…> document (if any) 6. AOB * Next call: Tuesday 24 May 2022 at 16:00 UTC

4 5

ICANN74 GNSO Policy Briefing Available for Download
by Julie Bisland June 1, 2022

June 1, 2022

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

June 2022 calls | Transfer Policy Review PDP WG
by Julie Bisland June 1, 2022

June 1, 2022

**We are sending in advance to get dates on everyone’s calendar. Dear all, The calls for June 2022 for the Transfer Policy Review PDP WG are listed below. The calls are each 90 minutes. * Tuesday, 07 June 2022 at 16:00 UTC * Monday, 13 June 2022 at 08:30 UTC at ICANN74 (zoom link will be available 24 hours before on the ICANN74 schedule) * Tuesday, 28 June 2022 at 16:00 UTC (.ics is attached) Future invitations will be sent out closer to the date of the call. You should have already received the meeting invite for the next call, 07 June. Thank you. With kind regards, Julie

1 0

Transfer Policy Review PDP WG
by ICANN Policy Calendar June 1, 2022

June 1, 2022

Meeting: Transfer Policy Review PDP WG Date/Time: Tuesday, 28 June 2022 at 16:00 UTC for 90 minutes Join the Zoom Webinar: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 Passcode: @TP/^*4wg# ALL: Before joining the call: * Please send apologies and 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://www.icann.org/resources/pages/expected-standards-2016-06-28-en> * Wiki Agenda meeting page: https://community.icann.org/x/cAD5Cw * Check your time zone: https://tinyurl.com/ymtx2xxu ONLY for Members & Alternates: * Please join via the above Zoom Webinar link and staff will promote you to Panelist * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form<https://docs.google.com/forms/d/e/1FAIpQLScXP3-H595xH4EFgaR3ydOr-1o9BLAVGUI…> to communicate who the alternate is replacing and for which period. This information will be posted to the Alternate Log-Transfer Policy Review PDP wiki page<https://community.icann.org/x/V4aUCQ>. * Members and alternates replacing members, please select Everyone when posting to the chat in order for everyone to see and to be captured afterwards. * Alternates (not replacing a member): Please rename your line in Zoom by adding THREE Zs “zzz” before your name, and in parentheses, (your affiliation - alternate), after your name. To rename in Zoom, hover over your name and click ‘rename’. * Alternates (not replacing a member) are not allowed to engage in the chat or use any of the other zoom room functionalities such as raising hands or agreeing/disagreeing. 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. For Audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Telephone: Dial (for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 07 June 2022
by Julie Bisland May 26, 2022

May 26, 2022

Please note: The call for Tuesday, 31 May has been cancelled; please remove it from your calendar. The next team call will be 07 June, see details below: Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 07 June 2022 at 16:00 UTC for 90 minutes. Zoom Room Information: Main Zoom Webinar link: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/95363727469?pwd=N3A3OWFS…> Passcode: @TP/^*4wg# If you are joining via audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Telephone: Dial (for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acdLFXPLp6__;!!PtGJab4!v…> Members, alternates, and observers all have different access and participation directions, please read below! ALL: Before joining the call: * Please send apologies and 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://www.icann.org/resources/pages/expected-standards-2016-06-28-en> * Visit the Wiki Agenda meeting page: https://community.icann.org/x/7BB1Cw * Check your time zone: https://tinyurl.com/y5mamr72 ONLY FOR MEMBERS & ALTERNATES: * Please join via the Main Zoom Webinar link above; staff will promote you to panelist. * Chat: Members (and alternates replacing members), please select Everyone so everyone can see and so it’s captured afterwards. * Alternate replacement confirmations – For tracking alternate replacements, use the google form [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…> to communicate the replacement (alternate) and the duration. This information will be publicly posted to the Alternate Log-Transfer Policy Review PDP<https://community.icann.org/x/V4aUCQ> wiki page. * Alternates (not replacing a member): Rename your line by adding THREE Zs (zzz) before your name and add, in parentheses (your affiliation - alternate) after your name. To rename in Zoom, hover over your name and click ‘rename’. * Alternates (not replacing a member) are not allowed to engage in the chat or use any of the other zoom room functionalities such as raising hands or agreeing/disagreeing. 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

Canceled: Transfer Policy Review PDP WG
by ICANN Policy Calendar May 26, 2022

May 26, 2022

31 May 2022 has been cancelled Meeting: Transfer Policy Review PDP WG Date/Time: Recurring every Tuesday at 16:00 UTC for 90 minutes, 03 May 2022 through 07 June 2022 Join the Zoom Webinar: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 Passcode: @TP/^*4wg# ALL: Before joining the call: Please send apologies and 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://www.icann.org/resources/pages/expected-standards-2016-06-28-en> Wiki Agenda meeting pages 2022: https://community.icann.org/x/Z4HOCg ONLY for Members & Alternates: * Please join via the above Zoom Webinar link and staff will promote you to Panelist * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form<https://docs.google.com/forms/d/e/1FAIpQLScXP3-H595xH4EFgaR3ydOr-1o9BLAVGUI…> to communicate who the alternate is replacing and for which period. This information will be posted to the Alternate Log-Transfer Policy Review PDP wiki page<https://community.icann.org/x/V4aUCQ>. * Members and alternates replacing members, please select Everyone when posting to the chat in order for everyone to see and to be captured afterwards. * Alternates (not replacing a member): Please rename your line in Zoom by adding THREE Zs “zzz” before your name, and in parentheses, (your affiliation - alternate), after your name. To rename in Zoom, hover over your name and click ‘rename’. * Alternates (not replacing a member) are not allowed to engage in the chat or use any of the other zoom room functionalities such as raising hands or agreeing/disagreeing. 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. For Audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Telephone: Dial (for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6

1 0

Notes and action items - TPR WG Meeting #48 - 24 May 2022 at 16:00 UTC
by Julie Hedlund May 24, 2022

May 24, 2022

Dear TPR WG members, Please find below the notes and action items from today’s meeting. Leadership along with the WG will consider whether to cancel the next meeting on Tuesday, 31 May 2022 at 16:00 UTC. Best regards, Emily, Julie, Berry, and Caitlin Action Items 1. WG members to review the draft questions and text on recommendation 13.1 for public comment and provide comments/suggestions if any. See: https://docs.google.com/document/d/1-iMcSboPsoTCHYye_u0uVmaVgNiOP7FKYXkO3FW…. 2. Staff to send to the WG list the latest version of the draft Initial Report (that which was sent after the WG meeting on 17 May) – COMPLETE; SEE ATTACHED. 3. Leadership along with the WG will consider whether to cancel the next meeting on Tuesday, 31 May 2022 at 16:00 UTC. Notes: Transfer Policy Review Phase 1(a) - Meeting #48 Proposed Agenda 24 May 2022 1. Roll Call & SOI updates 2. Welcome and Chair Updates * Roger Carney, Chair -- Rec 13.1: Overview: * With disagreement on where the TTL enforcement should be done the staff has been working on a question for the public comment period. Link to Google Doc for Community Question regarding standard TTL: https://docs.google.com/document/d/1-iMcSboPsoTCHYye_u0uVmaVgNiOP7FKYXkO3FW…. * Note that public comment is constructed with a survey with community questions by topic. This was followed for the EPDP for registration data. * Includes notes for the community, including what is a TTL and what are the WG proposals, and why the registry was originally proposed to enforce. WG members also can respond in the public comment period. * Google doc with the question is open for WG members to comment. Note that we are trying to keep the question and proposals brief. * Jim Galvin, RySG: * For the record – did not realize that the WG was seeking a formal RySG group position. * Would a position – other than informally that there is not support for this – result in a different action? * Clarifying question: Does this mean that rec 13.1 will stay stated as is in the public comment? * Roger Carney, Chair: * There was no formal call for action, but we were expecting WG members to consult with their groups. * Intent is to go to public comment with it as written and an official comment wouldn’t change that, but groups can comment in the public comment forum. * Discussion: * One proposal could be to put the TTL into the hash itself. * Embedding the TTL into the TAC was discussed by the TechOps group. * That could also be guidance for the IRT. * We are looking for broad feedback in the public comment, but targeted feedback from the respective SGs and Cs. After the public comment period closes the WG will review all the comments and evaluate whether changes are needed to the draft Initial Report that was posted for public comment. * The next phase of the process is to get us closer to consensus. * Jim Galvin, RySG: Statement for the record. I believed I was following the process. We all have an obligation to keep up with the work, but I missed the point at which 13.1 was closed. RySG has objected to this recommendation from the beginning, so perhaps I missed a possibility to bring this back to the agenda. I and my registry colleagues did not realize that this was closed and we should have made sure that this remained open. We will work with the process going forward. ACTION ITEM: WG members to review the draft questions and text on recommendation 13.1 for public comment and provide comments/suggestions if any. See: https://docs.google.com/document/d/1-iMcSboPsoTCHYye_u0uVmaVgNiOP7FKYXkO3FW…. ICANN74: * See related sessions: * GNSO Policy Update: Tuesday, 31 May at 18:00 UTC. * Dedicated Transfer Review Update of Initial Report: Thursday, 2 June at 14:00 UTC. 3. Return to items flagged for further discussion during last week’s call (see here [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1clAqB1wBeOf9…>) a. Discussion of Recommendation 19 email thread (please see here<https://mm.icann.org/pipermail/gnso-tpr/2022-May/000449.html>) (Mike R.) Proposed revision: “Evidence of fraud or [material] violation of the Registration Agreement. Implementation Guidance: The intent of “violation of the Registration Agreement” is not to allow the blocking of transfers due to minor violations, but to allow action in case of substantive contravention of the Registration Agreement.” Discussion: * Mike provided an email, see above, with the concern that a nefarious registrar could have a clause that could deny and transfer. * Mike had suggested language with a materiality assessment. * Sarah had suggested similar language and staff put that out for WG review, particularly by Mike. Since Mike is not on this call staff will follow up with Mike to ask for his comments and if he has alternate language. * Language is still too broad – could be anything that could be a violation. Think we need to be more specific. * Note that this is a “MAY” deny. * Note also that there is a separate option to deny for non-payment: I.A.3.9.1: Implementation Guidance: Registrars are prohibited from denying domain name transfer requests based on non-payment of fees for pending or future registration periods during the Auto-Renew Grace Period, provided that any auto-renewal costs borne by the Registrar are reversible for future period. * More specificity would help ICANN Compliance, such as “violation of registrar's domain use or anti-abuse policies” would be helpful. * There is a very narrow use case. * Leave the alternate language for now. b. Recommendation 12 (Mike R.): “Five calendar days, or 120 hours as stated in the report, is too long to wait for a TAC. While most registrars give this to you instantly or within minutes, we wouldn’t want to wait five days if the matter was urgent and a registrar had that kind of time latitude. We’d strongly prefer a 1-2 calendar day maximum.”’ Preliminary Recommendation 12: “The working group confirms that the Transfer Policy MUST continue to require Registrars to set the TAC at the Registry and provide the TAC to the RNH or their designated representative within five calendar days of a request, although the working group recommends that the policy state the requirement as 120 hours rather than 5 calendar days to reduce any risk of confusion. The working group further recommends that the policy MUST make clear that 120 hours is the maximum and not the standard period in which the TAC is to be provided.” Discussion: * In current policy there are two 5-day windows, so actually 10 days. So the suggestion in Rec 12 cuts that time in half. * Worth talking about whether a smaller time period is acceptable, and what are the pros and cons of leaving it at 5 or making it shorter. * Swimlane can be helpful here – particularly the moment when the RNH requests the TAC that there are a large number of transfer that have no issues keeping the transfer from happening in a number of minutes. Conversely, there are cases where various issues must be cured before the TAC is provisioned to the RNH. These 120 hours, are they the appropriate time to cure those issues. * Note that this is “up to” the 120 hours. It should be done as quickly as possible if not simultaneously. * WG seems to have coalesced around 5 days – not hearing support for changing to less than 120 hours. * Leave it as is and go to comment with this. IPC can comment in the public forum. 4. Begin review of items flagged in Proposed Revisions from Working Group members [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1s9xumJ1XBPdT…> document (if any) * Nothing else is flagged. * Probably can cancel next week’s call. * Updated version of the Initial Report was sent out after last week’s call incorporated changes agreed to on the call relating to RFCs and suggestions from Jim. * Staff will send last week’s version of the Initial Report along with the notes from this call. Didn’t hear any agreement to change the language from what was sent after last week’s call. * Leadership to consider with the WG whether to cancel next week’s meeting. * Plan is to talk about Phase 1(b) on Change of Registrant during ICANN74. WG should start reviewing those charter questions. ACTION ITEM: Staff to send to the WG list the latest version of the draft Initial Report (that which was sent after the WG meeting on 17 May) – COMPLETE; SEE ATTACHED. 5. AOB * Next call: Tuesday 31 May 2022 at 16:00 UTC ACTION ITEM: Leadership along with the WG will consider whether to cancel the next meeting on Tuesday, 31 May 2022 at 16:00 UTC.

1 0

Post Call | Transfer Policy Review PDP WG | Tuesday, 24 May 2022
by Julie Bisland May 24, 2022

May 24, 2022

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 24 May 2022 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/5hB1Cw> (attendance included) and the GNSO Master calendar <https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> . These include: * Attendance * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) * Transcript As a reminder only members and alternates can join the call as a Panelist, observers can join as an Attendee to listen. For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-tpr/> and the main wiki page<https://community.icann.org/x/P4aUCQ>. Thank you. With kind regards, Julie

1 0

**AT THE TOP OF THE HOUR** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 24 May 2022
by Julie Bisland May 24, 2022

May 24, 2022

**AT THE TOP OF THE HOUR** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 24 May 2022 at 16:00 UTC for 90 minutes. Zoom Room Information: Main Zoom Webinar link: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/95363727469?pwd=N3A3OWFS…> Passcode: @TP/^*4wg# If you are joining via audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Telephone: Dial (for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acdLFXPLp6__;!!PtGJab4!v…> Members, alternates, and observers all have different access and participation directions, please read below! ALL: Before joining the call: * Please send apologies and 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://www.icann.org/resources/pages/expected-standards-2016-06-28-en> * Visit the Wiki Agenda meeting page: https://community.icann.org/x/5hB1Cw * Check your time zone: https://tinyurl.com/3a27hdth [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3a27hdth__;!!PtGJab4!85CXdbs…> ONLY FOR MEMBERS & ALTERNATES: * Please join via the Main Zoom Webinar link above; staff will promote you to panelist. * Chat: Members (and alternates replacing members), please select Everyone so everyone can see and so it’s captured afterwards. * Alternate replacement confirmations – For tracking alternate replacements, use the google form [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…> to communicate the replacement (alternate) and the duration. This information will be publicly posted to the Alternate Log-Transfer Policy Review PDP<https://community.icann.org/x/V4aUCQ> wiki page. * Alternates (not replacing a member): Rename your line by adding THREE Zs (zzz) before your name and add, in parentheses (your affiliation - alternate) after your name. To rename in Zoom, hover over your name and click ‘rename’. * Alternates (not replacing a member) are not allowed to engage in the chat or use any of the other zoom room functionalities such as raising hands or agreeing/disagreeing. 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

ICANN74 schedule now published
by Terri Agnew May 23, 2022

May 23, 2022

https://www.icann.org/en/announcements/details/schedule-for-icann74-policy-… Dear all, This is the first ever ICANN meeting in hybrid format. Whilst some steps will seem familiar, others are brand new, please read the below carefully before creating your schedule. I MUST REGISTER TODAY FOR ICANN74 INFORMATION Sign into my ICANN Account, or create an account here<https://account.icann.org/login>. Register for ICANN74 by clicking in the ICANN SERVICES menu and selecting Meeting Registration Click on the ICANN74 Registration link. Click here<https://gnso.icann.org/sites/default/files/policy/2021/presentation/instruc…> for detailed instructions. The deadline to register for in-person participation is 8 June 2022 at 23:59 UTC. Before creating my schedule I must read this page carefully, to understand what’s new in the hybrid meeting format: https://74.schedule.icann.org/attend IN-PERSON PRIORITY SEATING GNSO Councilors who confirmed they will be traveling to the Hague: · If you have registered on the ICANN74 Website<https://74.schedule.icann.org/>, you will see the indication that your GNSO Council sessions have already been added to your schedule. GNSO PDP/EPDP/ST/SG/C Members: · If you signed up via the google survey as an active PDP/EPDP/ST/SG/C member, you will automatically be signed up to that session. · If you have not yet signed up to attend ICANN74, have not responded to the surveys sent by gnso-secs, and you will be attending on-site, please only select sessions that you will be attending as an active member or participant CAN I CREATE MY MEETING SCHEDULE NOW? * Please choose carefully when signing up for sessions—seating space is limited and the goal is to prioritize the sessions you will actively participate in * Upon accessing the schedule, I will be asked to confirm whether I’m attending remotely or on-site. * If I’m participating remotely, all good, please proceed to access to the ICANN74 schedule: https://74.schedule.icann.org/. * If I’m participating on-site, I must only attend the sessions in which I am an active participant. Please read the https://74.schedule.icann.org/attend page if you are unsure. Please proceed to access to the ICANN74 schedule: https://74.schedule.icann.org/. * 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 you, to your individual calendars Review the Participation Tools and update Zoom * All sessions will use Zoom rooms. Access details are available 24hrs prior on the ICANN74 Meeting Schedule<https://74.schedule.icann.org/>. * Visit the Participation Tools page<https://74.schedule.icann.org/participation-tools> for links to download the latest version of Zoom for access to the ICANN74 sessions. * Please see the ICANN Meeting Virtual Participation How-To Guide<https://74.schedule.icann.org/attend> for more information on how to get the most out of the virtual meeting tools. Links to Bookmark ICANN74 Meeting Schedule<https://74.schedule.icann.org/> GNSO ICANN74 Wiki Page<https://community.icann.org/x/vhN1Cw> GNSO Session agendas<https://community.icann.org/x/vBN1Cw> For all GNSO meeting-related queries (RP or others), please email us at: gnso-secs(a)icann.org and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team

1 0