- GNSO-TPR - lists.icann.org

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 13 February 2024
by Julie Bisland Feb. 6, 2024

Feb. 6, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 13 February 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…>. To join - 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/swDFE * Time conversion link: https://tinyurl.com/2ekrey4n 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

1 0

Notes and action items: TPR WG on 06 February at 1600 UTC
by Julie Hedlund Feb. 6, 2024

Feb. 6, 2024

Dear TPR WG members, Please find below the brief notes and action items from today’s meeting. The next meeting will be Tuesday, 13 February 2024 at 1600 UTC. Kind regards, Christian, Caitlin, Berry and Julie ACTION ITEMS/HOMEWORK: WG to complete the COR Reduction Rationale document at: https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DpDO2BYTl6TA…> Transfer Policy Review - Meeting #117 Proposed Agenda 06 February 2024 Notes: 1. Welcome and Chair updates * Less than a month from ICANN79 – just four scheduled calls. Get our recommendations in place. * Take self-assessment survey by Feb 21. * COR Reduction Rationale doc still has no input – need to fill that out. See action item above. * Zak, BC: Gave an update to BC – expressed their deep concern to remove all notifications and default locks. If that was a recommendation, would likely be a minority report: * Question – what locks? Answer – Opt out to be accepted on a 60-day lock: BC would like to see a default lock that registrars could opt out, with consistency in application. BC is interested in reducing the lock but against removing it. * That’s why we need the rationale document to be completed, such as the reason to remove the 60-day lock. * Steinar, ALAC: Looks like at ICANN79 will discuss the COR with public participation – will provide info if that is the case. 2. Mandatory Notifications wrap-up – see attached slides, starting at slide #5: Discussion: * Second bullet point, which do we want? Are we saying generic your info was updated? Or confirm specific change? WG needs to decide. * Stay away from the word “contact” – Suggest changing “contact information” to “registrant data”. Need to be clear. * Prefer the message lists field that was updated but not what changed in the field. * Look at the alert you get from a responsible bank as an example and minimize the amount of info provided in case the email was compromised and also avoid being too prescriptive. * Question: Wasn’t there another item re: triggers? Answer: We still need to discuss. * Ask ourselves what security goals we want to achieve if COR is not in the Transfer Policy. * Sounds like the group is okay specifying what fields have changed, but not what in that field changed. Identify known RDDS field but not what. * Question: Change of ownership with registrant data – who will see it (the old/new registrant)? Answer: That’s something that needs to be addressed. It depends, but I don’t think we can say how that would work. Need to get into these things more deeply. Notifications – Opt Out Pros/Cons: See Slide 6 Discussion: * Key point: registrant opt out. * If account is hacked notification goes to fraudulent registrant. If registrant opted out wouldn’t get notifications. * Need to look at what other industries do and why – should be a defensible rationale. It’s not about transfers – it’s about information changing. * Could turn on by default and let registrant opt out. * Uncomfortable with being able to turn off notifications – only the owner and only proactive. * Don’t see the outcry from registrants getting emails. * Could be situations when registrant would want to opt out. * maybe it should be an account setting, but not a registrar default in their terms etc. That seems like a good middle ground. * Agreement on mandatory with/without opt out. * Support for the three minimum fields (name, org, email) as triggers – see #3 below. * If there were a proactive opt out that might be okay if it was an informed decision. * If multiple changes notifications should be able to be combined. * Opt out okay if informed. * If we do have a registrant opt out it should be the same across the board for all registrars. * Note that we are talking about opting out of notifications, not locks. And should be consistently applied. * Agree: Same fields as today; mandatory but registrant can actively choose to opt out. 3. "Change of Registrant Data" discussion -- see attached slides, starting at slide #7: Discussion – slide 8 – Change of Registrant Data: * Need to decide what is that minimum set of triggers. * Prefer to keep the current set of triggers – second row. Ability to combine notifications is really helpful. * Look at what needs to be notified for security purposes. * Can still do verification even if combined. * Support for the three minimum fields (name, org, email) as triggers. Discussion – slide 9 – Material Change: * Need to decide what is that minimum set of trigger. * Include addition of data? That could be a material change if field was blank. * WG supports leaving Material Change as is. Discussion -- slide 10 – Privacy/Proxy/Designated agent * Question: Remove Designated Agent? Answer: WG has decided it won’t be defined in policy. * Registrar wouldn’t know if third-party privacy/proxy; If registrar does know, would a change trigger a notice? If assigned back to the registrant is that a notification? * No matter what: WG is saying, it doesn’t matter if it’s privacy/proxy if any one of those three fields changes it will trigger a notification. Note that the PPSAI process is still being worked out. * One of the important things is that it relates to the registrant data and not the PUBLIC data - so if the real data is redacted (not with P/P service) and is changed then the CORD is triggered. Discussion -- slides 11 & 12 – Prior and New Registrant * These terms are out of date. * Send notification when data changes in those three fields – see above – to prior registrant. * Is the opt out on the person or the domain name? Need to discuss details. * Need to continue discussion at the next meeting. 4. CORD Availability and Placement (time allowing) -- see attached slides, starting at slide #13: * Deferred to next meeting. 5. AOB: None.

1 0

**ON IN 6 MINUTES** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 06 February 2024
by Julie Bisland Feb. 6, 2024

Feb. 6, 2024

**ON IN 6 MINUTES** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 06 February 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…>. To join - 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/sQDFE * Time conversion link: https://tinyurl.com/mpnrptvm [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/mpnrptvm__;!!PtGJab4!-i0w50a…> 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

1 0

**REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 06 February 2024
by Julie Bisland Feb. 5, 2024

Feb. 5, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 06 February 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…>. To join - 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/sQDFE * Time conversion link: https://tinyurl.com/mpnrptvm [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/mpnrptvm__;!!PtGJab4!-i0w50a…> 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

1 0

Proposed Agenda - Meeting #117 Tuesday, 06 February 2024 at 1600 UTC
by Christian Wheeler Feb. 1, 2024

Feb. 1, 2024

Dear TPR WG members, Please find below the proposed agenda for our next call, taking place on Tuesday, 06 February 2024 at 16:00 UTC. As a reminder, the WG’s current Action Item is to provide input for the COR Reduction Rationale Google Doc, found here: https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr… Thank you for sharing your inputs and we look forward to seeing you all on Tuesday. Kind regards, Christian, Caitlin, Berry, and Julie ---------- Transfer Policy Review - Meeting #117 Proposed Agenda 06 February 2024 Proposed Agenda: 1. Welcome and Chair Updates 2. Mandatory Notifications wrap-up 3. "Change of Registrant Data" discussion 4. CORD Availability and Placement (time allowing) 5. AOB

1 0

Post Call | Transfer Policy Review PDP WG | Tuesday, 30 January 2024
by Julie Bisland Jan. 30, 2024

