Do you need to use the OpenFlow protocol in a software-defined network?
The OpenFlow protocol is not required to implement a software-defined network (SDN) to separate the data path from the control plane and tell network switches where to send packets. SDN architectures will take many different approaches, and each technology vendor will have a unique take on how to implement SDN.
For the OpenFlow community that uses standards developed by the Open Network Foundation (ONF) consortium, however, the answer is yes. The ONF recommends using OpenFlow as the foundation technology for SDN implementation. For many suppliers, including Big Switch, HP, IBM, Dell, Pica8, NEC and many others, OpenFlow is a fundamental part of their SDN offerings.
Many other suppliers may support OpenFlow, but the protocol is not of the key to their SDN architectures. For example, Cisco's SDN architecture, Open Network Environment, supports OpenFlow, but Cisco does not require the use of OpenFlow. Other suppliers that offer SDN solutions that do not depend on the OpenFlow protocol include Juniper, Brocade, Avaya, ADARA, LineRate, Embrane, Nicira (now part of VMware), PlumGrid, Pertino Networks, Plexxi and many others.
Dig deeper on OpenFlow
Related Q&A from Lee Doyle
SDN is valuable, but uses extend to other parts of the network for increased network flexibility, dynamic traffic flow, decreased latency and QoS.continue reading
An SDN controller, with or without OpenFlow, is not required for a software-defined network, and SDN architecture vendors take different approaches.continue reading
A software-defined network can have a centralized or distributed network architecture in the data center, LAN and WAN, depending on business needs.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.