IPv6 Excuse Bingo

We would have to rewrite our entire application to support it We forgot to include IPv6 in our last RFP IPv6 addresses are too long to remember Our Dynamic DNS doesn't support it Our DDOS mitigation platform can't monitor IPv6
Azure doesn't support it No one else has deployed it We have no roadmap for native IPv6 as we rolled out 6RD. Larger headers are less efficient It's too complicated
Our business intelligence team can't even parse IPv4 logfiles Vendor bugs It'll break our GeoIP We can use RFC6598
My transit provider doesn't support IPv6 Github doesn't support IPv6 Hex is hard End users don't care about IPv6 It's not mature enough
There's no certification track What do you mean I have to wrap an IP in square brackets? Can't we just buy more IPv4 addresses? Too many people have broken IPv6 stacks Android doesn't support DHCPv6
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses