IPv6 Excuse Bingo

Larger headers are less efficient Our vendor doesn't support it We forgot to include IPv6 in our last RFP NAT444 is fine Too many people have broken IPv6 stacks
We'll deploy IPv6 next financial year We don't need that many addresses IPv6 is just a fad Github doesn't support IPv6 We'll deploy IPv6 right after we deploy DNSSEC
End users don't care about IPv6 We have no roadmap for native IPv6 as we rolled out 6RD. It's too hard to support What's IPv6?
Azure doesn't support it There's no ROI on deploying IPv6 IPv6 isn't supported by OVH Cloud It's on our roadmap It's not supported by Google Compute
AWS doesn't support it There's no certification track Our recursive DNS can't handle the extra load Did you mean IPTV? Our business intelligence team can't even parse IPv4 logfiles
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses