Service Function Chain Control Plane Overview
draft-wang-msv-using-virtual-line-card-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-02-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
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                                            D. Wang
Internet-Draft                                                     Q. Wu
Intended status: Standards Track                                X. Zhang
Expires: August 17, 2014                                          Huawei
                                                            M. Boucadair
                                                            C. Boucadair
                                                          France Telecom
                                                       February 13, 2014

             Service Function Chain Control Plane Overview
               draft-wang-msv-using-virtual-line-card-01

Abstract

   As described in [I.D-boucadair-sfc-framework], the dynamic
   enforcement of a Service-derived, adequate forwarding policy for
   packets entering a network that supports such advanced Service
   Functions has become a key challenge for operators and service
   providers.

   This document is based on [I.D-boucadair-sfc-framework] and focusing
   on discussing how the Service Functions are discovered and
   provisioned and how Service Function Chaining path is setup.

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 August 17, 2014.

Copyright Notice

   Copyright (c) 2014 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

Wang, et al.             Expires August 17, 2014                [Page 1]
Internet-Draft                   SFC CP                    February 2014

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Conventions used in this document  . . . . . . . . . . . . . .  4
   3.  SFC Control Plane Overview . . . . . . . . . . . . . . . . . .  5
   4.  Signaling procedure  . . . . . . . . . . . . . . . . . . . . .  7
     4.1.  Building Service Topology  . . . . . . . . . . . . . . . .  7
     4.2.  Service Function Discovery . . . . . . . . . . . . . . . .  7
     4.3.  Service Function Map Selection . . . . . . . . . . . . . .  8
     4.4.  Building Service Function Chaining (SFC) Policy Tables . .  8
     4.5.  Service Function Chaining Path Setup and Policy
           configuration  . . . . . . . . . . . . . . . . . . . . . .  8
     4.6.  Service Availability . . . . . . . . . . . . . . . . . . .  9
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 11
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 13
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 13
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14

Wang, et al.             Expires August 17, 2014                [Page 2]
Internet-Draft                   SFC CP                    February 2014

1.  Introduction

   Service Function Chaining(SFC) refers to the delivery of added value
   services by invoking, in a given order, a set of Service Functions
   along the forwarding path towards a specific destination [I.D-quinn-
   sfc-problem-statement].  Service functions involved in a given SFC
   may include advanced Service Functions such as load-balancing,
   firewalling, intrusion prevention.  A given SFC domain may involve
   several instances of the same Service Functions.  Service Function
   instances can be automatically added or removed to an SFC.  Service
   functions can be co-located on the same physical node or be embedded
   in distinct physical nodes.

   As described in [I.D-boucadair-sfc-framework], the dynamic
   enforcement of a SF-derived, adequate forwarding policy for packets
   entering a network that supports such advanced Service Functions has
Show full document text