IPv6 Excuse Bingo

IPv6 isn't an Internet Standard yet It's too hard to support We'll deploy IPv6 next financial year IPv6 is a security risk Our vendor doesn't support it
There's no ROI on deploying IPv6 Our recursive DNS can't handle the extra load Can't we just buy more IPv4 addresses? Our Lawful Intercept doesn't support IPv6 yet There's no certification track
We have no roadmap for native IPv6 as we rolled out 6RD. I don't want to lose the security provided by NAT What do you mean I have to wrap an IP in square brackets? No one else has deployed it
It's not supported by Google Compute NAT444 is fine IPv6 is just a fad My transit provider doesn't support IPv6 We have IPv6, but we just want to keep things simple
Larger headers are less efficient Hex is hard What's IPv6? We can use RFC6598 Azure doesn't support it
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses