May 2023 - GNSO-TPR - lists.icann.org

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 06 June 2023
by Julie Bisland May 30, 2023

May 30, 2023

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 06 June 2023 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/-4LKDQ * Time conversion link: https://tinyurl.com/5n6u2c4t 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

Post Call | Transfer Policy Review PDP WG | Tuesday, 30 May 2023
by Julie Bisland May 30, 2023

May 30, 2023

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

Notes and action items: TPR WG Meeting #93 - 30 May at 1600 UTC
by Julie Hedlund May 30, 2023

May 30, 2023

Dear TPR WG members, Please find below the brief notes and action items from today’s meeting. The next meeting will be on Tuesday, 06 June at 1600 UTC. Best regards, Emily, Julie, Berry, and Caitlin ACTION ITEMS/HOMEWORK: ACTION ITEMS re: Charter question g3 and additional mechanisms needed to supplement the TDRP: 1. WG members to suggest additional use cases. 2. Staff to suggest in responding to the charter question the WG could a) formulate a question for feedback from the community and b) could recommend that another group could look at a registrant-initiated transfer dispute mechanism. ACTION ITEM: WG members to review the redlined Transfer Dispute Resolution Policy with Rec. 27 updates at: https://docs.google.com/document/d/12ncsCc_sYiBs2cRZVOPCrBes92aV0p-6S-7hNBk… and note anything that might be missing or require clarification. NOTE: The document is set for editing – please use suggestion mode so that changes are highlighted. Notes: Transfer Policy Review - Meeting #93 Proposed Agenda 30 May 2023 1. Welcome and Chair Updates * Work Plan: Reminder – on meeting #93 and on track to get through the remaining TDRP charter questions – good to get community input during the ICANN77 session. Following that clean up anything on TEAC/TDRP, then go into ICANN-approved transfers. 2. Recap Outcomes - Last Week’s Call g1) Is there enough information available to determine if the TDRP is an effective mechanism for resolving disputes between registrars in cases of alleged violations of the IRTP? If not, what additional information is needed to make this determination? Summary: No new recommendations. Respond to charter question by: * Summarizing the limited data reviewed by the WG (published TDRP cases) and note why it is limited (many disputes occur outside of the TDRP) * Summarizing how some limits of TDRP do not necessarily indicate a problem with the dispute mechanism itself, but the limited scope of the policy * Note that the WG believes the TDRP is effective for the limited scope of issues it is designed to address Discussion: * At-Large has indicated support for the registrants to have a way into the TDRP in cases where the process isn’t followed. * The tough part is that with the TDRP there has to be a clear policy violation – although most transfer dispute issues are not policy related. This WG is considering whether to make a recommendation to do something outside of this group. See charter question g3. g2) The ADNDRC reported to the IRTP Part D Working Group that in some of the cases it processed, appellees and appellants failed to provide sufficient information to support arbitration. Is this an issue that needs to be examined further in the context of the policy? Are the existing informational materials about the TDRP sufficient to ensure that registrars understand the process and the requirements for filing a dispute, including the information they need to give to the dispute resolution provider? Summary: No new recommendations. Respond to charter question by: * Summarizing the data reviewed by the WG ((i) the text of the TDRP relating to the documentary information required to be provided by filing and responding parties, (iii) the specific cases published on the TDRP providers’ websites, (iii) the existing information ICANN org provides on its web pages related to transfer disputes and transfer-related issues.)) * Summarizing how the WG group concluded that the required information to be filed by complainants and respondents is sufficiently clear and no conspicuous gaps exist. It is ultimately on the parties to provide evidence to support their case. The WG did note, however, that future updates to documentary evidence as a result of Rec. 27 must be drafted in a way that is understandable to parties, providers, and panelists. * Note that this may need to be reviewed in the future as more cases are filed to see if any gaps exist. 3. Charter Question g3 (draft scenarios) -- Use Cases from IRTP D Final Report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/filef…>, please see pp. 41-42 g3) If the TDRP is considered to be insufficient: i. Are additional mechanisms needed to supplement the TDRP? ii. Should the approach to the TDRP itself be reconsidered? If there is evidence to support that there is a problem, is a new dispute resolution process the best solution? * For example, if the working group believes that domain name hijacking is a significant problem that is not being addressed sufficiently, could the need be met by focusing on protections to prevent improper inter-registrant and inter-registrar transfers from occurring? As a reminder: * The IRTP Part D recommended not to develop dispute options for registrants. * The working group must provide a clear rationale if it believes that further work is needed on this issue. Use Cases * Use Cases from IRTP D Final Report, please see pp. 41-42 * Two registrant claimants dispute to be the Registered Name Holder immediately prior to or directly following an inter-registrar transfer (entirely b/w registrants; no compliance role) * Two registrant claimants dispute who is the Registered Name Holder of a domain name without an inter-registrant transfer having taken place. There are a number of reasons for such a situation to occur, including – but not limited to – a contractor registering a domain for a client, two business partners splitting, admin contact leave a company but remains listed in the Whois database. (entirely b/w registrants; no compliance role) * Any other use cases from the WG that need to be considered? Recommendation #9. The WG recommends that staff, in close cooperation with the IRTP Part C implementation review team, ensures that the IRTP Part C inter-registrant transfer recommendations are implemented and monitor whether dispute resolution mechanisms are necessary to cover the Use Cases in Annex C. Once such a policy is implemented, its functioning should be closely monitored, and if necessary, an Issues Report be called for to assess the need for an inter-registrant transfer dispute policy. Discussion: * Noticed in the two use cases – is that there is no Compliance role. This isn’t going against Policy so there’s no Compliance role. If there’s a gap it’s between identifying an issue, recognizing Policy hasn’t been broken, see what is the next step for registrars – gap between registrars agreeing that they don’t agree, and going to court. Is that the right gap? * It is often the case that registrants unfamiliar with Policy will realize their domain is transferred and do anything they can do to get the name back. From the chat: “additionally, transfer disputes often are raised but the issues are things covered by other policy, such as ERRP or EDDP * ie registrant fails to pay to renew, lazy attention to domain generally and later sees domain at different registrar and claims bad transfer because they do not understand the rules” Want to make sure other policy is followed before we create a new policy. * There’s more than just the transfer policy that affects a name. * Don’t want to encourage overuse on simple transfer issues, such as for non-payment. * Think it would be helpful for staff to understand: One thing to open of transfer policy to former registrants; it’s another thing to have ICANN handle compliance for non-transfer policy issues --- need a panel that had experience with property law, potentially very complicated. Does the WG want to recommend a new dispute mechanism to address a gap – what would it be, what would be the gap/issue to address? * Steinar, ALAC: The gaining registrar says I have captured all the information (followed the transfer policy process) but registrant disagrees – only option is to go to court right now. That is the gap. * Any other use cases – Zak? Is there something lighter weight than going to court? Also the jurisdictional issues are daunting. What wording should we provide in our Report for a recommendation? * Registries don’t have much of an interest, but rather than making a registrant-involved process limited to transfers, but could be broader than that --- where registrants have complaints about registrar practices. * That could be well beyond the scope of this group – not sure what group would drive that. * Staff could 1) send a note to the list re: use cases and 2) suggest in responding to the charter question the WG could formulate a question for feedback from the community and could recommend that another group could look at a registrant-initiated transfer dispute mechanism. ACTION ITEMS re: Charter question g3 and additional mechanisms needed to supplement the TDRP: 1. WG members to suggest additional use cases. 2. Staff to suggest in responding to the charter question the WG could a) formulate a question for feedback from the community and b) could recommend that another group could look at a registrant-initiated transfer dispute mechanism. 4. Charter Question g4 -- Note: Please review Sections 3.1.2 and 3.1.4 of the TDRP<https://www.icann.org/resources/pages/tdrp-2016-06-01-en> in advance of the meeting g4) Are requirements for the processing of registration data, as specified in the TDRP, compliant with data protection law? Discussion: * Think if you start with a TDRP and you use as little personal data as possible, would think a panelist would have a reasonable need for personal data. Put this back to the TDRP provider to make sure the data protection law is being followed. * Address/location may be relevant to determine jurisdiction or physical notice of process (if required). 5. Charter Question g5 -- Note: Please review Sections 3.1.2 and 3.1.4 of the TDRP<https://www.icann.org/resources/pages/tdrp-2016-06-01-en> in advance of the meeting g5) Are requirements for the processing of registration data, as specified in the TDRP, appropriate based on principles of privacy by design and data processing minimization? ACTION ITEM: WG members to review the redlined Transfer Dispute Resolution Policy with Rec. 27 updates at: https://docs.google.com/document/d/12ncsCc_sYiBs2cRZVOPCrBes92aV0p-6S-7hNBk… and note anything that might be missing or require clarification. NOTE: The document is set for editing – please use suggestion mode so that changes are highlighted. 6. AOB

1 0

ICANN77 GNSO Policy Briefing Available for Download!
by Julie Bisland May 30, 2023

May 30, 2023

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

**STARTS IN 15 MINUTES** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 30 May 2023
by Julie Bisland May 30, 2023

May 30, 2023

**STARTS IN 15 MINUTES** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 30 May 2023 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/-YLKDQ * Time conversion link: https://tinyurl.com/8rrs9a78 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/8rrs9a78__;!!PtGJab4!7blezbK…> 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 for meeting #93 on Tuesday 30 May 2023 at 16:00 UTC
by Caitlin Tubergen May 29, 2023

May 29, 2023

Dear Working Group members, Please find below the proposed agenda for the next meeting scheduled to take place on Tuesday, 30 May at 16:00 UTC. Kind regards, Emily, Julie, Berry, and Caitlin --------------------------------------------------------- Transfer Policy Review - Meeting #93 Proposed Agenda 30 May 2023 1. Welcome and Chair updates 2. Recap Outcomes - Last Week’s Call 3. Charter Question g3 (draft scenarios) • Use Cases from IRTP D Final Report<https://gnso.icann.org/sites/default/files/filefield_46639/irtp-d-final-25s…>, please see pp. 41-42 * Two registrant claimants dispute to be the Registered Name Holder immediately prior to or directly following an inter-registrar transfer (entirely b/w registrants; no compliance role) * Two registrant claimants dispute who is the Registered Name Holder of a domain name without an inter-registrant transfer having taken place. There are a number of reasons for such a situation to occur, including – but not limited to – a contractor registering a domain for a client, two business partners splitting, admin contact leave a company but remains listed in the Whois database. (entirely b/w registrants; no compliance role) * Any other use cases from the WG that need to be considered? 4. Charter Question g4 • Note: Please review Sections 3.1.2 and 3.1.4 of the TDRP<https://www.icann.org/resources/pages/tdrp-2016-06-01-en> in advance of the meeting 5. Charter Question g5 • Note: Please review Sections 3.1.2 and 3.1.4 of the TDRP<https://www.icann.org/resources/pages/tdrp-2016-06-01-en> in advance of the meeting 6. AOB

