On Tue, Mar 10, 2015 at 7:52 AM, TreeNet Admin <admin@treenetnz.com> wrote:
On 9/03/2015 6:36 p.m., Martin D Kealey wrote:
> On Thu, 5 Mar 2015, Tim Hoffman wrote:
>> Great that we are doing this, but what does this list offer that we cannot
>> gain from peeringdb?
> As I understand it, PeeringDB is restricted to those who are peering for
> Traffic; using *only* PeeringDB would therefore exclude people who are only
> doing "Content".

... and us little-fish Tier-4 providers who dont qualify for ASN
allocations cause theres a bigger fish providing the pipes.

> When some content provider's servers screw up and start throwing nasty
> traffic at you, it would be nice to be able to find them in the same place
> as network providers.
>
> Conversely, when their servers start getting attacked by some ISP's
> customer, they need direct access to the ISP's NOC to get the issue sorted
> promptly.
>
> Or do we all just resort to whois?

Aahh - wishes of fishes, stuff and things.


Check out http://puck.nether.net/netops/nocs.cgi.�� It's been in use in the US for years now and you can add your info regardless of size, as well as find info on other providers.

Regards,

Mike��