Service Function Chains Using Virtual Networking
draft-mackie-sfc-using-virtual-networking-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-10-17
Replaced by draft-fm-bess-service-chaining
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)
Service Function Chaining                                     S. Mackie
Internet-Draft                                               B. Risjman
Intended status: Informational                         Juniper Networks
Expires: April 17, 2015                                    M. Napierala
                                                                   AT&T
                                                               D. Daino
                                                         Telecom Italia
                                                             D.R. Lopez
                                                         Telefonica I+D
                                                             D. Bernier
                                                            Bell Canada
                                                            W. Haeffner
                                                               Vodafone

                                                       October 17, 2014

              Service Function Chains Using Virtual Networking
             draft-mackie-sfc-using-virtual-networking-01.txt

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), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on April 17, 2015.

Copyright Notice

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

Mackie                  Expires April 17, 2015                 [Page 1]
Internet-Draft       SFC Using Virtual Networking          October 2014

   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.

Abstract

   This document describes how service function chains (SFC) can be
   applied to traffic flows using routing in a virtual (overlay)
   network to steer traffic between service nodes. Chains can include
   services running in routers, on physical appliances or in virtual
   machines. Service chains have applicability at the subscriber edge,
   business edge and in multi-tenant datacenters. The routing function
   into SFCs and between service functions within an SFC can be
   performed by physical devices (routers), be virtualized inside
   hypervisors, or run as part of a host OS.

   The architecture uses a controller to calculate and install routes
   to implement an SFC, based on a topological model of the chain and
   knowledge of the network addresses that should pass through the
   chain. An advantage of the approach is that SFCs can be implemented
   without alteration to today's BGP standard, and without change to
   the current operation of routers.

   Service chains need to support load balancing between network
   functions, and symmetric forward and reverse paths are required when
   stateful services are involved. This document shows how these
   requirements can be met by using VRFs at the ingress and egress of
   each service instance and by performing load balancing after the
   egress of each service as part of the routing function.

Table of Contents

   1. Introduction.....................................................4
      1.1. Terminology.................................................5
   2. Service Function Chain Architecture Using Virtual Networking.....7
      2.1. High Level Architecture.....................................7
      2.2. Summary of Operation........................................9
      2.3. Service Function Chain Logical Model.......................10
      2.4. Service Function Implemented in a Set of SF Instances......10
      2.5. SF Instance Connections to VRFs............................12
         2.5.1. SF Instance in Physical Appliance.....................12

Mackie                  Expires April 17, 2015                 [Page 2]
Internet-Draft       SFC Using Virtual Networking          October 2014
Show full document text