My understanding was that Erik was discussing the distribution of IPv6 prefix info here, but maybe he wasn't.
When it is just about "finding who is a local gateway who would announce the IPv4 space you are in on internet, and who you can connect to", sure that could be added to the portal. As I am a coordinator for the regional network, I sometimes get requests via the portal from people who want to be on the IPIP mesh, and then explain them the alternative of connecting to our own gateway router. The portal could offer such info as an editable text for each regional subnet.
Maybe by setting up such a thing, we can then transition it into a system like I described, where the interconnects between those gateways can be made in a more modern way than we have now.
Rob
On 7/11/20 11:50 PM, Rob Janssen wrote:
I am thinking more of using BGP to distribute the info, could be used as routing info as well but not necessarily, usually one can configure BGP to store the info in a separate routing table used only for lookup in a firewall rule or similar. Everyone only needs to advertise their own IPv6 networks, and will receive all the others from the peers. No need to put all that info in a central database!
Of course you would require some BGP peers and the portal could be a source of contact info to set them up. But once you have enough peers so that the network does not split up into islands when some random participant stops, it does not require some central resource where all info is stored. And when we would have those global routers as explained in my proposal, they could run the BGP instance for this as well (and still not be essential for its operation).
Rob
On 7/11/20 11:41 PM, Erik Seidel wrote:
Make a list of HAMs who are announcing AMPRnet prefixes along with their locations and their contact info. Put it on the ampr.org portal so everybody can access it. That would be more formalized without being needlessly centralized.