| NAT444 is fine |
Larger headers are less efficient |
We forgot to include IPv6 in our last RFP |
What do you mean I have to wrap an IP in square brackets? |
Our business intelligence team can't even parse IPv4 logfiles |
| We'll deploy IPv6 next financial year |
We would have to rewrite our entire application to support it |
Did you mean IPTV? |
We'll deploy IPv6 right after we deploy DNSSEC |
IPv6 addresses are too long to remember |
| Hex is hard |
End users don't care about IPv6 |
 |
Our DDOS mitigation platform can't monitor IPv6 |
It's on our roadmap |
| It'll break our GeoIP |
Those stupid Privacy Extension addresses keep changing |
Too many people have broken IPv6 stacks |
We've still got plenty of IPv4 |
Azure doesn't support it |
| There's no certification track |
It's too complicated |
We have IPv6, but we just want to keep things simple |
We have no roadmap for native IPv6 as we rolled out 6RD. |
Our recursive DNS can't handle the extra load |
Made with excuses from