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

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

Post Call | Transfer Policy Review PDP WG | Tuesday, 25 June 2024
by Julie Bisland June 25, 2024

June 25, 2024

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

**2-MINUTE REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 25 June 2024
by Julie Bisland June 25, 2024

June 25, 2024

**STARTING IN 2 MINUTES** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 25 June 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/mADHEw * Time conversion link: https://tinyurl.com/skp9kfs3 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/skp9kfs3__;!!PtGJab4!7zCR1Y_…> 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

Transfer Policy Review PDP WG
by ICANN Policy Calendar June 25, 2024

June 25, 2024

Meeting: Transfer Policy Review PDP WG Date/time: Tuesday 25 June at 16:00 UTC for 90 minutes Alternate replacement confirmations – Members who are unable to attend, please complete the google form<https://docs.google.com/forms/d/e/1FAIpQLScXP3-H595xH4EFgaR3ydOr-1o9BLAVGUI…> to communicate who the alternate is replacing you. Join the Zoom Webinar: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 Passcode: @TP/^*4wg# ALL: Before joining the call: * Please send apologies and dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> * 2024 Wiki page: https://community.icann.org/x/S4BFE ONLY for Members & Alternates: * Please join via the above Zoom Webinar link and staff will promote you to Panelist * Alternate assignments will be posted to the Alternate Log-Transfer Policy Review PDP wiki page<https://community.icann.org/x/V4aUCQ>. * Chat: Please select Everyone when posting to the chat in order for everyone to see and to be captured afterwards. * Alternates (not replacing a member): Please rename your line in Zoom by adding THREE Zs “zzz” before your name, and in parentheses, (your affiliation - alternate), after your name. * Alternates (not replacing a member) are not allowed to engage in the chat or use any of the other zoom room functionalities such as raising hands or agreeing/disagreeing. ONLY for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. Observers will not be able to use chat or raise hands. For Audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6

1 0

**15-MINUTE REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 25 June 2024
by Julie Bisland June 25, 2024

June 25, 2024

**15-MINUTE REMINDER** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 25 June 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/mADHEw * Time conversion link: https://tinyurl.com/skp9kfs3 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/skp9kfs3__;!!PtGJab4!7zCR1Y_…> 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, 25 June 2024
by Julie Bisland June 24, 2024

June 24, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 25 June 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/mADHEw * Time conversion link: https://tinyurl.com/skp9kfs3 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/skp9kfs3__;!!PtGJab4!7zCR1Y_…> 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 #134 - Tuesday, 25 June at 16:00 UTC
by Caitlin Tubergen June 21, 2024

June 21, 2024

Dear TPR WG Members, Below, please find the proposed agenda for our upcoming meeting on Tuesday, 25 June at 16:00 UTC. Transfer Policy Review Working Group Meeting #134 Proposed Agenda 25 June 2024 1. Welcome and Chair Updates 2. Review of draft updates following ICANN80 3. Proposed updated format for Initial Report 4. Continued Presentation of High Impact Recommendations (beginning with Rec. 36) 5. AOB Thank you. Best regards, Caitlin on behalf of the TPR WG Support Team

1 0

ICANN80 TPR WG Meeting 11 June 2024
by Feodora Hamza June 21, 2024

June 21, 2024

