-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
If someone will lend me appropriate /24's, I'll copy 69box.atlantic.net into 70box, 71box, etc. and come up with a large (fairly comprehensive) list of IPs behind broken bogon filters.
http://puck.nether.net/~jared/papers/69-paper.html
I can rewrite this slightly and post it on slashdot and other places again..
I think it would be useful. The "Bogon Team" implemented several changes after 69/8 to make "change management" easier. This included maintain objects at Merit RADB, RIPE NCC RADB, and a way to track via DNS (see the details on http://www.cymru.com/Bogons/index.html). Of course the biggest service CYRMU added to help people with "change management" was the Bogon Route Server (http://www.cymru.com/BGP/bogon-rs.html). So with all these "change management" tools done for the operations community, it looks like we still need some "policing" service. Note from mine and Hank's "CIDR Police" Experiment, we know that have a "list of shame" is not effective. The only way it works is if you have people who act as 'police,' use the list of shame, and knock on people's door. 90% of the time, people eventually respond and make the changes. But the impact only remains as long as you have people to go knocking on the doors. -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.3 iQA/AwUBQas4TL/UEA/xivvmEQIf9gCcCGMjrDGhKvOGMAtXoOhYy/J/CcgAniBM zT0m/7YQhl7z+qjlbqaTNXWs =dA2u -----END PGP SIGNATURE-----