IPv6 Excuse Bingo

We would have to rewrite our entire application to support it Our business intelligence team can't even parse IPv4 logfiles My transit provider doesn't support IPv6 NAT444 is fine None of our customers want it
We can use RFC6598 IPv6 isn't supported by OVH Cloud Hex is hard IPv6 just isn't a priority Vendor bugs
We forgot to include IPv6 in our last RFP Those stupid Privacy Extension addresses keep changing IPv6 addresses are too long to remember I don't want to lose the security provided by NAT
Larger headers are less efficient We don't have a lab to test it It'll break our GeoIP AWS doesn't support it We have no roadmap for native IPv6 as we rolled out 6RD.
Our vendor doesn't support it No one else has deployed it There's no certification track It's on our roadmap We've still got plenty of IPv4
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses