her the northbound API i.e., application facing, or east/west API. The distribution of east/west state on the primary controller is based on a database distribution model, which permits federation of one vendor's controllers but restricts the interoperable state exchange. The Working Group of Architecture is indirectly attempting to address the architecture of OpenFlow as a general SDN architecture. The ONF has also attempted to merge the definition of SDN and OpenFlow. Without these standardized interfaces like OpenFlow, there is a question mark on the openness of the ONF definition of Application services (Figure 2) provided by most of the OpenFlow controllers are: path computation, topology (determined through LLDP, which limits topology to layer 2), and provisioning. To support Of-Config, they need to support a NETCONF driver. Downloaded 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 Introduction to OpenFlow Figure 1. Architecture of OpenFlow Flow Table Switch Flow Table Switch Flow Table OpenFlow Switch Flow Table Switch Flow Table Controller Switch Data Plane Control Plane There is still question going on about the SDN architecture and Openl Flow whether the type of services provided by an OpenFlow controller are sufficient to fulfil all the potential needs of the SDN applications. The main research on the macro topics of OpenFlow model are being conducted specifically at the Open Network Research Center (ONRC), and in many different academics and research facilities like (troubleshooting, the expression of higher level policies with OpenFlov semantics, and on protocols for verification layer between controllers and elements). Openl Flow is a set of protocols and an API; it is just a program and not a product in itself and not a single feature of a product. Without the application programs (single or many) and protocols the controller is useless for giving instructions on which flows goes on which elements i.e., switches and routers (for their own reasons). Presently OpenFlow pro