| NAT444 is fine |
It's not supported by Google Compute |
Hex is hard |
Our business intelligence team can't even parse IPv4 logfiles |
We have no roadmap for native IPv6 as we rolled out 6RD. |
| It's too complicated |
It's not mature enough |
We have IPv6, but we just want to keep things simple |
We don't need that many addresses |
There's no certification track |
| Too many people have broken IPv6 stacks |
IPv6 addresses are too long to remember |
 |
AWS doesn't support it |
Our DDOS mitigation platform can't monitor IPv6 |
| IPv6 is just a fad |
Azure doesn't support it |
We've still got plenty of IPv4 |
There's no ROI on deploying IPv6 |
We forgot to include IPv6 in our last RFP |
| IPv6 is a security risk |
Our Lawful Intercept doesn't support IPv6 yet |
I don't want to lose the security provided by NAT |
We would have to rewrite our entire application to support it |
We can use RFC6598 |
Made with excuses from