Good survey
I just completed it and I have some other comments.
The IPIP mesh is not plug and play, which for folks like me who are
interested in learning routing has been an invaluable learning
exercise. I hope something like this can always continue.
However there are other use cases that are more plug and play. One
being supporting internet connected infrastructure (ie. IRLP, Allstar,
DMR, D-Star etc). All of which mostly require a public IPV4 address
and the ability to port forward. Such is not the case with cellular
providers and will only become more of an issue as the global pool
IPv4 addresses shrinks. A system of geographic POP’s should be
deployed. The POP’s might want to use OpenVPN as it's well supported
and issues automated keys or the ARRL LoTW method. It would be wise
to limit the bandwidth to something modest and employ a DPI technique
to drop bittorrent fingerprints to ease overall administration.
Short of ARDC supporting POP’s, then you’re looking at outside groups
making this happen. But these will likely be service specific. Ex, I
believe IRLP has done so with some assigned address space.
Current geographic portal allocations are based on CIDR style routing.
Which makes sense if you intend to interact with existing (legacy) RF
networks. Perhaps a portal question should exist to point them to
their geographic allocation or not. If the intent is non RF or mesh,
then a different allocation methodology should be employed (next chunk
in sequence)
I’ll stress again knowing who is doing what is always good so one can
privately coordinate forwarding partners, etc, and just folks to
experiment with.
Steve, KB9MWR