I can then trivially
* put some devices on a VLAN (ie, a VOIP phone) and it will have a public IP, globally routable.
This works well in my experience, latency is super annoying on VoIP and for some reason behind a NAT sometimes it seems to route media through a third party server!
For a small business you can put a PBX on the VLAN and folks can remote register to it trivially (ie, phone.companyZ.com) - with COVID this is great.
You can VPN terminate more easily with a static ip block.
At home I can do a game server on the static IP block or I can host some of the simultaneous music composition stuff (trivially).
My question is simple - how do I get a static IPv6 block so I can do all this if I want to on IPv6.
I get IPv4 is outdated, but how do I do some of this stuff in the fancy IPv6?
You are telling me IPv6 means I don't need any public static IPs and can use some private IPv6 space (10.x was already plenty for that for me in ipv4) with a dynamic public IPv6.
Fine, how does this work. Seriously, what VPN endpoint am I configuring? How does my VOIP / SIP play with this? Do I need to go back to poking weird holes in a NAT? My OWN experience was this all doesn't play well together. Firewalls seem not to play well with dynamic prefixes - and that's just the start. Devices pick up the wrong IP's internally (SIP etc).
In short - 20 years into this, when I try to do something simple -> stick my VoIP phone on a static public IP and VLAN -> its a total pain.
At a small biz, if I try and put a PBX on a static public IPv6 - it's a total pain (and BTW - the SIP IPv6 support in most hardware and softphones is terrible).
This should be the winning use case. Phone calls / person to person audio would benefit TREMENDOUSLY from direct peering connections without any NAT!
But despite an insane number if IPv6 addresses at least in the US they won't assign you a block of even 20.