IPv4 exhaustion is technology’s version of chicken little and sky is failing. The sky has been falling on this for 20+ years, as we have been warned IPv4 is exhausting since the late 1990s. Here comes the IoT including Smart Home were supposed to strain the IPv4 space. I don’t know about you, but I don’t want my refrigerate and smart thermostat on the internet.
However, every time I go into AWS, I can generate an IPv4 address. Home ISP are stilling handing out static IPv4 if you are willing to pay a monthly fee. Enterprise ISP will hand you a /28 or /29 block without to much effort. Sure lots of companies, AWS, Google, Microsoft have properties on IPv6. But it’s not widely adopted. The original RFC on IPv6 was published in December of 1995.
I believe the lack of adaption is due to the complexity of the address. If my refrigerators IPv4 address is 192.168.0.33. It’s IPv6 address is 2001:AAB4:0000:0000:0000:0000:1010:FE01 which could be shorten to 2001:AAB4::1010:FE01. Imagine calling that into tech support or being tech support taking that call. Why didn’t the inventors of IPv6 add octets to the existing IP address? For instance, the address 192.168.0.33.5.101.49, would have been so much more elegant and easier to understand. I think it will take another 15-20 years before IPv6 is widely adapted and another 50 years before IPv4 is no longer routed within networks.