2 1

REMINDER | Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 30 May 2023
by Terri Agnew May 26, 2023

May 26, 2023

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 30 May 2023 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/-YLKDQ * Time conversion link: https://tinyurl.com/8rrs9a78 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/8rrs9a78__;!!PtGJab4!7blezbK…> 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

ICANN77 GNSO Sessions - How to Get Organized / Remote Participation Details
by Julie Bisland May 25, 2023

May 25, 2023

Dear all, With ICANN77<https://meetings.icann.org/en/icann77> just around the corner, please take a moment to read the information below for a seamless and successful meeting. REGISTER NOW! DEADLINE TO REGISTER IS 07 June 2023! * Sign into Your ICANN Account or create an account here<https://account.icann.org/login>. * Register by selecting the Meeting Registration tile. * Click on the Registration link. Before creating your schedule, please read this page carefully: https://meetings.icann.org/en/remote-participation. If participating on-site, please read the Health and Safety page<https://meetings.icann.org/en/77healthandsafety>. CREATE YOUR MEETING SCHEDULE * Access the ICANN77 schedule here<https://icann77.sched.com/>. The schedule shows up with blank circular radial buttons to the left of each session. Hover over the radial button and click “ADD TO MY SCHEDULE” or just click to add the checkmark. * Once you’ve selected all sessions, click the My Schedule link in the lower left corner or hover over your profile and select My Schedule. * Click the Phone icon * In the bottom section, “Export Calendar”, click the link next to “My Schedule”. When the .ics is exported, add it to the appropriate calendar. OR, after exporting, drag and drop the .ics file into your calendar. * Please remember, for security purposes, participation links will be posted 24-hours prior to the session start times. There will be no calendar invitations sent, as the meeting schedule allows you to download all sessions of interest to your individual calendars Review the Participation Tools and update Zoom * All sessions will use Zoom rooms. Access details are available 24hrs prior. * Visit the Participation Tools page<https://meetings.icann.org/en/remote-participation> for links to download the latest version of Zoom for access to the ICANN Meeting sessions. * Please see the ICANN Meeting Virtual Participation How-To Guide for more information on how to get the most out of the virtual meeting tools. Links to Bookmark ICANN77 Meeting Schedule<https://icann77.sched.com/> GNSO ICANN77 Wiki Page<https://community.icann.org/x/_oZXDg> GNSO Session agendas<https://community.icann.org/x/nIJXDg> For all GNSO meeting-related queries (RP or others), please email us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

ICANN77 Policy Outlook Report is now available for download!
by Julie Bisland May 24, 2023

May 24, 2023

Dear all, The ICANN77 Policy Outlook Report is now available: https://go.icann.org/outlook77 Thank you! Kind regards, Julie

1 0

June, July and August 2023 calls | Transfer Policy Review PDP WG
by Terri Agnew May 24, 2023

May 24, 2023

**We are sending in advance to get dates on everyone’s calendar. Dear all, The calls for June, July and August 2023 for the Transfer Policy Review PDP WG are listed below. The calls take place on Tuesdays at 16:00 UTC for 90 minutes., please be sure to download them as “recurring” vs. a one-time event to ensure all the dates show up on your calendar. * Tuesday, 27 June 2023 * Tuesday, 11 July 2023 * Tuesday 25 July 2023 * Tuesday, 01 August 2023 – see attached .ics for the August calls * Tuesday, 08 August 2023 * Tuesday, 15 August 2023 * Tuesday, 22 August 2023 * Tuesday, 29 August 2023 Future invitations will be sent out closer to the date of the call. Thank you. With kind regards, Terri

1 0