Re: [nznog] Reminder to update noc contact list/details

2017-05-25 Thread Dave Mill
I completely agree. We had this discussion about a year or so ago on this list and the general consensus was: -People should use peeringDB -And we should automate the NZNOG noc list - which we received offers from people to do However, nothing has changed since. So, if someone still wants to tr

Re: [nznog] Reminder to update noc contact list/details

2017-05-25 Thread Dave Mill
My post triggered a few updates to come through which are now all complete. To be clear I am only updating the list when I receive information from the organisation itself. At this stage I am: -Not removing organisation that I don't think exist any more - I might be wrong -Generally not removing

Re: [nznog] Reminder to update noc contact list/details

2017-05-25 Thread Jonathan Brewer
Hi All, On 26 May 2017 at 09:36, Dave Mill wrote: > > -People should use peeringDB > > Yes. NZ networks are increasingly tied to Australia. An NZ-specific NOC list is not all that useful anymore. PeeringDB is the best way forward. -JB ___ NZNOG maili

Re: [nznog] Reminder to update noc contact list/details

2017-05-25 Thread Brad Pearpoint
>PeeringDB is the best way forward. Great theory until you try to update your records and they don't believe you for whatever reason and refuse to enter into any dialogue to resolve the issue! The exact quote was: Brad, I'm not in th mood to discuss our policy. Like it or leave it. ___

Re: [nznog] Reminder to update noc contact list/details

2017-05-25 Thread Gavin Tweedie
Hey Brad, I've found the peeringdb team pretty good. If you want to discuss with me off-list I can try and help you solve whatever the issue is with the peeringdb guys. I'll second that everyone should keep their peeringdb up to date. Today might be National NZ PeeringDB Update Day? :) Gavin On

Re: [nznog] Reminder to update noc contact list/details

2017-05-25 Thread Nathan Ward
Hi, > On 26/05/2017, at 9:36 AM, Dave Mill wrote: > > I completely agree. > > We had this discussion about a year or so ago on this list and the general > consensus was: > > -People should use peeringDB > -And we should automate the NZNOG noc list - which we received offers from > people to

Re: [nznog] Reminder to update noc contact list/details

2017-05-25 Thread Don Gould
Firstly, I feel the need to thank the team of you that actually got us a better broadband network than the Australians, over the past few years. I extend this thanks, on a Friday afternoon, because it doesn't make me feel bad any more about posting rubbish to lists. I do, however, consider po

Re: [nznog] Reminder to update noc contact list/details

2017-05-25 Thread Mark Foster
Don, I submit that whilst your broadcast to NZNOG had the desired effect, you could've also gone in the front door and given them a call: http://www.canterbury.ac.nz/its/contact-us/ If you were to explain to their helpdesk that email deliveries were failing, they'd have gotten someone to sor

Re: [nznog] Reminder to update noc contact list/details

2017-05-25 Thread Michael Fincham
On Fri, 26 May 2017 13:31:10 +1200, Jonathan Brewer wrote: > An NZ-specific NOC list is not all that useful anymore. For contrast, I quite like having a local list so we're not dependent on PeeringDB (which is not to say I think people shouldn't update PeeringDB, it's still useful). The Intern

Re: [nznog] Reminder to update noc contact list/details

2017-05-26 Thread Peter Ensor
: nznog Subject: Re: [nznog] Reminder to update noc contact list/details On Fri, 26 May 2017 13:31:10 +1200, Jonathan Brewer wrote: > An NZ-specific NOC list is not all that useful anymore. For contrast, I quite like having a local list so we're not dependent on PeeringDB (which is not to

Re: [nznog] Reminder to update noc contact list/details

2017-05-27 Thread Nathan Ward
ipient relies on its own > procedures and assumes all risk of use and of opening any attachments. > > > > -Original Message- > From: nznog-boun...@list.waikato.ac.nz > [mailto:nznog-boun...@list.waikato.ac.nz > <mailto:nznog-boun...@list.waikato.ac.nz>] On Behal

Re: [nznog] Reminder to update noc contact list/details

2017-05-27 Thread Matthew Moyle-Croft
ents. >> >> >> >> -Original Message----- >> From: nznog-boun...@list.waikato.ac.nz >> <mailto:nznog-boun...@list.waikato.ac.nz> >> [mailto:nznog-boun...@list.waikato.ac.nz >> <mailto:nznog-boun...@list.waikato.ac.nz>] On Behalf

Re: [nznog] Reminder to update noc contact list/details

2017-05-27 Thread Nathan Brookfield
dures and assumes all risk of use and of opening any attachments. -Original Message- From: nznog-boun...@list.waikato.ac.nz<mailto:nznog-boun...@list.waikato.ac.nz> [mailto:nznog-boun...@list.waikato.ac.nz] On Behalf Of Michael Fincham Sent: Friday, 26 May 2017 5:21 p.m. To: nzn

Re: [nznog] Reminder to update noc contact list/details

2017-05-27 Thread Simon Lyall
On Sun, 28 May 2017, Nathan Brookfield wrote: Maybe a function where someone could 'Report Incorrect Data' that then triggers an email off to the contact and if they don't respond in a timely manner flag the entry as out of date or possibly even remove it from being public until it is located.

Re: [nznog] Reminder to update noc contact list/details

2017-06-28 Thread Dave Mill
Hi all Just to prod this thread again. During late May and early June a whole lot of updates, removals and additions to the noc-list came through. I had mad dreams of tidying up the HTML (take a look, its nasty) and also linking to peeringDB records but one month on I hadn't gotten around to it.