Analysis of the SFC scalability
draft-ao-sfc-scalability-analysis-02

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
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)
SFC WG                                                             T. Ao
Internet-Draft                                           ZTE Corporation
Intended status: Informational                                 G. Mirsky
Expires: September 14, 2017                                    ZTE Corp.
                                                          March 13, 2017

                    Analysis of the SFC scalability
                  draft-ao-sfc-scalability-analysis-02

Abstract

   SFC is an ordered set of service function, should be scalable to meet
   numerous requirements.  The scalability of SFC can be interpreted as
   ability of the SFC to accommodate one or more SFs joining the SFC ,
   or leaving the SFC without significant impact to SFC performance.

   This document presents four use cases on SFC scale-out and scale-in,
   and analysis of the requirements to support such capability.

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 September 14, 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

Ao & Mirsky            Expires September 14, 2017               [Page 1]
Internet-Draft       Analysis of the SFC scalability          March 2017

   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Four Use cases for scale-out/scale-in . . . . . . . . . . . .   3
     3.1.  Join  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Redundancy  . . . . . . . . . . . . . . . . . . . . . . .   3
     3.3.  By-pass . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.4.  Failure or Remove . . . . . . . . . . . . . . . . . . . .   4
   4.  Data Plane Requirements . . . . . . . . . . . . . . . . . . .   4
   5.  Control Plane Requirements  . . . . . . . . . . . . . . . . .   5
     5.1.  Centralized CP  . . . . . . . . . . . . . . . . . . . . .   5
     5.2.  Distributed CP  . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Information References  . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Service Function Chain (SFC) is the chain with a series of ordered
   Service Functions(SF).  The SFC maybe changed because of load balance
   , failure, or other management requirement.  We call it SFC
   scalability.  The SFC being scalable means that the Service Functions
   can be added or removed from the path of this SFC.  With this
   capability, SFC is more flexible and elastic to adapt all kinds of
   requirements.

   In this document, we will present four use cases on SFC scale-out and
   scale-in, and analysis some requirements to support such capability.

2.  Terminology

   SFC(Service Function Chain): An ordered set of some abstract SFs.

   SFC Scale-out: One or more SFs are added into the path of the SFC for
   the sake of load balance, protection or other new services
   requirement.

   SFC Scale-in: One or more SFs are removed from the path of the SFC
   for the sake of the SFs are by-passed or the SFs are failed.

Ao & Mirsky            Expires September 14, 2017               [Page 2]
Internet-Draft       Analysis of the SFC scalability          March 2017

3.  Four Use cases for scale-out/scale-in
Show full document text