We all know that it's a crappy argument, but lots of people try using it. Especially those who have large legacy implementations that either don't have or don't support filters on customer lines.
I agree with you. Still, the common argument is that it's to complex to maintain and to expensive to install. But again, I am sure the cost of dealing with the effects is close to the same amount. But few people realise this.
Over the years I have seen a lot of providers who let their customers advertise whatever they want into their internal route tables. I've seen
Well that is one thing. And that is plain stupidity of the operator who are putting their own network at risk. Starting to do sourceed packet filtering on ingress from customers is something else, and probably a larger task and problem. Best regards, - kurtis -