Service Function Chaining (SFC) Control Plane Components & Requirements
draft-ietf-sfc-control-plane-08

Document Type Active Internet-Draft (sfc WG)
Last updated 2016-11-15 (latest revision 2016-10-23)
Replaces draft-ww-sfc-control-plane
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Reviews
Stream WG state WG Document
Revised I-D Needed - Issue raised by AD
Document shepherd Martin Stiemerling
Shepherd write-up Show (last changed 2016-06-08)
IESG IESG state AD is watching
Consensus Boilerplate Yes
Telechat date
Responsible AD Alia Atlas
Send notices to "Martin Stiemerling" <mls.ietf@gmail.com>
Service Function Chaining (sfc)                        M. Boucadair, Ed.
Internet-Draft                                                    Orange
Intended status: Informational                          October 23, 2016
Expires: April 26, 2017

Service Function Chaining (SFC) Control Plane Components & Requirements
                    draft-ietf-sfc-control-plane-08

Abstract

   This document describes requirements for conveying information
   between Service Function Chaining (SFC) control elements and SFC data
   plane functional elements.  Also, this document identifies a set of
   control interfaces to interact with SFC-aware elements to establish,
   maintain or recover service function chains.  This document does not
   specify protocols nor extensions to existing protocols.

   This document exclusively focuses on SFC deployments that are under
   the responsibility of a single administrative entity.  Inter-domain
   considerations are out of scope.

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 April 26, 2017.

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

Boucadair                Expires April 26, 2017                 [Page 1]
Internet-Draft              SFC Control Plane               October 2016

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Assumptions . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Generic Considerations  . . . . . . . . . . . . . . . . . . .   6
     2.1.  Generic Requirements  . . . . . . . . . . . . . . . . . .   6
     2.2.  SFC Control Plane Bootstrapping . . . . . . . . . . . . .   6
     2.3.  SFC Dynamics  . . . . . . . . . . . . . . . . . . . . . .   7
     2.4.  Coherent Setup of an SFC-enabled Domain . . . . . . . . .   8
   3.  SFC Control Plane: Reference Architecture & Interfaces  . . .   8
     3.1.  Reference Architecture  . . . . . . . . . . . . . . . . .   8
     3.2.  Centralized vs. Distributed . . . . . . . . . . . . . . .  10
     3.3.  Interface Reference Points  . . . . . . . . . . . . . . .  11
       3.3.1.  C1: Interface between SFC Control Plane & SFC
               Classifier  . . . . . . . . . . . . . . . . . . . . .  11
       3.3.2.  C2: Interface between SFC Control Plane & SFF . . . .  13
       3.3.3.  C3: Interface between SFC Control Plane & SFC-aware
               SFs . . . . . . . . . . . . . . . . . . . . . . . . .  14
       3.3.4.  C4: Interface between SFC Control Plane & SFC Proxy .  16
   4.  Additional Considerations . . . . . . . . . . . . . . . . . .  16
     4.1.  Discovery of the SFC Control Element  . . . . . . . . . .  16
     4.2.  SF Symmetry . . . . . . . . . . . . . . . . . . . . . . .  17
     4.3.  Pre-deploying SFCs  . . . . . . . . . . . . . . . . . . .  17
     4.4.  Withdraw a Service Function (SF)  . . . . . . . . . . . .  17
     4.5.  SFC/SFP Operations  . . . . . . . . . . . . . . . . . . .  18
     4.6.  Unsolicited (Notification) Messages . . . . . . . . . . .  18
     4.7.  Liveness Detection  . . . . . . . . . . . . . . . . . . .  18
     4.8.  Monitoring & Counters . . . . . . . . . . . . . . . . . .  19
     4.9.  Validity Lifetime . . . . . . . . . . . . . . . . . . . .  19
     4.10. Considerations Specific to the Centralized Path
           Computation Model . . . . . . . . . . . . . . . . . . . .  20
       4.10.1.  Service Function Path Adjustment . . . . . . . . . .  20
Show full document text