Summary

  • RIPE NCC has put a resource tree on the RIPE Database website and is designing a related hierarchy and check experience for its LIR Portal.
  • A check such as “No exact match found” is useful when it reports a search result, not a verdict on the network.

An IP resource tree can look like a family reunion where half the guests arrived through an adoption, a subcontractor or an address block borrowed from an aunt. The first job of the interface is to show who sits under whom. The second is to resist calling the family suspicious because one name does not match the seating chart.

RIPE NCC has already deployed a tree view on the RIPE Database website’s Resources page. It replaces a table with a hierarchy of allocations, sub-allocations and assignments. On 21 October, RIPE Labs described a broader redesign of My Resources in the LIR Portal: select a resource and a side panel can bring together registration details, utilisation, RIPE Database objects and routing information. The Database page is deployed; the Portal design is still evolving. RIPE NCC planned usability tests at RIPE 93.

That distinction matters because the two screens are at different points in their lives. One is a live page. The other is a design being tested with members. Putting them in one sentence as if both have shipped would turn a roadmap into a release note.

The new checks aim at familiar operational questions. Is an IPv6 allocation announced but missing registered usage? Is an assignment smaller than expected? Is a registered assignment absent from routing data? Does address space appear to be in use without an assignment record? These are sensible prompts. They can save an operator from opening several tools and reconstructing a hierarchy by hand.

They also have different evidential weight. A check that compares an exact route-object match with routing information can find no exact match while a more-specific route, a covering prefix or another configuration explains what it sees. The system has found no exact match. It has not found a smoking router.

RIPE Labs gives “No exact match found” as a neutral result. That wording is doing real engineering work. “Issue” tells an operator that the system has already made a diagnosis. “To review” says the record deserves attention. The neutral label preserves the distinction between an observation and the explanation attached to it.

The design uses orange for attention, green for positive results and neutral states where the system lacks enough information to decide. That colour grammar is more than decoration. If an unchecked child resource sits below a green parent, the operator needs to know whether the child was checked, skipped or left behind because the hierarchy was too large. A green tree with silent gaps is an attractive way to hide uncertainty.

Scale makes the question practical. RIPE NCC says automated checks over large hierarchies may require many API calls. A screen therefore has to expose coverage: which resources were checked, which were not, and why. Otherwise “all clear” can mean “the query stopped before it reached the awkward branch.”

The operator’s next move should follow the evidence. A missing registration record can call for a registry correction. An unannounced assignment can call for a routing check. A possible use without an assignment can call for a conversation with the customer or the sponsoring LIR. A no-match result should first send the operator to the relevant route and registration records; it should not automatically trigger a correction ticket against an innocent prefix.

The useful promise in My Resources is not a prettier family tree. It is a shorter route from a visible relationship to the record that explains it. RIPE NCC’s own deployment note says the Database tree is live; the Labs account says the Portal design still needs member testing. The missing evidence is RIPE 93’s usability result: can operators distinguish a neutral result from an unchecked branch without opening another tool? A clear yes would make My Resources a diagnostic aid; a no would leave its colours doing the work of a warning label.

Official sources