e agents that allows the formation of numerous virtual switches with independent controller sessions make network slicing possible in OpenFlow. WIRE PROTOCOL In computer networking, a wire protocol refers to a process of obtaining the data from point to point. A wire protocol is required for the interoperability of more Downloaded: 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 Introduction to OpenFlow than one application. It generally refers to protocols higher than the physical layer (Open Networking Foundation Formed to Speed Network Innovation, 2011). They often refer to diffuse object protocols, or they use applications that were dedicated to work together. In contrast to transport protocols of fourth layer of OSI model (like TCP or UDP), a wire protocol is used to outline a common way to demonstrate the data at application level. It refers only to a common application layer protocol. In OpenFlow firstly, it instigates the idea of replacing ephemeral state (flow entries are not stored in permanent storage on the network element) for the stiff and unstandardized semantics of various vendor's protocol configuration (the potential to design ephemeral state along with programmatic control may be a short-term advantage of OpenFlow, as there are proposals to add this functionality existing programmatic methods like NETCONF). Ephemeral state also enhances the slower configuration commit models of past attempts at network automation. The result of such configuration is to create forwarding state (although distributed and learned in a distributed control environment). For many network engineers, the testing of proper configuration is to validate forwarding state i.e., examining at routing, forwarding, or bridging tables. Obviously, this leads to increase in burden to the controller(s) in the form of managing and maintenance of this state (if we need to be dedicated and always have certain forwarding protocols in the forwarding table) versus the distributed management of configuration stan