IPv6 Excuse Bingo

My transit provider doesn't support IPv6 What do you mean I have to wrap an IP in square brackets? We'll deploy IPv6 right after we deploy DNSSEC I don't want to expose my MAC address It's not supported by Google Compute
Vendor bugs It's on our roadmap There's no ROI on deploying IPv6 IPv6 isn't supported by OVH Cloud There's no certification track
We'll deploy IPv6 next financial year End users don't care about IPv6 We can use RFC6598 NAT444 is fine
We have IPv6, but we just want to keep things simple AWS doesn't support it Our Dynamic DNS doesn't support it Our vendor doesn't support it It's not mature enough
Hex is hard Azure doesn't support it No one else has deployed it IPv6 is just a fad Android doesn't support DHCPv6
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses