 is, it is pretty hard to learn and comprehend as compared to other controllers. Table 3. POX: Packets parser Events Generated From Messages From Switch Packets Parsed by pox/lib FlowRemoved, FeaturesReceived arp, dhcp, dns ConnectionUp, FeaturesReceived eapol, eap RawStatsReply, PortStatus ethernet, icmp PacketIn, BarrierIn, SwitchDescReceived, igmp, ipv4 FlowStatsReceived, QueueStatsReceived, llc, lldp, mpls AggregateFlowStatsReceived, rip, tcp, udp, vlan TableStatsReceived, PortStatsReceived Downloaded: 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 The Heart and Brain of SDN Now well we could have gone into the Frenetic and Pyretic controllers too but they are not only controllers but languages and controllers independently. FUTURE TRENDS Automation could never cause any harm to an industry but the level to which it grabs labour opportunities is tremendous . What it implies is, SDN has a vast field of growth in data centres for managing traffic Specific controllers which are more to open-source side can be developed for their usage, as many controllers are still on the enterprise and paid sides . In this growth, the plunging takes place in the jobs sector. Being more inclined to machines, people would be less needed. The pros and cons of any substance are present right in front It is a matter of, how are they implemented in use. For e.g. A new SDN controller is developed which implements Haskell (Function oriented language) and runs great on a piece of hardware The problem is it might not work for other hardware's. So in order to build a more sophisticated environment, usage of controller which is universal would be great instead of building SO many separate controllers. Apart form it, their use should be focused on a closed domain SO that they don't eat up all the job opportunities for the people. In order to use this architecture B2B security needs to be established from ground up CONCLUSION Definition as a logically centralized entity neither prescribes nor preludes implementati