El 01/10/16 a las 12:39, Rob Janssen escribió:
(Please trim inclusions from previous messages) _______________________________________________
The good thing about IPv6 is that due to the large address space it's possible to make it mandatory to encode the callsign in the last 64 bits of the address. This eliminates the problem that we have in IPv4 of trying to trace back which callsign is behind an IP.
I think it basically is a good idea, but it needs to be more flexible. We would like to be able to derive the callsign from the IP, but there should be no 1:1 mapping between callsign and IP, because that would mean only a single system can be online for each callsign.
The standard should leave some bits (at least 8) available for use as "SSID" as we had in the packet days (callsign-1 callsign-2 etc), maybe also with some encoding of alphanumeric values.
Good point, Rob.
I didn't make it clear enough in my previous message, but by "callsign" I mean "callsign + SSID". What is a valid callsign + SSID depends on which system to encode callsigns in IPv6's you use.
The system I'm using: https://github.com/darconeous/ham-addr/blob/master/ham-addr.txt.md
allows the following:
* A 8-character callsign can be encoded into an EUI-48. This can be used as a MAC for an ethernet device and SLAAC will derive the IPv6 accordingly. With a 6 character base callsign such as EA4GPZ, you can use EA4GPZ-?, where ? is any character from A to Z or 0 to 9, so you get 36 possible "callsigns + SSID". Actually, you can also encode a 9 character callsign as long as the last character is H, P, X or 5, so you can get 36*5 = 180 different "callsigns + SSID" using this ugly hack.
* An 11-character callsign can be encoded into an EUI-64. This can be used directly as the last 64bits of the IP address. With 6 character base callsign such as EA4GPZ, you can use EA4GPZ-????, so you get 36^4 possible "callsigns + SSID", which I think it's already much more than anyone will neeed. Also, you can use compound callsigns such as MW/EA4GPZ/P, should anyone have the need for this.
Other systems allow for different possibilities, but the idea is to always have some sort of SSID. One IP per callsign is not acceptable. I already have a router, a server, 2 ubiquiti devices and my laptop all running under my callsing, using different SSIDs.
73,
Dani.