Re: ISP's who where affected by the misconfiguration: start using IRR and checking your BGP updates

At 12:13 AM 25-02-08 +0100, Mikael Abrahamsson wrote:

>For us who actually have customers we care about, we
probably find it 
>better for business to try to make sure our own
customers can't announce 
>prefixes they don't own, but accept basically anything
from the world that 
>isn't ours.

You are a distinct minority.  My experience has shown that
most ISPs don't 
give a sh*t about filtering what their customers can
announce so what has 
happened, will continue to happen.

-Hank

On Mon, 25 Feb 2008, Hank Nussbacher wrote:

>> For us who actually have customers we care about,
we probably find it 
>> better for business to try to make sure our own
customers can't announce 
>> prefixes they don't own, but accept basically
anything from the world that 
>> isn't ours.
>
> You are a distinct minority.  My experience has shown
that most ISPs don't 
> give a sh*t about filtering what their customers can
announce so what has 
> happened, will continue to happen.

I've only dealt with a handful of the bigger networks, but
every transit 
BGP session I've ever been the customer role on has been
filtered by the 
provider.  From memory and in no particular order, that's
UUNet, Level3, 
Digex, Intermedia, Global Crossing, Genuity, Sprint,
Above.net, Time 
Warner, C&W, MCI, XO, Broadwing, and a few smaller ones
nobody's likely to 
have heard of.

As an ISP providing transit, all of our customers get
prefix-filtered.

------------------------------------------------------------
----------
  Jon Lewis                   |  I route
  Senior Network Engineer     |  therefore you are
  Atlantic Net                |
_________ http://www.lewis.org
/~jlewis/pgp for PGP public key_________