Last week, our IXP Manager at Rheintal IX was upgraded to the latest version and our Route Servers have been migrated to bird2. After the test operation in the last weeks, the Resource Public Key Infrastructure (RPKI) extension was successfully rolled out and activated on our route servers in the course of the upgrade.
Since the changeover, all announcements made by peering participants to our route servers are no longer checked for their existence exclusively via the IRR databases (RIPE, ARIN, RADB, etc.), but are now also validated for the legitimacy of the announced origin AS using RPKI Route Origin Validation (ROV). Invalid announcements are automatically filtered by our route servers to prevent false routing information from being redistributed to other route server peers. Announced Bogon prefixes, prefixes without corresponding route/route6 objects in the common IRRDBs (RIPE, ARIN, RADB, etc.) as well as prefixes with invalid Route Origin Authorization (ROA) or RPKI validation status INVALID are filtered.
The validation status for individual prefixes can be viewed via our BGP Looking Glass.
