Just have them login once a year and reup their registration.. Like they make you do for repeater coordination.. Allow a 90 day grace period and then lock it for 30 days if still no contact they obviously have abandon it.. or will return when they realize it is down.. Time frames I suggest are just that. That way no notice, no email reminders, no bother to the system or anyone.. They must login or get booted... Not trying to be mean.. but lets say ham A has died.. The portal may never know this... Lets say they changed email, no email reminder will ever reach them.. Let's say they lost interest, even an email or post card could simply get ignored..

If it's simple and the system can send an email to the Last Known Good email at say 11 Months... Fine.. Or make it a rolling 12 months from last login to the portal.. But no need to make it any more than simple..

Let's keep its K.I.S.S

73

Sorry working late and bored.. lol

-----Original Message----- From: 44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu [mailto:44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu] On Behalf Of lleachii@aol.com Sent: Tuesday, March 12, 2013 4:37 PM To: 44net@hamradio.ucsd.edu Subject: Re: [44net] Portal registrations

(Please trim inclusions from previous messages) _______________________________________________ Bill, WA7NWP,

I'm not sure this is best suggestion for many reasons:

- There was a discussion a few weeks back where it was determined that all stations do not necessarily run telnet (while having others test connectivity to my station, some were attempting to telnet to me). For example, my station is not a TNOS/JNOS based router, and therefore does not provide Converse (the telnet-based service we're referring to) by default. Under that guideline, my allocation would be purged.

- We also determined that, while all stations should make their IP addresses ping-able, that was not necessarily the case (either by intent or error).

- For various reasons, AMPRNet allocations may not necessarily be online or available through AMPR

- A Station does not necessarily have to download the encap to have a working allocation (one could manually add static routes from the portal list or use RIP44, for example)

- It would be impossible to use the download guideline for those using the RIP44 routing protocol, as it is multicast; and doesn't know what stations are receiving it or using it

We have to be mindful that all stations may not be identically configured, use the same Operating Systems, routing protocols nor system configurations to accomplish connectivity to AMPRNet.

73,

Lynwood KB3VWG

On 03/12/2013 03:00 PM, 44net-request@hamradio.ucsd.edu wrote:

Automate it for now and the future... If a client doesn't ping/poke/telnet/download or whatever within 30days/3months/whatever - purge the entry. You know - just like DHCP but at a higher level.. :)

Bill, WA7NWP

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