Summary

  • Minutes published on 26 August say ICANN staff would circulate more information about a proposal to retire WS2 Recommendation 5.8, which called for a five-member Ombuds Advisory Panel.
  • The Board adopted every consensus WS2 recommendation in 2019 and directed implementation. Recommendation 5.8 nevertheless remained not started, with no target date, through the latest public status report.
  • ICANN's retirement procedure has nine steps, including a criterion-based issue paper, SO/AC feedback, a minuted Board-group decision, Planning Prioritization Group reasoning, Public Comment and a final Board resolution.
  • The available minute does not show that 5.8 has been retired, that a required step was skipped or even which formal stage the proposal has reached. A public retirement receipt would resolve that boundary without exposing confidential case or personnel material.

One sentence changes the status of an eight-year promise

The news sits under “Any Other Business” in minutes for the ICANN Board Organizational Effectiveness Committee's 23 July meeting. Staff would update the committee on Work Stream 2 implementation at its August meeting. Staff also noted that additional information would be circulated regarding a proposal to retire Recommendation 5.8—the instruction that ICANN establish an Ombuds Advisory Panel—under the Process for Retirement of Non-Policy Recommendations.

The minutes were published on 26 August. They say an update will reach the OEC and Board “in due course.” They do not say the committee agreed to proceed. They do not name a retirement criterion, attach an issue paper or point to community feedback. At the 30 August cutoff, ICANN's Board index lists an OEC meeting on 25 August but provides no linked agenda or minutes for it.

That absence is a boundary, not a verdict. It does not prove that an issue paper has not been drafted, that Supporting Organizations and Advisory Committees were not contacted, or that an internal assessment is missing. It proves only that the public material now available does not let an outside reader place the proposal reliably on ICANN's own process map.

It is equally important not to jump to the other end. Recommendation 5.8 has not been publicly retired. Only the Board can complete that act through a resolution at the end of the procedure.

What Recommendation 5.8 promised

The 2018 CCWG-Accountability Work Stream 2 Final Report proposed a five-member advisory panel: at least two people with ombuds experience and the remainder with extensive ICANN experience. The panel would sit outside the Ombuds Office. It would advise and support, not become another Ombuds.

Its six functions were concrete. The panel would contribute to the selection of a new Ombuds; recommend candidates to the Board; recommend probation terms; recommend dismissal for cause; contribute to an external evaluation every five years; and advise on possible Ombuds involvement in non-complaint work.

Those words initially raised Board concerns about independence and fiduciary authority. Annex 9 therefore narrowed them. The panel would not be a decision-making body. It could not touch any live Ombuds matter, even on anonymised terms. It would exercise only the six listed functions. The Board would keep the appointment and dismissal powers. Advice about non-complaint work would occur only at the Board's request.

The guidance also required a formal selection process, candidates independent from SO/ACs, and publication of the process chosen by the Board. The point was not to create an appeals court for complaints. It was to introduce external experience into a bounded set of selection, performance and evaluation decisions while preserving confidentiality and Board authority.

That function list matters now. A retirement rationale cannot be tested by asking only whether an entity called a “panel” still sounds useful. The public needs to know whether each function was replaced, became unnecessary, proved too costly, lost support or remains an acknowledged gap.

Adoption was an authority event, not a suggestion box

On 7 November 2019, the ICANN Board adopted each consensus recommendation in the WS2 Final Report. Resolution 2019.11.07.38 directed the President and CEO to proceed to implementation. The next resolution told the organisation to start work, as much as possible, on items that did not have to wait for a budget cycle. Another required regular implementation reports.

The Board's rationale left room for prioritisation, staging, budget constraints and clarification. It recognised that more than 100 recommendations would take years and that the Board had to balance resources. It did not present adoption as a promise that no later evidence could change. Nor did it give the implementing agent an invisible power to redefine a recommendation out of existence.

This distinction is central. A community-developed recommendation and a Board adoption establish the authority source. A later retirement process is the lawful mechanism for changing that state. The two acts are not contradictory if the second one shows its evidence and authority. Retirement can be accountability; unrecorded abandonment cannot.

Six years of “not started” became a retirement proposal

The status trail is unusually clear at its endpoints and thin in the middle.

The November 2019 implementation assessment treated 5.8 as a recommendation modified by Annex 9 guidance. It described the need to align the panel with Board fiduciary duties and protect Ombuds independence and confidentiality. It did not recommend retirement.

By the fourth quarter of 2024, the quarterly report still labelled the work not started and said ICANN was assessing it from a cost-benefit perspective. Later reports changed the explanation. The second-quarter 2025 and first-quarter 2026 reports said the recommendation was being assessed in light of extensive changes already made or planned for the Ombuds Office. The tentative completion remained “TBD.” The current implementation page still reports “Not started.”

These sentences show that the organisation did not simply lose the item. They also show why a full issue paper matters. “Cost/benefit” could invoke the retirement process's cost criterion. “Extensive changes” could support an environment-change or override case. But a status sentence is not the criterion analysis. It does not disclose assumptions, alternatives, community support or the function-by-function comparison.

The June framework changes the context, not the burden of proof

On 7 June 2026, the Board approved a new, 24-page Ombuds Office Framework and Process. It replaces the 2009 framework, defines complaint and conflict-resolution paths, sets response and case-handling timelines, describes reporting and confidentiality, and commits the Board to a review roughly two years after it takes effect.

The Board said the framework incorporates WS2 recommendations. The preceding Public Comment page was more specific: it identified recommendations 5.2, 5.4 and 5.5 as addressed by the revision. The approved text does not establish the 5.8 panel or publish its selection process.

That is not proof of evasion. An operating framework for handling cases is not necessarily the document in which an external advisory body's constitution belongs. The Board also did not say the framework completed every Ombuds-related WS2 recommendation.

It does, however, create the obvious substitution question. The framework puts operational independence, performance reporting and a two-year review into the current design. Do those measures replace the panel's selection role, probation advice, dismissal feedback, five-year external evaluation and non-complaint-work advice? Perhaps some functions now have stronger substitutes. Perhaps others were judged unnecessary. The public record at cutoff does not provide the map.

Retirement is a nine-step governance act

ICANN finalised the Process for Retirement of Non-Policy Recommendations in January 2024. It is intended for exceptional cases involving community-developed, Board-approved recommendations outside a policy-development process. It is not a housekeeping shortcut.

Step 1 begins with an assessment against stated criteria. An issue paper identifies the recommendation, the criterion or criteria and whether ICANN org or an eligible SO/AC initiated the request. The criteria are environment change, superseding recommendations or advice, cost exceeding potential benefit, implementation time defeating value, and lack of broad community support.

Step 2 sends the issue paper to SO/AC leaders for coordinated feedback. Step 3 sends the updated paper to the responsible Board group. A decision to continue or withdraw must appear in minutes. Step 4 formally initiates the next phase, informs the relevant community actors and prepares materials for the Planning Prioritization Group.

At Step 5 that group determines whether the recommendation should remain active or be retired and generates a rationale. Step 6 opens standard Public Comment on the issue paper and that determination. Step 7 adds a summary and analysis of submissions. Step 8 produces a draft Board paper if support remains. Step 9 is the actual retirement: a Board resolution followed by updates to the relevant pages and reports.

This sequence separates initiation, evidence, consultation, recommendation and authority. It also prevents the word “proposal” from carrying more weight than it has earned.

The July minute cannot safely be mapped to a numbered step. Circulating information to the OEC could be preparation before the Board-group stage, part of that stage, or an internal update before formal initiation. The article therefore does not allege that ICANN has bypassed SO/AC feedback or any other requirement. The defect is narrower: the public cannot yet reproduce the state.

Publish a retirement-state receipt

A useful public record would not require a new bureaucracy. It would join artifacts ICANN's procedure already contemplates.

The receipt should name the recommendation and adoption resolution; the retirement originator and initiation date; the criterion invoked; the issue-paper version; and the original outcomes or functions at stake. For 5.8, it should then map all six functions to a current substitute, an accepted gap or a reason the function no longer adds value.

It should record the SO/AC feedback window and summary, the responsible Board group and minuted proceed-or-withdraw decision, the Planning Prioritization Group determination, the Public Comment record, the final Board paper and resolution if reached, and the date each public status page changed. Corrections should remain versioned.

This is Daniel Kade's proposed public receipt, not a claim about an existing ICANN field set. It does not call for personnel files, legal advice, Board deliberations or Ombuds case material. The process concerns the life cycle of a public recommendation; its receipt can remain entirely outside individual complaints.

Heng Lu's agency analysis is useful here as a discipline, not as ICANN law. An implementing agent should not quietly transform a principal's mandate into a different outcome. ICANN's retirement process recognises exactly that problem: it permits change, but assigns the change a criterion, a consultation chain and a final authority.

The strongest case for retirement should welcome that record. If an eight-year-old design has been overtaken by a better framework, the comparison will show it. If the cost is disproportionate, the issue paper can demonstrate it. If support has disappeared, consultation will reveal it. Transparency does not prejudice retirement; it distinguishes retirement from drift.

Sources

  1. ICANN — OEC minutes, 23 July 2026
  2. ICANN — Process for Retirement of Non-Policy Recommendations
  3. ICANN — CCWG-Accountability WS2 Final Report
  4. ICANN — Board minutes, 7 November 2019
  5. ICANN — WS2 Implementation Assessment Report
  6. ICANN — WS2 Implementation Summary Q4 2024
  7. ICANN — WS2 Implementation Summary Q1 2026
  8. ICANN — Ombuds Framework and Process Public Comment
  9. ICANN — Board minutes, 7 June 2026
  10. ICANN — Approved Ombuds Office Framework and Process
  11. ICANN — WS2 Ombuds implementation page
  12. ICANN — Board Activities and Meetings 2026
  13. Heng Lu — On the Agency Problem at the Core of Internet Governance