3 ms·
how is ipv6 more complicated then ipv4? the friction comes from having to manage two different network stacks at once, not the so called complexity of ipv6. ip
by kazen44 5y ago
how is ipv6 more complicated then ipv4? the friction comes from having to manage two different network stacks at once, not the so called complexity of ipv6.
ipv4 is a mess in many ways, ARP for instance, is a disaster once you reach a certain scale and many of the ipv4 header fields are unneeded leading to inefficiencies. multicast on ipv4 is a mess, rfc1918 is a neat idea but ipv6 fixes it in a far better way and gets rid of NAT in the process. (and no, NAT does not increase security, ipv6 still has firewalls !)
in my opinion, ipv6 is the far simpler protocol, it is the migration from ipv4 to ipv6 which is resulting in all this complexity, but it is not the fault of ipv4.
and before people ask why not just extend the address space... that only solves half of the problems ipv4 has and not to mention, results in having the same dual stack situation as we have right now. extending address space is simply not possible in a backwards compatible way. and if we have to break compatibility, we might aswell fix all the other issues with ipv4.
- effie 5y agoMost people don't care about ipv4 problems, it works. Does ipv6 solves ipv4 problems such as impossibility to extend it in backwards compatible way? Say, I want 256 bit address space... can IPv6 be extended in that way?
- kazen44 5y agoIPv6 has extension options (if that is what you are asking) by using additional headers if required. Also, forward-compatible address extension is something which is simply not possible with routing protocols in place today, and i highly doubt it will be a possibility in the near or far future considering the enroumous coordination effort required between Core players on the Default-free zone and internet at large.