cations. Through this, routing paths can be updated time-to-time or ad hoc by the controller and converted into rules and actions with a configurable lifespan, which are then updated to the switches forwarding table, jilting the actual flow of matched packets to the buffer of switch for the time span as per those rules. The major component of OpenFlow which shares common objective with SDN are: Decoupling of the control and data planes of the switches, the control plane is managed by the centralised controllers which may be one or more in number but synchronized. Downloaded 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 Introduction to OpenFlow Using an institutionalized interface communication between SDN controller and the switches for updating the forwarding table of switch over the network. The centralised controllers will be programmed via modern, extensible API's over the network. The control mechanism of OpenFlow are encrypted with the Transport Layer Security(TLS) and Secure Sockets Layer(SSL) OpenFlow Protocols from SDN Controller to each switch and router to provide the auxiliary security inside the Network. Also, Open Flow allows the controller to remotely manage switches. These switches may have origins from different vendors, with each one of them having its own proprietary interfaces and scripting languages. ARCHITECTURE The key components of the OpenFlow model, as shown in Figure 1, have become at least part of the common definition of SDN, mainly: Separation of the control and data planes (in the case of the ONF, the control plane is managed on a logically centralized controller system). Using a standardized protocol between controller and an agent on the network element for instantiating state (in the case of OpenFlow, forwarding state). Providing network programmability from a centralized view via a modern, extensible API. For instantiating flows, OpenFlow provides a standardized southbound protocol i.e., controller to element agent, while there is no standard for eit