Service Function Chaining using Virtual Networks with BGP VPNs
draft-ietf-bess-service-chaining-06

Document Type Active Internet-Draft (bess WG)
Last updated 2018-12-04
Replaces draft-fm-bess-service-chaining
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        R. Fernando
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                               S. Mackie
Expires: June 7, 2019                                   Juniper Networks
                                                                  D. Rao
                                                           Cisco Systems
                                                              B. Rijsman

                                                            M. Napierala
                                                                ATT Labs
                                                                T. Morin
                                                                  Orange
                                                        December 4, 2018

     Service Function Chaining using Virtual Networks with BGP VPNs
                  draft-ietf-bess-service-chaining-06

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.

   A BGP control plane for route distribution is used to create virtual
   networks implemented using IP MPLS, VXLAN or other suitable
   encapsulation, where the routes within the virtual networks cause
   traffic to flow through a sequence of service nodes that apply packet
   processing functions to the flows.

   Two techniques are described: in one the service chain is implemented
   as a sequence of distinct VPNs between sets of service nodes that
   apply each service function; in the other, the routes within a VPN
   are modified through the use of special route targets and modified
   next-hop resolution to achieve the desired result.

   In both techniques, service chains can be created by manual
   configuration of routes and route targets in routing systems, or
   through the use of a controller which contains a topological model of
   the desired service chains.

Fernando, et al.          Expires June 7, 2019                  [Page 1]
Internet-Draft     SFC using Virtual Networks with BGP     December 2018

   This document also contains discussion of load balancing between
   network functions, symmetric forward and reverse paths when stateful
   services are involved, and use of classifiers to direct traffic into
   a service chain.

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 https://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 June 7, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://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  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Service Function Chain Architecture Using Virtual Networking    7
     2.1.  High Level Architecture . . . . . . . . . . . . . . . . .   8
     2.2.  Service Function Chain Logical Model  . . . . . . . . . .  10
     2.3.  Service Function Implemented in a Set of SF Instances . .  11
     2.4.  SF Instance Connections to VRFs . . . . . . . . . . . . .  13
       2.4.1.  SF Instance in Physical Appliance . . . . . . . . . .  13
       2.4.2.  SF Instance in a Virtualized Environment  . . . . . .  14

Fernando, et al.          Expires June 7, 2019                  [Page 2]
Show full document text