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+Review...> 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-YRCpCP...> * 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/1DpDO2BYTl6TA7...> * 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@icann.org<mailto:feodora.hamza@icann.org> Website: www.icann.org<http://www.icann.org>