Network function virtualization: Difference between revisions

Revision as of 17:28, 28 July 2023

Revision as of 20:51, 31 October 2023

Line 48:

==Relationship to SDN==

Network Functions Virtualisation is highly complementary to [[Software-Defined Networking]] (SDN).<ref name="white">{{cite web |title=Network Functions Virtualization— Introductory White Paper |publisher= ETSI |date= 22 October 2012 |url= https://docbox.etsi.org/isg/nfv/open/Publications_pdf/White%20Papers/NFV_White_Paper1_2012.pdf |access-date= 20 June 2013 }}</ref> In essence, SDN is an approach to building data networking equipment and software that separates and abstracts elements of these systems. It does this by decoupling the control plane and data plane from each other, such that the control plane resides centrally and the forwarding components remain distributed. The control plane interacts with both [[Northbound interface|northbound]] and [[Southbound interface|southbound]]. In the northbound direction the control plane provides a common abstracted view of the network to higher-level applications and programs using high-level APIs and novel management paradigms, such as Intent-based networking. In the southbound direction the control plane programs the forwarding behavior of the data plane, using device level APIs of the physical network equipment distributed around the network.

Thus, NFV is not dependent on SDN or SDN concepts, but NFV and SDN can cooperate to enhance the management of a NFV infrastructure and to create a more dynamic network environment. It is entirely possible to implement a virtualized network function (VNF) as a standalone entity using existing networking and orchestration paradigms. However, there are inherent benefits in leveraging SDN concepts to implement and manage an NFV infrastructure, particularly when looking at the management and orchestration of Network Services (NS), composed of different type of Network Functions (NF), such as Physical Network Functions (PNF) and VNFs, and placed between different geo-located NFV infrastructures, and that's why multivendor platforms are being defined that incorporate SDN and NFV in concerted ecosystems.<ref>{{cite web|url=http://www.cisco.com/go/esp|title=Platform to Multivendor Virtual and Physical Infrastructure}}</ref>

Line 154:

* [[OASIS TOSCA]]

* [[Open Platform for NFV]]

* [[Software-defined networking]]

==References==