Benchmarking Methodology for Service Function Chain Performance
draft-kim-bmwg-sfc-benchmark-meth-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                             T. Kim
Internet-Draft                                                     H. Yu
Intended status: Informational                                  C. Jeong
Expires: May 4, 2017                                              Y. Han
                                                                 E. Paik
                                                                      KT
                                                        October 31, 2016

    Benchmarking Methodology for Service Function Chain Performance
                  draft-kim-bmwg-sfc-benchmark-meth-00

Abstract

   Service Function Chain is the ordered set of service functions such
   as firewall, Deep Packet Inspection(DPI), virtualized Evolved Packet
   Core (vEPC), and etc,. Operators make chains with several service
   functions depending on the service which they have to provide.  The
   chain needs to be evaluated to measure the SLA.  This draft describes
   the benchmarking methodologies for Service Function Chain(SFC)
   performance and the affecting factors to SFC performance.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 4, 2017.

Kim, et al.                Expires May 4, 2017                  [Page 1]
Internet-Draft        sfc performance benchmarking          October 2016

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Definition of Terms . . . . . . . . . . . . . . . . . . . . .   3
   3.  Test Setup  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Test Topology . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Test Traffic  . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Benchmarking Test . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Connectivity  . . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  Performance . . . . . . . . . . . . . . . . . . . . . . .   5
       4.2.1.  E2E Latency . . . . . . . . . . . . . . . . . . . . .   5
       4.2.2.  E2E Packet Loss Rate  . . . . . . . . . . . . . . . .   5
       4.2.3.  E2E Bandwidth . . . . . . . . . . . . . . . . . . . .   6
   5.  Factors affecting the SFC Performance . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Service Function Chain is the ordered set of service functions such
   as firewall, Deep Packet Inspection(DPI), virtualized Evolved Packet
   Core (vEPC), and etc,. The service functions include virtualized
   network functions and physical network functions.  As the network
   infrastructure become virtualized, operators make chains with several
   service functions depending on the service which they have to
   provide.  The chain needs to be evaluated to measure the SLA.

   This draft describes the benchmarking methodologies for Service
   Function Chain(SFC) performance and the influential factors to SFC
Show full document text