From: Jonathan Robinson via IFR2-team <ifr2-team@icann.org>
Organisation: Identity Digital
Reply to: "jonathan.robinson@identity.digital" <jonathan.robinson@identity.digital>
Date: Tuesday 25 February 2025 at 17:03
To: 'Reda Josifi' <reda.josifi@icann.org>, "ifr2-team@icann.org" <ifr2-team@icann.org>
Subject: [EXTERNAL] [IFR2-team] Re: Agenda: IFR2 meeting 25 February @ 18:00 UTC

 

All,

 

Please accept my apologies for today. Unfortunately, I have a diary clash which means I cannot attend the meeting.

 

I am supportive of publishing the draft prior to ICANN 82 and willing to review any final edits / comments that may arise during the meeting today or that are unable to be reviewed during the course of the meeting.

 

I plan to attend the ICANN 82 meeting in Seattle in person.

 

Regards,

 

 

Jonathan

 

 

Dear IFR2 team, 

 

Included and attached is the agenda for the next IFR2 team meeting scheduled for 25 February @ 18:00 UTC.

 

Second IANA Naming Function Review (IFR2) Meeting 31

25 February 2025 | 18:00 UTC

Agenda 

Homework Due 25 February

• Read Recommendations from IFR1

• Please note that Leadership has reviewed the IFR1 recommendations and has not found any issues.
• The frequency of reviews is captured in our draft IFR2 report recommendations but otherwise everything has been completed and does not have an impact on the SLAs.

• Read DRAFT IFR2 Report

• Please note that Article VIII, Section 8.1 incidental finding on the Ombudsman has been added as Incidental Finding #4 on page 6.
• Goal is to have draft report up for public comment prior to ICANN82 (7 March 2025)

• Think about report edits/final tasks that you would like to see happen prior to publishing the report for public review.

• Review and be prepared to discuss the priority levels and suggested timelines for Recommendations 1-4 on pages 3-5.

 

1) Welcome, Roll Call, SOI updates

 

2) Action Items (all action items tracked in the Google sheet linked here)

 

Reference	Date	Action item	Status
26-01	26 November 2024	Sam Eisner to provide IFR2 group more information on the amendment paths/recommendations and the level of detail needed for recommendations.	Sam will follow up with more information in the coming weeks.
26-03	26 November 2024	Peter 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 shared his thoughts via email on 19 February.
07-01	4 March 2024	As 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.	Open task in case the CSC brings anything else to the attention of the IFR2 group.

 

 3) Recommendations from IFR1

• Discuss any questions or concerns that came up during the team’s review of the IFR1 Recommendations. Leadership has reviewed and does not see any issues with recommendations from IFR1.

 

4) Draft IFR2 Report:

• Reference: IFR1 Report
• Goal is to have draft report up for public comment prior to ICANN82 (7 March 2025). Discuss and agree upon final report edits or tasks that you would like to see happen prior to publishing the report for public review.
• Discuss the priority levels and suggested timelines for Recommendations 1-4 on pages 3-5.

5)Next Meeting: 

• Monday, 10 March at 22:00 UTC

 

6) AOB, close