draft-ietf-bmwg-vswitch-opnfv-01.txt   draft-ietf-bmwg-vswitch-opnfv-02.txt 
Network Working Group M. Tahhan Network Working Group M. Tahhan
Internet-Draft B. O'Mahony Internet-Draft B. O'Mahony
Intended status: Informational Intel Intended status: Informational Intel
Expires: April 17, 2017 A. Morton Expires: October 19, 2017 A. Morton
AT&T Labs AT&T Labs
October 14, 2016 April 17, 2017
Benchmarking Virtual Switches in OPNFV Benchmarking Virtual Switches in OPNFV
draft-ietf-bmwg-vswitch-opnfv-01 draft-ietf-bmwg-vswitch-opnfv-02
Abstract Abstract
This memo describes the progress of the Open Platform for NFV (OPNFV) This memo describes the progress of the Open Platform for NFV (OPNFV)
project on virtual switch performance "VSWITCHPERF". This project project on virtual switch performance "VSWITCHPERF". This project
intends to build on the current and completed work of the intends to build on the current and completed work of the
Benchmarking Methodology Working Group in IETF, by referencing Benchmarking Methodology Working Group in IETF, by referencing
existing literature. The Benchmarking Methodology Working Group has existing literature. The Benchmarking Methodology Working Group has
traditionally conducted laboratory characterization of dedicated traditionally conducted laboratory characterization of dedicated
physical implementations of internetworking functions. Therefore, physical implementations of internetworking functions. Therefore,
skipping to change at page 1, line 48 skipping to change at page 1, line 48
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 17, 2017. This Internet-Draft will expire on October 19, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 46 skipping to change at page 2, line 46
5.5. Speed of Operation . . . . . . . . . . . . . . . . . . . 17 5.5. Speed of Operation . . . . . . . . . . . . . . . . . . . 17
5.6. Accuracy of Operation . . . . . . . . . . . . . . . . . . 17 5.6. Accuracy of Operation . . . . . . . . . . . . . . . . . . 17
5.7. Reliability of Operation . . . . . . . . . . . . . . . . 17 5.7. Reliability of Operation . . . . . . . . . . . . . . . . 17
5.8. Scalability of Operation . . . . . . . . . . . . . . . . 18 5.8. Scalability of Operation . . . . . . . . . . . . . . . . 18
5.9. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.9. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 18
6. Security Considerations . . . . . . . . . . . . . . . . . . . 18 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
9.1. Normative References . . . . . . . . . . . . . . . . . . 19 9.1. Normative References . . . . . . . . . . . . . . . . . . 19
9.2. Informative References . . . . . . . . . . . . . . . . . 21 9.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
Benchmarking Methodology Working Group (BMWG) has traditionally Benchmarking Methodology Working Group (BMWG) has traditionally
conducted laboratory characterization of dedicated physical conducted laboratory characterization of dedicated physical
implementations of internetworking functions. The Black-box implementations of internetworking functions. The Black-box
Benchmarks of Throughput, Latency, Forwarding Rates and others have Benchmarks of Throughput, Latency, Forwarding Rates and others have
served our industry for many years. Now, Network Function served our industry for many years. Now, Network Function
Virtualization (NFV) has the goal to transform how internetwork Virtualization (NFV) has the goal to transform how internetwork
functions are implemented, and therefore has garnered much attention. functions are implemented, and therefore has garnered much attention.
This memo summarizes the progress of the Open Platform for NFV This memo summarizes the progress of the Open Platform for NFV
(OPNFV) project on virtual switch performance characterization, (OPNFV) project on virtual switch performance characterization,
"VSWITCHPERF", through the Brahmaputra (second) release [BrahRel]. "VSWITCHPERF", through the Brahmaputra (second) release [BrahRel].
This project intends to build on the current and completed work of This project intends to build on the current and completed work of
the Benchmarking Methodology Working Group in IETF, by referencing the Benchmarking Methodology Working Group in IETF, by referencing
existing literature. For example, currently the most often existing literature. For example, currently the most often
referenced RFC is [RFC2544] (which depends on [RFC1242]) and referenced RFC is [RFC2544] (which depends on [RFC1242]) and
foundation of the benchmarking work in OPNFV is common and strong. foundation of the benchmarking work in OPNFV is common and strong.
See https://wiki.opnfv.org/ See [VSPERFhome] for more background, and the OPNFV website for
characterize_vswitch_performance_for_telco_nfv_use_cases for more general information [OPNFV].
background, and the OPNFV website for general information:
https://www.opnfv.org/
The authors note that OPNFV distinguishes itself from other open The authors note that OPNFV distinguishes itself from other open
source compute and networking projects through its emphasis on source compute and networking projects through its emphasis on
existing "telco" services as opposed to cloud-computing. There are existing "telco" services as opposed to cloud-computing. There are
many ways in which telco requirements have different emphasis on many ways in which telco requirements have different emphasis on
performance dimensions when compared to cloud computing: support for performance dimensions when compared to cloud computing: support for
and transfer of isochronous media streams is one example. and transfer of isochronous media streams is one example.
Note also that the move to NFV Infrastructure has resulted in many Note also that the move to NFV Infrastructure has resulted in many
new benchmarking initiatives across the industry. The authors are new benchmarking initiatives across the industry. The authors are
skipping to change at page 19, line 19 skipping to change at page 19, line 19
8. Acknowledgements 8. Acknowledgements
The authors appreciate and acknowledge comments from Scott Bradner, The authors appreciate and acknowledge comments from Scott Bradner,
Marius Georgescu, Ramki Krishnan, Doug Montgomery, Martin Klozik, Marius Georgescu, Ramki Krishnan, Doug Montgomery, Martin Klozik,
Christian Trautman, and others for their reviews. Christian Trautman, and others for their reviews.
9. References 9. References
9.1. Normative References 9.1. Normative References
[NFV.PER001]
"Network Function Virtualization: Performance and
Portability Best Practices", Group Specification ETSI GS
NFV-PER 001 V1.1.1 (2014-06), June 2014.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC2285] Mandeville, R., "Benchmarking Terminology for LAN [RFC2285] Mandeville, R., "Benchmarking Terminology for LAN
Switching Devices", RFC 2285, DOI 10.17487/RFC2285, Switching Devices", RFC 2285, DOI 10.17487/RFC2285,
February 1998, <http://www.rfc-editor.org/info/rfc2285>. February 1998, <http://www.rfc-editor.org/info/rfc2285>.
[RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis,
"Framework for IP Performance Metrics", RFC 2330,
DOI 10.17487/RFC2330, May 1998,
<http://www.rfc-editor.org/info/rfc2330>.
[RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for
Network Interconnect Devices", RFC 2544, Network Interconnect Devices", RFC 2544,
DOI 10.17487/RFC2544, March 1999, DOI 10.17487/RFC2544, March 1999,
<http://www.rfc-editor.org/info/rfc2544>. <http://www.rfc-editor.org/info/rfc2544>.
[RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way [RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way
Delay Metric for IPPM", RFC 2679, DOI 10.17487/RFC2679, Delay Metric for IPPM", RFC 2679, DOI 10.17487/RFC2679,
September 1999, <http://www.rfc-editor.org/info/rfc2679>. September 1999, <http://www.rfc-editor.org/info/rfc2679>.
[RFC2680] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way
Packet Loss Metric for IPPM", RFC 2680,
DOI 10.17487/RFC2680, September 1999,
<http://www.rfc-editor.org/info/rfc2680>.
[RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip
Delay Metric for IPPM", RFC 2681, DOI 10.17487/RFC2681,
September 1999, <http://www.rfc-editor.org/info/rfc2681>.
[RFC2889] Mandeville, R. and J. Perser, "Benchmarking Methodology [RFC2889] Mandeville, R. and J. Perser, "Benchmarking Methodology
for LAN Switching Devices", RFC 2889, for LAN Switching Devices", RFC 2889,
DOI 10.17487/RFC2889, August 2000, DOI 10.17487/RFC2889, August 2000,
<http://www.rfc-editor.org/info/rfc2889>. <http://www.rfc-editor.org/info/rfc2889>.
[RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation
Metric for IP Performance Metrics (IPPM)", RFC 3393,
DOI 10.17487/RFC3393, November 2002,
<http://www.rfc-editor.org/info/rfc3393>.
[RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network
performance measurement with periodic streams", RFC 3432,
DOI 10.17487/RFC3432, November 2002,
<http://www.rfc-editor.org/info/rfc3432>.
[RFC3918] Stopp, D. and B. Hickman, "Methodology for IP Multicast [RFC3918] Stopp, D. and B. Hickman, "Methodology for IP Multicast
Benchmarking", RFC 3918, DOI 10.17487/RFC3918, October Benchmarking", RFC 3918, DOI 10.17487/RFC3918, October
2004, <http://www.rfc-editor.org/info/rfc3918>. 2004, <http://www.rfc-editor.org/info/rfc3918>.
[RFC4689] Poretsky, S., Perser, J., Erramilli, S., and S. Khurana,
"Terminology for Benchmarking Network-layer Traffic
Control Mechanisms", RFC 4689, DOI 10.17487/RFC4689,
October 2006, <http://www.rfc-editor.org/info/rfc4689>.
[RFC4737] Morton, A., Ciavattone, L., Ramachandran, G., Shalunov, [RFC4737] Morton, A., Ciavattone, L., Ramachandran, G., Shalunov,
S., and J. Perser, "Packet Reordering Metrics", RFC 4737, S., and J. Perser, "Packet Reordering Metrics", RFC 4737,
DOI 10.17487/RFC4737, November 2006, DOI 10.17487/RFC4737, November 2006,
<http://www.rfc-editor.org/info/rfc4737>. <http://www.rfc-editor.org/info/rfc4737>.
[RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J.
Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)",
RFC 5357, DOI 10.17487/RFC5357, October 2008,
<http://www.rfc-editor.org/info/rfc5357>.
[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
"Network Time Protocol Version 4: Protocol and Algorithms
Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010,
<http://www.rfc-editor.org/info/rfc5905>.
[RFC6201] Asati, R., Pignataro, C., Calabria, F., and C. Olvera, [RFC6201] Asati, R., Pignataro, C., Calabria, F., and C. Olvera,
"Device Reset Characterization", RFC 6201, "Device Reset Characterization", RFC 6201,
DOI 10.17487/RFC6201, March 2011, DOI 10.17487/RFC6201, March 2011,
<http://www.rfc-editor.org/info/rfc6201>. <http://www.rfc-editor.org/info/rfc6201>.
9.2. Informative References 9.2. Informative References
[BrahRel] "Brahmaputra, Second OPNFV Release https://www.opnfv.org/ [BrahRel] "Brahmaputra, Second OPNFV Release
brahmaputra". https://wiki.opnfv.org/display/SWREL/Brahmaputra".
[I-D.huang-bmwg-virtual-network-performance] [I-D.huang-bmwg-virtual-network-performance]
Huang, L., Rong, G., Mandeville, B., and B. Hickman, Huang, L., Rong, G., Mandeville, B., and B. Hickman,
"Benchmarking Methodology for Virtualization Network "Benchmarking Methodology for Virtualization Network
Performance", draft-huang-bmwg-virtual-network- Performance", draft-huang-bmwg-virtual-network-
performance-01 (work in progress), April 2015. performance-02 (work in progress), March 2017.
[I-D.ietf-bmwg-virtual-net] [I-D.ietf-bmwg-virtual-net]
Morton, A., "Considerations for Benchmarking Virtual Morton, A., "Considerations for Benchmarking Virtual
Network Functions and Their Infrastructure", draft-ietf- Network Functions and Their Infrastructure", draft-ietf-
bmwg-virtual-net-04 (work in progress), August 2016. bmwg-virtual-net-05 (work in progress), March 2017.
[IFA003] "https://docbox.etsi.org/ISG/NFV/Open/Drafts/ [IFA003] "https://docbox.etsi.org/ISG/NFV/Open/Drafts/
IFA003_Acceleration_-_vSwitch_Spec/". IFA003_Acceleration_-_vSwitch_Spec/".
[LTD] "LTD Test Specification [LTD] "LTD Test Specification
http://artifacts.opnfv.org/vswitchperf/brahmaputra/docs/ http://artifacts.opnfv.org/vswitchperf/brahmaputra/docs/
requirements/index.html". requirements/index.html".
[LTDoverV] [LTDoverV]
"LTD Test Spec Overview https://wiki.opnfv.org/wiki/ "LTD Test Spec Overview
vswitchperf_test_spec_review". https://wiki.opnfv.org/display/vsperf/
LTD+Test+Spec+Overview".
[OPNFV] "OPNFV Home https://www.opnfv.org/".
[RFC1242] Bradner, S., "Benchmarking Terminology for Network [RFC1242] Bradner, S., "Benchmarking Terminology for Network
Interconnection Devices", RFC 1242, DOI 10.17487/RFC1242, Interconnection Devices", RFC 1242, DOI 10.17487/RFC1242,
July 1991, <http://www.rfc-editor.org/info/rfc1242>. July 1991, <http://www.rfc-editor.org/info/rfc1242>.
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation
Applicability Statement", RFC 5481, DOI 10.17487/RFC5481, Applicability Statement", RFC 5481, DOI 10.17487/RFC5481,
March 2009, <http://www.rfc-editor.org/info/rfc5481>. March 2009, <http://www.rfc-editor.org/info/rfc5481>.
[RFC6049] Morton, A. and E. Stephan, "Spatial Composition of
Metrics", RFC 6049, DOI 10.17487/RFC6049, January 2011,
<http://www.rfc-editor.org/info/rfc6049>.
[RFC6248] Morton, A., "RFC 4148 and the IP Performance Metrics
(IPPM) Registry of Metrics Are Obsolete", RFC 6248,
DOI 10.17487/RFC6248, April 2011,
<http://www.rfc-editor.org/info/rfc6248>.
[RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New
Performance Metric Development", BCP 170, RFC 6390,
DOI 10.17487/RFC6390, October 2011,
<http://www.rfc-editor.org/info/rfc6390>.
[TestTopo] [TestTopo]
"Test Topologies https://wiki.opnfv.org/vsperf/ "Test Topologies https://wiki.opnfv.org/display/vsperf/
test_methodology". Test+Methodology".
[VSPERFhome]
"VSPERF Home https://wiki.opnfv.org/display/vsperf/
VSperf+Home".
Authors' Addresses Authors' Addresses
Maryam Tahhan Maryam Tahhan
Intel Intel
Email: maryam.tahhan@intel.com Email: maryam.tahhan@intel.com
Billy O'Mahony Billy O'Mahony
Intel Intel
 End of changes. 19 change blocks. 
77 lines changed or deleted 24 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/