| It'll break our GeoIP |
My transit provider doesn't support IPv6 |
Our business intelligence team can't even parse IPv4 logfiles |
What do you mean I have to wrap an IP in square brackets? |
IPv6 just isn't a priority |
| It's not supported by Google Compute |
We'll deploy IPv6 right after we deploy DNSSEC |
We forgot to include IPv6 in our last RFP |
It'll make it easier for the government to track me |
We have no roadmap for native IPv6 as we rolled out 6RD. |
| We have IPv6, but we just want to keep things simple |
We don't have a lab to test it |
 |
IPv6 is just a fad |
Azure doesn't support it |
| Our Dynamic DNS doesn't support it |
Those stupid Privacy Extension addresses keep changing |
IPv6 isn't an Internet Standard yet |
We've still got plenty of IPv4 |
There's no ROI on deploying IPv6 |
| AWS doesn't support it |
IPv6 is slower than IPv4 |
There's no certification track |
We don't need that many addresses |
NAT444 is fine |
Made with excuses from