MEF 120 Lean NFV Overview and Framework
Lean NFV represents an approach to implementing Network Functions Virtualization in the context of MEF LSO.
NFV solutions have become fundamental in moving network functions to the Edge (where by Edge we mean a compute stack not in the cloud core, up to and including the premises edge). Lean NFV offers a uniform approach to integrating different components involved in NFV using MEF LSO APIs.
Lean NFV takes an approach of reducing the difficult task of integration that usually accompanies disaggregation, relying on a Key-Value Store (KVS)-like function as the universal point of integration and using a plug-in approach to the computing infrastructure. Lean NFV reduces reliance on monolithic controllers and other NFV elements so that independently developed components work together, whether they run in customer premises equipment (uCPEs), the network edge (public or private), data centers, or even the cloud core.
The purpose of this document is to define Lean NFV in the context of the MEF 55.1 LSO Framework. In this document, Lean NFV effects the functions of Infrastructure Control and Management. In this context it serves as a vehicle to instantiate two LSO APIs: Presto and Adagio. This document introduces the concept, provides a framework for the details (internal APIs and schema), and establishes principles that guide its design. The goal is to enable network operators to offer more customized services to their customers and to transform their businesses to adopt a software-first mindset.
Standards published by MEF are intended for general distribution to the public and may be downloaded from this site and reproduced without charge. Any reproduction of MEF documents shall contain the following statement: “Reproduced with permission of MEF Forum.” All rights granted to MEF under applicable copyright laws are expressly reserved. No permission is granted to any recipient or user of MEF publications to modify any of the information contained therein and MEF disclaims all responsibility and liability for such modifications.