Each week, SearchSDN takes to Twitter to see what users, including experts, analysts and editors, are saying about software-defined networking. Using Storify and searching hashtags, keywords, and tweetups, we scour the social media site to see what users have to say about SDN, OpenFlow, network virtualization and more. This week, we took to Twitter and got an earful from Tweeters about SDN security issues, requirements for a campus SDN, and the importance of SDN programmability and ease of use.
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.
Check out what Twitter users have said this past week about software-defined networking.
Hope everyone is considering the security implications of open APIs being bolted onto network gear in the name of orchestration. #SDN— Santino Rizzo (@santinorizzo) June 13, 2013
3 kinds of SDN: All run on x86 like Nicira. New OS/soft on new net HW like OpenFlow. Scripts define existing net HWs like Anuta. Need all.— Shoichi Morita 森田晶一 (@moritacocoa) June 11, 2013
interesting point about why Software Defined Networking. "it allows for portability of the IP address" says Bob Muglia @junipernetworks— monkchips (@monkchips) June 11, 2013
I think in the end campus #sdn will need to be a mix of tunneling and static flow technologies. VXLan and OpenFlow both have use cases— Wilbur (@thewilbur) June 13, 2013