IPv6 Excuse Bingo

We can use RFC6598 We'll deploy IPv6 next financial year Our DDOS mitigation platform can't monitor IPv6 Too many people have broken IPv6 stacks There's no certification track
I don't want to lose the security provided by NAT We forgot to include IPv6 in our last RFP It's not mature enough IPv6 is just a fad Those stupid Privacy Extension addresses keep changing
IPv6 just isn't a priority IPv6 addresses are too long to remember Azure doesn't support it IPv6 isn't supported by OVH Cloud
Our vendor doesn't support it It's too hard to support My transit provider doesn't support IPv6 We have IPv6, but we just want to keep things simple AWS doesn't support it
Our Lawful Intercept doesn't support IPv6 yet IPv6 isn't an Internet Standard yet Can't we just buy more IPv4 addresses? Our recursive DNS can't handle the extra load We have no roadmap for native IPv6 as we rolled out 6RD.
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses