The present 44net requires each gateway to communicate directly with each other, rather than through a central hub. But I hear you, we'd be in the same boat with our own IPv6 allocation.
OH7LZB has shown a basic proof of concept, showing how to use a P12 Log of The World Digital Certificate to verify who you are. We just need to attract some talent to 44net to get someone to take that a step further. For an automated DNS so folks can register their IPv6 hosts, etc. (John K7VE has a good start, minus the automatic certificate to user account part at http://ar-dns.net/) (I think I have QRZ talked into implementing uploading your cert to become a verified user (a star on your profile for swapmeet buying confidence etc)
Maybe that is what we should be talking about. How to promote ourselves and recruit some talented coders. That is what it takes to make things happen.
https://www.youtube.com/watch?v=7anDmQQfyu8 https://github.com/hessu/ham-cert-web-demo
<snip>
Let's get away from the central-hub-oriented architecture of the 44 net, and 'go native'.
But please, we need an architecture that involves very little administrative overhead, and with as little central control as possible. The sticking point is usually in how to determine that we're allowing legal ham traffic onto the ham bands, perhaps a set of certificate-issuing facilities of some sort. This would make it possible to have a number of facilities around the globe, independent of one another, that would issue certificates that ham stations would use to identify valid ham traffic coming over the Internet. The certs would not be needed over the air, eliminating issues about ham traffic encryption laws in most countries. If a particular certificate authority became an issue, it can be invalidated. In countries like the US, each state or region could have its own cert issuer. In smaller countries with few hams, several countries might get together and have a single cert issuer, rather than one per country.