- GNSO-TPR - lists.icann.org

Transfer Policy Review PDP WG
by ICANN Policy Calendar March 20, 2024

March 20, 2024

Meeting: Transfer Policy Review PDP WG Date/time: Occurs every Tuesday at 16:00 UTC for 90 minutes, 02 April – 04 June 2024 (note: 07 May – no meeting due to CPH Summit) Alternate replacement confirmations – Members who are unable to attend, please complete the google form<https://docs.google.com/forms/d/e/1FAIpQLScXP3-H595xH4EFgaR3ydOr-1o9BLAVGUI…> to communicate who the alternate is replacing you. 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> * 2024 Wiki page: https://community.icann.org/x/S4BFE ONLY for Members & Alternates: * Please join via the above Zoom Webinar link and staff will promote you to Panelist * Alternate assignments will be posted to the Alternate Log-Transfer Policy Review PDP wiki page<https://community.icann.org/x/V4aUCQ>. * Chat: 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. * 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# 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, 26 March 2024
by Julie Bisland March 19, 2024

March 19, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 26 March 2024 at 16:00 UTC for 90 minutes. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. Zoom 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/wQDFE * Time conversion link: https://tinyurl.com/mpe37d4n ONLY FOR MEMBERS & ALTERNATES: * Staff will promote members and alternates to panelist once joined. * Chat: Please select Everyone so everyone can see your chat, and so it’s captured in the recording. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. * Alternate assignments 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 3 Zs (zzz) before your name and add, your affiliation - alternate after your name. * 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 Policy Team Supporting the GNSO

1 0

Post Call | Transfer Policy Review PDP WG | Tuesday, 19 March 2024
by Julie Bisland March 19, 2024

March 19, 2024

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 19 March 2024 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/vwDFE> (attendance included) and the GNSO Master calendar [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…>. These include: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, and chat.) * Transcript * Agenda and Notes/Action Items 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

**STARTS IN 15 MINUTES** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 19 March 2024
by Julie Bisland March 19, 2024

March 19, 2024

**STARTS IN 15 MINUTES** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 19 March 2024 at 16:00 UTC for 90 minutes. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. Zoom 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/vwDFE * Time conversion link: https://tinyurl.com/axdbpsdb [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/axdbpsdb__;!!PtGJab4!_tI5KWj…> ONLY FOR MEMBERS & ALTERNATES: * Staff will promote members and alternates to panelist once joined. * Chat: Please select Everyone so everyone can see your chat, and so it’s captured in the recording. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. * Alternate assignments 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 3 Zs (zzz) before your name and add, your affiliation - alternate after your name. * 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 Policy Team Supporting the GNSO

1 0

**REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 19 March 2024
by Julie Bisland March 19, 2024

March 19, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 19 March 2024 at 16:00 UTC for 90 minutes. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. Zoom 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/vwDFE * Time conversion link: https://tinyurl.com/axdbpsdb [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/axdbpsdb__;!!PtGJab4!_tI5KWj…> ONLY FOR MEMBERS & ALTERNATES: * Staff will promote members and alternates to panelist once joined. * Chat: Please select Everyone so everyone can see your chat, and so it’s captured in the recording. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. * Alternate assignments 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 3 Zs (zzz) before your name and add, your affiliation - alternate after your name. * 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 Policy Team Supporting the GNSO

2 1

Proposed Agenda - Meeting #122 Tuesday, 19 March 2024 at 1600 UTC
by Christian Wheeler March 18, 2024

March 18, 2024

Dear TPR WG members, Please find below the proposed agenda for our next call, taking place tomorrow, 19 March 2024 at 16:00 UTC. This agenda may be revised. Thank you and we look forward to seeing you all virtually. Kind regards, Caitlin, Berry, Julie, Feodora, and Christian ---------- Transfer Policy Review - Meeting #122 Proposed Agenda 19 March 2024 Proposed Agenda: 1. Welcome and Chair Updates 2. ICANN79 TPR Sessions Debrief 2a. Discuss updates to CORD Draft Recs 2b. Poll questions 2c. Established Relationships (time permitting) 3. AOB

1 0

Notes and action items: TPR WG at ICANN79 Sessions 1 & 2
by Julie Hedlund March 2, 2024

March 2, 2024

