(Yes, I am a Verio employee, and I have have been yelled and screamed at by more people than I care to remember over this very issue.)
Umm....actually, it *is* the way things work. Trust me, I've fought this battle many, many times. In fact, I quickly ended up making a boilerplate e-mail reply when this issue came up because it got so damn tedious typing it in all the time. Verio's policies are directly based on ARIN IP allocation rules. The policy is adjusted to account for changes in it such as the recent allocations of/20 blocks in classical A space. If ARIN gives you a block, Verio will accept the BGP announcement for it. If you get your block from another ISP, then that ISP is responsible for making sure that it aggregates the routes to meet the Verio route filtering policy. It's draconian, but it makes for a pretty clean routing table.
Slashdot Mirror
#include disclaimer.h
/20 blocks in classical A space. If ARIN gives you a block, Verio will accept the BGP announcement for it. If you get your block from another ISP, then that ISP is responsible for making sure that it aggregates the routes to meet the Verio route filtering policy. It's draconian, but it makes for a pretty clean routing table.
(Yes, I am a Verio employee, and I have have been yelled and screamed at by more people than I care to remember over this very issue.)
Umm....actually, it *is* the way things work. Trust me, I've fought this battle many, many times. In fact, I quickly ended up making a boilerplate e-mail reply when this issue came up because it got so damn tedious typing it in all the time. Verio's policies are directly based on ARIN IP allocation rules. The policy is adjusted to account for changes in it such as the recent allocations of
Shouldn't it be http://www.megatokyo.com?