IPv6 Excuse Bingo

Vendor bugs Did you mean IPTV? What do you mean I have to wrap an IP in square brackets? My transit provider doesn't support IPv6 IPv6 addresses are too long to remember
Our business intelligence team can't even parse IPv4 logfiles It's on our roadmap We don't have a lab to test it IPv6 is a security risk IPv6 isn't supported by OVH Cloud
Too many people have broken IPv6 stacks There's no certification track It'll break our GeoIP We have IPv6, but we just want to keep things simple
NAT444 is fine Those stupid Privacy Extension addresses keep changing Azure doesn't support it It's too hard to support Our recursive DNS can't handle the extra load
IPv6 is slower than IPv4 There's no ROI on deploying IPv6 We can use RFC6598 We'll deploy IPv6 right after we deploy DNSSEC We'll deploy IPv6 next financial year
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses