IPv6 Excuse Bingo

I don't want to lose the security provided by NAT It's on our roadmap Our recursive DNS can't handle the extra load Our DDOS mitigation platform can't monitor IPv6 We would have to rewrite our entire application to support it
It's too hard to support End users don't care about IPv6 My transit provider doesn't support IPv6 IPv6 is a security risk Hex is hard
What's IPv6? IPv6 addresses are too long to remember Azure doesn't support it It's not supported by Google Compute
We can use RFC6598 There's no ROI on deploying IPv6 AWS doesn't support it What do you mean I have to wrap an IP in square brackets? We don't need that many addresses
It'll break our GeoIP Too many people have broken IPv6 stacks Our business intelligence team can't even parse IPv4 logfiles Vendor bugs IPv6 just isn't a priority
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses