IPv6 Excuse Bingo

We forgot to include IPv6 in our last RFP What do you mean I have to wrap an IP in square brackets? We would have to rewrite our entire application to support it Azure doesn't support it Android doesn't support DHCPv6
No one else has deployed it I don't want to lose the security provided by NAT End users don't care about IPv6 Can't we just buy more IPv4 addresses? Hex is hard
It'll break our GeoIP We have IPv6, but we just want to keep things simple Our vendor doesn't support it NAT444 is fine
We don't need that many addresses Those stupid Privacy Extension addresses keep changing Github doesn't support IPv6 We'll deploy IPv6 next financial year Our recursive DNS can't handle the extra load
None of our customers want it What's IPv6? IPv6 isn't supported by OVH Cloud We don't have a lab to test it Our business intelligence team can't even parse IPv4 logfiles
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses