Summary

  • The public directory entry for RIPE NCC Charging Scheme 2020 records it as a Switzerland-based internet registry that "performs registry functions for internet number resources", on the strength of one evidence link at confidence 0.82.
  • The page that link points to, as retained in this review, presents a numbered charging scheme under the document type label "charging scheme". The excerpt obtained contains no adopting body, no approval statement and no fee amount.
  • The instrument class is established independently: a General Meeting held 14 to 16 May 2025 adopted the RIPE NCC Charging Scheme 2026 by Resolution 9, recorded as approved.
  • Classification, not fee level, is the control surface. What a record says a thing is decides which questions a member, auditor or journalist can even ask of it.

The entry, read as written

The public entry for RIPE NCC Charging Scheme 2020 Only for Strategic Circle is not vague, and that is what makes it useful as an exhibit. It carries the alias "NCC Charging Scheme 2020", places the subject in region CH, and publishes a role sentence: "RIPE NCC Charging Scheme 2020 is a Switzerland-based internet registry, registered with RIPE NCC." The summary line repeats the claim in functional form: the subject "performs registry functions for internet number resources."

Every one of those words is a claim about an actor. A registry has a function. A registry has a territory. A registry can be registered with another registry, which is a relationship between two organisations. The entry's fields then behave the way actor records behave: they ask the reader to think about who runs this thing, where it operates and whom it serves.

Only one evidence link supports the whole structure, labelled "Public registry record evidence", carrying confidence 0.82. The overall record confidence is 0.85, and the last update shown is 2026-06-16. Those numbers describe the record's own state, not the world.

What the citation actually reaches

The cited URL is the membership payment path on the publisher's site: RIPE NCC charging schemes. The text retained from that page in this review reads, in the order it was captured, "Docs / RIPE Document Store", then "RIPE NCC Charging Scheme 2027", then "ripe-867: RIPE NCC Charging Scheme 2027", then "RipeDocument • charging scheme".

That excerpt does real work. It establishes that a charging scheme is published in the RIPE Document Store as a numbered RIPE Document, and that the store carries a document type label for exactly this class of document. It says nothing about adoption. The excerpt obtained contains no adopting body, no approval statement, no resolution date and no fee amount. It also presents the 2027 scheme year, not 2020.

A citation with that reach can support the sentence "a document of this family exists and is filed under this type label". It cannot support the sentence "this subject is an organisation that performs registry functions". Those are different claims, and the second is the one the record publishes.

Document identifiers deserve the same suspicion. In this review the ripe.net document path for RIPE-731 resolved to "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up", publication date 06 Nov 2019 — a routing-policy document. The point is not that anything is missing from the publisher's archive. The point is narrower and more useful: a number in a URL tells you a document exists, not what body adopted it or what it does.

The instrument class, established separately

The RIPE NCC charging scheme is not an obscure object. Its adoption route appears in the publisher's own meeting record. From the General Meeting May 2025 results, the retained passage reads: "The RIPE NCC General Meeting May 2025 took place from 14 - 16 May 2025. ... Resolution 9 — 'The General Meeting adopts the RIPE NCC Charging Scheme 2026.' The resolution was approved."

Read that sentence for what it is. A charging scheme is adopted by resolution of the membership meeting. It is an instrument of the membership's fiscal decision, not an operator inside the registry. The resolution is dated, numbered and recorded as approved — a document with a decider behind it.

I use that 2025 resolution as evidence of instrument class, and only that. The corresponding adoption record for the 2020 scheme was not obtained in this review. So the question a governance reader will immediately ask — which body adopted the 2020 scheme, on what date, by what margin, effective when — remains open here. An unanswered question is not a negative finding, and it is not a gap in the publisher's archive either. It is the boundary of this review.

The record contradicts itself, in public

The most interesting field in the entry is not the role line. It is the data gap: "Verify RIPE NCC Charging Scheme 2020's registry function, service territory, governance relationships, and current registry-listed role boundary."

That is a request for verification of precisely the four properties the summary and role fields already assert. The record publishes its own doubt and its own conclusion in the same breath. Whatever a reader thinks of the conclusion, the honesty of that field is not in question: the entry tells you what still needs checking.

This is where classification earns the word control surface. Fee levels are contested openly; they arrive as numbers in a document, and members argue about them in public with a resolution number attached. Classification is quieter. It arrives as a noun. Once the subject is typed as a registry, the natural next questions are operational — service territory, governance relationships, role boundary — and those are exactly the questions the data gap lists. Authority, the one question the charging scheme's adoption record actually answers, is not on that list.

What this article does not allege

Three boundaries matter more than the thesis.

The evidence reviewed here does not establish that RIPE NCC misdescribed its own charging scheme. It does not establish that any fee was levied wrongly, or that the classification was deliberate. Whether the classification was produced by an automated import or by human review is not established either. What is established is narrower: a public entry asserts a registry role, and the single citation attached to it reaches a document-store listing whose retained text contains no adopting body and no approval statement.

The 2026 scheme page is the clearest illustration of a boundary rather than a verdict. The page was identified, and its URL is real and stable; its text was not obtained in this review. So this article makes no fee-level claim at all: no amount, no category table, no effective date. Numbers read from a page nobody managed to open are the kind of thing that later turns into a correction.

The loop the classification hides

Why does a mislabelled entry matter more than a mispriced one?

Because a charging scheme determines what a member pays, and the fee determines who can afford to stay a member. Membership is not a subscription tier with a newsletter attached: it carries voting rights at the General Meeting that adopts the next charging scheme. The loop is fiscal decision, fee, membership, vote, next fiscal decision.

An entry that describes the fee instrument as an operator breaks that loop at the point where an outsider tries to enter it. Someone reading the entry to understand what this body is will be pointed at a document store. Someone reading an entry that says "adopted by resolution of the General Meeting" is pointed at a resolution, a vote and an effective period — the three things you need before you can argue with a fee.

There is a second-order effect too, and it is the one that should bother anyone who builds datasets. Type errors replicate. A classification that enters one record can enter the derivative table, the vendor feed, the due-diligence file and the comparison chart. Each copy strips a little more of the provenance, until an entry whose own data gap asked for verification reads, three hops downstream, as a bare statement that a Swiss registry exists under this name.

What would have to change

For the entry to mean something different, one thing would have to happen, and it is not a fee revision.

It would need a citation that reaches adoption, not merely existence: a resolution, a meeting outcome, an approval date. The publisher maintains such records — the 2025 results page is one, and it reads as exactly the kind of document a membership fee instrument should be sourced to. A second citation of that class, attached to this entry, would convert four asserted properties into four answerable questions, and the data gap field could be retired instead of published.

Until then, the record remains what its own fields say it is: an entry that asserts a registry role while asking someone to verify it. That is a strange thing to publish about a fee schedule. It is also, precisely, the shape of the problem this article is about.

Sources: General Meeting May 2025 results; RIPE NCC charging schemes; RIPE-731; RIPE NCC Charging Scheme 2026 page; the directory record discussed above Only for Strategic Circle.