imo the 'static' ip issue with ipv6 has not been solved by providers. cable internet cabals are content to use dhcpv6 to dole prefixes out, but these are the s

imo the 'static' ip issue with ipv6 has not been solved by providers. cable internet cabals are content to use dhcpv6 to dole prefixes out, but these are the same providers whos DNS servers typically post four-digit latency figures for DNS queries so the idea they they are to be the ones to solve DHCPv4's scalability issues remains laughable. just try getting a statically assigned prefix from their "business" or "corporate" offerings. wont happen. SLAAC is the best hope so far, but regular hosted customers do not understand that slaac is calculated by mac, so theyll need education to ensure immutable architectures dont crash and burn on lift-and-shift redeployments. either that, or enjoy hardcoding ip's in your prefix to the boxes. then theres networking. most corporate network engineering that would handle ingress or peer traffic to clouds (especially azure tenants) treat ipv6 as a cursory knowledge...something theyre aware of in theory but have never taken it upon themselves to practice. i predict AWS will send a lot of them scrambling for mouldy ccna texts and taking down the hybrid cloud at least twice a month until the basics sink in. and finally, firewall and security devices. There are a lot of vendors that have gotten a free pass to grandstand about how stellar their IPv6 support is, only to send customers to phone tree purgatory trying to find support for a device that either cant route between local, unique local, special purpose ranges, ::1, or even the special discard ranges for things like DDoS protection. frankly its not an AWS issue (yet) but the only guise ive seen handle this competently are...cloudflare.