IPv6 Excuse Bingo

It's not supported by Google Compute It's on our roadmap What do you mean I have to wrap an IP in square brackets? We can use RFC6598 NAT444 is fine
IPv6 is slower than IPv4 Our Dynamic DNS doesn't support it Larger headers are less efficient I don't want to expose my MAC address Android doesn't support DHCPv6
Github doesn't support IPv6 It's too hard to support IPv6 just isn't a priority It's not mature enough
Our vendor doesn't support it AWS doesn't support it There's no ROI on deploying IPv6 IPv6 isn't supported by OVH Cloud IPv6 is a security risk
Our business intelligence team can't even parse IPv4 logfiles End users don't care about IPv6 We forgot to include IPv6 in our last RFP We don't have a lab to test it I don't want to lose the security provided by NAT
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses