The telcos use it, ISPs use it. Cloud doesn't use it yet because AWS is backwards at migrating some of their services (eg RDS). But they support IPv6 in VPCs an

The telcos use it, ISPs use it. Cloud doesn't use it yet because AWS is backwards at migrating some of their services (eg RDS). But they support IPv6 in VPCs and for ingress/egress to the internet. Effectively they run dual stack and people are starting to realize that allocating subnets in /24 chunks is getting painful and it's much easier to allocate in /56 then /60 then /64 and that using ULAs and routing and NRDP and DNS is a much better way to do things. IPv4 in the cloud is mostly people not wanting to understand more than 10/8 and 172.16/12 and 192.168/16. IPv6 is actually easier but it requires learning about a new Layer 2/3 set of protocols. NDP is really better than arp/bootp/dhcp etc. Use SLAAC and then mDNS and DNS-SD. There was a really neat use of IPv6 on here the other day that lets you avoid the port mapping/iptables dance in K8s by treating a node as a LAN and giving each pod its own IPv6 "node area network" address. [1] [1] https://news.ycombinator.com/item?id=25245057 https://news.ycombinator.com/item?id=25245057