- GNSO-TPR - lists.icann.org

**REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 09 July 2024
by Julie Bisland July 8, 2024

July 8, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 09 July 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/DwBhF * Time conversion link: https://tinyurl.com/3xd6vdst [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3xd6vdst__;!!PtGJab4!9vfBdKw…> 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-07-02 Transfer Policy Review PDP WG Call
by Feodora Hamza July 3, 2024

July 3, 2024

Dear TPR WG members, Please find below the brief notes and action items from yesterday’s meeting. The next meeting will take place on Tuesday 9 July 2024 at 16:00 UTC. Kind regards, Feodora on behalf of the TPR WG Support Team 2024-07-02 Transfer Policy Review PDP WG Call<https://community.icann.org/display/TPRPDP/2024-07-02+Transfer+Policy+Revie…> AI: The the working group did request a word version of the report and ICANN Org provided it, but notes that beginning at annex 6, the line numbers differ slightly. So when WG members reference line numbers in the Google Doc, ICANN Org asks to confirm the line numbers in the PDF document that was sent. 1. Group 1(a) sections + WG homework AI: Homework 1 Google Doc: Group 1(a) - due 9 July: https://docs.google.com/document/d/1cFGxapltR3x9p49rPFV37RoNT6cBlwu8DPzndfZ… 1. Welcome and Chair Updates * WG is currently in review phase of initial report. * Aim is to be done by August. 1. Overview of Initial Report document * ICANN Org presented the updated initial report with a table of content and all recommendations included. * ICANN Org explained and showed the hyperlink solution they have implemented to allow readers to jump between Rec and Charter Question/Deliberations. * ICANN Org explained to WG that when you get into the summary of deliberations, the WG notice there might be some yellow highlighting. The yellow highlights represent changes that the group agreed to coming out of the public comment, review. That denotes changes from the 1st initial report * There are 3 types of highlighting in the report. There is also light blue highlighting. That's what ICANN Org used to denote any changes as a result of the most recent review of the recommendations and impact analysis. * The bright pink highlight is just an internal note that ICANN Org needs to check the reference. * There are line numbers for this report. It's very helpful to have line numbers, and for the group to note whatever line number they have a particular issue with. So when it comes to updating the master copy of the initial report, it makes it a lot easier. AI: The the working group did request a word version of the report and ICANN Org provided it, but notes that beginning at annex 6, the line numbers differ slightly. So when WG members reference line numbers in the Google Doc, ICANN Org asks to confirm the line numbers in the PDF document that was sent. 1. Group 1(a) sections + WG homework AI: Homework 1 Google Doc: Group 1(a) - due 9 July: https://docs.google.com/document/d/1cFGxapltR3x9p49rPFV37RoNT6cBlwu8DPzndfZ… 1. 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

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 09 July 2024
by Julie Bisland July 2, 2024

July 2, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 09 July 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/DwBhF * Time conversion link: https://tinyurl.com/3xd6vdst 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, 02 July 2024
by Julie Bisland July 2, 2024

July 2, 2024

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 02 July 2024 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/DQBhF> (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 [lists.icann.org]<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, 02 July 2024
by Julie Bisland July 2, 2024

July 2, 2024

**15-MINUTE REMINDER** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 02 July 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/DQBhF * Time conversion link: https://tinyurl.com/35mczfs2 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/35mczfs2__;!!PtGJab4!9L47fZl…> 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, 02 July 2024
by Julie Bisland July 1, 2024

July 1, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 02 July 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/DQBhF * Time conversion link: https://tinyurl.com/35mczfs2 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/35mczfs2__;!!PtGJab4!9L47fZl…> 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

Draft Initial Report & Proposed Agenda - TPR Working Group Meeting #134 - 02 July 2024
by Christian Wheeler June 28, 2024

June 28, 2024

Dear TPR WG members, Following Tuesday’s TPR WG call and feedback, support staff have prepared the attached draft Initial Report for your review. In addition to the updated format of the Initial Report, you will notice some highlighted text throughout: * Yellow highlight represents changes as a result of public comment (for Group 1(a)) * Blue highlight represents changes from the first round of edits we went through recently and staff-proposed updates * Pink highlight represents references to cross-check (changed Rec numbers or Annexes) We will provide an overview of the draft Initial Report during our next WG call (02 July), however please feel free to dive into the document now. For anyone interested in getting a head-start on the WG’s first homework assignment (due July 09), please click here<https://docs.google.com/document/d/1cFGxapltR3x9p49rPFV37RoNT6cBlwu8DPzndfZ…>. Please also find below the Proposed Agenda for our next call, taking place on Tuesday, 02 July 2024 at 16:00 UTC. Thank you and we look forward to seeing you virtually. If you have any questions regarding the draft Initial Report, please do let us know. Kind regards, Christian on behalf of the TPR WG Support Team ---------- Transfer Policy Review - Meeting #134 Proposed Agenda 02 July 2024 Proposed Agenda: 1. Welcome and Chair Updates 2. Overview of Initial Report document 3. Group 1(a) sections + WG homework 4. AOB

2 2

Re: [SSAC] Google Domains sale to Squarespace
by Steve Crocker June 27, 2024

June 27, 2024

Joe, The comment was passed along to me in a private conversation. The source is reputable but not directly involved in the transaction. It's best treated as a rumor, to be replaced with definitive information. I debated about passing this along before verifying it carefully because (a) several of you are in a much better position than I am to track this down, and (b) I trusted the source had a strong basis for their comment. Steve On Thu, Jun 27, 2024 at 10:34 AM Joe Abley <jabley(a)strandkip.nl> wrote: > Hi Steve, > > On 27 Jun 2024, at 16:09, Steve Crocker <steve(a)shinkuro.com> wrote: > > At the beginning of this TPR WG I raised the issue of preservation of > DNSSEC status when a domain registration is transferred. There wasn't much > interest, and this issue was generally treated as out of scope for this WG. > > Google Domains' sale of its registrations to Squarespace apparently > resulted in *all* of the registrations becoming unsigned. The numbers > are big enough to have resulted in a *drop* in the overall count of > signed domain names, and hence a topic of conversation. > > > Removal of DS RRDATA at the registry by a registrar uncoupled from a > corresponding request from a registrar sounds like a RAA compliance issue. > > However, the text and link that you cited states that delegations won't > be affected, which presumably implies that DS RRDATA would remain intact; > the delegation is, after all, the union of both the NS and the DS RRSet > above the zone cut. Is the information from Google incorrect? Do you you > have a reference for "all of the registrations becoming unsigned"? > > > Joe > -- Sent by a Verified [image: Sent by a Verified sender] <https://wallet.unumid.co/authenticate?referralCode=tcp16fM4W47y> sender

1 0

2024-06-25 Transfer Policy Review PDP WG Call
by Feodora Hamza June 27, 2024

June 27, 2024

Dear TPR WG members, Please find below the brief notes and action items from yesterday’s meeting. The next meeting will take place on Tuesday 2 July 2024 at 16:00 UTC. Kind regards, Feodora on behalf of the TPR WG Support Team 2024-06-25 Transfer Policy Review PDP WG Call<https://community.icann.org/display/TPRPDP/2024-06-25+Transfer+Policy+Revie…> AI: WG to take a look at mock up report and report back to ICANN Org in case they disagree with new format of initial report. AI: ICANN Org to remove word “partial” from Rec. 37. 1. Welcome and Chair Updates * The plan is is to spend the next month finalizing the full initial report for public comment. * The aim is to go through report by section. * During July there will be a lot of “homework” for the group to due the finalization of the initial report. 2. Review of draft updates following ICANN80 * ICANN Org presented the slides of the ICANN80 session<https://docs.google.com/presentation/d/1uFh08XvAW-Y5aEzFBwOsGYxuk6XWoATuGPa…> to show some of the updates that were either proposed from working group members or some suggestions from support staff to address the concerns that were expressed during ICANN80, and see if the working group is amenable to those changes, or if further changes are needed on these specific recommendations. * In Rec 5.3. the 5th bullet had some worrisome text for the registrar stakeholder group, particularly the bit about how to initiate a reversal. Some working group members noted that a transfer may be invalid, but it might not be possible to reverse it for a number of reasons, so that text might be misleading. * The highlighted text highlighted in light blue is the text the WG went over during ICANN 80 and was proposed by Sarah. It was also sent to the working group in writing, and there were no objections to it. * The language now details how the Rnh can contact the losing or prior registrar for support if they believe the transfer was invalid, and any deadlines or policies which may be relevant. * The notification to transfer completion is sent by the the losing registrar or the prior registered. So it's the losing registrar that'll be sending this notice out. * In Rec 22 registrars noted an issue with one of the reasons that registers must deny a transfer. The group has an exception procedure in place, for when the 30 day restriction would not apply, and it's limited circumstances. ICANN Org added some language in the rationale: it says registers must restrict the registered name holder from transferring a domain name within 30 days after the completion of an interregister transfer, unless the conditions described in recommendation 19.1 through 19.4 are met. * During ICANN80 agreed that for Rec 19 the language of 19.1 should be moved up. The actual text of the recommendation did not change just the formatting. * In Rec 19 the word necessary is mentioned for the 30 day lock. There was some discomfort with the word necessary. So in in bracketed tech support staff suggested the word needed. The WG group porposed appropriate. * In Rec 23 the WG proposed to eliminate the 60 day inter register transfer lock. The proposed update is to remove this restriction with a note that the working group recommends removal of that transfer lock. * Recommendation 25 defines what a change of registrant data is. There was a note about 25.3, which clarifies that a change of registrant data does not apply to the addition or removal of a privacy proxy service provider and the concern was that 25.1 should somehow point back to this to avoid any sort of confusion. * So the definition of change of registrant data is the same. But it's subject to the language in 25.3, which clarifies a change to a name or certain contact. Details that are result from a change of a privacy, proxy, provider, or addition or removal would be a material change. * The impact rating for Rec 4 was discussed during iCANN80. So rec 4 will involve a new notification that registrars send to registered name holders when the TAC is issued. * Rec 5: the concern from registrars for this recommendation is the inconsistent referral to the losing registrar or registrar record. ICANN Org we removed the reference to the register of record and changed it to the losing registrar. * Rec 26: the WG expressed concerns that the change of registrant data policy should be separate from the transfer policy, as they're 2 distinct things. The main oncern was that the working group should make it clear that it's not recommending a new Pdp. The WG is recommending that the recommendations related to change of registrant data be housed within a different policy, and that the current change of registrant be removed entirely from the transfer policy. 3. Proposed updated format for Initial Report * Aim of this item is to provide an overview of the mock up of what the new initial report will look like.<https://docs.google.com/document/d/1R7uGVJyUMupxnIDM4MpHs5t_EJHMRKdZ7DHnBjA…> * The final document will probably still look different. * 1st page includes a preamble to explain the new format of report. * The excecutive summary will be replaced with a prologue to set the stage for the reader and introduce the format of the report to them. * The initial report will also include the policy impact feature. * The main feature of the report will be to allow readers to bounce back from Rec text and charter questions via bookmark links. * The report will include an archive of the old numbering system and it's been realigned to complement the swim lane diagram. * The Annexes will have the charter questions and the summary deliberations down at the bottom. AI: WG to take a look at mock up report and report back to ICANN Org in case they disagree with new format of initial report. 1. Continued Presentation of High Impact Recommendations (beginning with Rec. 36) * Rec. 36 was restriction of fee adjustments. The working group recommends that if full portfolio transfer involves multiple registry operators, and one or more affected registry operators chooses to waive its portion of the collective fee. The remaining registry operators must not adjust their fees to a higher percentage due to the other registry operators waiver. * WG member pointed out that but not all full portfolio transfers involve fees and some rewording could be beneficial. * RySG suggested that the word “partial” should be removed from Rec 37. * Rec 37 is marked high impact because of the coordination effect of this. * Rec 38 is high impact because it's the the whole moving part of coordinating and and identifying the correct numbers to the correct people here. * Recommendation 40 is inclusion of bulk transfer after partial portfolio acquisition. AI: ICANN Org to remove word “partial” from Rec. 37. 1. AOB * Chair reminded WG we've got 5 weeks 5 meetings scheduled to complete our review of the initial report and our goal is to finish by the end of July. 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>

3 2

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 02 July 2024
by Julie Bisland June 25, 2024

June 25, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 02 July 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/DQBhF * Time conversion link: https://tinyurl.com/35mczfs2 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