Summary

  • On 8 September 2026, the Internet Architecture Board reappointed David Lawrence as the IETF liaison to the ICANN Board for the 2026–2028 term.
  • The June nomination notice said seating would be completed by ICANN87 “in November”; the July feedback notice said the appointee would begin at ICANN87 “in October.” ICANN schedules that Annual General Meeting for 17–22 October.
  • ICANN’s Bylaws say liaison terms begin at the conclusion of the annual meeting. They also distinguish four non-voting liaisons from 16 voting Directors.
  • Daniel Kade proposes a public term-transition receipt that resolves the handoff date and records the non-confidential selection stages without exposing private feedback or conflict details.

One appointment, two months

The IAB’s 8 September announcement closes the selection at its most visible point. It says the IAB, after seeking nominations and community feedback, reappointed David Lawrence as the IETF liaison to the ICANN Board for 2026–2028. That is the confirmed outcome. It does not say how much feedback arrived, describe the assessment or give the date on which the new term begins.

The earlier notices contain more process detail—and one small contradiction. The 9 June call for nominations set a 24 July deadline, described the term as normally two years and renewable, and said Lawrence, who had served since 2024, was willing to continue. It expected an appointment by the end of August, with seating completed by “ICANN 87 in November.”

The 31 July feedback notice reports that one candidate had accepted a nomination: the incumbent. It solicited comments until 24 August through two private email addresses and offered anonymisation on request. It also says there is no limit on length of service. This time the notice says the appointee will begin participating at ICANN87 “in October.”

The current ICANN87 meeting page supplies the calendar fact. The Annual General Meeting is scheduled in Bali from 17 to 22 October 2026, and the page says the AGM is where new members of the ICANN Board take their seats. November is not a second date for ICANN87 on that page.

This is a documentation discrepancy, not evidence of a failed appointment. The June page may contain a stale month. The schedule may have changed before the page was captured. The IAB may have completed every required private step. None of the reviewed public sources establishes operational harm. The narrow point is that the public selection record does not itself reconcile the dates.

The Bylaws supply the missing clock edge

ICANN’s Bylaws are more exact than either IAB notice. Section 7.9 says liaison terms begin at the conclusion of each annual meeting. It requires an appointing body to notify the ICANN Secretary in writing at least one month before the annual meeting begins. A liaison can be reappointed and remains until a successor is appointed, or until resignation or removal.

That means “seating at ICANN87” is convenient shorthand, not the complete rule. The current meeting begins on 17 October and ends on 22 October. Under the published Bylaws, the term transition is tied to the conclusion of that annual meeting. The 8 September public announcement arrived more than a month before the meeting began, but a public announcement is not proof of when the separate written notice reached the Secretary.

The distinction matters because continuity can conceal two different states. Lawrence is already listed on the current ICANN Board page as a liaison. A reader may therefore see the same person before and after ICANN87. The person does not change, but the appointment authority, term label and evidence date do. Governance records should preserve that boundary even when no chair changes hands.

The IETF Datatracker profile corroborates the identity and participation record. It does not establish the private evaluation or the effective date of the new ICANN term. Identity, selection and assumption of a term remain separate facts.

Access to deliberation is not a vote

The ICANN Board has 16 voting Directors and four non-voting liaisons. Only Directors count for quorum and Board votes. A liaison may attend meetings, participate in discussion and deliberation, and obtain Board materials under conditions set by the Board. Those are substantial information and coordination rights. They are not a Director’s voting authority.

The IETF-side boundary is equally important. RFC 4052 gives the IAB responsibility for managing liaison relationships and appointing IETF representatives. RFC 4691 describes a two-way communication role that conveys relevant IETF consensus rather than creating it as a personal view. Reappointment extends responsibility and access; it does not enlarge either institution’s constitutional powers.

That point should not be mistaken for a criticism of continuity. A liaison benefits from accumulated contacts, knowledge of two organisations and memory of unresolved dependencies. The public record also says the role demands substantial time across ICANN meetings, Board workshops and IETF work. A one-candidate field is not proof of an inadequate search, and a renewal is not proof of weak scrutiny.

It does, however, increase the value of a clean transition record. When the person remains the same, an institution loses the visible cue that normally prompts readers to ask when the old mandate ended, when the new one started and what rules still constrain it.

A term-transition receipt

The proposed record can be short. It should name the appointing body, role, incumbent status, term label and exact Bylaws handoff event. It should link the nomination notice, accepted-candidate count, feedback window and outcome. It can say that conflict review and appointment notice were completed without publishing personal disclosures, private comments or protected Board material.

The record should also identify the reporting destination and authority ceiling: which IETF body receives updates, that the liaison communicates IETF consensus rather than inventing it, and that the ICANN seat has discussion and material-access rights but no vote. A correction field can explain that the June notice’s November reference was superseded by the October meeting schedule.

Nothing here requires publication of who commented or what they said. “Feedback channel closed; feedback considered under the IAB process” is a process state. “No feedback was received” would be a factual claim requiring evidence that the public pages do not provide. The same discipline applies to conflicts: completion can be recorded without exposing the substance.

The 8 September announcement establishes who will continue. ICANN’s calendar establishes when the AGM occurs. The Bylaws establish where the term boundary lies. A single receipt would let those facts travel together, so continuity is documented as a new mandate rather than mistaken for an office with no clock.

Sources