18 Jun
2015
18 Jun
'15
5:21 p.m.
Realistically, if this is a one time purge to narrow down the subnets needed for ip ip
encap as part of a migration, would it be so wrong to send out an email that says
we're planning a migration, and please login or your tunnels will not be migrated?
I'd say this if done With sufficient notice should be acceptable. Worst case, some
ones stuff breaks and they have to login and then it's back working.
Again, only if the root reason for this is to migrate off of the current architecture.
I'm not speaking to the portal in general.
On June 18, 2015 12:12:01 PM EDT, Marius Petrescu <marius(a)yo2loj.ro> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
I would propose that also any API login for a specific user should be
taken
into account.
Using API actually means that something is active behind that user.
Marius, YO2LOJ
-----Original Message-----
From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu
[mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of
Brian
Kantor
Sent: Thursday, June 18, 2015 18:47
To: 44net(a)hamradio.ucsd.edu
Subject: [44net] portal purge
(Please trim inclusions from previous messages)
_______________________________________________
At my request, we're cleaning out obsolete entries from the portal.
A reminder is sent after 3 and 6 months with no login.
A warning is sent after 9 months with no login.
A notice is sent after 12 months with no login.
After 15 months, the user, their network allocations, and any
gateways belonging to them are deleted.
At the current time, there are 3 gateways and 70 allocations to
be so deleted.
- Brian
_________________________________________
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
--
Bryan Fields
727-409-1194
http://bryanfields.net