Dear TPR WG members, Please find below the brief notes and action items from today’s meetings at ICANN79, Sessions 1 & 2. The next meeting will be Tuesday, 19 March 2024 at 1600 UTC. Kind regards, Christian, Caitlin, Feodora, Berry and Julie ACTION ITEMS/HOMEWORK: None captured. Transfer Policy Review Proposed Agenda 02 March 2024 ICANN79 Session 1 – See attached slides. 1. Welcome and Chair updates * Got a packed agenda with two sessions over the next three hours. 2. Group 1(b) Change of Registrant Data (CORD) Draft Recommendation Review – “Where We Stand” a. Recap of current draft CORD recommendations – Start at slide 3. Discussion: Slides 7-8: * Question: New policy/expanding TDRP for registrants filing – says “and”, which seems like a redundancy, instead of “or”? Answer: Maybe that should be an “or”? * Not that we would be doing both, but “and” means we are exploring both. Slides 9-11: * WG is still discussing what to do with Prelim Rec 2 – having a COR standalone policy. * Question: This comes out of the policy and goes elsewhere? Who is that directed at? Answer: We will provide the Rec to GNSO Council so they can decide. * It is up to the GNSO Council. * Re: Designated Agent – won’t be defined in the transfer policy, but can still exist. * We put a lot of time into how other policies relate to this. Slides 12-15: * Question: Applies to other emails too? Answer: Not being specific in case things change. * Question: Does “unless” to both or just to the new one? Answer: Should only apply to the new email address. * Wondering if we could amend 3.4: Don’t think there can be a non-material change to a email address. Take out “material”. Also wonder on 3.5 if we are saying what you cannot do – are we setting precedent? Giving permission? Good to include because we have questions about what can be done. Do think there is precedent in the Registration Data Policy. Also, any change is considered material so good to take out. * Who can opt out? Registrants might have turned off notifications – both new and old. * Re: 3.5 – Maybe change to “MAY”. * Maybe we can come back to the question of which RNH the CORD opt out applies to at a subsequent meeting? I'm still feeling uncertain about it Opt out additional discussion --- Rec 3.4 and Rec 4: * Some aspects of opt out are unclear. * Thinking we should require that the new RNH gets the notice – how would they know they are now under a contract? * Most registrars would send two notices anyway. * Question: Rec 4.1 --- do we add “and a change of registrant data has occurred”? Answer: That make sense and seems to be the intent of the WG. * We need an email address to opt out – but we are saying we are sending notifications to gaining and losing RNHs even if opting out. We need to clear that up to now it reads that notifications are by email address. * Sometimes both parties already know, but it still makes sense that they both receive. * We are overcomplicating this: We need to write it in the singular to make it more clear. Also, you can’t opt out when you don’t have the name. When a name gets register or transferred in (in bound) it is covered by a different policy. Per registration (domain name). Slides 16-17: * When we are looking at all the accounts people have then you can have a lot of notifications. This gives users some control to reduce notifications in an informed way. END SESSION 1 NOTES ICANN79 Session 2 1. Welcome and Chair updates * No updates. Continuation from Session 1: 3. Revisiting Group 1(a) 30-day transfer restriction – start with slide 20 a. Recap of existing recommendations Discussion – see questions on slide 27: * Questions: Any issues with Compliance? Answer: Concern at the time was that there needs to be some objective yardstick, so we put in some criteria. * Doesn’t create a right to override the 30-day restriction. * Being able to point to policy is sometimes helpful with customers. * 30-day restriction is consistent across the policy. * Would think it would apply more to people with larger domain portfolios. * All kinds of scenarios where this fluidity would be helpful. * Question: Think about what it means to have a “Established Relationship” – what if requested in a problematic way? Answer: Can be investigated and denied. * Brings back the responsibility of the sponsoring registrar. * Sounds like the WG supports it, but is there proof that the registrar has to provide? * Need a definition of a “regular interaction”. Could be a series of business interactions. * Should we apply it to new registrations? * Not clear that someone other than the RNH could request it. Not clear. * Other recs apply to cases of fraud. * You want to have some restrictions in place for registrar is not holding the bag – registrar can verify and authorize or not. * If this results in consensus policy then the RAA is subject to that. * Do we see much fraud with transferring out? We’ve seen some. * Don’t see how the logic wouldn’t hold for a 30-day post-creation lock. Would be consistent. * Determination: Seems the WG likes this and it should apply to a post-transfer and a post-creation lock. b. Updates needed in light of current CORD recommendations - exemptions needed? * Don’t see an impact. c. Open mic – invitation for community feedback (in room and online) * None. 4. Any other business – Next meeting in two weeks on 19 March.

1 0

ICANN79 Presentation Slides
by Christian Wheeler Feb. 28, 2024

Feb. 28, 2024

Dear TPR WG members, Please find attached the slides we will use for our ICANN79 sessions this Saturday (2 March, 1:15pm and 3:00pm AST). We recommend familiarizing yourselves with these slides ahead of our two sessions. Our focus will be on slides 1-28. Thank you to our volunteers who will introduce slides 7-17. In the meantime, WG members please assist our volunteers by adding more rationale to the CORD Preliminary Recommendations + Rationale<https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr…> Google Doc. Thank you all again and we look forward to seeing you virtually and in person in San Juan. Safe travels! Kind regards, Caitlin, Berry, Julie, Feodora, and Christian

1 0

FW: Notes and action items: TPR WG on 27 February 1600 UTC
by Feodora Hamza Feb. 28, 2024

Feb. 28, 2024

Dear TPR WG members, Please find below the brief notes and action items from yesterday’s meeting. The next meetings will be Saturday, 02 March at ICANN79: Session 1 at 13:15-14:30 and Session 2 at 1500-1600 San Juan (UTC-4). Kind regards, Christian, Caitlin, Berry, Julie and Feodora ============================================================================================ 2024-02-27 Transfer Policy Review PDP WG Call<https://community.icann.org/display/TPRPDP/2024-02-27+Transfer+Policy+Revie…> Main discussion and action items 1. Welcome and Chair Updates * Link to the slides: https://docs.google.com/presentation/d/1JIYvzbYHJxK5srf2qbdKr_qslCl-TOcv9iQ… * Members are encouraged to take a look at the rationale document (https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr…) and add input where possible 2. ICANN79 TPR sessions Agenda * Two sessions during ICANN79 Saturday 2nd of March (link) * Links to wiki page agenda of ICANN79 sessions: * Session 1: Focus on Recommendations * https://community.icann.org/display/TPRPDP/2024-03-02+ICANN79+Transfer+Poli… * Session 2: Focus on Established Relationships: https://community.icann.org/display/TPRPDP/2024-03-02+ICANN79+Transfer+Poli… * 4 Members are encouraged to serve as volunteers to present during ICANN79 to present/read out recommendations * Volunteers: Rec 1: Prudence Rec 2: Theo Rec 3: Owen Rec 4: Sarah * Will rationale document be presented? Focus will be on recommendations document as rationale document is still work in progress. 1. CORD Prelim Recs & Rationale (& volunteers) * Link to doc: https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr…. * Rec 1.3. change included revised language to clarify if P/P is involved. * Rec 2 the order has been updated based on previous call. Clarifies what to keep Section II from the transfer policy. * Current Section II needs it own policy. * Recs should be taken into consideration as a whole and not in isolation. * Rec 2.1 includes changes that clarifies that the “designated agent” is not used properly and new wording has been added. “Designated agent”should be eliminated from “future standalone Change of Registrant Data Policy”. * “Designated Agent” removed from transfer policy, but it could be used elsewhere if need be for other processes. * Rec 2.2 Eliminate Section II b “Availability of Change of Registrant” from future standalone policy. It not necessary to include here. * Rec 2.4 Eliminiate 60-day lock from future policy. * Perception could arise that this Rec 2.4 might take away security measured. Hence, more rationale could be needed in the rational document? * Members referred also to other options for registrants to increase security for their domains. * Rec 3 group is adding that Registrars have to provide instructions how registrants can take action if the change was invalid. * Rec 3.4 wording changed from MUST to MAY send CORD notification to new Email address. * Rec 4 Registrars must provide an opt out for Change of Registrant Data notifications. * Rec 4.1. Registrars MUST enable Change of Registrant Data notifications by default when a domain name is initially registered. Registrars MAY disable Change of Registrant Data notifications if the Registered Name Holder elects to opt out of these notifications. * Discussion on is this a security feature and is this hapering security or enhancing it? Opt out as part of data protection option? * Email verification process is in place and could pose an overlap with Rec 4.1? Verification Email only goes to updated Email not existing Email. 2. Recap “Established Relationship” topic * Link to slides: https://docs.google.com/presentation/d/1JIYvzbYHJxK5srf2qbdKr_qslCl-TOcv9iQ… * TPR Swimlane Overview included in the slides. Two yellow boxes are included for the established relationship procedure: * Initiation * Transfer * Refresher on NACK-ing recommendations (Prelim Rec 16 and Prelim Rec 17). How does this affect registration data? * Small group redlined Rec 17 where registrars MUST apply 30-day post change lock and included that they may unlock earlier if an established relationship exists. * Rationale will be further explained and presented during ICANN79 and group should be prepared to speak for or against it during ICANN79. * Does the group believe that an “Established Relationship” role/procedure should be created? If so, what exemptions should customers be provided with? How do these exemptions impact TPR? 1. AOB * No comment

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 19 March 2024
by Julie Bisland Feb. 27, 2024

Feb. 27, 2024

NOTE: The next meetings take place during ICANN79; see session 1<https://icann79.sched.com/event/1a15v/gnso-transfer-policy-review-pdp-worki…> and session 2<https://icann79.sched.com/event/1a15y/gnso-transfer-policy-review-pdp-worki…> schedule pages (Zoom participation links will be published 24 hours before the session starts.) Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 19 March 2024 at 16:00 UTC for 90 minutes. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. Zoom 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/vwDFE * Time conversion link: https://tinyurl.com/axdbpsdb ONLY FOR MEMBERS & ALTERNATES: * Staff will promote members and alternates to panelist once joined. * Chat: Please select Everyone so everyone can see your chat, and so it’s captured in the recording. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. * Alternate assignments 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 3 Zs (zzz) before your name and add, your affiliation - alternate after your name. * 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 Policy Team Supporting the GNSO

1 0