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, 15 October 2024 at 16:00 UTC.

Kind regards,

Christian on behalf of the TPR WG Support Team

2024-10-08 Transfer Policy Review PDP WG Call

AI: Assignment 1 – Recs #1, 2, 4-11 (Group 1(a) TAC-related recs):  WG members to review via PCRT all comments pertaining to Recs 1, 2, 4-11 by Monday, 14 October.

AI: WG members to review the Proposed Schedule of Review (#3 below) and inform the WG if the schedule is not feasible / there is not sufficient time to review the public comments in their entirety, by Monday, 14 October.

1. Welcome 

• The Chair noted that more than half of the WG’s Initial Report recommendations received substantive comments. WG members must read all comments
received. 
• We are looking for new comments, ideas, and issues the WG has not already discussed.
• If proposed rec changes have been discussed, we can match to our previous discussion and note how we came to that conclusion.
• From here until December the WG will have a lot of homework. To help, staff has pulled together all the comments for the WG to read and easily digest
(PCRT)
• ICANN81 and the holiday season is fast approaching, so the WG will need to be on top of timelines and completing its homework assignments.

2. Overview of Public Comment Review Tool (new format)

• Staff provided an overview of the newly formatted Public Comment Review Tool (PCRT). The general structure is designed to ensure all comments are readable and organized, as WG members are required to review all comments.
• This PCRT contains: instructions, Action Items, WG discussion notes/outcomes, and all comments received from the TPR Initial Report public comment proceeding (i.e. commenters’ responses to each recommendation and the 3 closing Questions), which are provided both raw and organized by Rec.
• This PCRT Google Sheet will be the homebase for WG review of comment submissions. 
• Based on feedback received, we want to ensure everything is traceable and transparent, but given the size of the report and number of recommendations, a Google Sheet will get unwieldy, so we have hyperlinks on the PCRT Rec tabs to a separate Rec Drafting doc where WG members can edit text so that Rec editing and changes are easier to view. 
• Support staff remains open to any feedback on the PCRT / drafting doc structure and can modify them accordingly.
• Regarding outsider access to these documents: only WG members have commenting/suggesting rights, but non-members have viewing rights (PC Review links are found here: https://community.icann.org/display/TPRPDP/Initial+Report+-+Public+Comment+Review) 

3. Proposed Schedule of Review

· Assignment 1 – Recs #1, 2, 4-11 (Group 1(a) TAC-related group)  

o Deadline for Review – Monday, 14 October

· Assignment 2 - Recs #3, 12-23 (Group 1(a) - Restriction + denial of transfers)

o Deadline for Review – Monday, 21 October

· Assignment 3 – Recs #24-28 (Group 1(b) Change of Registrant Data)

o Deadline for review – Monday, 28 October

· Assignment 4 - Recs #29-33 (Group 2 TEAC + TDRP)

o Deadline for review – Monday, 4 November

· Assignment 5 – Rec #34 – 47 (Group 2 ICANN-approved transfers + BTAPPA)

o Deadline for review – Monday, 25 November

• TPR Leadership team and support staff looked at the comments received and put them into these groupings (e.g. Assignment 1: Group 1(a) TAC-related group) to give sufficient time to review all comments.
• WG members are tasked to review each group of recs/comments by Mondays, so the WG can discuss them together on Tuesday’s calls.
• The gap between Assignment 4 (due Nov 4) and Assignment 5 (due 25 Nov) is to account for ICANN81.

4. Walk-through of Example (Rec. #6)

• Support staff provided a walk-through of the TPR Public Comment Review – Final Report Recommendation Drafting Guide document using Rec #6 as an example
  • The red box contains rec language as presented in the Initial Report
  • The yellow box contains proposed draft/highlighted language considering comments received about that recommendation (e.g. for Rec #6: changing “SLA” to “Required Timing” and changing “5 calendar days” to “120 hours”)
• The green box will contain WG’s agreed rec language for the Final Report
• One WG member noted that this process is dependent on groups doing their homework. If WG members do not do their homework, that will be bad when going through comments. Some WG members may not have as much time, if so there is concern for potential imbalance.
• AI: WG members are asked to look at the proposed Schedule of Review and if any groups believe there is insufficient time to review public comments in their entirety, please speak up so we know what is feasible for the whole WG.
  • Homework is to review public comments in preparation for the call, however the WG discussion of those comments may not necessarily conclude during the dedicated meeting.
  • If there is a rec or comments your group is very concerned about, it is incumbent on you to attend the call, or appoint an alternate if you are unable to attend, to ensure your group’s concerns are heard
  • If you believe there is not sufficient time to review all comments, WG members must speak up soon, as TPR WG has committed to deliver a Final Report to the GNSO Council in early 2025
• The Chair noted that while reading time is not that much, thinking about how these comments impact other recs (including those that may not have received comments) will be a longer thought process

     5. AOB

• ICANN81 Session – Saturday, 9 November, 15:00 – 16:00 Local Time
  • We will likely not have heard all comments by this point but there will be some kind of rec review and discussion
  • We will have a fuller picture of the ICANN81 session agenda as we go through comments
  • We hope everyone can make it to the session, and encourage anyone interested in the topic to attend and participate
  • If over the next few weeks, we find there is a topic(s) tripping us up, we may decide to discuss it face-to-face at ICANN81 if needed