> For us, customer-triggered RTBH is provided as standard for all eBGP sessions > with customers. Once they send us the right community with their own > routes, we just pass that community on to the RR's via iBGP. The RR will relay > those routes to all other devices in the network, and as long as those devices > see that community (and are permitted to act on said community), traffic to > the routes that carry the community is dropped locally on those devices. >
Sounds standard practice. > > We don't perform any ingress iBGP policy for RTBH anywhere in the network. We match incoming routes tagged with RTBH from the RR and rewrite to the appropriate next-hop "/dev/null" by address family, which it sounds a lot like what you guys do. I would consider this to be "policy". Why would you not? > > Mark. -Tim. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
