4 ms·
Ah thanks! Does this mean that the end routers can be simpler too, or do they still need significant processing power?
by 72deluxe 13y ago
Ah thanks! Does this mean that the end routers can be simpler too, or do they still need significant processing power?
- lmm 13y agoDepends what they're doing; a typical home router isn't usually CPU-bound AFAIK. IPv6 packets can be larger, but conversely that means fewer packets for the same amount of data. Organizations that embrace IPv6 can probably simplify their networking by using globally-routable addresses for all devices (coupled with appropriate security measures - NAT qua NAT was never a security feature but it did give you an obvious single point at which to place a firewall). But I fear many companies will simply reproduce the complexities of their existing IPv4 networks in IPv6, at least initially.
- mgbmtl 13y agoOne big advantage of IPv6 is that routers will not have to deal with fragmentation. At higher debits, it should make a pretty important difference. http://en.wikipedia.org/wiki/IPv6_packet#Fragmentation http://en.wikipedia.org/wiki/IPv6_packet#Fragmentation IPv6 also deals better with packet headers, so it's easier to calculate for routers. I suspect however this will make more of a difference for high end routers with lots of traffic. As others have mentioned, the dual-stack transition does require more resources. Then again, you can implement NAT64 (or 464xlat), which seem to become more realistic/robust/more widespread solutions (running dual-stack also means managing two layers of routes, two layers of firewalls, etc). (Disclaimer: this is not my day job, I just find it lots of fun to play with on my local network and the Montreal local city mesh.)
- 1c4050b09 13y agoThey won't have to do NAT. They can just route packets. Plus, the header format is much simpler, and all fragmentation should happen at the end node.