On June 29th during MWC Shanghai 2023, ETSI ISG NFV organized a “Telco cloud-native roundtable” to present NFV work and engage participation from Asian operators who were invited. The goal was also to learn their experience, feedbacks and drive the evolution of the future telco cloud. The roundtable offered a valuable chance for synchronizing the latest progress and vision of the ETSI NFV standard community with the key telco operators in Asia-pacific area who attended the event.

NFVBlog Release5

ETSI ISG NFV Chair, Yoshihiro Nakajima, gave the opening speech and pointed out that Asia-Pacific is pioneering the 5G SA global implementation, with NFV telco cloud providing the much-needed foundation for such deployments. Therefore, this roundtable was targeted to hear the learnings of the operators within this area and their thoughts on the NFV future evolution for supporting 5G-Advanced and beyond business. He also highlighted the main characteristics of the NFV community, being built on openness and collaboration; characteristics that were fundamental pillars for its 10-years successful journey to create globally adopted standards in the industry.



Meeting at ETSI headquarters of Sophia Antipolis in May-June has been always wonderful with a lot happening (local festivals, fun and adventure activities) in and around Nice, Antibes, Grasse and Cannes. It can be a time to rejuvenate yourself in this perfect weather. Some of us were happy to spend the weekend due to Technical Steering Committee (TSC) workshop on 1st and 2nd of June 2023. This year as well, we were greeted with gorgeous weather and wonderful gathering of NFV delegates onsite for NFV#42 happened between 5th to 9th of June. People who couldn't travel were able to join remotely for this plenary as well continuing the hybrid meeting practices.

During the opening plenary on 5th June, Madalin Neag (part of ETSI Secretariat) presented the agenda for NFV#42 plenary meetings, working group sessions and proposal for special ISG sessions during that week. ETSI ISG NFV chair, Yoshihiro Nakajima-san presented to the ISG on the latest accomplishments of the group and introduced the background on the special ISG sessions in NFV#42 plenary meetings. The special sessions were reserved to discuss the collaboration with other SDOs and to collect new ideas on, how to efficiently steer future work in the NFV. Madalin presented the progress made since NFV#41. The TSC manager, Ulrich Kleber then presented detailed status of Releases 4, 5 and 6, including:

- 24 normative specifications were published for edition 4.4.1 in Release-4.
- 6 informative group reports were published in Release-5.

Diego Lopez, chair of NFV’s NOC (Network Operator Council), shared this group’s views on the future of ISG, the challenges with Versioning of the specifications, view on Convergence of network models and the analysis, prioritization of new features in Release 6. The details and insights shared were appreciated and appropriate actions were noted by the ISG to follow-up.



When ETSI ISG NFV met in Sophia Antipolis recently for their 41st plenary meeting, it was not only collocating the 10 year anniversary celebration (see separate blog post here) with a week full of technical discussions. It was also a major step to provide the next package of specifications in NFV’s Release 4. The new package contains edition 4.4.1 documents for both stage 2 and stage 3.

In stage 2, 14 documents were updated mainly with maintenance. In addition, 2 new group specifications were published:

ETSI GS NFV-IFA 048, which adopts the State-Task design pattern to specify the NFV-MANO policy information model. The information elements in the model are transferred through policy management interfaces over NFV-MANO reference points, which enable the enforcement of policies in the framework of NFV-MANO. Stack-Task design pattern supports representing different policy expression forms and provides more flexibility and extensibility in respects to policy.

ETSI GS NFV-IFA 047, which specifies the service requirements as well as service interfaces produced by the MDAF (Management Data Analytics Function). Following the recommendations from a previous Release 4 group report ETSI GR NFV-IFA 041 on enabling autonomous management in NFV-MANO, this specification specifies a new function named MDAF (equipped with AI/ML models) and its service interfaces, which improve decision making of NFV-MANO in automation processes especially for network service management and orchestration.  

In stage 3, there were 10 updated documents. The major highlights are described below:

ETSI GS NFV-SOL 018 - Profiling specification of protocol and data model solutions for OS Container management and orchestration:

The biggest part of the updates was about Cloud-Native VNFs and Container Infrastructure management. After the big leap forward in the support of containerized workloads in the NFV framework, which the previous edition 4.3.1 represented, the recently published 4.4.1 edition has brought additional support and consolidation of the feature.

Two new management services interfaces, CIS MCCO (Managed CIS Cluster Object) and CIS instance, as specified in ETSI GS NFV-IFA 036 “Specification of requirements for the management and orchestration of container cluster nodes”, are added to the scope.

Consequently, the latest published version of the reference Kubernetes® API are profiled as NFV protocol and data model solution for the new management services. Three kinds of Kubernetes® resource objects (daemonSets, CRDs and PersistentVolumes) are mapped to the NFV objects of the CIS MCCO management service interface. One kind of Kubernetes® resource object (Node) is mapped to the NFV objects of the CIS instance management service.  All mentioned resource objects are deployed as part of the cluster management.

For the above resource objects, their resource methods are profiled to match the corresponding NFV service interface requirements and flow sequence diagrams for the CIS MCCO and CIS instance operations are provided.

For the Support for the expression of virtual NIC interface requirements, the ‘cni’ capability specified and registered in the ETSI NFV NFVI Platform Capability Registry allows the expression in a VNFD of requirements related to secondary container cluster network and, based on them, allows MANO functions to select an appropriate CNI.

ETSI GS NFV-SOL 009 - RESTful protocols specification for the management of NFV-MANO:

The CIR function, container image registry, is added as a managed entity

Other enhancements:

In relation to the connectivity to primary cluster networks, support of address pools for load balancers and modelling of ingress is part of this edition.

OAuth2.0 scope values have been specified for the VNF LCM, the NS LCM and the VNF Package interfaces. They allow to restrict the authorization of the consumer to read or manipulate certain resources within an interface. In the next editions further scope values will be defined for other interfaces.

The VNF package specification was enhanced to align with the stage 2 provisions for licensing.

As an enhancement of “Flexibility with scalable VNF/NS instantiation”, new provisions were created that allow e.g. the consumer of the NS LCM interface to indicate the target scale level of a constituent VNF, or to specify in an NSD the target scale level of a nested NS.

RESTful protocols specification for the Policy Management Interface has added new provisions to align with the policy information model specified in the recently published ETSI GS NFV-IFA048.

After this big package it is planned to complete the Release 4 feature development in the next edition 4.5.1, which is planned for this summer.



The weather in Munich in late April was still a bit cold, but it did not prevent the ETSI NFV’s IFA working group (WG) from gathering in an interim face-to-face meeting under the warm hospitality of DOCOMO Euro-Labs. IFA WG is mainly responsible for delivering NFV stage 2 related specifications, including NFV architecture, interfaces and information model design, as well as informative work study on any new architectural related use cases exploring the evolution of NFV. This WG’s mission makes IFA an important WG within the ISG NFV, with always constant workload and substantial high-intense discussions. 

The proposal for an interim IFA meeting was made during the NFV#41 plenary meeting, held in March this year, in order to address the amount of work to be completed by the WG by this summer. The proposal was endorsed by the Technical Steering Committee (TSC) and the ISG, as a whole. The interim WG meeting targeted to speed up the progress of active work items which are part of Release 4 and 5 and promote many of the work items to catch up with the upcoming summer release drop delivery timeline. 

This interim meeting restarted the practice of past interim WG F2F meetings in ETSI NFV after 3 years’ hiatus due to the worldwide epidemic of COVID-19. The last memories of these interim meetings were from 2019, when IFA and SOL WGs jointly held interim meetings in Munich (same city, but with different hosting company) in March 2019. We would like to thank DOCOMO Euro-Labs for kindly hosting the interim WG meeting this time. Seven WG colleagues participated to the meeting on site and a dozen of other colleagues attended remotely.

IMG 0436 edited IFA332 group entrance 

It was a really nice and fruitful meeting experience in which more than 120 contributions were discussed, comments exchanged, revisions reviewed, and consensus reached in just only 3 days. Several Release 4 and 5 work items made very good progress and were identified for reaching finalization status in the upcoming one or two months, including:

Release 4:
Feature (FEAT) 17 on "Cloud-native VNFs and container infrastructure management", in particular on the new group specification (GS) development about CCM-VIM interfaces (work item DGS/NFV-IFA052),
FEAT20 on "NFV automation", specifically for the new GS development on intent management service interface (DGS/NFV-IFA050) andFEAT21 on "NFV support for 5G", with a special emphasis on the related normative work development to support PaaS services in NFV.

Release 5:
FEAT19b on "NFV connectivity integration and operationalization", to continue the development of the new group report (GR) about NFV network connectivity (DGR/NFV-IFA035),
FEAT28 on "Fault Management models", with the development of the new GS to define and specify alarms within the NFV context (DGS/NFV-IFA045), and
FEAT31 on "Flexible VNF deployment", to steadily progress the normative work with change requests (CR) to update existing NFV-MANO specifications. 

Other than these, below Release 4 and 5 work items also made some progress in this meeting, but the WG required to see more contribution inputs for determining when would the work items reach their stable drafts, including:
FEAT24’s new GS development on "VNF generic OAM" (as part of the work item DGS/NFV-IFA049),
FEAT19a on "NFV container networking", under the umbrella of the new GR development on container networking (DGR/NFV-IFA043), and
The release independent work item on VNF management gap analysis with open source (DGR/NFV-IFA051).

With much time now spent on the work items, we expect more slots of future WG meetings will be available for accommodating new features and work items to be started as part of the upcoming Release 6. When telco virtualized networks are evolving towards cloud-native in this era, the conflicts between traditional standard development processes and more dynamic and agile requirements from cloud native world is increasingly prominent, which makes WG a focus point to resolve the conflicts and gaps.

The WG meeting also handled several contributions that influence general ETSI NFV ISG matters, such as the agenda proposal for a joint workshop with O-RAN planned to be held in June, improving the efficiency of the WG working procedures, offloading workloads among EVE, IFA and SOL working groups for better WG working coordination in the future. Some of the above discussions will provide valuable inputs for NFV future workshop sessions in the next NFV#42 plenary. 

The time to parting is always reluctant, even more when WG colleagues have fallen in love with the daily supply of specialty drinks offered during the coffee breaks, lingered with some other local delicacies including the typical Bavarian pork knuckles that some of the delegates enjoyed at a social dinner. Delegates will start a new journey of next F2F meeting carrying the harvest from this meeting! 

See you all in June at ETSI headquarters for our upcoming NFV#42 plenary!



In early March, ETSI’s ISG NFV gathered again in ETSI headquarters in Sophia Antipolis. This 41st plenary meeting was collocated with a special event celebrating the 10 years anniversary of this very important Industry Specification Group adding together again many NFV friends from all around the world. (More details of NFV 10th anniversary can be found in the next post: https://www.etsi.org/newsroom/news/2204-etsi-s-conference-for-nfv-10th-anniversary-looks-to-the-future).

 Tweeter 540x308 nfv41The NFV#41 opening plenary was held at the very beginning of the week. ETSI ISG NFV chair Yoshihiro Nakajima started by highlighting the achievements from the NFV#40 - ETSI ISG NFV continues to deliver with very good pace. As well, he took advantage to briefly announce the 10th anniversary event -a good opportunity to not only celebrate the accomplishments that NFV has made in the past 10 years, but also to look forward to the future.

The TSC manager, Ulrich Kleber presented in depth the description of Releases 4 and 5, but also an overview of the Release 6. The updated schedule for those releases was detailed showing our group’s intention to speed up the standards’ creation process and alignment with the industry fast progress in this area.

Diego Lopez, NFV NOC’s chair, started his speech by talking about the recently-published NOC's white paper. He continued by sharing recent operators’ considerations on the relationship between ETSI standards and other cloud-related standards and specifications. Some proposals for future actions were triggered for the ISG including a more direct and dynamic interaction with open-source projects and convergence of K8s and NFV network models.

 The opening plenary was followed by the workshop dedicated to the anniversary of our group and by two extremely busy and productive days allocated to the WG sessions. More and more consensuses converged in the community on the visions, way forward directions and challenges reflected also in the two new NFV whitepapers created for the 10th anniversary milestone. Release 6 features kick off to fulfill these attractive objectives with concrete action plan.

The NFV#41 plenary meeting adopted an intensive schedule for its opening/closing sessions and working group meetings. During the past 3 months from NFV#40 plenary, several important ISG deliverables have been approved and published by the ISG, including:

  • ETSI GS NFV-006 v4.4.1: first Release 4 NFV architectural framework with supporting OS container management and orchestration
  • ETSI GR NFV-EVE 022 v5.1.1 on VNF configuration
  • ETSI GS NFV-IFA 048 v4.4.1 on MANO policy information model
  • ETSI GR NFV-IFA 044 v5.1.1 on flexible VNF deployment
  • ETSI GR NFV-REL 013 v5.1.1 on cognitive use of operations data for reliability

At NFV#41, not only 14 IFAed441 specifications (including maintenance and enhancement from Release 4 features), but also one new deliverable - ETSI GS NFV-IFA 047 - on MDAF service interface were approved by the ISG. 10 final drafts from SOLed441 work items were sent for approval process via remote consensus. All those were accomplished thanks to the great team cooperation between rapporteurs and contributors who have carefully followed the objectives and schedule of these work items.

  • Other highlights from NFV#41: 3 Release 6 and 1 Release 5 feature proposals being endorsed:

Release 6

- New infrastructure for NFV
- New application virtualization forms
- Deterministic communication technologies

Release 5

- Physical infrastructure management

 

  • One Release 6 NWI proposal on architectural support for NFV evolution will be feature independent and would be finalized in IFA
  • NWI proposals approved by the ISG:

- Continuation of the stage 2 work in release 4, define by a Super-WID with 16 NWIs. These form the edition 451 for IFA specifications and intend to complete the release 4 feature work.

- Specification of availability and reliability requirements in NFV automation

- Specification on Physical Infrastructure Management that will be sent for remote consensus

  • ISG approved one liaison reply that was sent out to ITU-T in response to SG11-LS46
  • In a joint WG session of IFA, SOL and SEC, transparent working procedures on stage 2/stage 3 were agreed for coordination of the development of security management features.

Until next plenary, having a very loaded work programme, ISG NFV will try to progress on Release 4, Release 5 and on the features proposals and crystallization for the upcoming Release 6. In parallel, in various meetings (at WGs and/or at leadership levels), we will continue to explore improvements on ISG organization, cooperation with other SDOs and working procedures which will help ISG NFV to follow the best path towards a successful evolution. All those will be consolidated during NFV#42.

In the early summer the ISG will meet again; hot discussions and debates on new organizational and work-programme-related topics are worth looking forward to.



The COVID-19 pandemic stopped ETSI NFV Industry Specification Group (ISG) face-to-face meetings for more than two years. As a result, the ISG blog posts for the plenary sessions were interrupted as well. Although people have been used to regarding online meetings as normal in the past two years, it is time now to call people back to face-to-face meetings with the gradual relaxation of epidemic prevention policies in many countries.

This time, the ETSI ISG NFV met again at NFV#38 from May 30th to June 3rd 2022, in Sophia Antipolis, France. The meeting took a hybrid format, ETSI headquarters hosted 23 delegates from Europe, Asia and North America. Many other delegates participated in the meeting remotely due to their inability to travel. This is the first time that ETSI NFV has returned to a face-to-face meeting after the COVID-19 pandemic since 2020.



NFV blog052021

A virtual event on NFV Evolution organized by ETSI in partnership with Telecom TV and sponsored by Huawei was held from 19 to 21 April 2021.  The objective of the event was for the ETSI NFV Industry Specification Group (ISG) to get feedback from the industry on implementation experience with the ISG’s specifications and on future topics to be addressed in next specification releases. The event was also an opportunity for the participants to get updated on ETSI NFV’s activities, deliverables and future plans, as well as on the progress made in open source communities with regards to the convergence with the ISG’s standards. The event was held in parallel with the 34th meeting of the ISG. The choice was not accidental as this was the meeting where the ISG launched the process for collecting proposals from its members and participants on the features to be addressed within the scope of its next specification release (NFV Release 5).

The event programme featured six original presentations selected from the responses received to an open call, addressing deployment experience, new use cases and technical requirements:

  • Mr. Yuya Kuno, NTT DOCOMO, presented DOCOMO’s experience in developing and operating NFV and future expansion.
  • Mr. Pierre Lynch, Keysight Technologies and Ms. Silvia Almagia, ETSI CTI Technical Expert jointly presented “Measuring NFV Evolution: ETSI NFV Plugtests”.
  • Mr. Borja Nogales, Universidad Carlos III de Madrid, presented “An NFV system to support service provisioning on UAV platforms: a walkthrough on implementation experience and standardization challenges”.
  • Dr. Lingli Deng, China Mobile, presented “From Orchestration Towards Automation”
  • Dr. Haopeng Zhu, Huawei Technologies Co., presented “Towards the future of NFV: Edge-native, Containerization, Networking-NFV convergence”.
  • Mr. Gianpietro Lavado, Whitestack, presented about the advances in deployment of standardized NFV Orchestration through ETSI OSM.


2020 turned out to be an unexpected year, with the COVID19 pandemic adversely impacting the “normal” day-to-day lives of humans across the globe. However, even during this turn of events and unforeseen testing times, communication networks demonstrated their efficacy in keeping people and businesses connected. More concretely, Network Functions Virtualisation (NFV) proved its feasibility by enabling the operators to gracefully manage high demand for network connectivity.

NFV blog evolution new vision imageUndaunted by this situation, the technical experts at the ETSI ISG NFV continued to work tirelessly developing and delivering specifications that help get and keep “everyone/everything connected”. And the hard work paid off as ETSI ISG NFV delivered during the second half of 2020 new and updated "protocols and data model" (stage 3) specifications incorporating NFV Release 3 features.

The experts in the Solutions (SOL) working group completed stage 3 work on a subset of the NFV Release 3 features. One of the first features that was already finalised in 2019 was "Management of NFV-MANO" (FEAT11) with the release of ETSI GS NFV-SOL 009 V3.3.1. This document specifies a set of RESTful protocols and APIs that can be used to manage different aspects regarding configuration, performance, fault and logging of entities implementing specified NFV-MANO functional blocks. The defined APIs leveraged the same RESTful principles used for NFV-MANO APIs in Release 2, i.e., the ones used for managing VNF instances, NS instances and on-boarding VNF Packages, NSDs and other artefacts.

New outcomes on the development of NFV-MANO APIs continued in 2020 with the release of ETSI GS NFV-SOL 011 V3.3.1, which specifies NFV-MANO APIs related to management across "NFV-MANO administrative domains" (FEAT08). These APIs are produced by the NFVO and allow different administrative domains to communicate over the Or-Or reference point to help coordinate the management of NS instances deployed on their respective administrative domains. The Or-Or reference point is set in between NFVO instances placed on different administrative domains, as specified in ETSI GS NFV-IFA 030. For instance, the APIs of ETSI GS NFV-SOL 011 enable reusing an NS instance deployed on a domain A and nest it into another NS instance deployed on a domain B. Due to the functional similarities with existing capabilities offered by the NFVO to other systems such as OSS/BSS, most of the APIs are identical or based on those specified in ETSI GS NFV-SOL 005.

The release of new API specification documents was completed in 2020 by the ETSI GS NFV-SOL 012 V3.4.1 "NFV; Protocol and Data Models; RESTful protocols specification for the Policy Management Interface". As its title hints, the document specifies a new NFV-MANO API based on RESTful principles that can be used for setting up a "Policy management framework" (FEAT07). The API, produced by the NFV-MANO functional blocks, offers the much needed management capabilities by the network operators to be able to transfer, update, delete, activate, de-activate policies, and subscribe to and get notifications related to policy management. Note that the specification of the data models and formats of the policy content is not within the scope of this document. Information and data modelling work on policy content is under development as part of the Release 4.



The ETSI Industry Specification Group (ISG) NFV has published the initial release of ETSI GS NFV-IFA 040 titled "Requirements for service interfaces and object model for OS container management and orchestration specification". This document is the first normative specification delivered for the NFV Release 4 feature on “Cloud-native VNFs and Container Infrastructure management”. The specification propagates the recommendations from the study in ETSI GR NFV-IFA 029 and formally specifies the new functions required for the management and orchestration of OS containers, the Container Infrastructure Service Management (CISM) and the Container Image Registry (CIR). The CISM is responsible for maintaining the containerized workloads while the CIR is responsible for storing and maintaining information of OS container software images.NFV release 4 FEAT 17 blogpost

To enable a consistent and generic system for the management of containerized VNFs, ETSI GS NFV-IFA 040 specifies an abstract NFV object model for OS container management and orchestration, including their relationship to the core information models of NFV-MANO. The abstract NFV objects are also expected to be used in specifications profiling APIs of de-facto standard solutions, to map the abstract NFV objects to objects of the specific de-facto standard solution. One of the introduced abstract NFV objects is the Managed Container Infrastructure Object (MCIO), an object managed and exposed by the CISM, characterized by the desired and actual state of a containerized workload. Managed objects from Kubernetes® such as Deployment or Service are examples which map to an MCIO. Another new NFV object is the Managed Container Infrastructure Object Package (MCIOP), a hierarchical aggregate of information objects including declarative descriptors and configuration files for one or multiple MCIOs. Helm charts as specified by CNCF® are an example which maps to an MCIOP.

Furthermore, ETSI GS NFV-IFA 040 specifies requirements on the list of services to be offered by architectural elements providing the CISM and CIR functions and on the interfaces for exposing these services to NFV-MANO and other consuming entities. The CISM shall provide services for the management of OS container workloads as well as for the management of OS container compute, storage, network resources and their configuration. The CIR shall provide a service for the management of OS container images. This document intentionally does not specify interface operations or information models​ but only requirements on the management service interfaces. This approach leaves further details to the specification of protocols and data models in the form of profiling de-facto standard open source solutions.



The ETSI NFV community met for its twenty ninth plenary meeting (NFV#29) from 17 to 21 February at the Home of NFV, ETSI Headquarters, in Sophia-Antipolis, France. This time, the plenary meeting took place amidst the unfortunate situation, the Coronavirus outbreak that has hit so many countries and seriously impacted standardization work, and life in general almost worldwide. Consequently, some of our delegates were not able to travel and attend the meeting physically. Our best wishes to all of you all around the world who have been impacted by the outbreak, "wishing you a good and quick recovery".

Addressing the impact of this outbreak on the handling of the plenary meeting, ETSI provided outstanding support, as usual, by enabling remote access for participants that could not travel. Furthermore, the ISG and working group officials made a very good job of adapting the schedule and working procedures to facilitate the active participation and contributions of the remote delegates. As for those of us that had the opportunity to attend the plenary physically, ETSI had provided a very useful new facility: the delegates participating F2F could check-in for the first time by scanning their meeting QR code using a check-in station in the ETSI lobby. check in

All in all, despite the circumstances, the plenary meeting was once again a success. All working groups made steady progress in most of the work items that are currently being developed as part of the Releases 3 and 4.

With regards to Release 4 work, Marcus Brunner (Swisscom), chair of the Network Operators Council (NOC) provided additional input from the network operators at the closing plenary. Some of the discussion points concerned the direction in which the specification of the cloud-native capabilities in NFV is being performed, including containers and Platform-as-a-Service (PaaS). On behalf of the NOC, Marcus also highlighted the importance of deeply embracing more efficient CI/CD and software upgrade mechanisms to cope with the challenges that operators are having for integrating and maintaining current and future NFV deployments. The plenary welcomed the input from the operator community and acknowledged the need for the ETSI NFV to stay focused and address the challenges with diligence.

A couple of weeks after this meeting, ETSI published a brand new animated video explaining the importance of virtualizing network functions in just two minutes.

 

As ETSI NFV has done on previous occasions, there was an evening session. This time the topic was not about ETSI NFV work program matters, or discussions specific to NFV technologies. Instead, colleagues from ETSI CTI introduced the new working methods and tools that ETSI are preparing to make the development of the specifications more agile. A demo enabled the delegates to see the already advanced development status of these tools. Several ETSI NFV delegates provided their feedback, which was also greatly welcomed by the presenters. As a matter of fact, several working groups in the ETSI NFV already make use of agile and software development tools while performing their work. I would say that the ETSI NFV has been a pioneer in ETSI in making use of version control, code development and bug tracking tools.



For its 27th plenary meeting, the ETSI Industry Specific Group (ISG) on Network Functions Virtualisation (NFV) met at Orange Gardens, the recent Research and Innovation Campus of Orange, located in Châtillon, a small town in the outskirts of Paris, France. The meeting is to be remembered as the one where the contents of NFV Release 4 started to materialize with the approval of 8 work items.

The opening session started with an uplifting presentation from Diego Lopez, the chair of the ISG, highlighting the challenges to be addressed by standardization bodies to cope with the transformation of the telco industry ecosystem and processes. I liked the comment he made to invite delegates to resist the temptation of creating new terms and acronyms (e.g. Cloud-Native Network Functions / CNF vs. Virtualised Network Functions / VNF) to catch-up with buzzwords. After all, whether the software of a VNF is designed according to cloud-native patterns or not, the VNF remains a VNF!

After the opening plenary, the bulk of the work was performed during three intense days where delegates divided in six working groups to process hundreds of contributions.

Group photo of participants at 27th NFV plenary meeting



After a year long effort, ETSI has just released the first specification of a Yet Another Next Generation (YANG) data model for NFV descriptors, ETSI GS NFV-SOL 006. The specification is based on ETSI GS NFV-IFA 011 and ETSI GS NFV-IFA 014, and can be found on the ETSI server, with the corresponding YANG files can be found on the Forge website. The specification covers VNFD, PNFD and NSD. It enables on-boarding of NFV descriptors on YANG-based MANO functions, in a standard way. The flexibility and the ability to define network services, and to do it quickly is the true strength of the specification.



The ETSI NFV community met for its twenty sixth plenary meeting (NFV#26) from 20-24 May 2019 at NFV’s home, ETSI Headquarters, in Sophia-Antipolis, France.

Photo of ETSI main building in drone view

Visiting the breezy and sunny Provence and Cote d’Azur in May is always quite an experience. Many of our meeting delegates were greeted this time at Nice Airport, by photographers (and paparazzi). The reason for such a warm welcome might not be due to the Cannes Film Festival taking place the same week, but instead due to “our NFV stars” setting down, yet again, for another productive and successful meeting.

Meeting room with chair people of nfv#26 plenary meeting

While the NFV#25 plenary meeting served as a warm-up for what would come after Release 3, NFV#26 should be forever remembered as the kicking-off of Release 4. Let me elaborate more on this.