

Why does so many network engineers don't like IPv6?
Hi @ll
short introduction to myself: I'm systems engineer with main focus on mail, virtualization and server infrastructure. More on Windows than on Linux. 20 years ago I did some Cisco certifications (CCNA, CCNP and CCSP if I recall correct) but never really practiced it in my professional career. Long story short: I understand some things when it comes to network ;-).
In my private life I do homelab stuff (at home around 30 devices - in DC 250 VMs + Container) of cause, I'm LIR at RIPE, have my own ASN, IPv4 and IPv6 and play around with that (a bit more) and spread part of my infra to family and friends.
Recently I talked to some of my colleagues (four in total) which are network engineers in our company (200k employees world wide - network is a serious business here) and had questions about IPv6 and how I may approach splitting prefixes etc. The first response was almost immediately and everytime "IPv6, wtf!?" followed by complaints about "Plug&play network - lol?", "SLAAC wtf!", "Never left beta state" and the best was "Is a bit like SMTP, you'll never get this to work properly". Today I had a conversation with one of these guys because we need to get our mail gateways to speak IPv6 in the next couple of months and his response was also something like "Yeah, let's do this, but we must do NAT to IPv4" (we don't to IPv6 internally). Really?!
I have other discussions like that with network engineers outside our business, so it's not limited to our company.
Maybe I oversee some major things but when I implemented IPv6 in my own environment, I was like "wtf, is that cool! Oh, and I don't need to do the shitty NAT stuff anymore - global routable".
What do I miss?
Edit: Typo