The IPv4 knowledge already exists. For people who aren't network engineers, the fact that they have to learn an entirely new, complex, networking protocol and associated services is a huge pain point. I think a lot of actual experts really underestimate how much friction that presents. And that level of pain means that those people are very resistant to moving to IPv6.
Valid point but all those "not network engineers" that build networks can either fight it or implement it. Either way they have to learn it because they get exposed to it at least passively as the article calls it.
Well, they clearly have a third option because that's the one they've been taking: neither fighting nor implementing it. Thus the slow pace of adoption.
That's not an endorsement on my part at all, just a recognition of what has happened.
I confess that I'm doing the same thing in my home network -- I won't move to IPv6 until I have no other choice, because that move will take a ton of time, sweat, and tears.
Just to stave off misguided attacks on me: I am not saying IPv6 sucks and we shouldn't move to it. Not at all. But moving to it is a very expensive proposition.
Oh, now you've asked for it! I like talking about my home network. But I'll just give the 10,000ft view here.
I'll start by acknowledging that it's larger and more complex than a whole lot of networks. I have three subnets (not counting a second WiFi AP for guest use that just routes directly to the internet and bypasses my network entirely).
I have a subnet for my 4 internet-facing servers, a subnet for devices that for one reason or another aren't capable of working through my VPN, and a subnet for my general use. This is entirely encrypted using a VPN server I also run.
I have a total of around 70 different computers and devices on the network.
When I played with moving to IPv6, two things became immediately obvious to me. The first is that it will break most of what I have going on, so I'll have to go through and debug most of the systems to make them work right again. The second is that I'll need to rethink the entire network topology (except for my "lame devices" subnet -- those devices also can't use IPv6, so I'll have to maintain an IPv4 network just for them).
Rethinking the topology is probably the part that I'm least excited about, because it seems that I'll have to essentially become an IPv6 expert to design and implement that sort of change.
In any case, I anticipate at least a week of having a broken network ("broken" meaning just basic internet connectivity) while I figure all that stuff out.
Right. Those are the "trivial" cases I mentioned.