IPv6 Excuse Bingo

We would have to rewrite our entire application to support it We forgot to include IPv6 in our last RFP We can use RFC6598 I don't want to expose my MAC address We have IPv6, but we just want to keep things simple
Hex is hard Those stupid Privacy Extension addresses keep changing IPv6 isn't supported by OVH Cloud Larger headers are less efficient What do you mean I have to wrap an IP in square brackets?
End users don't care about IPv6 It'll break our GeoIP Azure doesn't support it Our vendor doesn't support it
It's not supported by Google Compute There's no ROI on deploying IPv6 We'll deploy IPv6 next financial year Can't we just buy more IPv4 addresses? Did you mean IPTV?
No one else has deployed it Android doesn't support DHCPv6 AWS doesn't support it Our business intelligence team can't even parse IPv4 logfiles IPv6 just isn't a priority
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses