Summary

  • RIPE NCC’s Q3 2026 plan says a clarified RIS peering policy is in progress after a resource-limited delay, with the aim of a relevant, diverse and sustainably sized long-term archive.
  • RIS collects volunteered BGP update and withdrawal messages through Route Collector peerings; that is an observation input, not a complete account of routes, reachability, policy or intent.
  • Public materials establish a selective approach and an unavailable online request form, but they do not disclose individual admission outcomes or a full history of selection decisions.
  • A versioned, aggregate selection receipt could join policy, criteria, constraint, coverage goal, freshness and review without exposing sensitive peer information.

A service is allowed to choose

The old instinct says that a public data service should take every feed it can get. The 2023 RIPE Labs account of selective RIS peering gives the counterargument its proper weight. More BGP data can mean more duplication, more storage and processing cost, and more material that looks abundant without materially widening the observation. A collection policy that considers country, network type, topological contribution and long-term maintenance is not an embarrassment to hide. It is a governing choice.

The current public pages already say much of this in operational language. RIS receives BGP updates and withdrawals through Route Collector peerings. Networks can volunteer the feed; RIPE NCC also actively approaches networks it judges especially useful for observation. The peering-policy page says the online request form is not available. The public peer list identifies collectors and presents current peer and route figures with a data-source time. None of this is a confession that something has gone wrong. It is evidence that a measurement archive is designed, rather than found in nature.

What follows must remain equally precise. A collector feed does not settle what every router on the Internet saw. It does not show an operator’s private routing policy, commercial intention, traffic, or all possible reachability paths. A public list of present peerings is no more a record of every earlier selection decision than a station timetable is a history of every train that was considered. The archive can be powerful without carrying claims it cannot bear.

The policy sentence and the archival consequence

The Q3 plan puts the relation plainly enough to examine. The proposed policy update links relevance and diversity with a long-term archive, while putting sustainable data growth alongside them. These are not interchangeable values. A service could favour geographic spread and lose certain topological views. It could limit redundant feeds and become less convenient for a particular analysis. It could admit a useful peer today while setting a later review because operating conditions change. The merit of a policy is not that it eliminates those trade-offs; it is that it makes their governing logic testable.

RIPE NCC’s strongest case is therefore not “trust us, the archive is broad.” It is more mature: the archive has an explicit purpose, finite resources, visible collector infrastructure and a public basis for selective peering. The weakness is narrower. A reader can see the policy direction and a current output, but cannot readily connect a policy version to the aggregate reason classes, coverage objectives, review dates and changes that shaped the archive between those two points.

Calling this a gap should not smuggle in a finding about any network. The public material does not identify a rejected applicant, and no article should invent one. It does not prove a target was missed, a region was neglected, or a decision was arbitrary. It simply leaves the reader with two valid but separate records: a policy described at one level and a peer snapshot described at another.

Make the choice legible without making it unsafe

A selection receipt could bridge those records. It would be a small public object published with the policy or in a periodic archive note. First, it would identify the policy version, the date of effect and the next review. Second, it would state the objective in plain terms: perhaps diversity of observation and long-term usefulness, subject to finite operational capacity and sustainable growth. Third, it would distinguish criterion classes from decisions: country or network-type diversity, topological contribution, redundancy, collector feasibility, and resource constraint. A category is not a dossier on an individual peer.

The receipt could then report an aggregate baseline and target, a data-freshness time, and the public page accountable for maintaining the account. A change log would say whether a criterion or proxy changed, and why at the level of policy—not why a named network was admitted or declined. A review route could identify how a stakeholder raises a question about the policy. None of these fields requires disclosure of bilateral correspondence, contact details, private topology, security assessments, or a network’s commercial reasoning.

The distinction is important. Total disclosure can make an operational policy less safe, while no durable public account makes the policy harder to criticise intelligently. A receipt finds the middle ground: enough structure to examine the archive’s public selection logic, not enough detail to turn it into a map of private operations.

An archive should retain the reasons for its shape

The decision in front of RIPE NCC is not only whether to update a page. It is whether each policy revision leaves an intelligible trace in the archive it governs. A free-standing prose policy is easy to read on the day it is published. Years later, its relation to a different peer mix, a different collector arrangement or a changed capacity constraint becomes much harder to reconstruct. A current peer list solves another problem: it tells us something about now, not how now came to be.

That is where a modest receipt has real value. It assigns neither moral guilt nor scientific finality. It preserves an evidentiary relationship between purpose, constraint, observed scope and review. Researchers can use the archive more carefully. Operators can distinguish a designed sample from a universal sensor. RIPE NCC can change its policy without asking the public to treat every earlier state as unknowable.

The irreversible risk is not that selection exists. It is that selection becomes historic fact without a surviving public explanation of what it was trying to do. A well-governed archive does not abolish discretion. It leaves a bounded record of discretion’s public rationale.

Sources

  1. RIPE NCC RIS quarterly planning
  2. RIS peering policy
  3. Two years of selective peering with RIS
  4. Routing Information Service overview
  5. RIS Route Collectors
  6. RIS public peer list
  7. RIPE NCC Activity Plan and Budget 2026