Andrei Robachevsky, Shane Kerr. APNIC/APRICOT2001, February 2001, Kuala Lumpur, Malaysia. 1 Routing Registry Consistency Check Presented by Andrei Robachevsky RIPE NCC

Andrei Robachevsky, Shane Kerr. APNIC/APRICOT2001, February 2001, Kuala Lumpur, Malaysia. 2 Introduction RIPE IRR routes 4000 autonomous system numbers Quality of data varies widely Some require peers to use IRR - high quality Others used IRR historically - low quality Compare IRR with the Internet Identify problems Help correct problems

Andrei Robachevsky, Shane Kerr. APNIC/APRICOT2001, February 2001, Kuala Lumpur, Malaysia. 3 RIPE Routing Registry routes, 4000 aut-num’s 55% are not announced 60% are “foreign” (non-RIPE ASN or/and IP space) Internet RIPE IP/ASN space RIPE RR

Andrei Robachevsky, Shane Kerr. APNIC/APRICOT2001, February 2001, Kuala Lumpur, Malaysia. 4 Goals Track, report on, and increase accuracy of IRR data Track and report IP allocation usage in the Internet Develop tools to improve user interaction with the IRR Disseminate tool and user information

Andrei Robachevsky, Shane Kerr. APNIC/APRICOT2001, February 2001, Kuala Lumpur, Malaysia. 5 Routing Data The IRR records two types of data: Routes Routing Policies These are represented by: route objects, describing which AS originates each prefix aut-num objects, describing routing policies inet-rtr, as-set, route-set, etc., help describe routing policies

Andrei Robachevsky, Shane Kerr. APNIC/APRICOT2001, February 2001, Kuala Lumpur, Malaysia. 6 Comparison The main source of live data for this project is the RIPE NCC’s Routing Information Service Project.Routing Information Service Project Route advertisements RIPE database and Internet match Only in RIPE database or on Internet RPSL policy and AS paths Missing import or export attributes Cannot find unneeded import and export attributes Allocation Registry checks

Andrei Robachevsky, Shane Kerr. APNIC/APRICOT2001, February 2001, Kuala Lumpur, Malaysia. 7 Reporting and Tools Information will be available through web site and/or subscription General IRR consistency report in summary form Specific IRR consistency report Search for detailed information based on: AS number(s) IP address space Maintainer (mnt-by, mnt-routes, mnt-lower) Report on-demand, periodic, or monitoring Router configuration checker “Correction Wizard”

Andrei Robachevsky, Shane Kerr. APNIC/APRICOT2001, February 2001, Kuala Lumpur, Malaysia. 8 Project Status Compares RIS mrt dump with RPSL SQL dbase currently 2 locations with over 50 peer AS’s over 140k routes Determines mismatches between Internet and IRR Generates text reports Builds database Prototype interface available for specific report Prototype of “Correction Wizard” available

Andrei Robachevsky, Shane Kerr. APNIC/APRICOT2001, February 2001, Kuala Lumpur, Malaysia. 9 Demo Visit RRCC web page: Go to “Test Site” and follow link to test the prototype.

Andrei Robachevsky, Shane Kerr. APNIC/APRICOT2001, February 2001, Kuala Lumpur, Malaysia Next Steps Polishing and Finishing Current Software Regularly refresh with RIS data Complete logs of access Produce statistics to measure improved quality of data Analysis based on network IP ranges or maintainers Subscription services Publishing RIPE-201 Seeking community input

Andrei Robachevsky, Shane Kerr. APNIC/APRICOT2001, February 2001, Kuala Lumpur, Malaysia Possible Directions View from specific Route Collectors? Check aut-num policy with AS paths? Router configuration verification? Work with other IRR sites? Check other RIPE database information (e.g. recorded versus announced inetnum ranges)? Can send to if Questions or suggestions - input desired.

Andrei Robachevsky, Shane Kerr. APNIC/APRICOT2001, February 2001, Kuala Lumpur, Malaysia Questions?