Summary
- Recommendation 8.1.14 deleted the sentence that let ICANN refuse documents "under conditions not designated above"; ICANN's own implementation tracker records the work completed in Q1 2023.
- What survived is narrower and slower: a 30-day clock with a feasibility escape, a review section naming three Bylaws mechanisms by article number, and a public log that indexes requests without recording what any of them produced.
The sentence that was doing the work
Until 2023 the Documentary Information Disclosure Policy carried an escape hatch underneath its list. After the bulleted conditions and after the public-interest override, the 2012 text added this, in the institution's own voice:
Further, ICANN reserves the right to deny disclosure of information under conditions not designated above if ICANN determines that the harm in disclosing the information outweighs the public interest in disclosing the information.
Read it twice. The list above it was not the whole list. Whatever condition a requester happened to cite, ICANN could step outside the enumeration and refuse, on its own finding about harm and interest, weighed against each other by the holder of the documents.
That sentence is gone. ICANN's Work Stream 2 implementation tracker carries a line numbered 8.1.14 whose instruction is precisely the deletion — "The following sentence should be deleted" — followed by that sentence verbatim, and whose recorded status reads "Completed in Q1 2023". The current policy, amended 21 January 2023, no longer contains it: the text runs from the public-interest override straight to the administrative sentences about not compiling summaries and not answering requests for material already published.
The enumerated conditions became the whole list by deliberate amendment, dated to a quarter and attributable to a numbered recommendation. One thing this review does not print is the number of conditions: the retrieved renderings disagree on how that list is structured and I did not settle it. Treat the conditions as an enumerated set, not a countable one.
What the deletion left standing
The public-interest override survives, and it points toward disclosure: information within a condition "may still be made public if ICANN determines, under the particular circumstances, that the public interest in disclosing the information outweighs the harm that may be caused by such disclosure." That is a real valve. It is also ICANN's determination, made inside ICANN, on facts ICANN assembles.
The paper a refusal must carry is set by the companion Response Process. A response must name documents already published and where they sit on icann.org; identify responsive documents found appropriate for disclosure and where they will appear; and, for anything withheld or redacted, state the applicable condition, the rationale and information about applicable appeal processes. Where only portions fall under a condition, those portions are redacted and the rest is published.
Thirty days, with the escape inside the sentence
The clock reads: a written response "within 30 calendar days of receipt of the request, unless it is not feasible to do so", with an extension "not longer than an additional 30 calendar days" and written reasons. Sixty days is the outer bound, and that bound assumes the extension is invoked and explained. The feasibility clause is not a footnote to the deadline; it sits inside the commitment, which is where a drafter puts a phrase it expects to rely on.
Then the worked instance, which is the test of any clock. Request 20260401-1 arrived on 1 April 2026 and was answered on 1 May 2026 — thirty calendar days, no extension needed. It sought five categories of documents on ICANN's review of the Epik Inc. to Epik LLC Registrar Accreditation Agreement assignment and related compliance records. The answer produced no new documents for those categories. It pointed to already-published material — the template assignment agreement, compliance audit reports, monthly compliance reports, notices of breach — and withheld the fully executed assignment agreement and internal diligence materials under the deliberative-process condition, a third-party commercial-interest condition and a trade-secret and commercial-and-financial-information condition, adding that fully executed RAA assignment agreements "are not published by ICANN". A reader can check that against the list, condition by condition. What a reader cannot check is whether the answer is right, because the reasoning belongs to ICANN and the documents are the ones being withheld. Two of the condition lists in that response were truncated mid-sentence in the material I obtained.
Three routes, cited by article number
The 2012 policy headed this section "Appeal of Denials". The current one heads it "Review of DIDP Responses" and hands the reader three addresses: Reconsideration under Bylaws Article 4, Section 4.2; the Independent Review Process under Article 4, Section 4.3; or the Ombudsman under Article 5 — conditionally, in words that leave the reader to work out which applies.
Of those, the Bylaws state the first clearly. "The Board has designated the Board Accountability Mechanisms Committee to review and consider Reconsideration Requests." The committee may evaluate requests, dismiss insufficient or frivolous ones summarily, investigate and request further written submissions; its output is a recommendation to the Board. A request challenging Staff action must be filed within 30 days of the requester becoming aware of it. A DIDP refusal is Staff action. So the first instance of review sits with a committee of the Board of the institution that holds the documents, and the answer comes back as a recommendation to that same Board.
What the other two mechanisms can order, and whether either publishes a reasoned decision a stranger can read, is not established here: Article 4, Section 4.3 and Article 5 were not read. That gap is load-bearing. An instrument that names a remedy by article number has not incorporated the remedy; it has made the remedy conditional on a second document.
The log indexes correspondence, not outcomes
ICANN does publish, at volume. The requests and responses log runs in reverse chronological order, attaches the request to the response where the request is set out separately, and posts requests in full except for personal email addresses, phone numbers and mailing addresses absent exceptional circumstances. At retrieval the earliest listed entry was Request 20090206-1 and the most recent Request 20260901-1.
What the log page obtained on 19 November 2026 does not do is record a result. It lists numbers, requestors and links. It does not mark which responses released documents, which withheld them, or which did neither. That is a description of the page a requester is pointed to, not a claim about what ICANN publishes elsewhere.
There is a better instance than a refusal. Request 20230815-1, submitted 15 August 2023 and answered 14 September 2023 — thirty days again — identified two annual ICANN officer confirmation letters to Verisign, for December 2021 and December 2022, and stated: "These letters are responsive to Item No. 1(g) and will be published on the correspondence webpage by the end of the month." The same response withheld recordings of the 2022 Contracted Parties Summit after a public-interest balancing. Be precise about what that evidences: an undertaking to publish. Whether the letters went up by the end of that month was not verified here, because the correspondence webpage was not inspected.
The tally nobody can recompute
To know whether any of this discloses anything, you need the column the log omits. The only independent coding I could obtain is volunteer-edited. ICANNWiki states: "Since the initiation of the DIDP process, 166 DIDP requests have been filed (as of December 2021). Of those, 78 requests were declined, 45 were responded to with links to publicly available information, and 41 resulted in the disclosure of some amount of new information (documentary or otherwise). These statistics are based on the review of all requests by ICANNWiki editors."
Add the categories. 78, 45 and 41 make 164. The page says 166. Two requests are unaccounted for and the page does not say where they went. The definitions make reconciliation harder: "Declined" covers rejections of all or part of a request whether or not links were supplied, and "Information Disclosed" covers new information or context as well as documents, with the page noting that in most cases only some responsive documents were released.
So the best public count of what ICANN's disclosure route has produced — volunteer-coded, dated December 2021, and reachable in this review only through a retrieval that returned a 403 to a direct fetch — misses by two and overlaps by design. This is not a scandal. It is the state of the record, and it is why the amendment cannot yet be measured: the log has no outcome column and the substitute is a table nobody can reproduce.
A disposition column would fix it — released, partially released, refused with the condition named, pointed to published material — because a stranger could then recompute the route instead of trusting a wiki. Two smaller repairs would finish what the amendment started: a numbered, version-dated schedule of conditions, and a review section stating which mechanism decides a DIDP refusal and what it can order. Read as a route rather than as a text, the policy was improved at exactly one point — the point where a refusal could once stand on nothing in the policy at all. Everything downstream of that point is still assembled by hand.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






