A Radical New Router
spectrum.ieee.org
spectrum.ieee.org
If they truly have solved the problem(s) that other flow-based routers had, great, but this can only be determined in the real world.
The illustration states that P2P traffic is problem to be solved by this router. Article also states: "How Flow Routing Works
Flow managers keep track of streams of packets and can protect voice and video transmissions while reducing peer-to-peer traffic."
"Worse, peer-to-peer (P2P) services, used to download movies and other large files, are eating more and more bandwidth. P2P participants may constitute only 5 percent of the users in some networks, while consuming 75 percent of the bandwidth."
Also seems like this would make tiered internet easier in general. Doesn't this router have big implications on the Net Neutrality debate?
What I don't understand is how it distinguishes between audio/video streams and P2P traffic. I would think them pretty similar without inspecting packets.
See: http://en.wikipedia.org/wiki/Cisco_Express_Forwarding See: http://en.wikipedia.org/wiki/Quality_of_service
I feel like I'm telling Larry Wall what is up with Perl or something, but this guy is making route caching sound like something new, when it has been in crappy $4000 workgroup-class layer three switches now for almost a decade. This kind of deflates his "I should know" appeals to authority.
The buffer-alternative algorithm isn't well explained but sounds kind of novel and useful. It would be particularly so if it allows the network operator to manage flows on a per subscriber basis.
One other concern: if this router is cutting power/weight corners by decreasing its ability to calculate new routes ("flows"), it's possible that an ISP would be exposing themselves to a DoS of their network by intruders sending a lot of unique flow requests to the router. An obvious example of this would be several concurrent NMAPs of a large range of IPs.
If it can keep up with the large workloads they claim with only 300w and 3U (or so) of space, it's pretty compelling, all of these issues aside. I'm excited to see it in the real world.
My take is that flow routing is not necessarily cheaper than doing full routing on every packet, but building a router with virtually no buffers requires tracking flows and interacting with TCP.
What bothers me more is routing table updates. I don't see how they can avoid invalidating the whole flow cache on each routing flap. OTOH, rebuilding the said top 20% of flows should be pretty fast, too.
This _was_ an ad, right?
That seems counterintuitive to me.
That's not to say this is a huge win --- I don't think it is --- but yes, flow lookups are a simpler problem than per-packet routing and per-packet N-dimensional classification.
I like the idea of a router that shows you average signal strength throughout the day.
edit: OK, HN doesn't like puns? Good to know.