AWS doesn't support it | It's too complicated | We'll deploy IPv6 next financial year | Our vendor doesn't support it | It's on our roadmap |
IPv6 just isn't a priority | We would have to rewrite our entire application to support it | We have no roadmap for native IPv6 as we rolled out 6RD. | NAT444 is fine | It's too hard to support |
It's not mature enough | Larger headers are less efficient | It'll make it easier for the government to track me | Our Dynamic DNS doesn't support it | |
It's not supported by Google Compute | End users don't care about IPv6 | We have IPv6, but we just want to keep things simple | There's no certification track | We'll deploy IPv6 right after we deploy DNSSEC |
Too many people have broken IPv6 stacks | It'll break our GeoIP | IPv6 is a security risk | I don't want to expose my MAC address | Our DDOS mitigation platform can't monitor IPv6 |