On Tue, Feb 26, 2008 at 10:40 AM, hjan <hjan@libero.it> wrote:
I think that they should use remote triggered blackhole filtering with no-export community. In this way they do the job with no impact on the rest of internet.
so, certainly this isn't a bad idea, but given as an example: <http://www.secsup.org/CustomerBlackHole/> (Sorry not a perfect example, but illustrates my point) instead of: ip route my.offensive.material.0 255.255.255.0 Null0 tag 12345 the operator in question (person not place) types: ip route my.offensive.material.0 255.255.255.0 Null0 tag 1234 oops, a simple cut/paste mistake means that a route didn't get tagged properly, didn't get community tagged properly, didn't get set no-export and didn't get kept internally :( There is no SINGLE fix for this, there is a belt+suspenders approach: 1) Know what you are advertising (customer side of the puzzle) 2) Know what you are expecting to recieve (provider side of the puzzle) 3) plan for failures in both parts of this puzzle. -Chris