Versions Compared

Old Version 2

changes.mady.by.user Brenda Brewer

Saved on

compared with

New Version 3

changes.mady.by.user Brenda Brewer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

ATTENDEES:

  • Members: 
  • Observers: 
  • Apologies:
  • ICANN org: 

AGENDA:

  1. Welcome, Roll Call, SOI updates
    1. Welcome Ching Chiao (CSG appointment)
  2. Action Items (all action items tracked in the Google sheet linked here [docs.google.com])

Reference

Date

Action item

Status

08-01

19 March 2024

Team 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.

  • Homework to be completed ahead of the 2 April meeting agenda.

08-02

19 March 2024

In addition to flagging anything that needs clarification in the preamble and definitions section, team to put together questions for PTI.

  • To be completed as part of the 2 April meeting agenda.

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.

  • 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.

07-02

4 March 2024

Co-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.

  • Team will kick off the contract review as a group (see item 3 of the 19 March agenda).

3. Continue review of the IANA Naming Function Contract Definitions section with aim to develop questions for PTI and ICANN Legal

a. HOMEWORK: Review and add comments to the definitions [docs.google.com] spreadsheet (please initial any comments) with the intent to create a set of questions for PTI and Legal. As additional reference, see the RFC 1591 [rfc-editor.org] and FOI [ccnso.icann.org] documents. The purpose of such questions is to seek authoritative clarity and historical context as to why things are written as they are in the contract.

4. Next steps:

a. Provide written questions to PTI and ICANN Legal in advance (team to agree a close date for questions).

b. Invite PTI and ICANN Legal to an upcoming meeting.

5.  AOB, close

RECORDINGS:


DOCUMENTS:


MEETING NOTES: