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.

ETSI GS NFV-TST 010 (TST010) is a published API conformance testing specification for NFV Management and Orchestration (NFV-MANO) APIs. Specifically, it contains conformance tests for the APIs used on the following reference points:

  • Os-Ma-Nfvo, defined by ETSI GS NFV-SOL 005 (SOL005)
  • Ve-Vnfm, defined by ETSI GS NFV-SOL 002 (SOL002)
  • Or-Vnfm, defined by ETSI GS NFV-SOL 003 (SOL003)

The figure below shows the reference points supported by TST010:

NFV TST010 blogpost

The latest released version of TST010 is Version 2.6.1 (available from the ETSI website), which means that it supports the corresponding 2.6.1 versions of the above SOL documents (i.e. SOL02, SOL003 and SOL005). Version 2.4.1 is also available, and it similarly corresponds to the 2.4.1 versions of the SOL documents. This will always be the case going forward as well: the TST010 version will always match the corresponding version of the SOL documents specifying the reference points being tested.

The ETSI NFV Industry Specification Group (ISG) has completed the initial release of ETSI GS NFV-SOL 014 titled "YAML data model specification for descriptor-based virtualised resource management". The specification focuses on a set of YAML-based data models used between NFVO and VIM (Or-Vi reference point), and also between VNFM and VIM (Vi-Vnfm reference point) for exchanging information on virtualised resources and their management. The work item and resulting document addresses specification gaps in the area of virtualised resource management and aim at enhancing the integration and interoperability of VNFM and NFVO with VIM solutions.

imageNFVblogSOL14 Medium

In the ETSI NFV specifications, interfaces and information models for the Or-Vi and Vi-Vnfm reference points have been specified in ETSI GS NFV-IFA 005 and ETSI GS NFV-IFA 006 respectively. Based on those specifications, the objective of ETSI GS NFV-SOL 014 is to define a set of YAML-based data models for representing information exchanged over these reference points as input and outputs to perform virtualised resource management. The descriptor-based virtualised resource management assumes a type of VIM which supports templates declaring parameters, requirements, lifecycle and composition of sets of virtualised resources.

Following intense technical work, ETSI NFV has just released ETSI GS NFV-SOL 016, the first stage 3 specification of NFV-MANO procedures in NFV Release 2 addressing interactions across several NFV-MANO functional blocks and/or interfaces. This specification builds on the ETSI NFV-MANO API specifications ETSI GS NFV-SOL 005, ETSI GS NFV-SOL 003 and ETSI GS NFV-SOL 002 which have defined the mandatory and optional operations and data attributes per individual NFV-MANO interface. As these specifications are focusing on individual interfaces, it is left up to the operator or the integrator to stitch together the information across different NFV-MANO interfaces to realize the NFV-MANO procedures involving interactions across several NFV-MANO functional blocks and/or interfaces, also referred to as end-to-end procedures. This might lead to various interpretations of how the end-to-end NFV-MANO procedures should work. ETSI GS NFV-SOL 016 defines procedures for selected key NFV-MANO procedures with the target to improve interoperability end-to-end.

labyrinthblogNFV Medium

The first released version of ETSI GS NFV-SOL 016 addresses five selected key NFV-MANO procedures, namely on-boarding of a VNF package, instantiation of a network service, termination of a network service instance, scaling of VNF instances in a network service instance and changing the external connectivity of VNF instances in a network service instance.

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.

ETSI ISG NFV was warmly welcomed back to Japan for NFV#28! Five years have passed since the group was in Okinawa in May 2014 for NFV#6.

This time, the ETSI NFV Industry Specification Group (ISG) met from 2 to 6 December 2019 at Across Fukuoka in Fukuoka, Japan. Fukuoka is located on the north of Kyushu, the southernmost of the four major Japanese islands. Fukuoka is well known for its local food, especially, the Hakata-Ramen, which are extremely tasteful and popular. In addition, it was the perfect season to see autumn leaves in Japan.

Group photo with participants of NFV#28 

In the opening plenary, Diego Lopez the ISG chairman, shared his current perspectives on NFV standardization and the industry’s landscape using a Japanese cartoon. I feel the technology trends around the network industry are getting shorter whilst the scope continues to broaden in response to the demands of network technology evolution, the expansion of open source, and new use cases. I think our ETSI NFV community is adjusting towards the right way forward from a standards point of view and cooperating with other SDOs remains important. Release 4 is going at full speed, and as an example, the discussion around container technology and its adaptation for NFV use cases is gaining much more momentum, with an increasing number of work items and related contributions.

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 chairman 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.

Refreshed after the winter break and starting 2019 with renewed energy, the ISG community met for its 25th ISG plenary meeting in the sunny Beijing, hosted by Huawei Technologies.

The meeting was held in the week after the Chinese New Year, which left the cheerful spark of the celebrations over Beijing city.


Several elections were held during February and the formal appointments were made at the NFV#25 plenary. Two ISG Vice-chair positions were filled, by the re-election of Cristina Badulescu, Ericsson and Bruno Chatras, Orange for the next term. The new Security WG Chair is Alex Leadbeater, BT, a veteran in the SEC WG and the former SEC WG Vice-chair. Stefan Arntzen, Huawei, current Reliability WG Chair was re-elected and will continue for another term.

A productive meeting closing a prolific year, the 24th NFV ISG meeting had a fortunate setting in a mildly weathered first week of December on French Riviera.

The NFV#24 meeting was marked by some internal community metamorphosis, such as the approval of the restructuring of the ISG and the election of a new Network Operators Council (NOC) Chairman.

Don Clarke (CableLabs), our NFV NOC Chairman over the last years, is one of the biggest industry advocates for ETSI NFV work and its network transformation potential to support the service providers. He kept us connected to the operators’ perspective and the practical deployment aspects, and for all this I’ve got good indication that I’m not alone in feeling thankful for all Don’s hard work.

We welcomed Marcus Brunner (Swisscom), the new NOC Chairman, as we dived right away into the latest NOC priorities while Marcus walked us through them on behalf of the NOC. The operators consolidated view on current deployment pain points, encouraged the NFV community to preserve focus on multi-vendor orchestration systems, simplifying procedures and APIs, as well as completing specifications to support essential network operations such as VNF migration, updates and upgrades, multi-site connectivity.

One of the week’s highlights was the pre-planned co-location with a rising star, ETSI ISG ZSM (Industry Specification Group Zero touch network and Service Management). The evening joint workshop was moderated by the two ISG Chairs and their respective lady Vice-Chairs. In the very well-attended workshop, the young ISG ZSM introduced the ZSM current architecture as defined in the ZSM 002 specification, and afterwards both ISG representatives presented the results of an early joint analysis on identifying the relationship in between ZSM and NFV, and the next steps in their collaboration.

NFV24 blog

The NFV#24 week rewarded us with good progress in exchange for the long working days we have spent together drafting, reviewing and revising contributions, out of reach from the warming sun of the French Riviera.

I’d never been to Montreal (or Quebec) until this summer, and I had the double pleasure of visiting Montreal just before my holidays, as well as soon after them. These visits allowed me to get acquainted with Quebecois summer (surprisingly warmer than back home, in Southern Spain), several delicacies (both poutine and the amazing smoked meat, and some really good microbreweries), the crowded Montreal airport (at least on Friday evenings), and the easygoing nature of a city that makes life so smooth and work so productive.

And a productive week it was indeed. It was the first meeting after I was appointed chair of ETSI NFV for a second term, an honor I really appreciate and that I can only respond to by committing to do my best to keep ISG NFV where this extraordinary community has already brought it: at the core of the radical transformation towards the next generation of networks. And the leadership team is strengthened with the re-appointment of Joan Triay (NTT DOCOMO) as chair of the Technical Steering Committee, leaving the technical management of our extensive work program in the best possible hands.

It was also a meeting for consolidating our vision for the future, defining a common view that, with all the natural differences among the diverse organizations contributing to the NFV effort, will guide us in a new two-year term for the ISG. There was an in-depth discussion about the future of the group during one of our much-loved evening sessions, and the goals for the new term were agreed and submitted to the ETSI Director General for approval, just in time to be discussed at the September ETSI Board meeting.Group photo of participants at NFV23The initial phase, in which the basic NFV concepts and the NFV architectural framework were defined, established a firm foundation for the extensive specification work required to enable an open ecosystem for this new technology. Building on this foundation, as well as climbing a very steep learning curve, required the two first terms of the ISG, with the third that is about to be completed, focused on making the NFV promise suitable for real operations, and establishing the baseline for telecommunications and enterprise networks evolution, infrastructure deployment, service development, and management automation in a software-defined networking world.

What is more, the ISG has managed to explore and enhance the consensus mechanisms required to more rapidly define standards by fostering collaboration with SDOs and related initiatives, especially open-source communities. We have facilitated fruitful practical collaboration with these communities, and the industry in general, boosting prospects for interoperability, as demonstrated by the three successful interoperability events held to date. The ETSI NFV community intends to continue consolidating, improving and evolving the NFV foundation specifications as the key enablers of an ecosystem and strengthening the cross-industry collaborative mechanisms which will boost progress and ensure an agile response to the evolving industry needs.

As I flew to Sophia Antipolis for the twenty second plenary session of the ETSI NFV Industry Specification Group (ISG), I reflected how far we had come since publication of the now famous white paper introducing the NFV concept.

Until that moment in October 2012, the term “Network Function Virtualisation” did not exist, it had emerged from a meeting of the founding group in Paris in the summer of 2012 to distinguish the topic from SDN which by then was gaining momentum. We were all experienced telecommunications R&D leaders who knew that our goals were ambitious and would be highly disruptive to the industry, so we would need to be extraordinarily diligent to bring all the industry players on board, large and small, and with everyone able to be heard and to contribute their energies and expertise.

We chose ETSI to host the effort for many different reasons, but perhaps the most important ones were transparency of governance proven by many years of global standards development, and open membership for small players, especially independent software vendors whom we felt would be important contributors. We have never regretted the decision to come to ETSI who have provided fantastic support, and the rigorously consensus-driven decision-making process has kept us grounded.

leadership-NFV22-2018All of that seemed so long ago and I couldn’t have imagined that along the way I would move to the United States and start a new career in the cable industry while retaining my role as chair of the ETSI NFV Network Operator Council. After a 40+ year R&D career in BT, it was a seamless transition that was as unlikely as it was life changing for me.

Looking back over the past six years, there have been moments of great pride, such as when agreement was reached in a late-night session on the ETSI NFV Architectural Framework, interspersed with moments of doubt as strident voices from the world of software repeatedly criticized our efforts.

As with all things, time is a great leveler, five years on the NFV Architectural Framework has withstood the test of time and is being deployed at scale, and open source groups have begun to realize that the telecommunications networks environment is very different to the enterprise IT environment. Telecommunications networks are critical national infrastructures that underpin global commerce and security and as such demand analytical rigor and auditability that only implementations based on high quality specifications endorsed by the key stakeholders can provide.

Even as we took a page from the open source book and opened our draft specifications for external scrutiny and feedback and continually sought ways to speed up our work. And we founded OPNFV to enable open source groups to collaborate and provide feedback to ETSI NFV.

