Follow up to previous post regarding SAAVIS
jared at puck.nether.net
Wed Aug 12 15:57:07 CDT 2009
On Aug 12, 2009, at 4:37 PM, Joe Provo wrote:
> On Wed, Aug 12, 2009 at 11:20:28AM -0700, goemon at anime.net wrote:
>> On Wed, 12 Aug 2009, Christopher Morrow wrote:
>>> On Wed, Aug 12, 2009 at 9:57 AM, Drew
>>> Weaver<drew.weaver at thenap.com> wrote:
>>>> Anyone know why SAAVIS would be allowing PEER1 (AS 13768) to
>>>> routes for whatever IP addresses they want?
>>> sadly savvis didn't learn the pccw lesson, which is also the
>>> turk-telecom lesson which is also the as7007 lesson which is...
>>> sad really in 2009.
>>> for the sake of $diety put a prefix-filter on your customer bgp
>>> sessions, it ain't hard!
>> sounds too much like "work" to me. not interested.
> The irony is that MCI had (and C&W maintained for quite some time)
> a functional, highly automated IRR-based customer filtering system
> [props to the Cary team]. Somewhere along the M&A highway, the
> work to maintain it was substituted with the work to dismantle it.
> Sad to see crap emitted with 3561 in the path.
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
If there were a customer portal where you could visit to say "update
my prefix-list/acl to include the following new prefix(es), and push
the change /now/" I presume that would drive customer utilization of
these services and allow people to manage things "better".
There are lots of leaks all the time, as can be evidenced by the leak
detection stuff I set up here:
More information about the NANOG