Each week, @SearchSDN explores Twitter to see what users are saying about software-defined networking, network...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
virtualization, OpenFlow standards and more. This week SearchSDN, hosted its first ever tweetup. SDN analysts, bloggers, experts and SearchSDN editors weighed in on SDN use cases, such as automated network provisioning and bandwidth calendaring. Participants also debated the basics of SDN architecture and the dreaded "SDN washing." Here's a roundup of the questions posed by SearchSDN and tweets from the lively conversation.
Question 1: Is a network architecture truly SDN if it doesn't include separation of the data and control planes? Why or why not?
I'd say the majority of people (researchers, vendors, practitioners) emphasized control & data plane separation #SDNchat— Shamus McGillicuddy (@ShamusTT) April 26, 2013
#SDNchat IMHO separation of data and control is a key part of evolving functionality from capacity separately.— Abner Germanow (@abnerg) April 26, 2013
Question 2: There's been a lot of talk about moving OpenFlow from testing to production. Is OpenFlow SDN ready to scale?
#SDNchat the days when SDN was only OpenFlow are over and done. Today it's OpenFlow + Overlays— Sean Kerner (@TechJournalist) April 26, 2013
Question 3: Do you have examples of SDN washing? What can be done to limit the hype and focus on the technology?
SDN use cases
In response to our last question, another conversation was started centered on SDN use cases.