IPv6 Excuse Bingo

We forgot to include IPv6 in our last RFP IPv6 is a security risk I don't want to lose the security provided by NAT Hex is hard IPv6 addresses are too long to remember
It'll make it easier for the government to track me It'll break our GeoIP None of our customers want it IPv6 is just a fad Our Dynamic DNS doesn't support it
It's not mature enough Larger headers are less efficient What do you mean I have to wrap an IP in square brackets? It's too complicated
Vendor bugs We have IPv6, but we just want to keep things simple We'll deploy IPv6 right after we deploy DNSSEC NAT444 is fine We don't have a lab to test it
End users don't care about IPv6 Azure doesn't support it There's no certification track We don't need that many addresses We can use RFC6598
Made with excuses from ipv6excuses.com
Suggest a new excuse: Tweet to @ipv6excuses