Market Leader Programs
5G Transport - A 2023 Heavy Reading Survey 2023 Open RAN Operator Survey Coherent Optics at 100G, 400G, and Beyond Open RAN Platforms and Architectures Operator Survey Cloud Native 5G Core Operator Survey Bridging the Digital Divide 5G Network Slicing Operator Survey Open, Automated & Programmable Transport The Journey to Cloud Native
Do people ever learn? We've been there in mid 90's, when Cisco came with NetFlow Switching (not to confuse with NetFlow stats), same promises - better QoS, faster lookup, etc. Result - it does NOT scale. One more time - it does NOT scale. Way too many flows in the Internet. We realized that we need to bite the bullet and implement line rate FIB lookup for each packet. We can do it faster than any hash tables lookup today, no problem.
Router architecture 101 - the amount of state the router has to maintain MUST NOT depend on the amount of traffic going through it.
You can stretch this a bit at the edge, where the number of flows is somewhat limited. In the core - forget about it. As skeptic said - DoS attacks are a huge problem here - picture a DDoS using millions of infected hosts and servers, huge number of new flows, overloading the flow table and keeping valid new flows out.
RSVP-like mechanism in the network, and I'm afraid it is on a per-flow basis too. We have been there with IntServ in the IETF. Result - it does NOT scale. Once more - it does NOT scale. That's why we moved to DiffServ.
So now we have at least two major architectural mistakes productized, and crystallized in silicon.
This is really an example of how VCs used to spend money just a while back. Guys, you should have talked to someone with at least a tiny bit of clue. Kiss your money good bye.