IPv6 Excuse Bingo

It's on our roadmap We would have to rewrite our entire application to support it It's too hard to support Those stupid Privacy Extension addresses keep changing Can't we just buy more IPv4 addresses?
We'll deploy IPv6 right after we deploy DNSSEC End users don't care about IPv6 None of our customers want it Our business intelligence team can't even parse IPv4 logfiles It's not supported by Google Compute
We have no roadmap for native IPv6 as we rolled out 6RD. Our Lawful Intercept doesn't support IPv6 yet What do you mean I have to wrap an IP in square brackets? We forgot to include IPv6 in our last RFP
Our Dynamic DNS doesn't support it IPv6 is slower than IPv4 We can use RFC6598 Azure doesn't support it My transit provider doesn't support IPv6
IPv6 is a security risk It'll break our GeoIP Our recursive DNS can't handle the extra load It's not mature enough I don't want to lose the security provided by NAT
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses