Rick, there is probably not much inside the ASICs...the whole concept of software defined networks is that switch can be very simple like a cross-bar, has tons of very high speed IOs and all packet processing functions are done in very faast processor outside the switch core...we are moving back to cheap but dumb switches...Kris
SDN starts from openness. The primary goal is to ease management and potentially improve network utilization. To me, a consortium shall be formed and a set of standards shall be agreed among different vendors to ensure active routing/switching reconfiguration can be in a larger scale. I can understand the benefit of proprietary solution to a company. I believe the power of standard and agreement to a bigger scale.
I have not designed a networking ASIC for at least 10 years but still remember few things on the topic ;-).You probably need 1 Tb/s aggregate bandwidth (or more) so with 10 Gb/s per pin (differential) that requires 400 pins. Plus ground, power, control etc. Can be 1000+ IO pins at the end. Plus billion little muxes inside the core. Requires careful engineering, probably cost few million $ to tape-out but no smart packet processing as it is done today (famers, packet processors, etc) which will be done elsewhere.
The bottom line is that it's still a matter of N-to-N connections and no software can solve that problem. BTW, in today's complex routers there is lots of software already so the software component is not new, it is just executed somewhere else so networking can be controlled by the box operator not by the box manufacturer.
At the end all the software can do to help get packets where they need to go is simplify the core switching problem to something like a cross-bar, you can't go simpler than that! BTW, all switching concept are very elegantly explained by Carl McCrosky is our Wiley book "Network Infrastructure and Architecture: Designing High-Availability Networks".
Looking forward to your interview with Insieme folks! Kris
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.