IPv6 Excuse Bingo

There's no certification track Our business intelligence team can't even parse IPv4 logfiles IPv6 addresses are too long to remember Those stupid Privacy Extension addresses keep changing I don't want to lose the security provided by NAT
We can use RFC6598 End users don't care about IPv6 IPv6 isn't supported by OVH Cloud We have no roadmap for native IPv6 as we rolled out 6RD. Our recursive DNS can't handle the extra load
We forgot to include IPv6 in our last RFP We don't have a lab to test it IPv6 is slower than IPv4 It's not supported by Google Compute
No one else has deployed it We have IPv6, but we just want to keep things simple IPv6 isn't an Internet Standard yet I don't want to expose my MAC address It's too complicated
Our Lawful Intercept doesn't support IPv6 yet It's not mature enough Larger headers are less efficient Our vendor doesn't support it 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