Good point Tim. Potentially you could use the NOC Contact list as a list of ISP’s that are operating in NZ and are part of the NZNOG community, which simply links to their PeeringDB entry. I’d imagine doing it this way could also be a way to encourage NZ ISP’s to make sure their PeeringDB is up to date as discussed at NOG? Just throwing an idea out there with the above. But I do agree with Tim that the idea of a separate contact list seems redundant. Especially given the push for NZ ISP’s to be up to date on PeeringDB... Cheers, Fraser

On 6/03/2015, at 4:04 pm, Tim Hoffman wrote:

Dave,

Great that we are doing this, but what does this list offer that we cannot gain from peeringdb?

Tim

Sent from my iPhone

On Mar 5, 2015, at 7:01 PM, Dave Mill mailto:dave(a)mill.net.nz> wrote:

...

Hi all

After our recent discussions on the (lack of) updates to the NZNOG website NOC contact list I have (foolishly?) volunteered to help. The URL of the page is http://www.nznog.org/noc-list http://www.nznog.org/noc-list .

If you have any updates, or if you have previous updates that haven't been handled, then please pass them on to noc(a)nznog.org mailto:noc(a)nznog.org . I will do my best to update in a timely manner.

Also, if you're aware of anything on the contact list that is blatantly wrong (perhaps you're still listed against a company where you no longer work) then let me know. I'll do my best to correct the information or chase up relevant contacts.

If I fail in my duties I'll produce a beer for you at the next NZNOG conference dinner..

Cheers Dave _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz mailto:NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog http://list.waikato.ac.nz/mailman/listinfo/nznog

---

NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

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". 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? -Martin

On 9 March 2015 at 18:36:23, Martin D Kealey (martin(a)kurahaupo.gen.nz(mailto:martin(a)kurahaupo.gen.nz)) 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".

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?

Hi, 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 this works. 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. asblah.peering.com 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 be outdated. 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. [1] 4) ??? 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. [1] 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 that’s fair. -- Nathan Ward

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

On Tue, Mar 10, 2015 at 7:52 AM, TreeNet Admin wrote: the US for years now and you can add your info regardless of size, as well as find info on other providers. Regards, Mike

On Fri, 13 Mar 2015, Don Gould wrote:

Given the size of our community it just staggers me that we can't just have a simple wiki page that is open and everyone can just edit.

It works like this. The NZ Internet consists of: 1. Carriers 2. Network admins at Big ISPs 3. Network admins at Little ISPs 4. Technical people involved with Networks. 5. Anyone else. NZNOG caters to groups (2) and (3). Sometimes somebody from group (1) will say something but it is a little beneath them[1] and while a bunch of people from group (4) hang around they are only tolerated as much as they support the core two groups. Now the point is that anyone from groups (2) and (3) should already have an entry in peeringdb so there is no point duplicating this work. If you are really lucky group (1) might even have an entry that goes somewhere useful. Alternative proposals will fail unless they appeal to the needs and wants of the core NZNOG group. I suspect a wiki with the cellphone number of the DNS guy at Spark[2] is not going to be something that is supported. [1] and big companies don't like their staff talking in public [2] Which 8 years ago was me & a couple of other guys :) -- Simon Lyall | Very Busy | Web: http://www.simonlyall.com/ "To stay awake all night adds a day to your life" - Stilgar