Dear TPR WG members, Please find below the brief notes and action items from this week’s meeting. The next meeting will take place on Tuesday, 3 December 2024 at 16:00 UTC. Kind regards, Feodora on behalf of the TPR WG Support Team 2024-11-26 Transfer Policy Review PDP WG Call<https://community.icann.org/display/TPRPDP/2024-11-26+Transfer+Policy+Review...> Documents: 1. Link to Public Comment Review Tool (PCRT):https://docs.google.com/spreadsheets/d/1lyX27uECA5bNKRw-UOIH2bAaTRvec1YkX1EK... [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1lyX27uECA...> 2. Link to Rec Drafting Guide: https://docs.google.com/document/d/1YODFe-aZOi1AQ3c8f2-y8MXtcUU4PjzsByFzk-dp... [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1YODFe-aZOi1AQ...> Action Items: 1. ICANN Org to refine language for Rec. 9, Rec. 17, and Rec. 18 based on discussions. 2. WG Members to consult teams on Rec. 17 feasibility. Reminder: Assignment 4 - Recs #29-33 (Group 2 TEAC + TDRP) 11/04/2024 Assignment 5 – Rec #34 – 47 (Group 2 ICANN-approved transfers + BTAPPA) 11/25/2024 1. Welcome and Chair Updates * Owen S. updated his SOI as he is the new chair of the registrar stakeholder group now. 2. Continue Discussion of Recs 25-28 (Change of Registrant Data) using Public Comment Review Tool<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1lyX27uECA...> * Rec. 28.1 – Change of Registrant Data * Reviewed concerns about security risks when opting out of notifications for registrant data changes. * Proposal to reset the opt-out option during specific events (e.g., domain registration, transfers). * Members pointed against overcomplicating policy and emphasized limited use cases for opt-out. * Members noted language referring to “change of registrant” should be rather “change of registrant data.” * Group agreed not to include the proposed language. Cited Rec. 28.3 for handling security measures. * Rec. 28.4 – Two-Factor Authentication (2FA) for Opt-Out * Comment to add mandatory 2FA for opting out of notifications. * Proposal rejected. Emphasis on security measures already outlined in Rec. 28.3. 1. Review Draft Revisions to Recs 3, 12-24, 25-28 using Public Comment Review Tool<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1lyX27uECA...> * Rec. 5 – TAC Definition * Update: TAC definition clarifying that the TAC is required to be presented for a domain name to be transferred from one registrar to another registrar, and when presented, authorizes an eligible transfer. * Outcome: Updated language approved without bracketed text. * Rec. 9 – Resetting TAC * Update: Allow registrars to reset TAC in emergencies (e.g., security breaches). * New Suggestion: Add provision for registries to reset TAC. * Outcome: Agreement to draft new language for registry actions under similar circumstances as 9.4. * Rec. 17 – Transfer Confirmation Notifications * Update: Mechanisms for immediate transfer approval within notifications. * Discussion: Members highlighted potential misuse of such mechanisms in hijackings. Other proposed for clearer implementation guidance. * Pending finalization. Members to discuss feasibility with their teams. * Rec. 18 – Reasonable Basis for Lifting Transfer Locks * Issue: Original “reasonable basis” language considered vague. * Proposal: Add specific examples (e.g., escrow intermediary, documented acquisition). * Discussion: Members recommended broader, open-ended language to accommodate varied scenarios. * Outcome: Agreement to refine language based on combined suggestions. * Rec. 19 – Time Zone for Notifications * Proposal: Use UTC for transfer completion notifications. * Debate: Proponents: UTC offers consistency across global audiences. Opponents: Registrants may find UTC confusing; local time zones better suited for usability. * Outcome: Agreement to mandate inclusion of time zone but leave format flexible. 1. Begin Discussion of Recs 29-33 using Public Comment Review Tool<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1lyX27uECA...> 2. 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@icann.org<mailto:feodora.hamza@icann.org> Website: www.icann.org<http://www.icann.org>