I worked at an (residential) ISP and not a single customer has ever asked about IPv4 or IPv9 or any IPvX. They were buying 'Internet' or even 'Wi-Fi'. Now, on on the DSL reports there are plenty of questions 'When will ISP_X will support IPV6'
> I work at an ISP and not a single customer has ever even mentioned IPv6. There zero demand on the residential side.
It is one of these things that customers who know they want it will look for an ISP that offers it. There is no point in asking one who doesn't in 2021 because they will be like "oh we will look into it", and then close your ticket.
> I am a customer, and I just filter out providers that don't have IPv6 as I assume they are incompetent.
> I wouldn't waste time asking someone to support it. It's 2021.
True. Glad to see I'm not the only one who thinks like this. The ISPs that don't support it usually have huge ancient antiquated middle boxes that can't be upgraded. I wouldn't choose an ISP with old cumbersome infrastructure.
You get plenty of requests for the static part of it and less so for actual ipv4. If there was an option for static ipv6 then people would also request that instead. Static IPs have use cases that people in the wild need, however I don’t think anyone cares if it’s ipv4 or ipv6.
My experience was that my ISP (major cell provider) silently moved everyone to IPv6, did DNS64 for most legacy stuff, and provided RFC1918 IPv4 NAT for anything else.
That is one of the most disappointing aspects of ipv6. Even if you implement it perfectly you are still stuck with having to deal with ipv4 with no end in sight. Had backward compatibility been a primary goal, is there any doubt we would have made vastly more progress at this point 20+ years later?
It's an address space expansion. You were always going to need hacky stuff for legacy clients, and for any service that wants to be reachable by said clients.
Exactly this. There is no "backwards compatible" way to have more addresses in a protocol that's wedded to 32-bit addresses. That's just how numbers work. The protocol with a larger address space will be incompatible, and so anybody who seems surprised/ disappointed hasn't even really thought about the problem.
I just got a /32 from ARIN to start implementing it on our network but it is by no stretch of the imagination worth the effort. I will probably have at least 40 hours into testing it and no increased revenue will be realized by it. Maybe IPv6 was the the right thing to due but the practical implementation is ridiculous.
I doubt you'll see more revenue from it. If you're low on v4 addresses and you're willing to put (some) subscribers behind CGNAT, then inplementing v6 should reduce the number of v4 addresses you need and thus reduce your costs.
If you give each subscriber an IPv4, then yeah, added operational cost, no revenue, maybe added capital cost depending on your equipment. Not much upside for a small ISP. In a competitive market, v6 can get you some points with the technical folks, but not many.
There's not much upside for a legacy network that already has all the IPv4 it needs, but an upstart ISP will do well starting with IPv6 and layering CGNAT IPv4 on top. With 30% of the Alexa top 500 supporting IPv6 (and a lot of the top traffic sites like Google/YouTube, Facebook/Instagram, Netflix etc) it will reduce the amount of IPv4 you need to buy