| What do you mean I have to wrap an IP in square brackets? |
Too many people have broken IPv6 stacks |
There's no certification track |
Our DDOS mitigation platform can't monitor IPv6 |
We forgot to include IPv6 in our last RFP |
| AWS doesn't support it |
I don't want to expose my MAC address |
There's no ROI on deploying IPv6 |
It's not supported by Google Compute |
I don't want to lose the security provided by NAT |
| Our vendor doesn't support it |
NAT444 is fine |
 |
It's not mature enough |
We've still got plenty of IPv4 |
| We have no roadmap for native IPv6 as we rolled out 6RD. |
Android doesn't support DHCPv6 |
Did you mean IPTV? |
IPv6 addresses are too long to remember |
IPv6 is slower than IPv4 |
| IPv6 isn't an Internet Standard yet |
Our business intelligence team can't even parse IPv4 logfiles |
We'll deploy IPv6 next financial year |
IPv6 just isn't a priority |
We can use RFC6598 |
Made with excuses from