General SDN or purpose-driven?
If you ask people if they want to have a single vendor provide "networking" or if they will go with a hybrid, most people will tell you that they will go with multiple vendors. The term "network" is simply too broad to consider one vendor for all aspects.
When ends up happening is that people build out specific parts of a network (datacenter switching, WAN aggregation, campus, whatever). And for each of those, they can make a set of decisions.
Talking about SDN in general does two things: it paints too big a picture, and it presumes that the thing being deployed is SDN. SDN is a tool. It is useful, but it is not the thing you deploy. You deploy network monitoring (Tap applications). That you use SDN is interesting (possibly even differentiating), but it is not the highest order thing.
What the suvey tells me is that people know SDN is coming but don't yet know enough about how to use it, else they wouldn't be talking about it as the thing. Collectively, we have to get past talking about the underlying tech and more about what that tech actually does.
Mike Bushong (@mbushong)