Service Function Chaining (SFC) Architecture
draft-ietf-sfc-architecture-03

The information below is for an old version of the document
Document Type Active Internet-Draft (sfc WG)
Last updated 2015-01-12 (latest revision 2015-01-05)
Replaces draft-merged-sfc-architecture
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state In WG Last Call
Document shepherd Jim Guichard
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Jim Guichard" <jguichar@cisco.com>
Network Working Group                                    J. Halpern, Ed.
Internet-Draft                                                  Ericsson
Intended status: Standards Track                       C. Pignataro, Ed.
Expires: July 9, 2015                                              Cisco
                                                         January 5, 2015

              Service Function Chaining (SFC) Architecture
                     draft-ietf-sfc-architecture-03

Abstract

   This document describes an architecture for the specification,
   creation, and ongoing maintenance of Service Function Chains (SFC) in
   a network.  It includes architectural concepts, principles, and
   components used in the construction of composite services through
   deployment of SFCs, with a focus on those to be standardized in the
   IETF.  This document does not propose solutions, protocols, or
   extensions to existing protocols.

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 July 9, 2015.

Copyright Notice

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

Halpern & Pignataro       Expires July 9, 2015                  [Page 1]
Internet-Draft              SFC Architecture                January 2015

   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
     1.1.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Assumptions . . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Definition of Terms . . . . . . . . . . . . . . . . . . .   4
   2.  Architectural Concepts  . . . . . . . . . . . . . . . . . . .   6
     2.1.  Service Function Chains . . . . . . . . . . . . . . . . .   7
     2.2.  Service Function Chain Symmetry . . . . . . . . . . . . .   8
     2.3.  Service Function Paths  . . . . . . . . . . . . . . . . .   9
   3.  Architecture Principles . . . . . . . . . . . . . . . . . . .  10
   4.  Core SFC Architecture Components  . . . . . . . . . . . . . .  11
     4.1.  SFC Encapsulation . . . . . . . . . . . . . . . . . . . .  12
     4.2.  Service Function (SF) . . . . . . . . . . . . . . . . . .  13
     4.3.  Service Function Forwarder (SFF)  . . . . . . . . . . . .  13
       4.3.1.  Transport Derived SFF . . . . . . . . . . . . . . . .  15
     4.4.  SFC-Enabled Domain  . . . . . . . . . . . . . . . . . . .  15
     4.5.  Network Overlay and Network Components  . . . . . . . . .  15
     4.6.  SFC Proxy . . . . . . . . . . . . . . . . . . . . . . . .  15
     4.7.  Classification  . . . . . . . . . . . . . . . . . . . . .  17
     4.8.  Re-Classification and Branching . . . . . . . . . . . . .  17
     4.9.  Shared Metadata . . . . . . . . . . . . . . . . . . . . .  18
   5.  Additional Architectural Concepts . . . . . . . . . . . . . .  18
     5.1.  The Role of Policy  . . . . . . . . . . . . . . . . . . .  18
     5.2.  SFC Control Plane . . . . . . . . . . . . . . . . . . . .  19
     5.3.  Resource Control  . . . . . . . . . . . . . . . . . . . .  20
     5.4.  Infinite Loop Detection and Avoidance . . . . . . . . . .  20
     5.5.  Load Balancing Considerations . . . . . . . . . . . . . .  21
     5.6.  MTU and Fragmentation Considerations  . . . . . . . . . .  22
     5.7.  SFC OAM . . . . . . . . . . . . . . . . . . . . . . . . .  22
     5.8.  Resilience and Redundancy . . . . . . . . . . . . . . . .  23
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  24
   7.  Contributors and Acknowledgments  . . . . . . . . . . . . . .  24
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  26
   9.  Informative References  . . . . . . . . . . . . . . . . . . .  26
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  26
Show full document text