Summary

  • The Internet Architecture Board (IAB) asked the ICANN Board on 15 October to address six safeguards before the proposed Root Server System (RSS) Council is chartered.
  • The February model gives Root Server Operators 12 of 24 voting seats. The IAB wants broader group representation, equal group weighting and independent review before the first phase begins; these are requests, not adopted rules.

The IAB’s liaison statement is a new intervention in a design process that has already run through public comment. The IETF Datatracker record shows that the IAB sent it to the ICANN Board on 15 October “for information.” It is not a Board decision, and it does not report a failure in root-server operations. The IAB says the proposed structure could put the Root Server Operators (RSOs) in a position of long-term funding and operational continuity without enough tools to hold them accountable. That is the IAB’s assessment, not a finding of misconduct or proof of capture.

The letter lists six changes it wants before the Council is formed. First, it asks for formal participation by more groups, naming the At-Large Advisory Committee, IETF/IAB, Governmental Advisory Committee, GNSO constituencies, Regional Internet Registries, civil society and end users. Second, it wants the RSO, TLD and “other” groups to have equal voting weight. Third, it wants to prevent one organization from voting in more than one group.

The remaining requests are an independent external appeals process for operator designation, removal and performance suspension; a check on the Council comparable to the Empowered Community’s check on the ICANN Board; and a concrete, binding and diversified funding plan before chartering to reduce the risk of donor influence.

The current Functional Model draws a different initial map. It gives the Council 24 voting positions: 12 appointed individually by the RSOs, six from gTLD registries and six from ccTLD registries. Three liaisons—from IETF, IANA and the Root Zone Maintainer—may participate without votes. The model’s stated aim is parity between the 12 RSO votes and 12 votes from non-RSO participant communities. On that design, RSOs collectively hold half of the voting seats; that calculation does not by itself establish capture.

The IAB wants a third, broader group with voting weight equal to the RSO and TLD groups. But the proposed model asks a community to show both direct operational dependency on the RSS and sufficient organization to appoint representatives before it receives participant status. Other interested groups can comment and may seek recognition later if they meet those criteria. The IETF is already named as a non-voting liaison. The IAB’s letter does not specify who would appoint the additional groups, how many representatives each would receive or how “other” would be bounded.

Those omissions matter because adding a constituency and giving it a vote are two separate design decisions.

The disagreement is partly about timing. The model is explicitly phased: Initiation would create the Council and Secretariat but is limited to setup, transparency and preparation. Later phases would establish policies, appeals and accountability. In its public-comment disposition, the model says voting and quorum rules are to be defined in Initiation and Establishment; independent review is for Establishment; and explicit funding caps and diversification criteria are also assigned to Establishment. The IAB wants some of those conditions binding before the Council is chartered.

It argues that deferring them may leave the community with too few practical opportunities to correct the structure after it exists.

The RSSAC058 success criteria require a functional description to identify appropriate decision mechanisms, including participation and voting thresholds. Criterion C1 does not set a particular share for each group. The IAB invokes it to argue that the model’s 50% RSO share is a poor fit; the proposed equal weighting of three groups is the IAB’s interpretation and remedy, not a requirement in RSSAC058.

ICANN Board Chair Tripti Sinha’s 13 October preview said the Board would continue discussing the model and staff would preview implementation work, timelines and possible guardrails. The Board calendar still listed the 18 October regular meeting as upcoming at the time of this check. The reviewed public record contains no adoption resolution or public response to the IAB letter. The public-comment proceeding documents the earlier consultation; it does not convert the new liaison statement into consensus.

Sources