Considerations for Benchmarking Service Function Chain
draft-kim-bmwg-sfc-benchmark-00

Document Type Active Internet-Draft (individual)
Last updated 2017-07-03
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                                    B. Koo
Intended status: Informational                                   J. Park
Expires: January 4, 2018                                         E. Paik
                                                                      KT
                                                           July 03, 2017

         Considerations for Benchmarking Service Function Chain
                    draft-kim-bmwg-sfc-benchmark-00

Abstract

   Service Function Chain(SFC) is a ordered set of service functions.
   Packets flow restrictively at the service functions according to the
   order.  To enable a network service, operator composes the service
   function chain logically.  Though SFC is efficient where network/
   service requirements are dynamically changing, the reliability of SFC
   should be guaranteed.  This memo describes the considerations for
   benchmarking SFC reliability.

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 January 4, 2018.

Kim, et al.              Expires January 4, 2018                [Page 1]
Internet-Draft     considerations for benchmarking sfc         July 2017

Copyright Notice

   Copyright (c) 2017 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.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Considerations for Benchmarking SFC Reliability . . . . . . .   3
     3.1.  Configuration Parameters for Benchmarking Test  . . . . .   3
     3.2.  Testing Parameter Benchmarking Test . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   As Service Function Chain(SFC) is the ordered set of service
   functions.  It is logically defined on demand of a service.  To
   enable the service, SDN controller set flow rules at each physical/
   virtual switch which belongs to the SFC.  SFC is efficient where the
   network/service requirements are keep changing dynamically.  The
   number of physical/virtual switches which will accept the flow rules
   is differ from the size of the domain or service.

   As an operator perspective, at the stage of SFC creation,
   modification, and deletion, the reliability of SFC should always be
   guaranteed.  To apply the change of the SFC, SDN controller will set
   flow rules at some switches and delete flow rules at other switches.
   For certain reasons such as the heavy traffic on the target switches
   which should accept new rules or the link failure between the target
   switches and the SDN controller, the new SFC may not be applied
   properly.

   This draft memo describes considerations for benchmarking Service
   Function Chain reliability.

Kim, et al.              Expires January 4, 2018                [Page 2]
Internet-Draft     considerations for benchmarking sfc         July 2017

2.  Scope

   At the time of writing this memo, SFC standardization is now in
   progress.  But operators and vendors are implementing SFC their own
   way.  This memo does not target NSH enabled architecture and target
   general operation circumstances.  The scope of SFC reliability
Show full document text