Hello! Apologies for the late notice but I won’t be able to join todays call. I woke up to no electricity in the house so internet is down. If there are questions for PTI, please add to the sheet and I’ll respond when power is restored. Thank you! Marília Hirano Sent from my iPhone On Jul 9, 2024, at 2:43 AM, Jonathan Robinson <jonathan.robinson@identity.digital> wrote: Please accept my apologies for the meeting today. I am on leave / PTO for this week and next. I expect to attend the next meeting (23 July) in person. Thank-you, Jonathan From: IFR2-team <ifr2-team-bounces@icann.org> On Behalf Of Jennifer Bryce Sent: Wednesday, July 3, 2024 10:12 PM To: ifr2-team@icann.org Subject: [IFR2-team] Agenda and homework: IFR2 meeting 9 July @ 11:00 UTC Dear IFR2 team, Included and attached is the agenda for the next IFR2 team meeting scheduled for 9 July @ 11:00 UTC. HOMEWORK DUE 9 July: Read and make comments on the following sections of the IANA Naming Function Contract (pages 10 – 14): * Article VII: Audits, Monitoring and Reviews * Article VIII: Escalation Mechanisms * Article IX: Term; Renewal; Transition and Termination Keep the following questions in mind: 1. Are there any deficiencies (anything missing) in the text? 2. Does anything require clarification? 3. Is the text/content still necessary? 4. Is there any additional information or data needed to make an assessment about this text? Add any comments or questions to the IFR2 workbook [docs.google.com]<https://urldefense.com/v3/__https://docs.google.com/spreadsheets/d/13-bJJ1vd...> column ‘H’, rows 40 - 55. Please initial your comments. NOTE: If there are already comments in the cell, to add another line within the cell press ⌘ + Enter on a Mac or Ctrl + Enter on Windows. Second IANA Naming Function Review (IFR2) Meeting 16 9 July 2024 | 11:00 UTC Agenda 1. Welcome, Roll Call, SOI updates 1. Action Items (all action items tracked in the Google sheet linked here [docs.google.com]<https://urldefense.com/v3/__https://docs.google.com/spreadsheets/d/1DFJ30deC...>) Reference Date Action item Status 11-01 30 April 2024 IFR2 team to put together a list of ongoing questions to ask ICANN Legal. * Ongoing - See ‘Questions for Legal [docs.google.com]<https://urldefense.com/v3/__https://docs.google.com/spreadsheets/d/13-bJJ1vdg4NCujHCnRo40T29KnvVIQbwm0u9GaGBbYI/edit*gid=467621701__;Iw!!PtGJab4!4uawoq7mg45WPoU1UEtH5i55x5JtfSdTgtVF_hFQmghBqLQF8aZe4JY8QiIZTvgrZpiJX-enlILQWRpbqteF0HiH4eMTAeTdT9uqZ0NcGtfp$>’ 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. 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. * Ongoing - On hold for future consideration, once the IFR2 gets to a place in its work where it feels it can phrase the question most meaningfully. 1. Review findings and comments from the homework reading (see rows 40 – 55 in the workbook [docs.google.com]<https://urldefense.com/v3/__https://docs.google.com/spreadsheets/d/13-bJJ1vd...>): · Article VII: Audits, Monitoring and Reviews · Article VIII: Escalation Mechanisms · Article IX: Term; Renewal; Transition and Termination 1. Next steps: * Next meeting 23 July @ 18:00 UTC. * Homework assignment to be agreed based on meeting progress. 1. AOB, close _______________________________________________ IFR2-team mailing list IFR2-team@icann.org https://mm.icann.org/mailman/listinfo/ifr2-team _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.