Maintaining Consistancy Among Distributed Routing Registries

Brian Renaud

Table of Contents

• Stan Barber's Notes
• May 1995 NANOG Home Page

Stan Barber's Notes

Internal Consistency in the RABD

Routes Without Origins

There are routes without an origin. They will remain until there is evidence that they are not needed. This is also true of the widthdrawn.

Correct Maintainers

These will be fixed manually. Those that don't exist will be established if they are mailled in.

Advisory Lists with non-existent peers

These can cause problems for folks that use the advisories. This will probably be a non-issue once ANS no longer needs the advisory lines.

Multiple Registrations

Good for multiply homed. Bad when cannot delete.

Subset of Aggregate

What should the RADB do about this? It has been suggested that notification be made. RIPE-181 covers this topic.

The RA does not want to do more policing than the community wants. The RA will remove the routes without origins and correct the non-existant peers.

Enke Chen from internetMCI suggested that the acknowledgement should contain the output from whois for all RRs.

Initially, statistics will be provided on a regular basis.

It was also suggested that some consistancy checking be done across all RRs.

Consistency Between Routing Registries

Disjoint Registries is good!

However, there needs to be a precendence for duplicates.

Distributed Routing Registries

The distributed database problems really involve tool making.

Tools are available in a number of domains.