29 Dec
2020
29 Dec
'20
5:15 p.m.
There where such proposals back in the 90's, with fantastic nonexisting
results.
First, assigning IPs without establishing a network topology first is
futile. You need to be able to create subnets and group users together
by topology criteria to ensure routing, not by some arbitrary callsign
rule. It would be mononeuronal to maintain hundreds of /32 addresses
instead of handling a few /24 subnets and delegating the management to
the subnet admins.
Think of it like an ISP: You hand out a static IP to a user, as long as
he is your client. If he chooses a different provider, he will get a new
IP and you would reclaim yours.
Second, these allocations should be done on a need to do basis, with a
user getting an IP for his use depending on where/how he plans to log
in/connect. It is useless to assign IPs to users which do not intend to
use them anyway. Also, unused addresses should be reclaimed and should
not linger around indefinitely.
An IP is just an IP, it does not belong to a specific callsign. The
correspondence between callsign and IP being done at DNS level. It is
not needed for a user to have a arbitrary assigned perennial IP address,
and that address should be changed according to the network needs.
Marius, YO2LOJ
On 29.12.2020 21:03, Roland Schwarz via 44Net wrote:
Marius,
On 29.12.20 at0 16:19 wrote Marius Petrescu via 44Net:
...> The main issue is to separate regular users from a backbone
infrastructure.
...
Sure, but there is something special about 44net: I believe a 44 address
should be like your callsign in the internet. This is a selling point,
and if I read the howto in amprnet where it says that more than 6million
addrsses are still unassigned I believe eberything should be done to
assign every ham a fixed IP.
So any technical solution should keep that in mind, I believe.
73 roland, oe1rsa