[116656] in North American Network Operators' Group
Re: Follow up to previous post regarding SAAVIS
daemon@ATHENA.MIT.EDU (Justin Shore)
Wed Aug 12 17:14:24 2009
Date: Wed, 12 Aug 2009 16:12:39 -0500
From: Justin Shore <justin@justinshore.com>
To: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <ACC05272-318E-4E81-A48C-3CE22AA2F943@puck.nether.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>, nanog-post@rsuc.gweep.net
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Jared Mauch wrote:
> I've come to the conclusion that if someone put a nice web2.0+ interface
> on creating and managing these objects it would be a lot easier.
I've looked into IRR several times, usually after events like PCCW.
Each time the amount of work to 1) figure out how to implement IRR and
2) actually implementing it far outweighed the benefit of doing it for
my network. I would love to implement it and looking towards the future
I will someday have to. Until it becomes much easier to do so, I don't
foresee smaller SPs like myself allocating the necessary resources to an
IRR project until we're forced to because of our individual growth or an
idiot PCCW-type event that generates lots of bad PR.
> There are lots of leaks all the time, as can be evidenced by the leak
> detection stuff I set up here:
>
> http://puck.nether.net/bgp/leakinfo.cgi
Crossing fingers hoping I'm not in that list...
Justin
