On Jan 3, 2013, at 4:19 PM, Jeff Wheeler wrote: > On Thu, Jan 3, 2013 at 3:18 PM, Robert Raszuk <[email protected]> wrote: > > How are you going to clean the NLRIs in your network (both transit or > > stub) which were withdrawn in the messages your BGP implementation > > declared "bad" and decided to ignore ? > > I can fix them later, maybe even after I've had time to fully analyze the > problem and get a software update from my vendor. Maybe I'll try a refresh > or a session-reset, but I won't be at the mercy of repeatedly flapping > session and phone ringing off the hook with angry customers!
They're going to complain no matter what. Also, if you're not a fully-peered DFZ ISP, perhaps you don't need full routes to make your decisions anyways. I am sympathetic to a point, but either way someone has to look at the problem and correct it (likely with a code spin) assuming you don't take the offending device offline. This is the shared fate everyone has in the BGP world for the distributed online database we operate. Also, if you're seeing some problem, I'm sure that some other set of people out there will be seeing it as well. The shared pain/cost will exist. If you can't take the risk of speaking BGP, have your ISP send you default (or nothing) and advert your prefixes and call it a day. - jared _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
