[102721] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: ISP's who where affected by the misconfiguration: start using

daemon@ATHENA.MIT.EDU (Jon Lewis)
Mon Feb 25 09:32:46 2008

Date: Mon, 25 Feb 2008 09:28:47 -0500 (EST)
From: Jon Lewis <jlewis@lewis.org>
To: Hank Nussbacher <hank@efes.iucc.ac.il>
cc: nanog@merit.edu
In-Reply-To: <5.1.0.14.2.20080225092337.00ae9918@efes.iucc.ac.il>
Errors-To: owner-nanog@merit.edu


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_________

home help back first fref pref prev next nref lref last post