Summary

  • On 6 September, the ICANN Board authorized its President and CEO, or his designee, to enter an Information Transparency Platform Next Generation support-services contract and make related disbursements. The resolution was published on 9 September.
  • Several contract particulars and part of the rationale are marked “Confidential Negotiation Information.” The public record does not establish the vendor, price, term or whether the authorized contract has since been signed.
  • A companion resolution says the redacted portions remain confidential until the President and CEO decides they may be released. ICANN’s standing guidelines place this redaction class in an annual review process.
  • The governance gap is narrow: the rules provide a decider, a review cadence and a redaction register, but the decision page provides no item-specific next-review date or future disclosure commitment.

The Board created two gates

The approved resolutions from 6 September 2026 do more than announce a technology project. Resolution 2026.09.06.01 authorizes the President and CEO, or his designee, to enter a contract and make disbursements for ITP Next Generation support services. Resolution 2026.09.06.02 deals with a different act: it keeps specified portions confidential for negotiation purposes until the President and CEO determines that they may be publicly released.

Those are distinct controls. The first answers who may bind ICANN and spend. The second answers who may change the public state of the record. Neither should be inferred from the other. An authorization is not proof that the contract is executed; a completed negotiation would not by itself prove that every redaction is ready to lift.

What is visible is deliberately bounded. The Board says ICANN staff and the Board Finance Committee recommended approval. It says the fiscal impact is incorporated into the Project Fund. It labels the decision an Organizational Administrative Function that does not require public comment. It does not publish the current amount, counterparty, term or other concealed particulars. Nothing in the open source set supports guessing them.

A platform for public information becomes the test case

The subject makes the disclosure mechanics unusually legible. ICANN describes the Information Transparency Platform as the system that manages, organizes and delivers public information across its web properties. Since 2017, it says, the platform has supported structured content, multilingual publishing, taxonomy management and modern content delivery.

For the Next Generation architecture, ICANN says it is simplifying the platform rather than extending the present implementation. The stated aims include fewer enterprise platforms, lower licensing and maintenance costs, faster delivery and less dependence on specialized outside developers. These are expected benefits, not independently measured results. The resolution authorizes support services for the transition; it does not supply a baseline, target cost or dated realization report.

That distinction matters because ITP is itself part of the evidence surface. A publishing platform can make documents easy to find while leaving the lifecycle of a redaction hard to reconstruct. Searchability is not the same as accountability. The public needs to be able to tell not only that words were withheld, but whether the withholding was later reviewed, continued, narrowed or ended.

ICANN’s rules already give secrecy a lifecycle

The Guidelines for the Posting of Board Briefing Materials start with a presumption that material will be posted, call for the smallest necessary redaction and require a clear justification. They classify “Confidential Negotiation Information” and “Confidential Business Information” as subject to annual review for possible release.

The guidelines also describe two controls that are easy to miss. ICANN maintains a Redaction Register for redactions in Board resolutions, minutes and briefing materials dating from August 2016. When information is released, the register is meant to record the release date. And if reviewable information has not been published within 15 years, the next annual review is to publish it unless a significant reason remains to continue the redaction.

The 15-year language is not a scheduled embargo. It is a presumptive long-stop with an exception. Nor does “annual review” mean this September item is already late; the resolution is new. The current record supports a more precise observation: the policy supplies a general cadence, while the resolution page supplies no date for the first item-specific review and no dated promise to release the text.

The current ICANN Bylaws require prompt publication of Board resolutions while recognizing specified nondisclosure grounds. ICANN’s publication practices express the same structure: publish operational information unless a compelling reason supports redaction, and withhold the smallest necessary amount. Its Documentary Information Disclosure Policy offers a request route but also recognizes commercial prejudice, competitive position and confidentiality agreements as reasons not to disclose. A request is an accountability mechanism, not a guarantee of immediate access.

Prior ITP numbers cannot fill the blanks

Historical records add context without solving the current redactions. In 2017, the Board approved the original Information Transparency Initiative and estimated its cost at US$6.3 million plus a 30 percent contingency. That figure belongs to the original initiative and its FY18–FY22 planning. It is not evidence of the price of the 2026 support contract.

The 2023 ITP renewal resolution gives much more procurement detail while still redacting the vendor and commercial terms. It says 31 vendors were invited to an RFP, seven submitted full proposals, finalists were scored and interviewed, and a reverse auction was used. The Board Finance Committee minutes say the committee considered the prior process and costs reasonable and affordable. Those are facts about the earlier cycle. They do not identify the 2026 vendor, prove that the same process was repeated or turn a historical assessment into a current audit.

The older decision pages still illustrate why release history matters. A reader arriving years later should not have to compare screenshots or infer from unchanged brackets whether a redaction was never reviewed, reviewed and retained, partly released, or replaced by a later document. All four states can look identical on one static page.

Publish the review, not the negotiating position

ICANN does not need to expose a live bid or weaken its bargaining position to make the control observable. A redaction-release receipt could be keyed to the meeting and resolution number. It could record the redaction class and public locations, initial authority, whether annual review applies, the date of each review, the reviewer or office, the result, a bounded reason for continued withholding, the next review date and any later release link.

Contract execution, review and disclosure should be separate fields. A contract may be signed while negotiation-sensitive details remain protected. A review may legitimately continue a redaction. A later release may reveal only part of the record. Preserving those distinctions would allow the public to see the governance process without demanding the confidential substance.

This receipt is an editorial proposal, not an ICANN requirement. The present record does not show misconduct, a missed review, an improper payment or a broken procurement. It shows a Board authorization with a defined release gate and a standing policy with a clock—but no public, item-specific appointment with that clock.

Sources