ved. It should also be possible to accurately monitor and reroute network traffic as defined by policy. Openness: Aligned with the Open NFV strategy in the HP NFV business unit, the NFV framework should be capable of accommodat- ing a wide range of NFs in a nonintrusive manner. It should support open-source-based and standard solutions as much as possible, mean- ing that the NFs should be implemented, deployed, and managed by operators, enterprises, or third-party software vendors. NFV Orchestration NFV management and orchestration component, that is, MANO, is an integral piece of NFV architecture and a critical component to the success of NFV. It is responsible in managing all the resources for NFV framework; not just the networking resource but also the compute and storage resources. According to ETSI's MANO working group, it con- tains three key components: the NFV orchestrator, VNF manager, and virtualized infrastructure manager (VIM). NFV orchestrator is responsible for the installation and preparation for new services, which is also called the network service onboard- ing process. It handles the entire life cycle of the new network ser- vice, including resource allocation, validation, and authorization. While the VNF manager handles the life cycle of each VNF instance, the NFV orchestrator operates at a higher level. Its functionality includes registering a network service in the catalog, and onboard- ing the network service, instantiating the network service, scaling up/down, managing VNF forwarding graph related to the network service, and finally terminating the service. VNF manager, as the name indicates, handles the life cycle of each VNF instance. It includes the configuration, preparation, 3.4 NFV Orchestration and running of the VNF instance, monitoring its healthiness and interacting with other MANO components on behalf of the VNFs. The actual tasks of VNF manager include the following: instantiate a VNF, monitor its resource utilization, scale up/down the VNF, update or upgrade, and finally termin