BGP noise tonight? (fwd)

Tue Oct 9 16:37:06 UTC 2001

On Tue, Oct 09, 2001 at 12:27:55PM -0400, Christopher A. Woodfield wrote:
> 
> As it turns out, both 2008 and 3300 are Infonet, US and Europe. So this 
> was their foo.
> 
> The problem is obviously that the RFC-proscribed behavior with bad 
> prefixes works on paper, as it serves to isolate the network originating 
> the problem prefix. However, that is totally dependent on /every/ router 
> doing so, thus preventing the problem from spreading, which as we 
> discovered, does not happen.
> 
> The ideal alternative behavior is to drop the bad prefix--not dropping 
> the peer, but not passing the bad prefix along either. I've been told that 
> there are recent Cisco IOS revs that do this instead of passing it along, 
> but they have other unresolved bugs that prevent their widespread use.
>
> Should someone think about possibly updating the RFC?

	you are stuck in the situation that operators are faced in deciding
what software to run on their network.  if the internet-draft is updated
you still need vendors to change their behavior and people to upgrade.

	- jared