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 14 May 2024 at 16:00 UTC. Kind regards, Christian, Caitlin, Berry, Julie and Feodora 2024-04-30 Transfer Policy Review PDP WG Call<https://community.icann.org/display/TPRPDP/2024-04-30+Transfer+Policy+Review...> Main discussion and Action Items AI: WG group to complete rationale document by 13th of May 2024. Input is essential for initial report. 1. Welcome and Chair Updates * No meeting on the 7th of May 2. Updates to Group 1(a) Rec 17 * Review updated text in Rec 17 Ideas [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1z3-ZScMQBiAif...> document * The word “exception” has been removed in Rec17 as proposed by RrSG * The language that suggested “case by case basis” has been change to avoid ambiguity: * c) - the registrar must ensure the removal of the restriction by the registered name holder is authorized via secure mechanism – has been removed as it is covered by A) and B). * Language change for d) (new c) the registrar must manually (manually has been removed) confirm that the specific request includes a reasonable basis (was changed from legitimate rationale). I) well informed, documented, clearly intentional agreement of consent to opt out by registrant, II) mutual agreement between prior and current registrar of a transfer back to the prior registrar III) legitimate circumstances surrounding escrow intermediary affecting the completion of the aquistion of the involved registered domain name IV) (…), V) Intentional release of the registered domain name that had transferred to the registrar where it becomes evident the domain name use would be in violation of the registrars Acceptable Use Policy, Terms of Serivce, local law or other similar governance. * WG was discussing to remove above language on exceptions into rationale document, however, some suggested this might be helpful as implementation guidance and should be kept in the Rec text. Others pointed out that it should be clear that these exceptions are not exhaustive. * Chair concluded to have the enumeration included in the rationale rarther than the Rec text. * F) includes new languages “regardles of outcome” : The registrar must maintain a record demonstrating the request to remove the restriction (regardless of outcome) for a period of no fewer thant 15 months following the end of the registrars spnsorship of the registration. 3. Discussion of Group 1(a) Rec 16 (10-15 min) * Is an exception procedure fit for purpose? * WG discussed that exception procedure of Rec 17 doesn’t fit for Rec 16 since the two Rec are substantially different from each other. * If so, review updated text in Rec 16 Ideas [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1Mcw7J8KZyA8-0...> document * No update 4. Removal or reduction of post-CORD transfer restriction * Review Proponent Rationale Doc [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1jXzgRXMGhkUb3...> * Chari reminded WG that orginial view of WG was to remove the restirction, the opt out ability and all that goes with it * WG agreed to keep the original removal of lock for public and take it from there. 5. CORD Recommendations + Rationale [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DpDO2BYTl6TA7...> homework AI: WG group to complete rationale document by 13th of May 2024. Input is essential for initial report. 1. AOB * During the CP summist Rrs and Rys will meet for a working lunch to cover 14 recommendations on transfer policy that need technical updates and discussion. 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>