Author: Michael Dillon
Submitted On: 17 January 2008
This is a suggestion that comes from a RIPE mailing list. As part of the evaluation of this suggestion, please ask Jeroen Massar directly for any clarifications. HIs email address is firstname.lastname@example.org
For ARIN region it would really help already a lot if they had a populated and used routing registry which was correctly cross referenced to their main whois database.
Then, if ISPs are really serious in their work, they could just start using the inetnum/inet6nums to see which prefixes should be in their routing tables, as the ones which are not registered there should clearly not be.
This can be done for the RIPE, AFRINIC & APNIC region, but not for ARIN.
Not sure about LACNIC there though.
The next ultimate step of course is routing PKI, but that definitely will never happen unfortunately.
Oh and people afraid of 'loosing their routes to important people', should of course do two things when generating filters from RIR data:
- Also have a local repository with important stuff
(eg your own and your friends stuff)
- Always manually confirm/checkup the changes ;)
(Though at some point it should be trustable)
Updated: 31 January 2008
31 January 2008
This suggested that ARIN should provide a populated and used routing registry which is correctly cross-referenced to ARIN's main whois database. This project is on our to do list. We expect to begin work later this year.