Jan. 30, 2024

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 30 January 2024 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/rwDFE> (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

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 06 February 2024
by Julie Bisland Jan. 30, 2024

Jan. 30, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 06 February 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…>. To join - 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/sQDFE * Time conversion link: https://tinyurl.com/mpnrptvm 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

1 0

Notes and action items: TPR WG on 30 Jan at 1600 UTC
by Julie Hedlund Jan. 30, 2024

Jan. 30, 2024

Dear TPR WG members, Please find below the brief notes and action items from today’s meeting. The next meeting will be Tuesday, 06 February 2024 at 1600 UTC. Kind regards, Christian, Caitlin, Berry and Julie ACTION ITEMS/HOMEWORK: WG to complete the COR Reduction Rationale document at: https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr… Transfer Policy Review - Meeting #116 Proposed Agenda 30 January 2024 Notes: 1. Welcome and Chair updates * Planning for ICANN79: * Only 4 meetings leading up to ICANN79; need to complete COR recommendations. * Two sessions – agendas TBD. * WG Self-Assessment Survey: Link will be sent tomorrow for an interim survey. 2. Transfer Complaint metrics with ICANN Contractual Compliance -- ICANN Compliance (Holida Yanik): Sent attached report in response to WG request. Discussion: * Discrepancies may arise because one case may involve several domain names. Also, cases may span both old and new (NSP) systems. * As we consider this, how to correlated it to registrations – how many complaints involve multiple domain names? Don’t have those numbers, but it is quite often. * Just a picture of what is going on in the wider world – just a small fraction. Good that most cases are closed without going to the registrar, but also reflects a lot of confusion. Suggests that the WG’s plan to go with a simple approach for COR is the right approach. * The numbers are small so need to look at the pain points. * Found it very confusing to go through the report -- such as the difference between unauthorized CORs and CORs denied. It seems like there is a low percentage of complaints relative to registrations. This supports the notion of moving to a notification process. * ICANN Compliance: Not all registrants are aware of ICANN. Page 2 – unauthorized complaints; page 4 – inability to complete the COR (registrants). * From the chat: * These are just the Complaints that made it to ICANN, not the entire universe of Complaints, most of which would have been dealt with by the registrars themselves. * Yes - so in our notice process we've discussed requiring the Rr to provide info about how to address complaints, sounds like that will indeed be useful. 3. COR Polls and Discussion: Elimination, Notifications, and Definitions – See attached slides. * The reason for the poll questions is to help determine a recommendation. Poll 1: At this stage in the group's discussions, are you convinced that the Change of Registrant (COR) policy should be eliminated entirely? 1. YES, there should no longer be any COR policy anywhere – 50% 2. NO, there should remain a reduced COR policy somewhere – 50% Poll 2: At this stage in the group's discussions, are you convinced there should be mandatory notifications sent to the Prior & New Registrant when specific contact fields are updated? 1. YES, notifications should be mandatory – 60% 2. NO, notifications should be optional – 40% Discussion: * There is a close split because there are only two choices – no option to opt out. * Trying to be as clear as possible. * Some agreement to have COR somewhere else – doesn’t include inter-registrar policy addressed elsewhere. * Notifications should exist but dealt with elsewhere, outside of the Transfer Policy. * Elimination completely but address elsewhere? What is the specific proposal? There isn’t one – but there are requirements spread around elsewhere. But don’t think everything is covered, such as mandatory notifications. * Not a strong recommendation that some other group needs to determine where these notifications are addressed; not sure what you would get. * GNSO Council would have to make the decision of where that is addressed. * Question: Is COR a Transfer Policy issue? * If we are eliminating COR, first we are eliminating the 60- or 30-) day lock; looks like a complete gutting of protections. * If we eliminate COR, could we keep the option for the registrar to put on a lock if it determines that a transfer is fraudulent. * Not gutting protections, but policy isn’t doing what it was designed to do (for protecting registrants); also, it’s not a transfer, but a change of ownership. Keep the bare minimum. * Staff: If section 2 of Transfer Policy is removed and MUSTs turned to MAYs for notifications, this would no longer be a policy, but perhaps an advisory. * Maybe Section 2 is changed to an advisory section on notification. * Don’t think removing entirely (no notifications) would be acceptable by the public. Have to keep the notifications. Against putting it back to Council to decide – no idea how long that would take. * 50/50 split is just the starting point – what would it take to get everyone to agree? A two-pronged approach to addressing disputes, including a registrant initiated transfer dispute resolution policy. * Sounds like elimination of Section 2 is not supported by this group. * Agree that we need a policy that allows a registrant to reverse a transfer. * Need to work out the details of a notification system. * If we stick with a reduced COR and registrars have their own policies, do we still need to define “material change”. Could be confusing if registrars all define it differently. * Potential middle path – having the option for the registrant opt out of a mandatory notification? * Still see a big issue. What if the person opting out is doing it for fraudulent reasons? * If we are going to require it we shouldn’t allow an opt out. * Let’s assume if COR changes to notifications those should be mandatory. * Think about what a notification would entail. * Opt out could need to be confirmed/verified as valid. * Not envisioning the notification as an email. Could be something else. * Keep a small modified Section 2 that is mandatory notifications. Still need to address definitions and the details of notifications. * See slides 6 and 7 – notification definitions and triggers. Poll 3: For the purposes of a reduced COR/notification policy, what does the WG need to define? 1. Change of Registrant 2. Change of Control 3. Both 4. Neither Discussion: * Neither can be to leave it as is. * Not sure definitions are irrelevant – just what triggers a notification – change of registrant data. * Don’t need to complete the poll. Support for Change of Registrant data as the trigger for notification. Might still need some clarification of what that would be. ACTION ITEM: WG to complete the COR Reduction Rationale document at: https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr… 4. AOB

1 0

**15-MINUTE REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 30 January 2024
by Julie Bisland Jan. 30, 2024

Jan. 30, 2024

**15-MINUTE REMINDER** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 30 January 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…>. To join - 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/rwDFE * Time conversion link: https://tinyurl.com/4cx3tpnt [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4cx3tpnt__;!!PtGJab4!7A25DqA…> 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

1 0

**REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 30 January 2024
by Julie Bisland Jan. 29, 2024

Jan. 29, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 30 January 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…>. To join - 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/rwDFE * Time conversion link: https://tinyurl.com/4cx3tpnt [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4cx3tpnt__;!!PtGJab4!7A25DqA…> 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

1 0