12 Jul
2020
12 Jul
'20
6:20 a.m.
I also firmly believe that any new service should be
dual-stack v4 and v6.
We should be encouraging the use of IPv6 as a primary goal. We could get a /32 or so from
one of the RIRs as AMPRNet v6.
Yes Rob and newcomers;
We have had discussion on trying to get a v6 allocation for ham radio
before. And even if that could happen, we'd be in the same routing
and infrastructure (data center) boat that we have now.
Conclusion:
It seems very unlikely hams will need their own allocation as the
smallest IPv6 prefix assigned to a residential connection is a /64
subnet yielding 18,446,744,073,709,551,616 hosts.
We just need a means of advertising the ham netblocks (possibly
announced by RIP/ RSS) and automatically configuring filtering (an
iptables whitelist).
A DNS to register the ham hosts in, etc. An ideal situation would be a
totally self-service DNS that uses LoTW (Logbook of the World) P12
certificates to authenticate hams, where they could then enter the
IPv6 address(es) from their residential connection that are for ham
use.
This is what I mentioned before.
On Sat, Jul 11, 2020 at 4:31 PM Rob Janssen via 44Net
<44net(a)mailman.ampr.org> wrote:
IPv6 has been discussed before, and I think the predominant opinion is
that we should NOT get a /32 for
an IPv6 version of AMPRnet (and get the same routing issues as we now
have for IPv4), but rather we
should encourage everyone to get IPv6 space from their own ISP or from a
local IPv6 tunnel provider,
and then devise some way to communicate our IPv6 subnets to eachother
(so they can be used to
further trust some IPv6 source addresses as being from fellow AMPRnet
users) and maybe even route
them over our own network.
Rob
On 7/11/20 11:10 PM, Jason McCormick wrote:
We should be encouraging the use of IPv6 as a
primary goal. We could get a /32 or so from one of the RIRs as AMPRNet v6.
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net