Several companies have announced they have OpenFlow-enabled switches, but for these companies, there is still no strategy and no reasoning as to why their switch should be used when deploying an OpenFlow based SDN. Furthermore, they lack a strategy overall looking at the various components of a Software Defined Network. From a hardware standpoint, some of the same features and characteristics (buffers, table sizes, etc.) will still need to be compared as we already do today in traditional networks, but even that, isn’t documented in these announcements. A lot of these vendors think they are on the offensive [vs. Cisco] announcing OpenFlow enabled switches (without a controller), but they really aren’t, in my opinion.
Greg Ferro does a nice job here directly stating the networking incumbents should step up with an SDN strategy. I agree 100%. Brad Casemore also chimes in with his thoughts. If you aren’t already reading their blogs, I encourage you to do so because you’re missing out.
Several companies have announced they have OpenFlow-enabled switches, but for these companies, there is still no strategy and no reasoning as to why their switch should be used when deploying an OpenFlow based SDN. Furthermore, they lack a strategy overall looking at the various components of a Software Defined Network. From a hardware standpoint, some of the same features and characteristics (buffers, table sizes, etc.) will still need to be compared as we already do today in traditional networks, but even that, isn’t documented in these announcements. A lot of these vendors think they are on the offensive [vs. Cisco] announcing OpenFlow enabled switches (without a controller), but they really aren’t, in my opinion.
5 Comments
I mentioned in my previous post Nick McKeown, uber smart Entrepreneur and Professor at Stanford, gave what I thought was the finest presentation of the week at the Open Networking Summit hosted in Santa Clara this week. As I wait to board my plane back to the East coast, here is a more detailed recap of the presentation and what I took away from it…
Here is a quick summary on what I think worked well, what didn't work, and some thoughts on improving ONS next year.
What worked?
With just a few minutes to spare until the 5:30 start of the evening event and exhibits, I thought I’d give a really quick summary of Day 1 at the Open Networking Summit 2012. Note there were two tutorial sessions today and I attended the one for engineers.
The first thing you noticed by seeing everyone’s badges/name tags with associated company, and was confirmed by Brandon’s presentation in the first slide, was there was and is a truly broad audience here. There are the obvious participants from the big name manufacturers, but also, there are between 1-3 people from at least 60 “other” companies, which is the category I fall into since I’m the only one representing BlueWater from NY/NJ. I also had the pleasure of sitting next to the sole person from Aruba Networks as well. Not sure what that tells you about their SDN strategy. |
AuthorJason Edelman, Founder & CTO of Network to Code. Categories
All
Archives
May 2015
|