It’s Read The Fucking Manual not Fuck The Reading Manual

Correct, the ISP would assign you a /56 of public IPs that all share a prefix which you can slice and dice into however you see fit. All devices receive a publicly routable IP which your router/firewall would limit access to. So no running out of IPs ever, no network/IP collisions if you have to connect to another private network, etc.

I always bring it up when the network is experiencing problems that they wouldn’t have with IPv6. Running out of IPs in a given scope, increasing costs of public IPs, etc.

First of all, enterprises usually have at least one public IP (the one I work at right now has more public IPs than they have server VMs)

Secondly enterprises have big enough and complex enough networks to see other benefits of IPv6. For example IPv4 has some problems when broadcast domains are too large, so your internal network sizes are artificially limited when following best practices. Without private networks you don’t have to worry about IP collisions between different private networks that you have to route between (comes up more than you’d think!) etc etc.

I’ve encountered way too many administrators and network admins who swear that “IPv6 does nothing but cause trouble” but the truth is, the trouble it’s causing is because you can’t half-implement IPv6. You either roll it out to the whole network or you don’t, and the longer you kick that can down the road the harder it’s going to be.

Basically too many professionals who haven’t learned a new technology since 2005 and refuse to try new things keep holding the world back