IPv6 Excuse Bingo

There's no ROI on deploying IPv6 Android doesn't support DHCPv6 Can't we just buy more IPv4 addresses? Github doesn't support IPv6 Vendor bugs
End users don't care about IPv6 We would have to rewrite our entire application to support it We forgot to include IPv6 in our last RFP Our Lawful Intercept doesn't support IPv6 yet Too many people have broken IPv6 stacks
We've still got plenty of IPv4 IPv6 isn't supported by OVH Cloud My transit provider doesn't support IPv6 AWS doesn't support it
Our vendor doesn't support it It'll break our GeoIP Our business intelligence team can't even parse IPv4 logfiles It's not mature enough It's too complicated
We have no roadmap for native IPv6 as we rolled out 6RD. We can use RFC6598 What do you mean I have to wrap an IP in square brackets? I don't want to expose my MAC address IPv6 isn't an Internet Standard yet
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses