December 2024 - GNSO-TPR - lists.icann.org

Proposed Agenda - Transfer Policy Review Working Group Meeting - Tuesday, 07 January 2025 @ 16:00UTC
by Christian Wheeler 19 Dec '24

19 Dec '24

Dear TPR Working Group members, Please find below the proposed agenda for our upcoming meeting on Tuesday, 07 January at 16:00 UTC. As a reminder, the working group’s current Action Item is to review the discussion notes and responses columns in the Public Comment Review Tool<https://docs.google.com/spreadsheets/d/1lyX27uECA5bNKRw-UOIH2bAaTRvec1YkX1E…> and flag any concerns or suggested changes. Support staff is currently updating this sheet with the recent Group 2 discussions. Additionally, if you are interested in getting a head-start on the next task, please take a look at the TPR WG Recs for Final Report Google Doc<https://docs.google.com/document/d/1vBi7kQFcCvsxLU6LA2E9IzH-DId1pIj3IAR2DXU…> and identify any recommendations you CANNOT LIVE WITH in the TPR Final Report (due date: Monday, 13 January 2025). Please feel free to share the TPR WG recommendations with your respective groups in the meantime. Thank you and we hope you have a pleasant holiday and restful break. Kind regards, Christian on behalf of the TPR WG Support Team --------------------------- Transfer Policy Review Working Group Meeting Proposed Agenda 07 January 2025 1. Welcome and Chair Updates 2. Review proposed updates to Rec 35 3. Discuss Public Comment Review Tool (PCRT) notes/responses 4. Discuss Final Report 5. AOB

1 0

2024-12-17 Transfer Policy Review PDP WG Call
by Feodora Hamza 18 Dec '24

18 Dec '24

Dear TPR WG members, Please find below the notes and action items from this week’s meeting. The next meeting is scheduled for Tuesday, 7 January 2025 at 16:00 UTC. Wishing you all a joyful holiday season and a well-deserved break! Kind regards, Feodora on behalf of the TPR WG Support Team 2024-12-17 Transfer Policy Review PDP WG Call<https://community.icann.org/display/TPRPDP/2024-12-17+Transfer+Policy+Revie…> Action Items: 1. WG group to review responses in the public comment review tool. 2. ICANN Org to draft revised language for Recommendations 34-36 regarding fee thresholds. Expand explanatory text and rationale for public comments in the final annex. 3. ICANN Org to consolidate finalized recommendations into the “green box” section. Green Box indicates what would be included in the final report. Documents: Public Comment Review Tool (PCRT) <https://docs.google.com/spreadsheets/d/1lyX27uECA5bNKRw-UOIH2bAaTRvec1YkX1E…> Agenda 1. Welcome and Chair Updates 2. Discussion of Additional Question 3 (other comments) Key Comments received (which were not yet covered in WG discussion) · To reduce from 60 days to 30 days, with an optional opt-out after 7 days Outcome: Recommendation 18 allows flexibility for lock removal if certain criteria is met. · Implementation timelines: Requests for alignment with the Registration Data Policy (effective August 2025). Suggested timelines include a 12-18 month implementation period post-policy announcement. Outcome: this would be a decision of the IRT, and would not likely interfere with implementation of the Reg Data policy. 1. Discussion of Recommendations needing additional discussion flagged by WG and/or Leadership Key discussion points: · Recommendation 9: Addition of sections 9.4 and 9.5 to account for rare cases where registries may need to null a TAC without the registrant’s approval. Outcome: Language deemed acceptable; minimal expected execution of these scenarios. · Recommendation 17: Clarification added in 17.5 does not prevent registrars from sending a transfer approval mechanism to the RNH, but rather stipulates that this mechanism must not be included within the transfer confirmation. Outcome: Updated language approved. · Recommendation 18: Floor open to see if the group had updates on 18.3 “reasonable basis”. Recommendation 18 emphasizes flexibility in opt-out mechanisms for transfer locks without the need to wait seven days per commenter. Outcome: Updates supported. · Recommendation 21: Registrar denial of transfer requests due to evidence of fraud or DNS abuse clarified. Registrars MAY provide specific evidence/rationale upon request. Outcome: Updated language approved. · Recommendation 26: 26.2 is regarding the change of registrant data, and the working group is recommending removing Section 2b “Availability of change of registrant” from the future policy. However, the working group recommends retaining the following statement from Section 2 b, 1. “In general, registrants must be permitted to update their registration data”. Outcome: Approved updated language. · Recommendation 27: Implementation guidance added for notification consolidation. A link may be used for cases involving large volumes of domains. Outcome: Language accepted. · Recommendation 33: Debate over expanding TDRP to registrants. The WG Chair pointed out that the decision is with the GNSO Council. Outcome: Suggestion to highlight need for a separate process for registrants rather than expanding TDRP. WG agreed that this should be further discussed at the GNSO Council. · Recommendation 34: Revised fee structure: Fees applicable only for registry families exceeding 50,000 domains. Outcome: The WG Chair suggested updating related Recs (language) to account for the agreed threshold. Action Item: Staff to draft updated language for final approval. · Recommendations 41 and 42: Simplification of language regarding agents, resellers, and service providers to avoid ambiguity. Requirement for registrars to document and retain notification records for compliance reviews. 1. AOB · Staff has been going through the Public Comment Review Tool and providing summaries of the working groups responses to each comment to ensure proper documentation. Feodora Hamza Policy Development Support Manager (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +32 496 30 24 15 Email: feodora.hamza(a)icann.org<mailto:feodora.hamza@icann.org> Website: www.icann.org<http://www.icann.org>

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 07 January 2025
by Julie Bisland 17 Dec '24

17 Dec '24

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 07 January 2025 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: 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://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> * Visit the Wiki Agenda meeting page: https://community.icann.org/x/a4CpG * Time conversion link: https://tinyurl.com/3z3xexud 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, 17 December 2024
by Julie Bisland 17 Dec '24

17 Dec '24

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 17 December 2024 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/5gEfFw> (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 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://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/gnso-tpr…> and the main wiki page<https://community.icann.org/x/P4aUCQ>. Thank you. With kind regards, Julie

1 0

**15-MINUTE REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 17 December 2024
by Julie Bisland 17 Dec '24

17 Dec '24

**15-MINUTE REMINDER** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 17 December 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: 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://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> * Visit the Wiki Agenda meeting page: https://community.icann.org/x/5gEfFw * Time conversion link: https://tinyurl.com/8ux48c3t 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

Proposed agenda - Transfer Policy Review Working Group Meeting - Tuesday, 17 December 2024 @ 16:00UTC
by Christian Wheeler 16 Dec '24

16 Dec '24

Dear TPR Working Group members, Please find below the proposed agenda for our upcoming meeting on Tuesday, 17 December at 16:00 UTC. Transfer Policy Review Working Group Meeting Proposed Agenda 17 December 2024 1. Welcome and Chair Updates 2. Discussion of Additional Question 3 (other comments) 3. Discussion of Recommendations needing additional discussion flagged by WG and/or Leadership 4. AOB Kind regards, Christian on behalf of the TPR WG Support Team

1 0

**REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 17 December 2024
by Julie Bisland 16 Dec '24

16 Dec '24

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 17 December 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: 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://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> * Visit the Wiki Agenda meeting page: https://community.icann.org/x/5gEfFw * Time conversion link: https://tinyurl.com/8ux48c3t 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

2024-12-10 Transfer Policy Review PDP WG Call
by Feodora Hamza 12 Dec '24

12 Dec '24

Dear TPR WG members, Please find below the notes and action items from this week’s meeting. The next meeting will take place on Tuesday, 17 December 2024 at 16:00 UTC. Kind regards, Feodora on behalf of the TPR WG Support Team 2024-12-10 Transfer Policy Review PDP WG Call<https://community.icann.org/display/TPRPDP/2024-12-10+Transfer+Policy+Revie…> Action Item: · WG members to review the Q3 “Other Comments”<https://docs.google.com/spreadsheets/d/1lyX27uECA5bNKRw-UOIH2bAaTRvec1YkX1E…> in the Public Comment Review Tool (PCRT) and flag comments that require further discussion in the WG, i.e., comments, ideas, and issues the WG has not already discussed. · WG members to flag recommendations where further discussion is needed, i.e., text that is better discussed during working group meeting time instead via the PCRT or on list. · WG to consider ICANN org’s comment on Rec. 35, i.e., - An alternative bulk transfer fee model where registries with fewer than 50,000 domains cannot charge fees, and registries with >50,000 domains share the $50,000 cap. 1. Welcome and Chair Updates 1. Continue Discussion of Group 2 Recs 29-47 (TEAC, TDRP, Bulk Transfers) using Public Comment Review Tool<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1lyX27uEC…> Recommendation 31: TEAC Communication Updates Comments Received: Concerns were raised regarding the need for continual updates (every 72 hours) for unresolved cases that have escalated to external venues (e.g., court cases). The suggestion was to allow the gaining registrar to terminate updates once the issue is escalated. Discussion Points: Rich Brown highlighted that the current policy allows the gaining registrar to declare the issue closed informally, thus eliminating the need for additional policy language. Rick Wilhelm supported retaining the current text, stating that unresolved cases escalated to external venues inherently mark resolution under the policy. WG Chair emphasized that the existing language already provides the necessary flexibility. Group Decision: Maintain the current text without additional language, as the process for closing disputes is already implicit. Recommendation 32: Communication Methods for TEAC Comments Received: Suggestions to replace email communication with a centralized system for security and consistency similar to RDRS (ticketing system). Discussion Points: * Implementing a centralized system would be impractical given the process is informal and doesn’t require further policy language. * The WG chose for traceability and simplicity, especially given the nature of TEAC cases. * The idea of a centralized system was discussed previously and dismissed for various reasons. Group Decision: Retain original text of recommendation. Recommendation 33: TDRP and Registrant Access Comments Received: WG made a request to GNSO Council for an Issue Report to explore suitable mechanisms to explore pros and cons of a TDRP. Comments were supportive of exploring this potential mechanism. One commenter suggested that an Issue Report is not needed but that this group could expand the TDRP to registrant filer. The other comments suggested to delete the whole recommendation as they oppose any judicial procedures for handling transfer disputes. Discussion Points: * Expanding TDRP to registrants would not solve all of the issues mentioned, particularly with respect to compromised accounts. * The WG is not recommending a new dispute mechanism but recommending the GNSO Council explore this topic given its complexity. * Registrants can be more involved and file a complaint. * The issue is of paramount importance to registrants and whatever is decided upon this recommendation, it should not be in conflict, and should not stop any informal processes that the registrar has between themselves when there is a dispute. Group Decision: No agreement to include additional language to recommendation. Informational text should be moved into footnote. Let GNSO Council explore the matter. Recommendation 34: Registry Fees for Portfolio Transfers Comments Received: Clarify the distinction between voluntary and involuntary transfers. Suggest splitting clauses to improve clarity. The second comment that supported the change is in relation to 34.2. 34.2 talks about how the registry may choose to waive the fee associated with the full portfolio transfers. Discussion Points: * Agree to renaming the recommendation to remove references to voluntary/involuntary to reduce ambiguity. * ICANN provided additional context on its comment, and specifically suggested an alternative fee model where registries with fewer than 50,000 domains cannot charge fees, while registries with more domains share the $50,000 cap. Group Decision: Retitle the recommendation to remove "voluntary/involuntary." Split clauses for clarity. Further discussion required on Michael Song’s proposed fee model. Recommendation 35: $50,000 Transfer Fee Ceiling Comments Received: Concerns about the $50,000 ceiling being arbitrary and costly. Requests to include mandatory timeframes for transfers to protect registrants. Discussion Points: * This question was deliberated significantly, and the WG came to the conclusion that the $50,000 ceiling is a fair and predictable cap for transfer fees. Members agreed that imposing strict timelines is impractical due to the varying complexity of transfers. Group Decision: No changes to recommendation text. Recommendation 40: Registrar Notification for BTAPPA Comments Received: Comments suggested incorporating footnotes directly into the recommendation text for clarity – in case text is meant to be authoritative. Discussion Points: Group members supported incorporating footnotes directly into the recommendation. Group Decision: Include footnotes in the recommendation text. Recommendation 41: Expansion of BTAPPA to Registrar Agents Comments Received: One comment included support of expanding the transfer policy to include BTAPPA. Commenter recommended that the WG make clear that the qualifying circumstances required for BTAPPA should remain required in the transfer policy. Other comments asked for clarification of term “reseller”. Discussion Points: * The WG is going to maintain the fact that the registry may deny BTAPPA requests – meaning BTAPPA will not always get executed. * Consider removing the word an agent of the registrar. Recommendation 42: Required Registrar Notifications of BTAPPA Comments Received: Comments proposed adding a clause to ensure notifications are documented and accessible for compliance. Group Decision: Agreement to add proposed language to new clause in recommendation, “regardless of the means used to notify registrants, Registrars MUST document, retain, and make notifications available to ICANN org to facilitate the investigation of a BTAPPA complaint.” Recommendation 46: Comments Received: One comment is about concerns regarding the potential costs associated with this expansion. Other comment asked instead of leaving it open on how the notice of fees is transmitted to registrars, could there be a standard way to provide this. Discussion points: * It’s not necessary to include means of communication in the policy text for this. * The group discussed multiple ways that registries could provide this, and the WG decided to to make it flexible and and leave it that way. 1. Begin Discussion of Additional Questions posed in Public Comment Forum (Q1 – Q3) using Public Comment Review Tool<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1lyX27uEC…> * The group reviewed outstanding tasks, focusing on recommendations not previously considered, report format updates, and general comments. * Feedback on IDN variant transfers concluded that no changes were necessary, while concerns about earlier inputs being overlooked were addressed by improving documentation transparency. 4. AOB Feodora Hamza Policy Development Support Manager (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +32 496 30 24 15 Email: feodora.hamza(a)icann.org<mailto:feodora.hamza@icann.org> Website: www.icann.org<http://www.icann.org>

1 0

Post Call | Transfer Policy Review PDP WG | Tuesday, 10 December 2024
by Julie Bisland 10 Dec '24

10 Dec '24

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 10 December 2024 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/5AEfFw> (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 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://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/gnso-tpr…> and the main wiki page<https://community.icann.org/x/P4aUCQ>. Thank you. With kind regards, Julie

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 17 December 2024
by Julie Bisland 10 Dec '24

10 Dec '24

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 17 December 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: 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://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> * Visit the Wiki Agenda meeting page: https://community.icann.org/x/5gEfFw * Time conversion link: https://tinyurl.com/8ux48c3t 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