IPv6 Excuse Bingo

Too many people have broken IPv6 stacks We have IPv6, but we just want to keep things simple We can use RFC6598 Our Dynamic DNS doesn't support it We don't have a lab to test it
Can't we just buy more IPv4 addresses? Our DDOS mitigation platform can't monitor IPv6 There's no ROI on deploying IPv6 It'll make it easier for the government to track me We forgot to include IPv6 in our last RFP
Vendor bugs My transit provider doesn't support IPv6 Github doesn't support IPv6 Azure doesn't support it
Our recursive DNS can't handle the extra load Our business intelligence team can't even parse IPv4 logfiles I don't want to lose the security provided by NAT I don't want to expose my MAC address No one else has deployed it
There's no certification track What do you mean I have to wrap an IP in square brackets? We have no roadmap for native IPv6 as we rolled out 6RD. We've still got plenty of IPv4 Our Lawful Intercept doesn't support IPv6 yet
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses