IPv6 Excuse Bingo

Our vendor doesn't support it IPv6 isn't supported by OVH Cloud IPv6 addresses are too long to remember Our Lawful Intercept doesn't support IPv6 yet There's no ROI on deploying IPv6
We can use RFC6598 No one else has deployed it We have IPv6, but we just want to keep things simple It's not supported by Google Compute My transit provider doesn't support IPv6
It'll make it easier for the government to track me We forgot to include IPv6 in our last RFP Can't we just buy more IPv4 addresses? Github doesn't support IPv6
We have no roadmap for native IPv6 as we rolled out 6RD. We would have to rewrite our entire application to support it What do you mean I have to wrap an IP in square brackets? AWS doesn't support it There's no certification track
Our Dynamic DNS doesn't support it It's on our roadmap IPv6 just isn't a priority Our business intelligence team can't even parse IPv4 logfiles We've still got plenty of IPv4
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses