Page tree
Skip to end of metadata
Go to start of metadata

VSPERF provides a framework where the entire NFV Industry can learn about NFVI data-plane performance and try-out new techniques together. 


VSPERF is contributing to development of ETSI NFV test specifications through the "TST" (the Test and Open Source Working Group).


A new IETF benchmarking specification RFC8204 has been approved based on VSPERF work since 2015.

IETF Summary Draft: vSwitch Performance Characterization

In order to communicate about this project in related
standards development organizations, the project team has agreed
to summarize the direction of our LTD spec in an Internet Draft,
and contribute that draft to the IETF Benchmarking Methodology
Working Group, or BMWG. The BMWG was re-chartered in 2014 to
include benchmarking for Virtualized Network Functions (VNF)
and their Infrastructure, so this appears to be welcome input.

BMWG is one of the longest-running working groups in IETF.
Many of the RFCs referenced in the LTD originated in the BMWG,
including foundation RFC 1242 and RFC 2544. OPNFV may benefit
from additional review of the IETF Benchmarking community, and
this Internet Draft affords that opportunity.

The current volunteer members from the vsperf project are:
Maryam Tahhan
Billy O'Mahony
Al Morton

The current authors have agreed to prepare the draft using one
of the IETF memo preparation tools, XML2RFC.

The initial "00" version of the draft was submitted July 3, 2015 for IETF-93 in Prague.

The revised "01" version was submitted October 16, 2015 for IETF-94 in Yokohama.

The revised "02" version was submitted March 21, 2016 for IETF-95 in Buenos Aires. This version was adopted by the working group.

The WG "00" version was submitted July 8, 2016 for IETF-96 in Berlin.

The WG "01" version was submitted October 14, 2016 for IETF-97 in Seoul, Korea.

The WG "02, 03, and 04" versions were submitted to the Internet Engineering Steering Group for evaluation and subsequent approval on June 8, 2017.

The RFC Editor organization will now process the text and assign the RFC number in the months ahead.



  • No labels