Summary

  • The task force's final report numbers fifteen recommendations. Not one carries an assigned owner or a target date, and the community tracker that records their status has neither an owner column nor a date column.
  • No single document in this set attaches a recommendation number, a disposition, a named accountable owner and a calendar date at once. The one dated commitment anyone did commit to paper — a January 2025 version of the document describing the RIPE–RIPE NCC relationship — was met.

The RIPE Accountability Task Force did something most review bodies avoid. It declined to decide anything. "Based on its review, the task force has a number of recommendations it would like the RIPE community to consider," reads the closing section of its final report, ripe-723. That sentence is the hinge of the whole document, and it is worth reading slowly. The addressee is not a board, a council or an executive. It is the community.

The recommendations themselves occupy printed page 28 of the retrieved text. There are fifteen of them, numbered 1 to 15, covering RIPE NCC commitments, chair funding disclosure, policy-capture safeguards, obsolete-document explanations, document categories and metadata, chair succession, external-representation reporting, working-group chair selection, onboarding and training, newcomer guidance, chair-collective responsibilities, task-force documentation, plenary authority and minutes, and a recurring accountability review.

Two structural facts travel with that list. None of the fifteen names an owner. None of the fifteen names a target date. That is not an impression from reading the prose; it is the shape of the document, and the inspecting tool reported it as such: zero recommendations with an assigned owner, zero with a target date. Where a body is named at all it is offered as a possibility rather than an assignment — item 11 suggests the RIPE NCC as a possible implementer, and the discussion around item 9 does something similar.

The report also carries two dates and one internal inconsistency, both of which I record without resolving. The ripe-723 PDF states July 2019. A separately hosted copy of the same report, the Final Report, carries a cover date of 10 May 2019 and the same fifteen numbered items. Two dates for one document is a fact about the record, and nothing in this article turns on which is right. The inconsistency is smaller and more telling: the body of section 5.0 cites recommendation 12 for task-force documentation, while the closing list assigns that subject to recommendation 13. A numbering defect in a document whose recommendations were never individually owned is not a scandal. It is a preview of how much attention each number was going to receive.

The tracker has statuses, not owners

The community tracker published under the task force's own section of the RIPE site is where the fifteen numbers currently live, Accountability Task Force Recommendations. Retrieved on 13 November 2026, it reports thirteen recommendations completed, one in progress and one pending. The completed set is 1, 2, 3, 5, 6, 7, 9, 10, 11, 12, 13, 14 and 15. The work in progress is 4. The pending item is 8.

Now the two facts that matter more than the tally. The page has no owner column. It has no target-date column. It also displays no publication or update date, which means the only date attached to the statuses is the date I read them — and the phrase "13 completed" is a description of the page at retrieval, not a compliance figure with a timestamp behind it.

The tracker is also candid about its own authority. It notes that the task force "did not necessarily expect that all of them would result in action" (tracker). That is the review body's own framing, and it should govern how the statuses are read. A completed entry on a community tracker is not a board acceptance. A pending entry is not a formal deferral. Neither proposition is established by this page.

The board record discusses tracking, never a number

The two Executive Board entries I could read are procedural, and both are more interesting for what they do not say.

The 179th Executive Board meeting minutes, covering meetings on 11–12 December 2024 and published on 30 December 2024, record at section 7.3 that "Hans Petter asked if this could be removed from future agendas with the actions added to the Board list and the Board agreed with this" (179th minutes). The requestor is Hans Petter Holen, Managing Director; the named progress reporter is Mirjam Kühne, RIPE Chair; the decision date is 12 December 2024. There is no resolution identifier and no formally assigned accountable owner. The two outstanding work areas were documenting the RIPE–RIPE NCC relationship and improving document consistency.

Read that carefully. The disposition here is an agreement about where follow-up gets tracked. It is not a substantive acceptance of any recommendation, and the minutes name no recommendation number. There is a second, sharper detail. The agreement was to add the actions to the Board list — and the action register displayed on that same page contains only EB453 and EB454, both concerning other subjects. The tracking commitment left no trace in the register it was meant to enter.

Earlier, the 159th minutes — stated date 2022/07/08, covering meetings on 30 June and 1 July 2022 — record under section 11 the RIPE Chair's update of 1 July: "The last call for the Task Force Guidelines has ended and the guidelines will soon be published as RIPE Document" (159th minutes). That is progress reported. It carries no target date, no owner and no recommendation number. Mapping it to recommendation 13 is my inference from the subject matter, and I label it as mine.

Where a date existed, the date held

One entry in this file does carry a month, and it belongs in the article precisely because it cuts against the gloom.

Section 6.1 of the 179th minutes records a planned next version of the relationship document for January 2025. The document history in ripe-838, The Relationship Between RIPE and the RIPE NCC then lists: first draft published 24 October 2024; second draft published 30 January 2025; consensus declared 7 March 2025; final version published 31 March 2025. The author is Daniel Karrenberg, the commissioning role is the RIPE Chair, and there is no board-assigned owner.

January 2025 was planned and a second draft appeared on 30 January 2025. The comparison of those two dated facts is mine; I am not claiming the minutes caused the draft. The earlier consultation deadline held too: the version 2 draft page records the first draft published on 24 October 2024 with a comment deadline of 25 November 2024.

So the machinery can carry a dated step. It does so when a person writes one down.

The test a member actually needs

Strip away the theory and an accountability review has to answer three questions per recommendation. Does it name the actor who owes the work? Does it carry the date the work is due? Is there a record matching the number to a disposition?

The report fails the first two by construction: no owners, no dates. The tracker keys a status to every number, so the third question has an answer there — but the tracker names no actor and carries no date. The board minutes carry an actor and a date but name no number. Across the whole retrieved set, no single document holds all three at once. That is the finding, and it is not an accusation. It is an auditability gap a member can verify in an afternoon.

What I could not read matters and stays scoped. The 176th, 177th and 183rd Executive Board minutes were located and did not open for me. Their contents are not obtained in this review, and a failed retrieval of a document is not evidence that its contents say nothing. No item-by-item board register of acceptance, partial acceptance, deferral or rejection was established from the documents successfully read.