I'm a little disappointed you're wasting list bandwidth after this has been well discussed, and not a single post has offered a better technical alternative to de-aggregating my ARIN /20 (given my network topology).
-Ralph
Announce your largest aggregate, and announce more-specifics tagged no-export to those peers who agree to accept them?
Which is worse than announcing just the more specifics to 2 different transit providers in 2 different cities.
Upgrade the connectivity between your sites? Technically sound, economically stupid. You offering to pony up the $5K/mth for an OC3 so I can have a redundant link between Ottawa and Toronto?
Besides the technical aspects of my network, I didn't see any proof that relaxed prefix filtering (and no I'm not saying accept /32's - the more specifics I got Verio to accept were /23's) would cause significant (i.e. >30%) routing table bloat when that was recently discussed. -Ralph