ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Item #DateDescription of action item or decisionOwnerStatusAny additional notes
2
02-015 Dec 2023For Jennifer B. to work with Brenda to schedule next call for 60 minutes on the 9th of January.ICANN teamCompleted
3
02-025 Dec 2023For the ICANN team to share the Terms of Reference from the first IFR. For the review team to call out the specific areas and questions for discussion so that an agreement can be reached on the next call.ICANN teamCompletedDocument considered adopted by consensus as no further comments were submitted to the ICANN support team.
4
02-035 Dec 2023For the ICANN team to make sure that the URL on the wiki is separate from the first IFR wiki.ICANN teamCompleted
5
02-045 Dec 2023For the ICANN team to work together with Co-Chairs on an agenda for the next meeting and share it in advance.ICANN team, Co-ChairsCompleted
6
02-055 Dec 2023For ICANN team to start working with Co-Chairs on getting the briefings lined up. They will start with a briefing at the next meeting.ICANN team, Co-ChairsCompleted
• CSC - ICANN79 (Wednesday 6 March @ 13:15 AST (UTC – 4)
7
02-065 Dec 2023For the ICANN team to come up with suggested meeting plan for January, February, and early March to share with the team—that way the review team members can check their calendars and send their apologies in advance.ICANN teamCompleted
8
02-075 Dec 2023For the ICANN team to work with the co-chairs to look into the possibility of allowing meeting access to observers.ICANN teamCompletedNoted in Terms of Reference document.
9
02-085 Dec 2023For the ICANN team to go back and see if there was a blog published to announce the first IFR and if so, republish a similar blog for IFR2.ICANN teamCompletedIFR2 blog will be published in advance of ICANN 79. Draft will be shared with the review team ahead of publication.
10
07-016 Mar 2024As follow up from the 6 March CSC briefing: Co-chairs to consider formally asking the CSC liaison if there is anything they would like to bring to the attention of the IFR2.ICANN teamCompletedOpen task in case the CSC brings anything else to the attention of the IFR2 group.
11
07-026 Mar 2024Co-chairs will pre-select sections from the contract to be assigned ahead of the 19 March meeting. Proposed approach for the next steps after that is for IFR2 members to pick parts of the contract to review in-depth and report back to the team.ICANN teamCompletedTeam will kick off the contract review as a group (see item 3 of the 19 March agenda). The review team will continue the contract review on 2 April.
12
08-0119 Mar 2024Team to re-read definitions section (Article 1) of the IANA Naming Function Contract before the next meeting. As additional reference, see the RFC 1591 [rfc-editor.org] and FOI [ccnso.icann.org]documents.IFR2 TeamCompleted
Homework to be completed ahead of the 2 April meeting agenda.
13
08-0219 Mar 2024In addition to flagging anything that needs clarification in the preamble and definitions section, team to put together questions for PTI.IFR2 TeamCompletedTo be completed as part of the 2 April meeting agenda.
14
09-012 Apr 2024ICANN support team to work with PTI to schedule a meeting based on their availability.ICANN TeamCompletedPTI will remain available to hold briefings at any time at the request of the IFR2.
15
09-022 Apr 2024ICANN support team to share the questions that the review team prepared for PTI in a separate email.ICANN TeamCompletedMarilia sent an email addressing the review team's questions, explaining the intent of the definitions section, why definitions were phrased a certain way as well as the placement of definitions in the contract. The email was drafted by ICANN legal.
16
09-032 Apr 2024Co-chairs will work with ICANN support team to prepare for the 30 April meeting where the review team will be split into two groups, reviewing two different parts of the contract in parallel.ICANN Team/Co-ChairsCompleted
17
10-0116 Apr 2024Leadership to discuss and decide on next steps in terms of group assignments for future meetings. Idea of parallel work will be revisited after today’s exercise.ICANN Team/Co-ChairsCompleted
To be discussed as part of agenda item 4 during the meeting today (30 April).
18
10-0216 Apr 2024ICANN support team to share with IFR2 review team Google docs so that the review team can finish Statement of Work (SoW) review for homework. The review team to input comments/questions in the shared Google docs.ICANN TeamCompletedLinks shared with Groups A and B – homework output to be discussed as agenda item 3 during the meeting today (30 April).
19
11-0130 April 2024IFR2 team to put together a list of ongoing questions to ask ICANN legal.IFR2 TeamCompletedSee ‘Questions for Legal’ tab in the IFR2 IANA Naming Function Contract Breakdown workbook. Staff will also share questions with Legal as they come up, as appropriate, to answer questions via email or during regular meetings if possible.
20
11-0230 April 2024IFR2 review team to review Article 4, Sections 4.2 and 4.3 for homework and will add feedback to the spreadsheets linked below.
• Group A workbook: https://docs.google.com/spreadsheets/d/13-bJJ1vdg4NCujHCnRo40T29KnvVIQbwm0u9GaGBbYI/edit#gid=1490640604
• Group B workbook: https://docs.google.com/spreadsheets/d/13-bJJ1vdg4NCujHCnRo40T29KnvVIQbwm0u9GaGBbYI/edit#gid=1856503680
IFR2 TeamCompleted
21
11-0330 April 2024ICANN support staff to share the above homework assignment with the review team in an email.ICANN TeamCompleted
22
11-0430 April 2024ICANN Team/Co-chairs to discuss ICANN80 planning at the next leadership call on 7 May.ICANN Team/Co-ChairsCompleted
23
12-0114 May 2024Complete review of IANA Naming Function Contract Article IV (Sections 4.2 – 4.10) and will add feedback to the spreadsheet linked below.
https://docs.google.com/spreadsheets/d/13-bJJ1vdg4NCujHCnRo40T29KnvVIQbwm0u9GaGBbYI/edit#gid=1621245865 		IFR2 TeamCompleted
24
12-0214 May 2024ICANN support team to share the above homework assignment with the review team in an email.ICANN TeamCompleted
25
12-0314 May 2024ICANN support team to share 'Save the Date' for ICANN80ICANN TeamCompleted
26
12-0414 May 2024ICANN support team to reach out to PTI to get clarification on questions raised during this meeting.ICANN TeamCompleted
27
13-0128 May 2024IFR2 Co-chairs to discuss with ICANN support team how to best maximize in-person meeting in Kigali and face to face time with PTI. ICANN Team/Co-ChairsCompleted
28
14-0111 June 2024ICANN support team to share homework assignment with the review team via email.ICANN Team/Co-ChairsCompleted
29
14-0211 June 2024IFR2 review team to decide on meeting cadence.IFR2 TeamCompletedMeeting cadence to remain at 1 hour every other week. Can be revisited at any time.
30
15-0125 June 2024ICANN support team to share homework assignment with the review team via email.ICANN TeamCompleted
31
16-019 July 2024ICANN support team to share homework assignment with the review team via email.ICANN Support TeamCompleted
32
16-029 July 2024ICANN support team to reach out to PTI/Marilia, CSC and ICANN legal for clarifications on questions that came up during today's meeting.ICANN Support TeamCompleted
33
17-0123 July 2024ICANN support team to share homework assignment with the review team via email.ICANN Support TeamCompleted
34
18-016 August 2024ICANN support team to share homework assignment with the review team via email.ICANN Support TeamCompleted
35
19-0120 August 2024ICANN support team to put together a task list of remaining items that need to be completed before the end of the project.ICANN Support TeamCompleted
Development of the list is complete.

Outstanding: Staff will work with leadership on a prioritization exercise and developing a revised project schedule based on outstanding tasks to be completed.
36
19-0220 August 2024ICANN support team to email homework assignment to the review team. The team should read the Implementation report of IFR1 recommendations.ICANN Support TeamCompletedComplete upon distribution of 3 September agenda.
37
19-0320 August 2024Marilia to provide the IFR2 review team with reports from the last three months of the Customer Satisfaction Survey, the post ticket survey, with a brief description of what it
measures, and the last three months of the response rate satisfaction. Marilia to also
provide the review team with the links to the Annual Survey from previous years.		PTICompletedComplete.

Marilia shared with the team via email on 23 August 2024. This information is ready for team review as a future homework assignment and discussion at a future meeting.
38
20-013 September 2024ICANN support team to schedule a session for ICANN81. ICANN Support TeamCompletedMeeting scheduled for Wednesday, November 13th from 13:15-14:30
39
20-023 September 2024Co-chairs to coordinate formal request to allow Rick and Jonathan present to registry stakeholder groups. Peter to identify presenter from ccTLD group.Co-ChairsCompleted
40
20-033 September 2024PTI/Marilia to check whether the transition plan was reviewed with the involvement of the CSC. Article IX, Section 9.3: Transition (see row 54 in the workbook).PTI/MariliaCompleted
41
20-043 September 2024ICANN support team to email homework assignment to the review team. ICANN Support TeamCompleted
42
21-0117 September 2024ICANN support team to email homework assignment to the review team. ICANN Support TeamCompleted
43
21-0217 September 2024Elizabeth to summarize the review team's learnings and incidental findings from the contract.ICANN Support Team/ElizabethCompleted
44
22-011 October 2024ICANN support team to email homework assignment to the review team. ICANN Support TeamCompleted
45
23-0115 October 2024Leadership to draft document articulating oversight authorities for the IANA function. A conversation on the openness and transparency of this structure will follow.ICANN Co-ChairsOutstanding
46
23-0215 October 2024Leadership to circulate draft recommendations to review team.ICANN Co-ChairsOutstanding
47
24-0129 October 2024ICANN support team to look into the formal relationship between the ICANN and PTI Boards (particularly as it pertains to the Domain Name function and report back to the review team.Review team to decide on whether more transparency and openness needed.ICANN Support TeamCompleted
48
24-0229 October 2024Elizabeth to summarize contract review’s ‘nice to have’ marked items in a table to share with the IFR2 Team.Technical WriterCompleted
49
25-0113 November 2024ICANN support team to conduct a poll on the list regarding future IFR2 meeting times. ICANN Support TeamOutstandingEmail sent on 19 November proposing that the team continues to meet. Leadership will discuss change to meeting time if there are team members who would like to change meeting time.
50
25-0213 November 2024ICANN support team to invite ICANN Legal to next meeting to further clarify their stance on Article 8.ICANN Support TeamCompletedSam Eisner, from ICANN Legal, will join the call on 26 November.
51
25-0313 November 2024IFR1 recommendation follow up: IFR2 review team to discuss the reporting obligations and review frequency.IFR2 TeamCompletedTask postponed for discussion to after the review team has reviewed the IFR1 recommendations.
52
25-0413 November 2024Review team to triage findings and suggestions from the compiled ‘nice to have’ list.IFR2 TeamCompletedDiscussion will continue on 10 December.
53
26-0126 November 2024Sam Eisner to provide IFR2 group more information on the amendment paths/recommendations and the level of detail needed for recommendations.Sam EisnerCompletedSam's guidance was shared via email on 25 February 2025.
54
26-0226 November 2024Peter to draft a description of what the perceived problem the IFR2 review team is facing re: Article 8 and share it with the IFR2 team.Peter KochCompletedPeter shared his thoughts via email on 19 February.
55
26-0326 November 2024Review team to look through the CWG for more information on Article 8 (why power was invoked to the president of the contractor.)IFR2 TeamCompletedJonathan, Rick and Peter are working on this task.
56
27-0110 December 2024IFR2 Leadership team to share homework assignment with the group.IFR2 Leadership TeamCompleted
57
28-0114 January 2025IFR2 Review team to read draft report for homework.IFR2 TeamCompleted
58
29-0128 January 2025Leadership team will work with Elizabeth to align on updated language, before moving on to proposed language for ‘incidental findings’ section.IFR2 Leadership TeamCompletedLeadership team to notify IFR2 team when the changes to the draft report have been made so that the review team could review the document prior to the next meeting.
59
29-0228 January 2025IFR2 Leadership team to share homework assignment with the IFR2 team.IFR2 Leadership TeamCompleted
60
30-0111 February 2025Leadership to revisit IFR1 recommendations and double check that SLAs are not mentioned in the recommendations.IFR2 Leadership TeamCompleted
61
30-0211 February 2025Leadership to share homework assignment with the IFR2 group via email.IFR2 Leadership TeamCompletedHomework will include revisiting the IFR1 recommendations.
62
31-0125 February 2025Elizabeth to publish another version of the draft report, capturing comments and feedback from the 25 February meeting. The updated draft report will be shared with the review team by Friday, 28 February. The review team will be given until Tuesday, 4 March to review the report and submit any final comments to the Leadership team.Technical WriterCompletedCompleted on 1 March.
63
31-0225 February 2025Draft IFR2 report to be posted for public comment.ICANN Support TeamCompletedThe draft report will be posted for public comment after ICANN82.
64
32-0110 March 2025The ICANN support team to publish a summary report once the public comment period has ended.ICANN Support TeamOutstandingThe public comment period ended on 28 April 23:59. The new report publication has been moved from 12 May date to 22 May to 29 May.
65
32-0210 March 2025Final report to be updated with any new feedback from the Public Comment.IFR2 Team/ICANN Support teamOutstanding
66
33-0114 May 2025ICANN support to schedule the next meetingICANN Support TeamCompleted
67
34-013 JuneICANN support staff to share IFR2 final report and IFR2 Comments Spreadsheet with the IFR2 email list for final approval.
ICANN Support Team
Outstanding
68
34-023 JuneICANN support staff to work with co-chairs in getting an approval supermajority vote from the ccNSO and gNSO coucils. The final report will then be shared with the ICANN Board. The ICANN Board will have 45 days to act on the recommendations from the IFR2.
ICANN Support Team
Outstanding
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100