[106865] in North American Network Operators' Group

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

Re: Public shaming list for ISPs announcing other ISPs IP space by

daemon@ATHENA.MIT.EDU (Joe Malcolm)
Fri Aug 15 07:53:36 2008

Date: Fri, 15 Aug 2008 11:53:23 +0000
From: Joe Malcolm <jmalcolm@uraeus.com>
To: nanog@nanog.org
In-Reply-To: <20080814190917.GI53528@puck.nether.net>
Errors-To: nanog-bounces@nanog.org

Jared Mauch writes:
>	No really, the reason for some leaks isn't because so-and-so was 
>never a customer, they were.  5 years ago.  nobody removed the routes from 
>the IRR or AS-SET or <insert method here> and now the route is learned via
>some other location and it's bypassed your perimiter security and
>infiltrated your BGP.

The issue of cleaning up legacy state for former customers applies to
many things beyond route announcements - though the latter may be one
of the more visible remnants. I suspect relatively few companies can
accurately and completely track the state associated with a customer
such that it can be removed once the customer billing stops. (Or they
stop paying.) This really needs to be automated and the backend
databases need a way to associate records with particular billing
entities, or else you will find yourself slowly cleaning up after past
customers at inconvenient moments for years.

Joe


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