This sounds similar to the goals of the NewArch project, http://www.isi.edu/newarch/ back in 2003? The original idea seems to have died with the funding?
Revolutionary? The concept isn't new. On software based router, we cache route information after the first lookup from the routing table for a certain period of time based on parameters like destination ip address, nexthop and interface. So instead of looking up the route table again, we just look up the cached route. It's called IP Flows and it's way old.
there will be additional latency and significantly more overhead involved in routing IPV6 traffic
Errmm.. I think you would actually find out that with some IPv6 features like route aggregation and the checksum-less IPv6 header, things should be faster. But yes IPv6 routing without hardware capable of switching IPv6 packets will definately be slower.
If the entire net were converted to IPV6 today, it would melt.
The only reason it's going to melt is because the majority of "IPv6 support" out there uses software-based routing
Fortunately people will likely continue to use IPV4 for a long time and the IPV6 traffic will grow slowly enough that router technology will improve as necessary.
Router technology IS already here. Most hardware vendors already support IPv6 switching.
That's if you're assuming that they're not spending most of the time waiting for approvals from various departments to touch their network products and also to schedule any equipment upgrades. I was involved once in an IPv6 pilot project for a certain government and most of the time spent was just waiting for permissions to touch various equipments. The actual task could probably be done in a day (or hour?) or a week if there's a need for equipment or topology upgrades.
And yes IPv6 is easy; easier than IPv4. Most network manufacturers now support IPv6 out of the box. If your old router does not support IPv6, most likely there will be firmware upgrade that would fix this problem. But of course to get wirespeed IPv6 switching and routing, you would need a hardware upgrade if that capability is not already present in your device.
Slashdot Mirror
When will sites learn not to store actual passwords and to just store a hash of the password.
This sounds similar to the goals of the NewArch project, http://www.isi.edu/newarch/ back in 2003? The original idea seems to have died with the funding?
I'm sure you could have a look into the code and figure out how it does it since it's open-sourced? ;)
It's just an attempt by General Failure to spy on us again... General Failure reading this, General Failure reading that ....
Where's the sandworms?
The value of an idea lies in its execution
Revolutionary? The concept isn't new. On software based router, we cache route information after the first lookup from the routing table for a certain period of time based on parameters like destination ip address, nexthop and interface. So instead of looking up the route table again, we just look up the cached route. It's called IP Flows and it's way old.
What we need is caja, http://code.google.com/p/google-caja
Try looking in the approved lists on http://www.ipv6ready.org/
Try looking in http://www.ipv6ready.org/
there will be additional latency and significantly more overhead involved in routing IPV6 traffic
Errmm.. I think you would actually find out that with some IPv6 features like route aggregation and the checksum-less IPv6 header, things should be faster. But yes IPv6 routing without hardware capable of switching IPv6 packets will definately be slower.
If the entire net were converted to IPV6 today, it would melt.
The only reason it's going to melt is because the majority of "IPv6 support" out there uses software-based routing
Fortunately people will likely continue to use IPV4 for a long time and the IPV6 traffic will grow slowly enough that router technology will improve as necessary.
Router technology IS already here. Most hardware vendors already support IPv6 switching.
That's if you're assuming that they're not spending most of the time waiting for approvals from various departments to touch their network products and also to schedule any equipment upgrades. I was involved once in an IPv6 pilot project for a certain government and most of the time spent was just waiting for permissions to touch various equipments. The actual task could probably be done in a day (or hour?) or a week if there's a need for equipment or topology upgrades. And yes IPv6 is easy; easier than IPv4. Most network manufacturers now support IPv6 out of the box. If your old router does not support IPv6, most likely there will be firmware upgrade that would fix this problem. But of course to get wirespeed IPv6 switching and routing, you would need a hardware upgrade if that capability is not already present in your device.