rers within their platform Operating Systems. NFV can also be applied to appliance vendors in a way that does not take advantage of the processing scale/innovation seen by many customers in their data centers. Different from NFV, SDN involves different control modules, interfaces and the applications that are mandatory for its proper working. NFV just needs shifting of network applications based on dedicated hardware to virtual containers on Commercial-off-the-shelf (COTS) hardware. More illustratively, SDN is present whereas NFV is future (Matias et al., 2015). NFV unites forwarding devices and middle-boxes shaping a common control framework. Use of NFV enables network policies to get implemented by the operators irrespective of the placements viz. placement of functions etc. and also it provisions no need of thinking about the steering which includes how to route traffic through these functions. The network services are deployed on generic x86 Downloaded 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 Virtualizing Network Functions in Software-Defined Networks hardware facilitating flexible resource allocation, scale-out architectures, bare metals or virtual machines etc. (Kolias, 2014; McKeown et al., 2008). The network services and functions can be further categorized into three major categories- simple virtualized services, service chaining, and services virtualization or platform virtualization. Requirements of Networking Through NFV Today's environment where networks are static and quite expensive to manage imposes a number of challenges in supporting NFV: Real-time and dynamic provisioning: The automatic deployment of VNFs, VNF FGs and their management in the NFV infrastructure. Provisioning of physical and virtual infrastructures with seamless control. Carrier-grade should allow robustness and scalability. Openness and interoperability: The network elements and VNFs from different vendor must co-exists. The NFV allows the interoperability and co-existence through open interface