Minutes of the 2024-11-05 IAB Business Meeting
Dublin, Ireland

1. Attendance

Present

  Matthew Bocci
  Jay Daley
  Roman Danyliw (IETF Chair)
  Dhruv Dhody
  Wes Hardaker
  Cullen Jennings
  Suresh Krishnan
  Mirja Kühlewind
  Cindy Morgan (IAB Executive Administrative Manager)
  Tommy Pauly (IAB Chair)
  Colin Perkins (IRTF Chair)
  Alvaro Retana
  Qin Wu

Regrets:

  Alissa Cooper (remote)
  Ryan Polk (ISOC Liaison)
  John Scudder (IESG Liaison)
  David Schinazi
  Christopher Wood
  Greg Wood

Guests:

  Olaf Kolkman, Internet Society
  David Lawrence, incoming ICANN Board Liaison
  Sally Wentworth


2. ISOC Policy Program/Roundtable Update

  Olaf Kolkman updated the IAB on the ISOC Policy Program and
  Roundtable at IETF 121. There were about 35 people at the roundtable.
  Olaf noted that European locations are particularly well-suited to
  holding policy roundtables, and that they will probably not plan one
  for IETF 122 in Bangkok because it will be difficult to get local
  policymakers to attend.

  Olaf Kolkman said that he is considering some kind of tutorial about
  WSIS for IETF 122. He will write up a concept note for the tutorial
  and send it to the IAB.

  Twelve people participated in the policymaker program at IETF 121,
  including five people from the African continent. More were invited,
  but it was difficult for them to get the necessary visas.


3. Chat with the new ICANN Board Liaison

  The IAB met with David Lawrence, who will be seated as the new IETF
  Liaison to the ICANN Board of Directors at ICANN 81.

  In addition to the monthly written reports, the IAB invited David
  Lawrence to attend an IAB teleconference once per quarter for more
  in-depth discussions. Both David and the IAB agreed that two-way
  communication is important for this liaison relationship.


4. Liaison RFC updates 4052/4053 (Mirja/Suresh)

  Suresh Krishnan and Mirja Kühlewind previewed the slides they will
  present about updating RFC 4052 and RFC 4053 during the IAB Open
  session at IETF 121.

  RFCs 4052 and 4053 need updating because some of the information and
  described processes are not fully up to date. Updating those RFCs
  will also provide an opportunity to better explain what liaison
  management means and when it makes sense to create a formal liaison
  relationship. The focus will be on requirements and high-level
  guidance, with low-level details on tooling and processes moved to a
  wiki that can be more dynamically updated.

  Since RFC 4052 and 4053 are BCPs produced by the IAB, the -bis
  documents will go through the regular IAB adoption and consensus
  process before moving over to the IETF stream as AD-sponsored
  documents to get IETF consensus and IESG approval.