Dear TPR WG members, Please find below the brief notes and action items from yesterday’s ICANN80 session on TPR. The next meeting will take place on Tuesday 25 June 2024 at 16:00 UTC. Kind regards, Christian, Caitlin, Berry, Julie and Feodora ICANN80 TPR WG Meeting 11 June 2024 Main discussion and Action Items Documents: TPR WG ICANN80 Session Slides<https://docs.google.com/presentation/d/1uFh08XvAW-Y5aEzFBwOsGYxuk6XWoATuGPa…> Transfer Policy Review Working Group Draft Recommendations for Initial Report<https://docs.google.com/document/d/1xUJMqgb096HXIJ6xWNpNC_w5g6TukZxIbcN7_PT…> AI: WG members that could not attend the ICANN80 session are strongly encouraged to listen to the recording of this session. AI: RrSG to provide exact wording to be added to Rec 5.3. Provide language for requested instructions. AI: ICANN Org to reconsider word “necessary” in proposed update. AI: ICANN Org to move the entire text of 19.1 to Rec 19. 19.2 becomes 19.1 AI: ICANN Org to move ahead and cross I.A.3.8.5 off and add rationale why it was removed. AI: WG to move ahead with proposed update as seen in slide no. 13. AI: ICANN Org to move ahead and add additional language to 25.1 (see above) and add wording for 25.3 (see above). AI: WG to move ahead and keep the proposed update language for Rec 5. AI: RrSG to provide specific language for the proposed update for Rec 26. AI: ICANN Org to keep new reordering but old numbers should be referenced in the table for reference. AI: ICANN Org will reach out to WG members individually where Recs need to be made more “digestible” for the initial report. Agenda: 1. Welcome and Chair Updates * There is no meeting on the 18th of June * Aim is to finish the initial report by the end of July 1. Review of outstanding recommendations following review period * Presentation of “cannot live with” recommendations * Rec 5.3 Registrar Stakeholder Group * Proposed Update: Instructions detailing how the RNH can take action if the transfer was invalid (how to initiate a reversal) and any deadlines by which the RNH must take action. 4.2. Instructions detailing how the RNH can take action if the request is invalid (how to invalidate the TAC) * 27.2 Instructions detailing how the registrant can take action if the change was invalid (how to initiate a reversal) AI: RrSG to provide exact wording to be added to Rec 5.3. Provide the above requested instructions. ii. Rec 22 Registrar Stakeholder Group · Proposed Update: Rec 22 A domain name is within 60 30 days (…) · [Rec 19 or 19.1: However, the working group recognizes that there may be situations where early removal of the 30-day restriction described in Recommendation 19 is necessary.] AI: ICANN Org to reconsider word “necessary” in proposed update. AI: ICANN Org to move the entire text of 19.1 to Rec 19. 19.2 becomes 19.1 iii. Rec 23 Registrar Stakeholder Group · Proposed Update: I.A.3.8.5 should be removed as there is no longer a lock associated with the CoR · Rationale: The Working Group is not proposing any revisions at this time. Per the working group charter, Change of Registrant will be addressed in Phase 1(b) of the PDP. The working group will revisit I.A.3.8.5 once it has completed deliberations on Change of Registrant. AI: ICANN Org to move ahead and cross I.A.3.8.5 off and add rationale why it was removed. iv. Rec 24 Registrar Stakeholder Group · Proposed Update: Clarification needed about auto renewal refunds to losing registrar from registry and/or to registrant from losing registrar. · WG members raised concerns that this might be outside the policy scope. AI: WG to move ahead with proposed update as seen in slide no. 13. b. Side comment on Rec 25.3 by Registrar Stakeholder Group * Proposed update: Can ensure clarification where the P/P email address differs from the RNH and the P/P furnished email address, so that we can identify which prevails. As I read this, changing P/P where the email address changes might trigger 25.1, but does 25.3 override that? I could see some Rr interpreting this as yes, some no. * 25.3: A “Change of Registrant Data” does not apply to the addition or removal of Privacy/Proxy Service Provider (P/P) data in RDDS when such P/P services are provided by the Registrar or its Affiliates. * 25.1: Add “Subject to the language in 25.3” AI: ICANN Org to move ahead and add additional language to 25.1 (see above) and add wording for 25.3 (see above). c. CAN LIVE WITH but prefer this change * Rec 5 - RrSG · Proposed update: The policy states “The working group recommends that the Losing Registrar MUST send a “Notification of Transfer Completion” to the RNH without undue delay but no later than 24 hours after the transfer is completed. For the purposes of sending the notification, the Registrar of Record MUST use contact information as it was in the registration data at the time of the transfer request. AI: WG to move ahead and keep the proposed update language. ii. Rec 26 – RrSG · Proposed Update: Clarification that a new PDP is not required for the new Change of Registrant Data Policy AI: RrSG to provide specific language for the proposed update. d. Discussion of Recommendation Reordering * ICANN Org provided rationale and aim of rec reordering. * Rec reordering is inspired by swim lane diagram * Rec 1 to 19 have been reordered. * Reordering is also proposed based on the suggestions to adjust the initial report format and make it more digestible for the public comment phase. * WG agreed that the new order is more logical. * Concerns have been raised that it might be difficult to “connect the dots” in terms of following the historical development of the Recommendations. AI: ICANN Org to keep new reordering but old numbers should be referenced in the table for reference. 3. Presentation of High Impact Recommendations and their policy impact (High impact means that there is a substantive change to the original policy text.) 1. Rec 26: Removal of requirements to obtain confirmation from Prior and New Registrant. Rec 26.4. Removal of post-Change of Registrant Data transfer restriction (AKA 60-day lock). 2. Rec 27 and Rec 28: Read together with Recommendation 28, these two recommendations (Rec. 27 and Rec. 28) have a high impact, in that a mandatory notification is now a notification that registrants may opt out of. 3. Rec 33: The changes, or lack of changes, to the TDRP results in a low impact to the policy; however, the high indiciation denotes the potential future policy work in completing an Initial Report on the requested issues. 4. Rec 35 to Rec 38: The recommendation, in combination with Recommendations 36-38 introduces the idea of a collective fee and various requirements associated with this new calculus. Specifically, rather than a threshold of 50,000 PER TLD, this involves a threshold of 50,000 across all TLDs, which significantly increases the amount of full portfolio transfers where fees are involved. Additionally, these recommendations create new coordination requirements for registrars, registries, and ICANN org. 5. Rec 40: New requirement to some registries who do not currently offer BTAPPA. 6. Rec 41: This recommendation involves a significant expansion of the BTAPPA service. AI: ICANN Org will reach out to WG members individually where Recs need to be made more “digestible” for the initial report. 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>

2 1

Starting in 15 minutes: ICANN80 TPR WG Meeting
by Christian Wheeler June 11, 2024

June 11, 2024

Hello TPR WG members, As a reminder, the ICANN80 Transfer Policy Review PDP Working Group session<https://icann80.sched.com/event/1dr30/gnso-transfer-policy-review-pdp-worki…> begins in 15 minutes (13:30 UTC). Please find the Agenda and Zoom link information below. Additionally, you will find the link to the session slides here<https://docs.google.com/presentation/d/1uFh08XvAW-Y5aEzFBwOsGYxuk6XWoATuGPa…>. These slides pull the comments and related recommendations directly from the current TPR WG Recs for Initial Report google doc<https://docs.google.com/document/d/1xUJMqgb096HXIJ6xWNpNC_w5g6TukZxIbcN7_PT…>. For the full list of WG recommendations, rationale, and impact levels, please refer to the google doc<https://docs.google.com/document/d/1xUJMqgb096HXIJ6xWNpNC_w5g6TukZxIbcN7_PT…>. Agenda: 1. Welcome and Chair Updates 2. Review of outstanding recommendations following review period 3. Presentation of High Impact Recommendations 4. AOB • Zoom Meeting Link: https://icann.zoom.us/j/97910700107?pwd=TkFiRG5qa0U3QjduVHJ5cWxMMUwzUT09 • Zoom Meeting ID: 979 1070 0107 • Zoom Meeting Passcode: !3g#nxQT0= • Zoom International Dial-In Numbers: https://icann.zoom.us/u/aCrDDIkeP • Zoom Phone Passcode: 326 889 6019 Kind regards, Caitlin, Julie, Feodora, Berry, and Christian

