Reality Checking of the RIPE Routing Registry

Joachim Schmitz, JS395-RIPE

Presentation at RIPE 32


Use of the RIPE database

Data submission is either

depending on data type.

A database only makes sense if data is

What is stored in the RIPE db?

allocation registry A
routing registry R
both B

registry object uptodate? comment
A inetnum
IP address allocation
ok controlled resource
A domain
- RIPE is no domain registry
R route ? subject of investigation
R inet-rtr, as-macro, comm
or equivalent RPSL objects
used in conjunction with
policy descriptions
B autnum
> AS number allocation
> routing policies (RIPE-181 or RPSL)
controlled resource
subject of investigation
B maintainer ok mandatory at RIPE for allocations
B person, role
- can of worms

Checking status of routing/policy data

Are these groups uptodate?

Do we care?

Disregarding internal networks and private peering, routing information on the Internet is essentially public (traceroute, looking glass...). It must be public because otherwise networks would not be reachable, meaning that at least the basics of routing policies are known.

If things go wrong the IRR is a perfect reference as long as data are properly registered. Then, it may also be used for building configurations.

Even though in general nobody is obliged to register routes and policies, many big providers demand that their peers properly register. This information is then actually used to install filters at least on the boundary routers.

Scope of Checking?

How to check?

Routing information on the Internet and registry data have different formats. To compare both sets

and analyze the lists.

What to check?

directly from the Internet

Which tools are available?

Who checks?


Project Proposal for the RIPE NCC

Joachim Schmitz, JS395-RIPE, 27-Jan-1999, RIPE-32, Amsterdam, NL