IPv6 Excuse Bingo

Our vendor doesn't support it We don't need that many addresses We can use RFC6598 Larger headers are less efficient Github doesn't support IPv6
Azure doesn't support it It's not supported by Google Compute AWS doesn't support it IPv6 isn't supported by OVH Cloud We'll deploy IPv6 next financial year
It's on our roadmap Hex is hard No one else has deployed it Too many people have broken IPv6 stacks
What do you mean I have to wrap an IP in square brackets? There's no ROI on deploying IPv6 End users don't care about IPv6 My transit provider doesn't support IPv6 Can't we just buy more IPv4 addresses?
There's no certification track We forgot to include IPv6 in our last RFP Our business intelligence team can't even parse IPv4 logfiles Android doesn't support DHCPv6 Did you mean IPTV?
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses