| It's not supported by Google Compute |
Vendor bugs |
AWS doesn't support it |
Our vendor doesn't support it |
IPv6 is slower than IPv4 |
| Android doesn't support DHCPv6 |
Our business intelligence team can't even parse IPv4 logfiles |
It'll make it easier for the government to track me |
Can't we just buy more IPv4 addresses? |
There's no ROI on deploying IPv6 |
| I don't want to lose the security provided by NAT |
IPv6 isn't an Internet Standard yet |
 |
It's not mature enough |
IPv6 is a security risk |
| We have no roadmap for native IPv6 as we rolled out 6RD. |
IPv6 addresses are too long to remember |
Too many people have broken IPv6 stacks |
It's too complicated |
We forgot to include IPv6 in our last RFP |
| End users don't care about IPv6 |
Our recursive DNS can't handle the extra load |
Azure doesn't support it |
Larger headers are less efficient |
Those stupid Privacy Extension addresses keep changing |
Made with excuses from