IPv6 Excuse Bingo

We don't have a lab to test it AWS doesn't support it It's not supported by Google Compute Android doesn't support DHCPv6 Github doesn't support IPv6
End users don't care about IPv6 Our recursive DNS can't handle the extra load We'll deploy IPv6 right after we deploy DNSSEC We don't need that many addresses Our business intelligence team can't even parse IPv4 logfiles
It's on our roadmap Did you mean IPTV? Larger headers are less efficient Azure doesn't support it
IPv6 addresses are too long to remember It's too hard to support It's not mature enough We have IPv6, but we just want to keep things simple Hex is hard
We have no roadmap for native IPv6 as we rolled out 6RD. NAT444 is fine I don't want to expose my MAC address IPv6 isn't supported by OVH Cloud What do you mean I have to wrap an IP in square brackets?
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses