Re: [admin] [summary] RE: YouTube IP Hijacking

[Adrian Chadd <adrian () creative net au>]

On Tue, Feb 26, 2008, Jared Mauch wrote:

> > The problem isn't that the router config is too easy Jared, its that
> > there's no nice and easy  way of doing it right from scratch that matches
> > the sort of newbie network operators that exist today. For examples

>       The problem is that some of us have developed tools that
> are considered our companies "property", so we can't just go ahead and
> release it to the public.

I know. I even had to write some of that.

>       Who is gonna start the project to get this going?  How do you
> integrate it with your existing provisioning system?  I've regularly heard

I didn't say it had to be integrated into -existing- systems. I said
there's no nice and easy way of doing it right now -from scratch-.

> Perhaps this is something that renesys or cariden could market and sell?
> (just to name two nanog sponsors that have some sort of dataset or tools
>  that could apply).

>       I'd like to see this all cleaned up and get better.  I track
> obvious leaks that should be caught by as-path filtering and proper
> policy here:
>
>       http://puck.nether.net/bgp/leakinfo.cgi
>
>       there's a stats page one can find so you can track the number
> of leaks/day that are seen, including the most common as-paths.
>
>       if you're smart try appending ?days=3 on the end of the statistics cgi.

I can't see this linked off the NANOG wiki. So much clue out there, so
little put into the Wiki for those like me to poke with a stick.

... and its there - http://nanog.cluepon.net/index.php/InternetTools

Now comes the fun task of trying to scrape the last 12 months of NANOG
mailing list posts to find all the interesting data and tool URLs which
should really be in the Wiki.




Adrian