Summary

  • ICANN’s FY26 annual report records 32 Public Comment proceedings and 375 submissions. The five busiest received 146, roughly 39% of the total. The count shows where attention went; it says nothing by itself about which arguments changed a decision.
  • The Universal Acceptance guidelines provide a case to follow. The consultation summary collated comments but deferred its detailed guideline and priority analysis to the expert group. The final guidelines say they were updated after feedback. Readers need a visible bridge between those two records.

The busiest boxes need the clearest trail

Imagine an institution putting 32 boxes along a wall and reporting that 375 letters arrived. The counter is honest. The wall still leaves the visitor wondering what happened inside. ICANN’s newly published FY26 annual report puts real numbers on its Public Comment machinery: 32 proceedings, 375 submissions, an average 11.71 submissions per proceeding, and an average open period of 50.9 days. The five busiest proceedings took 40, 37, 27, 25 and 17 submissions. Together they took 146, or 38.9% of the year’s reported mail.

That distribution is useful. The Universal Acceptance guidelines drew the largest pile, 40. A second draft of the Regional Internet Registry governance document drew 17 and still made the top five. A small submission count can be a large governance matter; a crowded docket can contain repetitive arguments. ICANN’s Public Comment page publishes submissions and summary reports and says the Board, supporting organizations, advisory committees and ICANN org may open proceedings. The public can inspect what entered. The hard part is following what left.

The annual report’s unit is a submission. It does not count unique people, affected users, votes or adopted proposals. That distinction matters when an organization presents consultation as proof of openness. Forty letters may come from forty constituencies or from overlapping participants with shared positions. The useful question is neither whether forty is impressive nor whether seventeen is enough. It is which arguments survived the journey from box to text, which were rejected, and who signed off on the choice.

One docket shows the handoff

Take the most crowded box. ICANN’s 12 May summary report on the draft Universal Acceptance guidelines groups similar comments and warns that the summary may omit detail from original submissions. It sorts input into general comments, comments on particular guidelines, and implementation-priority comments. This is a useful filing system. The report then says the expert group will discuss the last two groups; they are not analyzed further in that report. ICANN org will use the input in its implementation planning.

The final guidelines dated 20 August say the expert group reviewed community feedback, updated the guidance and suggested priorities for phased implementation. They provide substantial guidance on stakeholders and a section on prioritization. What the four cited public documents do not provide in one place is an issue-by-issue disposition: this request from the consultation, this text change or rejection, this reason, this owner, this implementation priority. A diligent reader can compare draft, comments, summary and final text. The reader still has to be the clerk who reconstructs the decision.

That missing join is a governance question with practical stakes. Suppose a contributor asks ICANN to define measurable accessibility for software that accepts internationalized email addresses. The summary can record the argument. A final guideline can mention accessibility. The test is whether a public decision record says how that request was handled and who will measure implementation. Without that connection, advocates can claim victory and officials can claim responsiveness while operators are left guessing which obligation, if any, changed. A linked disposition would settle the question with a document instead of a guess.

Heng Lu’s criticism of participation being mistaken for mandate applies at the level of paperwork. The person who sends a comment is heard; the body with authority still decides. Both acts deserve a receipt. ICANN already keeps the first receipt unusually well: dates, submissions, reports. The next receipt could be a compact table linking each substantive issue to a disposition, a final provision, an implementation owner and a dated explanation. The public could then see where a reason met a decision.

Thirty-two open boxes look impressive in a photograph. The institution earns confidence at the desk behind them, where arguments are either used, set aside or parked for later. Count the letters by all means. Then count the reasons.