IPv6 Excuse Bingo

IPv6 addresses are too long to remember NAT444 is fine There's no certification track There's no ROI on deploying IPv6 My transit provider doesn't support IPv6
Hex is hard I don't want to lose the security provided by NAT We have no roadmap for native IPv6 as we rolled out 6RD. Too many people have broken IPv6 stacks It's not supported by Google Compute
IPv6 is slower than IPv4 Vendor bugs AWS doesn't support it We'll deploy IPv6 next financial year
What do you mean I have to wrap an IP in square brackets? IPv6 isn't supported by OVH Cloud Larger headers are less efficient Our Dynamic DNS doesn't support it Did you mean IPTV?
Our DDOS mitigation platform can't monitor IPv6 It'll make it easier for the government to track me It'll break our GeoIP We can use RFC6598 Azure doesn't support it
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses