| Our DDOS mitigation platform can't monitor IPv6 |
We'll deploy IPv6 right after we deploy DNSSEC |
Larger headers are less efficient |
None of our customers want it |
AWS doesn't support it |
| It's too hard to support |
There's no certification track |
Android doesn't support DHCPv6 |
IPv6 addresses are too long to remember |
Too many people have broken IPv6 stacks |
| We can use RFC6598 |
End users don't care about IPv6 |
 |
There's no ROI on deploying IPv6 |
We have IPv6, but we just want to keep things simple |
| NAT444 is fine |
We don't need that many addresses |
Our recursive DNS can't handle the extra load |
It's on our roadmap |
It's too complicated |
| It's not supported by Google Compute |
It's not mature enough |
Did you mean IPTV? |
We don't have a lab to test it |
It'll break our GeoIP |
Made with excuses from