| My transit provider doesn't support IPv6 |
It's too complicated |
We would have to rewrite our entire application to support it |
Our Dynamic DNS doesn't support it |
IPv6 just isn't a priority |
| We'll deploy IPv6 next financial year |
Github doesn't support IPv6 |
IPv6 is just a fad |
We have no roadmap for native IPv6 as we rolled out 6RD. |
I don't want to expose my MAC address |
| End users don't care about IPv6 |
Our vendor doesn't support it |
 |
We forgot to include IPv6 in our last RFP |
AWS doesn't support it |
| I don't want to lose the security provided by NAT |
What do you mean I have to wrap an IP in square brackets? |
We have IPv6, but we just want to keep things simple |
Our recursive DNS can't handle the extra load |
It's too hard to support |
| There's no ROI on deploying IPv6 |
Our business intelligence team can't even parse IPv4 logfiles |
Larger headers are less efficient |
It's not mature enough |
It'll break our GeoIP |
Made with excuses from