The Routing Registry Consistency Check (RRCC) project intends to help identify, correct and keep the routing data in the RIPE Database up-to-date. A coupling to the RIPE NCC's address assignment activities is also an objective of this activity.
The idea is to compare the actual state of the Internet routing tables with the information contained in the RIPE Routing Registry. Data from the Routing Information Service (RIS) Project is used to provide a view of the "actual" state of the Internet. With this information RRCC hopes to allow network administrators to easily correct their routing information in the RIPE Database.
The goals of the RRCC project are intended to focus on making the RIPE Routing Registry more useful to network engineers. In order to do this, three initial tasks have been proposed:
Additionally, the project has longer term goals:
Currently, for given ASs, the route objects representing routes that originate from the AS are checked. Routes that are present in the RIPE Database but not advertised on the Internet are detected and routes that are advertised on the Internet but not in the RIPE Database are detected.
Also, for given Autonomous Sytems, non-registered peerings are detected.
Updates are produced that can be sent to the Whois Database to fix the detected errors, if any.
"Per-maintainer reports" are provided with the email interface.
The current development target is to release the RRCC scripts that are used to implement these functionalities.
Query the RRCC Database.
You can obtain "per maintainer reports" about your inconsistencies. These reports are sent only to the owners of the maintainers. If you would like to receive the report for your inconsistencies, send an email to [email protected] containing the maintainer name in its body, the attribute type to be checked and the appropriate authentication.
attribute-type can be one of mnt-by, mnt-lower or mnt-routes.
Report will include routes that are in the range specified by inetnums and routes with this maintainer in their attribute-type attributes, and with the origins with this maintainer in their aut-num objects' attribute-type attributes.
If you supply an existing maintainer and the proper authentication, the report of the inconsistencies related to the maintainer will be mailed back to you.
If you wish to discuss the design, please contact the RRCC project at [email protected]
Please contact [email protected] with any comments or questions about this project.