- GNSO-TPR - lists.icann.org

Proposed Agenda - TPR Working Group Meeting #128 - 30 April 2024
by Christian Wheeler April 25, 2024

April 25, 2024

Dear TPR WG members, Please find below the proposed agenda for our next call, taking place on Tuesday, 30 April 2024 at 16:00 UTC. As a reminder, the WG’s current Action Items are provided here: AI: WG to propose updates and legitimate rationale examples in Rec 17 Ideas<https://docs.google.com/document/d/1z3-ZScMQBiAiff57ZbX4AEz1lh9hUvgjc-YRCpC…> document by 29 April. AI: WG to consider whether an exception procedure is fit for purpose for Rec 16 (30-day transfer restriction following initial registration) by 29 April. AI: WG proponents of keeping/reducing post-CORD transfer restriction to provide rationale in Post-CORD transfer restriction: Proponent Rationale Doc<https://docs.google.com/document/d/1jXzgRXMGhkUb3sNDc_hxXek_lTCJhD-3iWIvSoG…> by 29 April. AI: WG to continue providing rationale to the Recs in TPR Group 1(b) Recommendations and Rationale<https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr…> document by 13 May. Thank you and we look forward to seeing you all virtually. Kind regards, Caitlin, Julie, Feodora, Berry, and Christian ---------- Transfer Policy Review - Meeting #128 Proposed Agenda 30 April 2024 Proposed Agenda: 1. Welcome and Chair Updates 2. Updates to Group 1(a) Rec 17 a. Review updated text in Rec 17 Ideas<https://docs.google.com/document/d/1z3-ZScMQBiAiff57ZbX4AEz1lh9hUvgjc-YRCpC…> document 3. Discussion of Group 1(a) Rec 16 (10-15 min) a. Is an exception procedure fit for purpose? b. If so, review updated text in Rec 16 Ideas<https://docs.google.com/document/d/1Mcw7J8KZyA8-0PYZxlOa4SuysAEQ5fFLJ-eKo_9…> document 4. Removal or reduction of post-CORD transfer restriction a. Review Proponent Rationale Doc<https://docs.google.com/document/d/1jXzgRXMGhkUb3sNDc_hxXek_lTCJhD-3iWIvSoG…> 5. CORD Recommendations + Rationale<https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr…> homework 6. AOB

1 0

Action Item for Proponents of post-CORD transfer restriction
by Christian Wheeler April 24, 2024

April 24, 2024

Hello TPR WG Members, Regarding the WG’s third Action Item (see the recap email below), support staff have created this Google Doc<https://docs.google.com/document/d/1jXzgRXMGhkUb3sNDc_hxXek_lTCJhD-3iWIvSoG…> to capture the rationale from all proponents of keeping/reducing the 60-day post-COR(D) transfer restriction. We ask that the BC and IPC representatives, as well as any other WG members who support keeping a post-CORD transfer restriction, please provide their rationale via this document<https://docs.google.com/document/d/1jXzgRXMGhkUb3sNDc_hxXek_lTCJhD-3iWIvSoG…> by end of day Monday, 29 April. These inputs will inform the next discussion planned for Tuesday, 30 April, when the WG will again consider whether to maintain or eliminate this restriction (Group 1b, Rec 2.4) as part of its Initial Report recommendations. Thank you, and if you have any questions or concerns, please let us know. Kind regards, Caitlin, Berry, Julie, Feodora, and Christian From: Feodora Hamza via GNSO-TPR <gnso-tpr(a)icann.org> Reply-To: Feodora Hamza <feodora.hamza(a)icann.org> Date: Wednesday, April 24, 2024 at 8:28 AM To: "gnso-tpr(a)icann.org" <gnso-tpr(a)icann.org> Subject: [GNSO-TPR] 2024-04-23 Transfer Policy Review PDP WG Call - Follow-up 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 30 April 2024 at 16:00 UTC. Kind regards, Christian, Caitlin, Berry, Julie and Feodora 2024-04-23 Transfer Policy Review PDP WG Call<https://community.icann.org/display/TPRPDP/2024-04-23+Transfer+Policy+Revie…> Main discussion and action items AI: WG should propose updates and legitimate rationale examples to Rec 17(b) by 29 April. AI: Chair called WG to think about Rec 16 and for those who want to keep the post-CORD lock to provide rationale by 29 April. AI: For proponents of keeping/reducing the post-CORD lock to provide rationale (looking to Charter questions) by 29 April. AI: Reminder: WG is asked to include rationale to the Recs in the document. 1. Welcome and Chair Updates * Chair reminded the WG that the meeting 7 May is cancelled due to CP Summit. * Chair reminded the WG that not many meetings are left until ICANN80, so the WG should use the remaining meetings to work on the initial report. 2. Discussion of Group 1(a) Rec 17 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1z3-ZScMQBiAi…> * Brainstorm updates to text · NSCG expressed concerns to remove the 30 day lock. · WG members reminded that the lock removal would be only exceptional, that would be well documented. · Org reminded WG that there 2 transfer restrictions that should not be conflated. · WG seems to agree on the 30 day restriction lock, but with the exception of established customer relationship, this is were Rec 17 (b) comes into play. · However, the the current language that the group was looking at some were still very uncomfortable, and wanted stricter guard rails around that to make their particular groups more comfortable with the language so support. · Org has proposed changes of langugage for WG to consider. The changes describe what the exception could look like. · WG wanted to emphasize that the new examples proposed by staff should bee seen as illustrative, as there might me be more examples? · Org Compliance had raised some enforcement issues with current wording of Rec 17. · WG group how this can be operationalized. · WG discussed how to ensure that the change request is valid? Authentication mechanism? AI: WG should propose updates and legitimate rationale examples to Rec 17(b) by 29 April. * Determine applicability to Rec 16 · Org reminded WG they need to clarify any applicability of 17b to Rec 16 · Rec 16 is about initial registration. 17 is about a a post transfer. AI: Chair called WG to think about Rec 16 and for those who want to keep the post-CORD lock to provide rationale by 29 April. AI: For proponents of keeping/reducing the post-CORD lock to provide rationale (looking to Charter questions) by 29 April. * Decide path forward to Public Comment 1. Discussion of post-CORD transfer restriction * .Removal or reduction to 30 days? 2. Rationale Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DpDO2BYTl6TA…> * Not discussed AI: Reminder: WG is asked to include rationale to the Recs in the document. 1. AOB * Not discussed. 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

2024-04-23 Transfer Policy Review PDP WG Call - Follow-up
by Feodora Hamza April 24, 2024

April 24, 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 30 April 2024 at 16:00 UTC. Kind regards, Christian, Caitlin, Berry, Julie and Feodora 2024-04-23 Transfer Policy Review PDP WG Call<https://community.icann.org/display/TPRPDP/2024-04-23+Transfer+Policy+Revie…> Main discussion and action items AI: WG should propose updates and legitimate rationale examples to Rec 17(b) by 29 April. AI: Chair called WG to think about Rec 16 and for those who want to keep the post-CORD lock to provide rationale by 29 April. AI: For proponents of keeping/reducing the post-CORD lock to provide rationale (looking to Charter questions) by 29 April. AI: Reminder: WG is asked to include rationale to the Recs in the document. 1. Welcome and Chair Updates * Chair reminded the WG that the meeting 7 May is cancelled due to CP Summit. * Chair reminded the WG that not many meetings are left until ICANN80, so the WG should use the remaining meetings to work on the initial report. 2. Discussion of Group 1(a) Rec 17<https://docs.google.com/document/d/1z3-ZScMQBiAiff57ZbX4AEz1lh9hUvgjc-YRCpC…> * Brainstorm updates to text * NSCG expressed concerns to remove the 30 day lock. * WG members reminded that the lock removal would be only exceptional, that would be well documented. * Org reminded WG that there 2 transfer restrictions that should not be conflated. * WG seems to agree on the 30 day restriction lock, but with the exception of established customer relationship, this is were Rec 17 (b) comes into play. * However, the the current language that the group was looking at some were still very uncomfortable, and wanted stricter guard rails around that to make their particular groups more comfortable with the language so support. * Org has proposed changes of langugage for WG to consider. The changes describe what the exception could look like. * WG wanted to emphasize that the new examples proposed by staff should bee seen as illustrative, as there might me be more examples? * Org Compliance had raised some enforcement issues with current wording of Rec 17. * WG group how this can be operationalized. * WG discussed how to ensure that the change request is valid? Authentication mechanism? AI: WG should propose updates and legitimate rationale examples to Rec 17(b) by 29 April. * Determine applicability to Rec 16 * Org reminded WG they need to clarify any applicability of 17b to Rec 16 * Rec 16 is about initial registration. 17 is about a a post transfer. AI: Chair called WG to think about Rec 16 and for those who want to keep the post-CORD lock to provide rationale by 29 April. AI: For proponents of keeping/reducing the post-CORD lock to provide rationale (looking to Charter questions) by 29 April. * Decide path forward to Public Comment 1. Discussion of post-CORD transfer restriction * .Removal or reduction to 30 days? 2. Rationale Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DpDO2BYTl6TA…> * Not discussed AI: Reminder: WG is asked to include rationale to the Recs in the document. 1. AOB * Not discussed. 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, 23 April 2024
by Devan Reed April 23, 2024

April 23, 2024

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

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 30 April 2024
by Devan Reed April 23, 2024

April 23, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 30 April 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/dAATEw * Time conversion link: https://tinyurl.com/yrxe2zbk 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, Devan Policy Team Supporting the GNSO

1 0

15 MINUTES REMINDER | Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 23 April 2024
by Devan Reed April 23, 2024

April 23, 2024

15 MINUTES Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 23 April 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/hAATEw * Time conversion link: https://tinyurl.com/4s2y64ps <https://urldefense.com/v3/__https:/tinyurl.com/4s2y64ps__;!!PtGJab4!-Zo9Gom…> 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, Devan Policy Team Supporting the GNSO

1 0

REMINDER | Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 23 April 2024
by Devan Reed April 22, 2024

April 22, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 23 April 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/hAATEw * Time conversion link: https://tinyurl.com/4s2y64ps <https://urldefense.com/v3/__https:/tinyurl.com/4s2y64ps__;!!PtGJab4!-Zo9Gom…> 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, Devan Policy Team Supporting the GNSO

1 0

Group 1(a) Rec 17 - Proposed Update Ideas
by Christian Wheeler April 19, 2024

April 19, 2024

Hello TPR WG members, Earlier this week, we heard the WG seems to be aligning that Group 1(a) Rec 17 needs an update, which would enable Registrars in limited/special circumstances to remove the 30-day transfer restriction following an inter-Registrar transfer. What is not yet agreed are the appropriate guardrails to sufficiently address WG member concerns about security, gaming, clarity, and enforceability. As it stands, the currently proposed text for an updated Rec 17 (“Established Relationship”) does not appear to have broad support from the WG. The current Action Item for all proponents of a Rec 17 exception procedure is to put forward suggested changes to the preliminary recommendation text by EOD Monday—preferably via the mailing list so as to enable WG consideration before our call on Tuesday, 23 April (16 UTC). To help kick-off the WG’s Rec 17 brainstorm, support staff has drafted a Rec 17 Ideas document<https://docs.google.com/document/d/1z3-ZScMQBiAiff57ZbX4AEz1lh9hUvgjc-YRCpC…> which offers some ideas for a proposed update to Rec 17, should the WG wish to consider them. Please continue to think about and propose solutions as we head into our next meeting. Thank you. Kind regards, Caitlin, Julie, Feodora, Berry, and Christian

1 0

Proposed Agenda - TPR Working Group Meeting #127 - 23 April 2024
by Christian Wheeler April 18, 2024

April 18, 2024

Dear TPR WG members, Please find below the proposed agenda for our next call, taking place on Tuesday, 23 April 2024 at 16:00 UTC. Thank you and we look forward to seeing you all virtually. Kind regards, Caitlin, Julie, Feodora, Berry, and Christian ---------- Transfer Policy Review - Meeting #127 Proposed Agenda 23 April 2024 Proposed Agenda: 1. Welcome and Chair Updates 2. Discussion of Group 1(a) Rec 17 a. Brainstorm updates to text b. Determine applicability to Rec 16 c. Decide path forward to Public Comment 3. Discussion of post-CORD transfer restriction a. Removal or reduction to 30 days? 4. Rationale Document<https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr…> 5. AOB

1 0

2024-04-16 Transfer Policy Review PDP WG Call- Follow Up
by Feodora Hamza April 16, 2024

April 16, 2024

