This seems reasonable for recovering allocations, but how do you deal with coordinators that go silent and stop processing requests for their area?

The same process occurs, the regional co-ordinators and above them, the country co-ordinators are seen by the system as "responsible" for the subnet allocated to them. If a regional or country co-ordinator fails to respond and there are allocated addresses within their subnet obviously the subnet is not de-activated or deleted, however the responsibility does pass to the next level up.

If a regional co-ordinator failed to respond the subnet defaults back to the country co-ordinator, who can then attempt to find someone else to look after the region.

Ultimately, if a country co-ordinator fails to respond, the country's subnet would default back to Brian, who then has to try and find a new country co-ordinator.

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?

Countries vary in their setup, some just have one person that looks after the entire subnet, others, e.g. the US have regional co-ordinators to spread the workload, some have specific rules for allocating IP's, and so on. All the portal is trying to do is maintain an up to date list of what IP's are being used and who is responsible for them, how they are allocated is up to the country's co-ordinator, who are we to dictate how a country is to allocate their IP's?

Regards,

Chris

Bob

From: Chris Smith <chris@g1fef.co.uk>
To: w7szs@noapra.org; AMPRNet working group <44net@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@hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html

_________________________________________
44Net mailing list
44Net@hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html