IPv6 Excuse Bingo

We have no roadmap for native IPv6 as we rolled out 6RD. IPv6 isn't supported by OVH Cloud I don't want to lose the security provided by NAT Github doesn't support IPv6 End users don't care about IPv6
Our DDOS mitigation platform can't monitor IPv6 We'll deploy IPv6 next financial year AWS doesn't support it It's on our roadmap It's too hard to support
Our Lawful Intercept doesn't support IPv6 yet We forgot to include IPv6 in our last RFP There's no ROI on deploying IPv6 Our business intelligence team can't even parse IPv4 logfiles
We'll deploy IPv6 right after we deploy DNSSEC We don't have a lab to test it Hex is hard IPv6 addresses are too long to remember Our recursive DNS can't handle the extra load
Azure doesn't support it Larger headers are less efficient What do you mean I have to wrap an IP in square brackets? We would have to rewrite our entire application to support it IPv6 isn't an Internet Standard yet
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses