On 9 March 2015 at 18:36:23, Martin D Kealey
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
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
Or do we all just resort to whois?
I was the person who Jamie referred to as sticking up their hand to help. I think my
solution addresses your issues for the most part. It does still favour (though not limit
the list to) people eligible to participate in PeeringDB, though I expect that there’s
only a handful of people who should be on the NOC list who don’t have ASNs, so I think
I had originally intended to pull data from PeeringDB (they publish a big MySQL dump,
though the JSON thing that Jon mentioned will be nice), but then we’d get in to a fight
about publishing details and opt in/out and all that sort of thing and we wouldn’t
actually do anything. Given this discussion came up because of outdated information in the
NZNOG phone tree, I figure the best way is to just link to people’s PeeringDB entries in
place of their normal contact details, then automate some process that pops up new
PeeringDB entries that relate to NZ, and I’ll email them.
links do not require authentication.
Anyway, a week or so back I suggested this to Jamie, and he gave me access to poke the
website. At the time, I talked to him about this being the re-producing details thing and
haven’t mentioned my new plan to him, so, Jamie - if you’re not keen on the new thing and
would rather it be the data rather than links to PeeringDB, drop me a line and we can
figure out how to make it work.
Failing that, it is my intention to (starting this week):
1) Immediately, add PeeringDB links, and leave existing other info, but note that it might
2) Immediately, start monitoring PeeringDB for new people that might want to be on the
NZNOG list, and I’ll email them.
3) In say 2 months, I’ll remove all the existing info from people who I’ve added PeeringDB
links for, and along with it the “this might be outdated” note. If you want me to do
something different for you, get in touch with me in the mean time - let me know if you
want me to leave out a PeeringDB link, or if you want me to leave in some NZNOG specific
details, or whatever. 
5) Profit. Maybe I’ll sell your details to a spam list and make millions. Maybe some
second hand network equipment company will want them. I’ll think of something.
This email address is a fine way to reach me, and I’ll reach out to whatever email address
people have listed on the NZNOG page as well when it comes time for (3).
In the future I’ll likely note whether people have LGs or route servers listed as part of
the automated process - but again, refer to PeeringDB for the actual details.
 If you have a PeeringDB entry, and opt to do something different to the default of
having just it listed, you don’t get to complain about update times in the future. I think