The NFV community met for the 21st time (NFV#21) from February 26 to March 2, in a familiar setting:

ETSI-snowflakes-NFV21-2018ETSI headquarters in Sophia Antipolis, France.

The flawless organization, the friendly faces greeting us, the countless wonderful coffee machines, everything was normal. What was less familiar: it snowed. On the Cote d’Azur. Twice(!). For a total of approximately 15cm. This is very rare in this region. Apparently, the last time it snowed was during NFV#1, back in January 2013. While we are solving the challenges for NFV, the weather is telling us we can easily deal with another one!

Despite the predictable flight delays resulting from the frigid European weather, the event was well attended by over 80 members of the core team. And it was a busy, productive week.

Work on Release 3 is well under way. There are currently 17 new features being actively developed, along with 15 active work items related to Release 3. In addition, multiple Release 2 deliverables (13 as of now) are being currently propagated to Release 3 (with their corresponding work items). At NFV#21, a third maintenance cycle for Release 2 work items was also approved, so the maintenance work will continue for the first half of 2018. That’s a lot of balls up in the air at the same time, and it’s a remarkable achievement that this highly focused group can pull this off.

The results of the 2nd ETSI NFV Plugtests were center stage at this meeting: the findings were presented to the plenary and discussed within the TST working group who will incorporate the feedback into their documents going forward. Clearly the industry is progressing with more energy compared with just one year ago. The Plugtests results will be summarized in a separate blog post and presented at upcoming conferences.

Two new working group leaders were elected since the last plenary meeting: Julien Maisonneuve (Nokia) and Ulrich Kleber (Huawei). Julien brings extensive leadership experience, while Uli brings new perspectives including valuable open source experience. These roles require a lot of personal commitment and long hours across multiple time zones. We are very grateful to both of them.

With the publication of ETSI GS NFV-SOL005, the specification of the RESTful APIs exposed by an NFV Orchestrator (NFVO) towards operations support systems (OSS), the ETSI NFV Industry Specification Group (ISG) has successfully met its objective to deliver a full set of API specifications enabling an open ecosystem where Virtualized Network Functions (VNFs) will be interoperable with independently developed management and orchestration systems, and where the components of a management and orchestration system are themselves interoperable.

Encouraging interoperability within an open ecosystem was a key objective for ETSI NFV when it was launched in late 2012 by global carriers.

These API specifications are the result of a wide industry consensus. Compliance to them permits a wide range of multi-vendors deployment scenarios. For example, a VNF can be managed by a generic VNF Manager (VNFM) function (stand-alone or combined with an NFVO), an NFVO can consume the services of a VNF-specific VNFM, and the services exposed by an NFVO can be consumed by higher-level service orchestration functions.

Furthermore, the ISG has completed revisions of two previously published API specifications which detail the REST APIs between an NFV Orchestrator (NFVO) and a VNF Manager (VNFM), and between a VNFM and a VNF or its Element Manager, respectively ETSI GS NFV-SOL 003 and ETSI GS NFV-SOL 002, completed in July 2017. Revised versions have been approved in December 2017, the main change being the support of a TLS-based option for controlling API access authorization (as an alternative to the use of OAuth 2.0).

ETSI NFV industry adoption survey

2018-02-07 Posted by NFV support 4205 Hits

The ETSI Industry Specification Group on NFV is developing a set of specifications and reports with the goal to enable an open NFV market, where Virtualised Network Functions (VNFs) are interoperable and packaged in a way that is independent of the vendor supplying them or the service provider consuming them, are interoperable with independently developed management systems, and are operable in a manner that is independent from the underlying hardware.

Since its creation the ISG has produced over 60 specifications and reports. It is of paramount importance to the ISG to make sure that the specifications it produces meets the expectations of the industry.

The ISG has created a survey to help understand which of these specifications are the most useful to the industry. Should you wish to participate to this survey, please follow this link: https://www.surveymonkey.com/r/NFV_Industry_Adoption

The ETSI NFV Industry Specification Group (ISG) met on 4-8 December 2017 for its twentieth plenary meeting (NFV#20) at ETSI Headquarters in Sophia-Antipolis, France. This time, the breezy and sunny Provence & Cote d’Azur in the spring changed to a rather chilly and icy setting, but nothing that our brave ETSI NFV ISG delegates could not handle perfectly with heated discussions and some extra coffee (or tea).

As reported in previous posts, the NFV ISG has been planning and progressing the set of Release 3 feature reports. The latest interim NFV Announcement report provides an overview of the progress made by the different NFV ISG working groups until and up to NFV#19. At the NFV#20 meeting, a significant step forward was achieved with approval to create the related normative work items. But this meeting wasn’t all about Release 3, as the working groups were also very busy completing the second round of Release 2 maintenance work.

Describing all the great work performed by the working groups and NFV ISG delegates worldwide is not an easy task. The meeting venue was again the perfect setting for many intense interactions and discussions. As Technical Manager, my sincere appreciation and thanks go out to all the delegates for the work achieved as well as the excellent collaboration between the working groups.

Among the many highlights at NFV#20, there was one shadow; NFV#20 was the meeting in which, unfortunately, we said goodbye to Yun Chao Hu (EVE WG Chairman, Huawei), a long-standing NFV contributor from the inception of NFV. Yun Chao has worked exceptionally hard to help our work. An award for Yun Chao’s outstanding work and support to the NFV ISG was delivered by our ISG Chairman, Diego Lopez (Telefonica). We wish to Yun Chao “all the best in your future professional tasks, and hope to see you again in other places”.

Photo of Yun Chao Hu and Diego Lopez at NFV20

Anyway, let us highlight a few relevant achievements from NFV#20.

NFV-19-1smallLast week in Denver, CableLabs hosted over 130 delegates from all over the world to the 19th plenary session of the ETSI NFV Industry Specification Group, the cradle and main playground for the Network Function Virtualization technologies that are bringing radical transformation to the telecommunications industry. With over 300 member companies including 38 global network operators, ETSI NFV is the leading forum developing the foundation international standards for NFV.

This blogpost provides a snapshot report on the progress of ETSI NFV standardization.

Home-of-NFVThe ETSI NFV Industry Specification Group (ISG) has completed an essential step towards enabling an open ecosystem where Virtualised Network Functions (VNFs) will be interoperable with independently developed management and orchestration systems, and where the components of a management and orchestration system are themselves interoperable.