michael.dillon@bt.com wrote:
2) Get all the folks who are running RBLs/DUNs to update their lists when address status changes (slightly more realistic than (1)). could arin help automate this?
What about RIPE, on whose list we are posting? In any case, I went to ARIN's suggestion page here: https://app.arin.net/suggestion/ and made that very suggestion.
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) Greets, Jeroen