"In many of the programmability approaches that vendors are trying the APIs become so incredibly specific that it's simply not profitable for a third-party vendor -- and really barely worth the customer's time -- to write on top of these incredibly specific APIs," he says. "There's a fairly broad consensus of folks realizing that unless there's a baseline of standardization, there's some that will never create an ecosystem of third-party applications for this."
With respect to XMPP, Forster says it's "clever" but doesn't mask the complexity of automation scripts written to it.
"XMPP doesn't let you write a Perl script that can roll back (unintended commands)," he says. "The Perl scripts that you write on top for automation still end up being pretty complicated."
But what's not debatable is the visibility OpenFlow is bringing to SDNs, and vice versa.
"OpenFlow is critical, and not because it's the answer," says Andre Kindness, an analyst with Forrester Research. "It's one of the answers. But it's the only one getting a lot of play because there are a lot of communities working on it. It's a huge amount of brainpower working on it. It's driving a lot of discussions and new ways of thinking. We got a good horse race going on here."
Read more about LAN and WAN in Network World's LAN & WAN section.