5 ms·

Transitioning to native IPv6 requires running dual stack for quite some time, we'll never get there if we don't start

• tialaramex 7y ago
  Not necessarily. A network can go entirely IPv6 internally and just have adaptors at the edge to translate parts of the Internet that aren't IPv6 yet. Doing this means all IPv4 network addressing headaches vanish internally. Oh there are going to be 260 remote offices instead of 100 like you said at the kick off meeting? No problem, my subnets are easily big enough either way. And with this approach your budget for the edge reduces over time as more of the network supports IPv6, whereas with a NAT gateway your budget increases as throughput rises. You do need to be really firm during purchases, if the "IPv6 support" in that shiny new product is actually more of a wishlist item than an actual feature, you're getting a full refund, no second chances. That goes for desk phone (if your outfit still has those), printer/ copiers, IoT devices, and everything.
• koolba 7y ago
  I’ve heard some variant of that for over two decades and still here we are.
  • kitteh 7y ago
    In the early 2000s the issue was the routing hardware did ipv6 shitty. That took a few years to get to a better spot (and a few years more to get it almost at IPv4 parity feature wise). Then it took a few more years for transit providers to roll it out...then the broadband networks. Now we're in a time when v6 support is mixed across cloud companies and there are large swaths of geographical areas that are lagging (sup Central and South America + china). Were closer...