On 21/07/19 17:42, Rob Janssen via 44Net wrote:
The above is an idea how to add IPv6 addresses to the 44.137.0.0/16 network that is BGP connected in a datacenter and where users are connected via VPN and radio paths. The added IPv6 addresses would be from the datacenter space and would be routed along the same paths as the 44.137 traffic. Of course that is suboptimal, but it works for users that do not have IPv6 themselves.
It might be better for many to use a tunnel broker where possible, but that is a fallback option. It's just that was a different situation to the bigger discussion of how to deploy IPv6 globally.
I have 2 AMPRnet IPv4 allocations - one BGP connected, one IPIP connected. Both sites have IPv6 available. Here, where the IPIP mesh terminates has a /56. I currently have a /64 on the VPS, but as
there's
only one host, it wouldn't be difficult to carve that into AMPRnet and non AMPRnet parts, because IPs are assigned by hand and are all on the same interface.
In my opinion it is not a good idea to deploy a system based on splitting a /64 net in smaller subnets. You could do that locally, but you would not want to give other local users an IPv6 network that is smaller than a /64. This is going to cause all kinds of difficulties. That is why my intention is to give every user at least a /64.
That /64 (minus 1 IP) is assigned to a single machine (it's a VPS), so this is a special case. There will never be additional machines involved (if there were, I'd request a larger block from the provider, and a good chance of getting it).