1 0

TPR - Group 1A Recommendation Reorder Proposal and Updated Swimlane
by Berry Cobb June 7, 2024

June 7, 2024

Dear TPR WG, Please find attached a proposal from staff to reorder the Group 1A recommendations for the full Initial Report. You’ll recall this being discussed at our last working group call on May 21st. Staff have compiled all of the proposed recommendations into the draft report including the charter questions, WG responses, recommendation text, and rationale. It made the core body of the report around 100 pages (140+ total). To help reduce the length for the core part of the report, staff had the idea to place the charter questions and WG deliberation summaries (required for transparency) into an annex and create forward and backward navigation links within the document should the reader choose to dive deeper to better understand a proposed recommendation. However, what we encountered was the current order of the recommendation text lost its context to its corresponding charter question and as a result the recommendation text seemed illogical. It’s staff view, even with the charter questions and WG responses and its current order of recommendations, it is still very confusing in addition to being lengthy. Our goal is make this report as easy to understand as possible given that most consumers will not be as intimate with the proposed recommendations as the WG. Thus, the idea was to find a more logical order of the recommendations matching the flow we’ve been using alongside the TPR Group 1A swimlane. Within the .DOCX, you will see the new proposed order with redlines of the prior recommendation number along with the new recommendation number. Note, this document is not to be referenced as authoritative recommendation text. It is only for the purpose to illustrate the proposed reordering. The second attachment (PDF) is an updated swimlane that you all should be familiar with. This latest version includes an update to the post transfer restriction exception procedure (formerly rec #17) and updated recommendation labels where a recommendation in the report is directly represented on the swimlane. Disclaimers about the swimlane: 1. The swimlane is only a conceptual representation of a proposed transfer process only acting as a guide to easily understand the proposed Group 1A recommendations. It is NOT a policy requirements document. 2. The swimlane it constructed as a very high-level. It does not account for all variations of possible transfer transactions given the varying business models and business procedures across contracted parties. 3. Where a process step box does not have a recommendation label, it is NOT specific to any proposed recommendation or a policy requirement. These process steps are only used to maintain logical continuity of a transfer transaction from beginning to end. 4. A deficiency of the swimlane model is it does NOT accurately represent time scales. This conceptual model blends system processes that occur in seconds, vs business procedures that can vary from near seconds to several days vs. proposed durations based on the policy recommendations. Finally, this is only a proposal. The ultimate decision to reorder the Group 1A recommendations is for the WG and Chair. If we have time on our 4 June conference call, we can make this an AoB item. Thank you. B Berry Cobb Policy Development – Senior Program Manager Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 424 443 8960 Phone: +1 202 570 7240 Fax: +1 202 789 0104 Twitter: @berrycobb www.icann.org<https://www.icann.org/>

2 1

2024-06-04 Transfer Policy Review PDP WG Call
by Feodora Hamza June 7, 2024

June 7, 2024

Dear TPR WG members, Please find below the brief notes and action items from yesterday’s meeting. The next meeting will take place during ICANN80 on Tuesday, 11 June | 13:30–15:00 (UTC). Kind regards, Christian, Caitlin, Berry, Julie and Feodora 2024-06-04 Transfer Policy Review PDP WG Call<https://community.icann.org/display/TPRPDP/2024-06-04+Transfer+Policy+Revie…> AI: All those parties that have not contributed to the document, please complete any input before the ICANN80 session. AI: WG members agreed to provide wording for that change in Rec 22 by ICANN80. AI: WG members to provide wording for changes in Rec. 24 by ICANN80. AI: WG to go through cannot live document and provide final input by ICANN80. AI: ICANN Org asked WG to go through GNSO project list and review the details. AI: WG to consider the adjusted numerical order of recommendations 1. Welcome and Chair Updates 2. Preparation for ICANN80 * Review any "Cannot Live With" recommendations<https://docs.google.com/document/d/1xUJMqgb096HXIJ6xWNpNC_w5g6TukZxIbcN7_PT…> AI: All those parties that have not contributed to the document, please complete any input before the ICANN80 session. i. BC informed the WG that they can live with all recs as they currently stand. ii. RrSG pointed to rec 5.3 and noted that there's a requirement that these notifications to the domain owner should explain how to take action if the transfer was invalid. RrSG would like to add further guidance here. iii. WG opened the discussion on transfer reversals and the right amount of instruction to provide. iv. Some WG members pointed out that the TEAC requirements are already quite detailed and don’t need further work. v. Discussion moved to Rec 22 and 23, which focus on the reasons why a transfer would be denied. vi. RrSG pointed out to the 60 day lock after transfer, which has exceptions to it in Rec. 20 and 19. Hence, Rec 22 should also mention the exceptions to this. WG asked the exception removes the restriction, so do you need to mention it? AI: WG members agreed to provide wording for that change in Rec 22 by ICANN80. vii. Rec 23 mentions 60 day lock after transfer, but that was removed? viii. Rec24 talks about auto renewal and that a transfer cannot be denied if the fee has not been paid. WG members discussed how the fees would be reimbursed in cases like these? Chair proposed to add more clarity on that. AI: WG members to provide wording for changes in Rec. 24 by ICANN80. ix. Rec 5 – change wording in both parts to “losing registrar” x. Rec 26 – RrSG suggest for this rec to be a standalone policy. However, WG proposed to add wording to make clear that the WG is suggesting that no PDP is needed at the moment. xi. Rec 25 – RrSG suggested to clarify email address change as material change (25.1) to note the exception of 25.3. WG suggested to add clarity here. AI: WG to go through cannot live document and provide final input by ICANN80. * If none/few, discuss presentation of “High Impact” recommendations<https://docs.google.com/document/d/1xUC5hoTNeU_UIbCriwDHyli6MqefylEfXIwRfYv…> i. There about 10 high impact policy change items. ii. There only high impact recs in group 1B and group 2 recommendations. iii. These high impact items will be discussed during ICANN80 if there remaining time. * Speaker volunteers 1. Discuss post-ICANN80 plans * The goal is to have a final draft of the initial report by 25th of July. * There is no WG meeting on the 18th of June. * Due to holiday season in August, ICANN Org highly recommends to be done with the initial report by the end of July taking into account the generally low participation rate during holiday season. AI: ICANN Org asked WG to go through GNSO project list and review the details. * ICANN Org explained that due to the density of the initial report, we might need to break with the standards of these reports in order to provide a more digestable version to the readers and public commentators. * The new component to this proposed structure is that there will be embedded links within the document. * ICANN Org also proposed to adjust the recs numerical order for consitency with the swimlane and coherence in the initial report. AI: WG to consider the adjusted numerical order of recommendations. 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

Post Call | Transfer Policy Review PDP WG | Tuesday, 04 June 2024
by Julie Bisland June 4, 2024

June 4, 2024

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

June & July 2023 | Transfer Policy Review PDP WG
by Terri Agnew June 4, 2024

June 4, 2024

**We are sending in advance to get dates on everyone’s calendar. Dear all, The calls for June & July 2024 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 the .ics as “recurring” vs. a one-time event to ensure all the dates show up on your calendar. * Tuesday, 25 June 2024 * Tuesday, 02 July 2024 * Tuesday, 09 July 2024 * Tuesday, 16 July 2024 * Tuesday, 23 July 2024 * Tuesday, 30 July 2024 Future invitations will be sent out closer to the date of the call. Thank you. Kind regards, Terri Policy Team Supporting the GNSO With kind regards, Devan

1 0

Transfer Policy Review PDP WG
by ICANN Policy Calendar June 4, 2024

June 4, 2024

Meeting: Transfer Policy Review PDP WG Pattern: Weekly on Tuesdays 16:00 UTC for 90 minutes ( 02 July – 30 July 2024) Alternate replacement confirmations – Members who are unable to attend, please complete the google form<https://docs.google.com/forms/d/e/1FAIpQLScXP3-H595xH4EFgaR3ydOr-1o9BLAVGUI…> to communicate who the alternate is replacing you. Join the Zoom Webinar: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 Passcode: @TP/^*4wg# ALL: Before joining the call: * Please send apologies and dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> * 2024 Wiki page: https://community.icann.org/x/S4BFE ONLY for Members & Alternates: * Please join via the above Zoom Webinar link and staff will promote you to Panelist * Alternate assignments will be posted to the Alternate Log-Transfer Policy Review PDP wiki page<https://community.icann.org/x/V4aUCQ>. * Chat: Please select Everyone when posting to the chat in order for everyone to see and to be captured afterwards. * Alternates (not replacing a member): Please rename your line in Zoom by adding THREE Zs “zzz” before your name, and in parentheses, (your affiliation - alternate), after your name. * Alternates (not replacing a member) are not allowed to engage in the chat or use any of the other zoom room functionalities such as raising hands or agreeing/disagreeing. ONLY for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. Observers will not be able to use chat or raise hands. For Audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6

1 0

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

June 4, 2024

NOTE: the TPR PDP WG meets next during ICANN80<https://icann80.sched.com/event/1dr30/gnso-transfer-policy-review-pdp-worki…>, Tuesday 11 June at 15:30 local time (13:30 UTC). There is no call on 18 June. *************************** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 25 June 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/mADHEw * Time conversion link: https://tinyurl.com/skp9kfs3 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

**10-MINUTE REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 04 June 2024
by Julie Bisland June 4, 2024

June 4, 2024

**10-MINUTE REMINDER** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 04 June 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/gQATEw * Time conversion link: https://tinyurl.com/ys6nzm4b [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/ys6nzm4b__;!!PtGJab4!4ljptaS…> 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

GNSO_TPR // 02 June 2024 Project Package
by Berry Cobb June 3, 2024

June 3, 2024

Dear TPR WG, Please find a link below to project package for the GNSO_TPR PDP (02 JUN 2024). This package is a snap-shot in time and developed by the leadership team to report on the working group’s activities and status of the project. It is also distributed to the GNSO Council to keep them informed as managers of the PDP. The package is deposited on the wiki so that we can track access statistics. Link: https://community.icann.org/x/MQDQCQ 1. Page 01 – Summary Dashboard, Project SitRep, and Activity Metrics 2. Page 02 – Meeting metrics, Roster, & Group Attendance 3. Page 03,4 – Project Plan, Gantt chart 4. Page 05 – Workplan Key points: * Aspirations of releasing the Initial Report for public comment July 2024, ahead of our target for August 2024. Please let staff know if you have questions. Thank you. B Berry Cobb Policy Development – Senior Program Manager Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 424 443 8960 Phone: +1 202 570 7240 Fax: +1 202 789 0104 Twitter: @berrycobb www.icann.org<https://www.icann.org/>

1 0

Updated TPR Mail Archive
by Berry Cobb June 3, 2024

June 3, 2024

Dear TPR WG, Recently, ICANN org updated it’s Mailman service to the latest offering. As a result the archive has changed. Please follow this link to the new list: https://lists.icann.org/hyperkitty/list/gnso-tpr@icann.org/ Thank you. B Berry Cobb Policy Development – Senior Program Manager Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 424 443 8960 Phone: +1 202 570 7240 Fax: +1 202 789 0104 Twitter: @berrycobb www.icann.org<https://www.icann.org/>

1 0

**REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 04 June 2024
by Julie Bisland June 3, 2024

June 3, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 04 June 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/gQATEw * Time conversion link: https://tinyurl.com/ys6nzm4b [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/ys6nzm4b__;!!PtGJab4!4ljptaS…> 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

Re: TPR - Working Group Self Assessment Survey | Complete by Wednesday, 21 February 2024 at 23:59 UTC.
by Berry Cobb June 1, 2024

June 1, 2024

Dear Transfer Policy Working Group, Please find a link below to the WG Self-Assessment survey results conducted back in February 2024. There were eight total responses and the results have been shared with the GNSO Council leadership team. While the response rate was low, the results were favorable overall. https://community.icann.org/display/TPRPDP/Working+Group+Self-Assessment This same survey will be deployed at the conclusion of this working group. Should you have any questions, please reach out to staff. Thank you. The Policy Development Support Team Berry Cobb Policy Development – Senior Program Manager Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 424 443 8960 Phone: +1 202 570 7240 Fax: +1 202 789 0104 Twitter: @berrycobb www.icann.org<https://www.icann.org/> From: Ntfy-gnso-tpr <ntfy-gnso-tpr-bounces(a)icann.org> on behalf of Terri Agnew <terri.agnew(a)icann.org> Date: Wednesday, January 31, 2024 at 08:45 To: "ntfy-gnso-tpr(a)icann.org" <ntfy-gnso-tpr(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [NTFY-GNSO-TPR] ACTION NEEDED | TPR - Working Group Self Assessment Survey | Complete by Wednesday, 21 February 2024 at 23:59 UTC. Dear Transfer Policy Review Members and Alternates, On 15 March 2023, the GNSO Council approved <https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/20…> a process and questionnaire for Working Groups to conduct periodic Self-Assessments during their lifecycle. These periodic surveys are intended to supplement Self-Assessments that already occur when a Working Group closes. The goal is to provide the GNSO Council with important information about how its Working Groups are functioning and whether there are any issues that may need to be addressed as the Working Group proceeds. This working group will soon deliver its full Initial Report for public comment, a key milestone in the group’s work. This is an opportune moment for you to reflect on how the group is functioning and whether there are areas that may benefit from improvement. Please read the following instructions carefully: · The survey tool is provided in Survey Monkey and is available at this link <https://urldefense.com/v3/__https:/www.surveymonkey.com/r/MD5MRBH__;!!PtGJa…> : The survey is only being shared with Members and Alternates. Please do not share this link with others. · Background information and instructions are contained within the survey. There is no login requirement, so you will not need user credentials. · This questionnaire is organized into 22 questions divided into five short sections. Simply answer the questions on each page and, when you reach the end, click “Submit.” If you receive a response that “Your response has been recorded”, your feedback was successfully populated. · There is no option to save and continue later. If you would like to browse the questions in advance, they are attached. · The survey should take approximately 15 minutes depending upon the number of comments you choose to provide. · The survey will be open for three weeks and will close on Wednesday, 21 February 2024 at 23:59 UTC. A member of the GNSO policy support staff will monitor the completion process and be available to provide technical assistance if needed. If you are having difficulty with the survey and need assistance, you can email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. Additional information about how your input will be used: You may remain anonymous when responding to this survey, meaning that you do not need to provide your name. If you choose to provide your name and/or email address, this will only be seen by staff administering this survey. Staff will only use this information to get in touch with you if there are any follow-up questions after the survey has been administered. After this survey is closed, a report will be produced summarizing the results. The report will include: · Aggregated responses to all questions in which respondents select from a menu of choices or from a numerical scale. · Full text of any narrative responses, such as comments or explanations of their numerical scores. The report will be publicly available: · It will be sent to Council leadership, the Working Group leadership team, and will be shared with the full Council, upon request. · It will also be sent to the publicly-archived Working Group mailing list and posted on the Working Group’s public wiki. Based on the survey results, Council leadership, Council and/or the Working Group leadership team will consider whether there are any changes that should be considered to enhance the Team’s operation. Thank you for your willingness to provide feedback about the Working Group and your participation in it. Kind regards, The Policy Development Support Team

1 0