1 Feb
2013
1 Feb
'13
7:51 a.m.
This seems reasonable for recovering allocations, but how do you deal with coordinators
that go silent and stop processing requests for their area?
Are regional coordinators really necessary, can't the blocks be managed centrally with
an automated system, as long as the block being requested are within some specific
guidelines?
Bob
________________________________
From: Chris Smith <chris(a)g1fef.co.uk>
To: w7szs(a)noapra.org; AMPRNet working group <44net(a)hamradio.ucsd.edu>
Sent: Friday, February 1, 2013 4:38:42 AM
Subject: Re: [44net] Coordinator Privileges on Amprnet Portal
(Please trim inclusions from previous messages)
_______________________________________________
Hi David,
A couple of issues that I see coming down the line as
a regional coordinator.
1. Persons receiving an allocation disappear after a period of time, abandoning the
allocation in the process, and don't release the allocation. There is no apparent
method for the regional coordinator to attempt contact with the person and or release the
allocation if the person cannot be contacted or found.
This is already addressed in the new system: After a suitable period of time following the
initial allocation, the system will email the end user of the allocated subnet with a link
asking them to click on the link to confirm they are still active and using the IP's.
For anyone not wishing to click on a link in an email, the email will also advise them
that they can login to the portal as usual to confirm their ongoing use of the subnet.
If there is no response, a second email is sent a while later, this time an email is also
sent to the co-ordinator, so they are aware that the first contact attempt timed out. The
co-ordinator may be able to assist at this point by giving the person a
"nudge".
If the second email gets no response, a third email is sent to both end user and
co-ordinator, advising that the allocated subnet has been de-activated, but that it can be
re-activated if they respond to the email.
At this point the subnet is removed from any gateways and DNS, but remains in the database
as a de-activated entry.
After a suitable period of time a final email is sent to user and co-ordinator advising
them that the subnet has been deleted and returned to the pool.
Regards,
Chris
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html