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
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.
ncham
Sent: Friday, 26 May 2017 5:21 p.m.
To: nznog
Subject: Re: [nznog] Reminder to update noc contact list/details
On Fri, 26 May 2017 13:31:10 +1200, Jonathan Brewer
<jon.bre...@gmail.com<mailto:jon.bre...@gmail.com>> wrote:
> An NZ-specific NOC list is not all that useful anymo
software. The recipient 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
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
>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.
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