1 Oct
2016
1 Oct
'16
6:45 a.m.
The most popular allocations from ISPs I have seen are either a /48 or a /56. Since /56 is
the smallest I have found, maybe we can also use these 8-bits (bit 56 to bit 64) for a
special meaning, such as the area (K4, SV2, etc.), or the country (K, SV, etc.). That way
each person can have a ham subnet, and then maybe use the first bits of the remaining 64
to encode more information. This however breaks SLAAC, but assuming these will be
typically servers, you can configure them statically. Now about the users I am not quite
sure how it will work without resorting to solutions like stateful DHCPv6.
Antonios
On 01 Oct 2016, at 13:39, Rob Janssen
<pe1chl(a)amsat.org> wrote:
(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.
Rob
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net