13 Jan
2016
13 Jan
'16
6:50 p.m.
I was one of the very early, if not original, regional coordinators (Utah
back then, Western Washington now, with a gap in between).
I don't have a problem of periodically letting someone know I'm alive --
but with the advent of portal.ampr.org it would be pretty simple to run a
query that says, 'are there requests that haven't been serviced in (time
period)' and when was the last time I logged in. If I haven't logged in
and there are waiting requests -- ping me with an email (unlikely in my
case, if I'm alive and not on a no Internet situation -- I'm online pretty
much 14 hours a day between job and personal). Allow a reasonable amount
of time for me to respond, by simply logging in.
As Brian said, this whole thread started because ONE person didn't get a
response from the designated coordinator for his area.
I like the idea of putting the portal into an open source development
environment, like GitHub. There does need to be a core team that makes
sure that features aren't stepping on each other.
The last couple of times I tried to use the dns-robot, it failed. I would
like to see the portal handle the DNS, without the need to import the old
hosts file. If people are active, they can login to the portal and setup
their DNS records. The portal could expire DNS and address entries if
someone didn't login in a predetermined time (a year or more).
Delegated DNS is also a good solution, for example HamWan.Org -- and the
overall network should handle DNS records that are not in the central
ampr.org DNS server.
On Wed, Jan 13, 2016 at 4:30 PM, VK4AA Sam <vk4aa(a)vk4aa.com.au> wrote:
> (Please trim inclusions from previous messages)
> _______________________________________________
> Sounds like parania is setting in here.
> Whats wrong with rhe system Brian started.
> This is a hobby... Your trying to make is so complex, why dont you go
> further and ask for bloid tests maybe make use of a work dongle to co-auth
> a log in, maybe even a yubiko key. Why not get even further paranoid by
> using a vlan and...
>
> Sounds way over the top to me for a hobby... It is not that we are
> protecting the crown jewels
>
> My 5c worth
> If it works dont touch it as it will destroy it
>
> Sent from my Samsung 6 Edge!
>
> -----Original Message-----
> From: Stacy <kg7qin(a)arrl.net>
> To: AMPRNet working group <44net(a)hamradio.ucsd.edu>
> Sent: Thu, 14 Jan 2016 4:27
> Subject: Re: [44net] Verifying the identities of IP coordinators
>
> (Please trim inclusions from previous messages)
> _______________________________________________
> If there is a problem with coordinators "dropping out" for various
> reasons (forgot to update contact into, deceased, etc), then there is a
> possible way to automate this:
>
> -Say every 3-6 months (maybe more, maybe less), have the ampr.org system
> send out a message to the registered coordinators address asking to
> verify/update their contact info. You could also make this a
> semi-annual affairs in like January and July (or any other two months).
> Failure to do so after 3 tries over a week or so results in a message
> being sent to a predefined address (even this list) saying that the
> automated verification system failed to receive a response from x. You
> could even go one step further and have several coordinators for the
> verification system itself which receive notification of the first
> several failed attempts at contacting a coordinator, so they can take
> steps to get in touch and keep the final messages from going out to the
> list. The possibilities are endless, and it likely would not be too
> difficult for someone with a moderate amount of <insert favorite
> scripting language for web apps here> using a database backed system to
> implement it (or add fields to the existing ampr.org databases for
> verification).
>
> This would help ensure that any "gaps" are fixed within a reasonable
> amount of time for this volunteer run project.
>
> Just my 2 cents.
>
> 73
> Stacy
> KG7QIN
>
> On 01/13/2016 09:42 AM, R P wrote:
> > (Please trim inclusions from previous messages)
> > _______________________________________________
> > what is the problem (if any at all) that the AMPR.ORG DNS have with
> so much Records in it ?
> > if there is no problem why bothering to clean it up ...
> > Ronen - 4Z4ZQ
> > http://www.ronen.org
> >
> > ________________________________________
> >
> > _________________________________________
> > 44Net mailing list
> > 44Net(a)hamradio.ucsd.edu
> > http://hamradio.ucsd.edu/mailman/listinfo/44net
>
> _________________________________________
> 44Net mailing list
> 44Net(a)hamradio.ucsd.edu
> http://hamradio.ucsd.edu/mailman/listinfo/44net
>