Dear TPR WG members, Please find below the brief notes and one main action item from today’s meeting. Action Item: By Monday, 22 April: WG members who recommend an exemption procedure for Rec. 17 to put forward suggested changes to the recommendation text; examples could include additional auditing requirements, detailed definition for "case-by-case basis," additional parameters around definition of established customer relationship, etc. The next meeting will take place on Tuesday 23 April 2024 at 16:00 UTC. Kind regards, Christian, Caitlin, Berry, Julie and Feodora 2024-04-16 Transfer Policy Review PDP WG Call<https://community.icann.org/display/TPRPDP/2024-04-16+Transfer+Policy+Revie…> Action Item: By Monday, 22 April: WG members who recommend an exemption procedure for Rec. 17 to put forward suggested changes to the recommendation text; examples could include additional auditing requirements, detailed definition for "case-by-case basis," additional parameters around definition of established customer relationship, etc. 1. Welcome and Chair Updates * No meeting schedule for 7 May due to CP Summit 2. Discuss textual updates to CORD Recommendations * CORD Recommendations for Initial Report: https://docs.google.com/document/d/1_lZLOmNQJKqAsAqxHTv8W5TQeRIm58YvS4vCPIw… * IPC seems to be generally in line with BC comments to "cannot live with section” of document. * Rec 3 has been slightly restructured and added to ref to Rec 2. Added language to show cohesion. * Reg 3.4. CORD has been replaced with written out “Change of Registration Data”. * Rec 4.4. clarifies retention period of opt-out data for at least 15 months. * The WG seems to agree with the 15 months recommendation. * Rec. 4.6 added language where RRs MAY change their opt-out options at the data field level. 3. Continue discussion of Group 1(a) Rec 17 (Established Relationships) * UPDATED: Group 1(a) Rec 17: Registrars MUST apply a 30-day post-change of registrar restriction by default for all domain names transferred into a Registrar; however, on a case-by-case basis and where an Established Relationship exists, the Registrar MAY remove the post-change of registrar restriction on the domain name in fewerless than thirty (30) days for the purpose of an inter-registrar transfer, provided the Registrar maintains a record of both the restriction removal and the related rationale for a period of no fewer than fifteen (15) months following the end of the Registrar’s sponsorship of the registration.). * Some groups expressed some concerns regarding Rec 17 during the last meeting. * Rec 17 includes now new wording on definition of “established relationship”. * At Large expressed concerns on the purpose of Rec 17. * RrSG question if the 30 day will prevent abuse of domain name registration. Some business models might not be comfortable with the 30 day lock. * WG members stated that the argument of security might not work for this Rec. and the lock might be losened. * Lock is seen as a security mechanism to reduce the speed of fraud. WG members suggested to remove the lock and add dispute resolution. Dispute resolution, as explained by other members is out of scope. At Large suggested to keep all locks as security measure in this case. * The flexibility to remove the lock might add to costumer satisfaction with Rr services. * ICANN Org explained the background of Rec 17 (For more information, listen to 17 Jan 2023 WG call<https://community.icann.org/display/TPRPDP/2023-01-17+Transfer+Policy+Revie…> ) and recalled the reason it is being discussed now is because the WG proposes (Rec 2.4) that a CORD no longer requires a 60-day transfer restriction, and the WG is testing whether there is sufficient security with a mandatory 30 day post-transfer lock (previously agreed rec 17) or with a limited exception. * ICANN Org called for WG to decide how these locks and removals are being determined on in detail. * WG members called for more data to support the lock removal and provide further reasoning. * The group should further clarify the rationale behind Rec 17 and if it can go to public comment. * Chair proposed to include Rec 17 for public comment to hear the thoughts of the wider audience. * Rec 16 text might need change depending on outcome of discussion. * ICANN Org asked WG to please epxand on what "case-by-case basis" means and to add further rationale behind the 30 days lock as well as of what an “established relationship” means. 4. AOB * RySG asked how long does one have to submit a dispute? 15 months? See Rec. 4.4. * ICANN Org proposed to discuss offline on Rec 17 before it goes out for public comment or can it be published as is? * WG Chair proposed to publish Rec 17 as if for public comment but have different options as mentioned by other WG members in the back. * ICANN Org proposed to have a small sub-team on pros and cons of Rec 17. * Rec 17 to be further discussed during the next meeting. 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