Embed Notice

@uberbrady @risottobias Okay, show me this vaunted incompatibility that is apparently everywhere. Name me an even remotely modern operating system that doesn't support IPv6. Show me on the protocol doll which modern protocols haven't had IPv6 for years now. Show me a modern application that doesn't support IPv6 that isn't also a horrendously closed off and proprietary solution. APIs, libraries, utilities, documentation, IPv6 support is in all of it and has been for _well_ north of a decade now.

You can run dual-stack, you can run 6to4 translation, you can go full hog wild native, you can tunnel it. YOU HAVE OPTIONS FOR DEPLOYMENT, and none of them will break your shit unless you are beyond careless and clueless.

I've worked for three ISPs that have successfully deployed IPv6 to end users and core services. You know the hardest customers to get connected in v6? IT professionals who think they know networking. If it ships with IPv6 on, they will turn it off. If it ships off, it's gonna stay that way. They don't think they need it, they don't understand, and they don't want to understand it. IT professionals who don't want to learn anything new are the single biggest obstacle remaining to IPv6 adoption. I've been fighting for heavy adoption of IPv6 for over 15 years now, and the uphill battle has always been bullshit beliefs and abject laziness from barely competent IT professionals.

Don't even get me started on the blight that is the modern MSP.

Sorry if that was a bit harsh, I'm tired of this argument, plus I just got off a truly irritating phone call. You'll forgive me if I don't check for spelling and skipped words.

tl;dr: you are right, you are wrong, you are very wrong.