Service Function Chaining (SFC) Architecture
draft-quinn-sfc-arch-04

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-01-29
Replaces draft-quinn-nsc-arch, draft-beliveau-sfc-architecture
Replaced by draft-merged-sfc-architecture
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)
Network Working Group                                      P. Quinn, Ed.
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Informational                          A. Beliveau, Ed.
Expires: August 1, 2014                                         Ericsson
                                                        January 28, 2014

              Service Function Chaining (SFC) Architecture
                      draft-quinn-sfc-arch-04.txt

Abstract

   This document describes an architecture used for the creation of
   Service Function Chains (SFC).  It includes architectural concepts,
   principles, and components used in the construction of composite
   services through deployment of SFCs in a network.  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 August 1, 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
   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

Quinn & Beliveau         Expires August 1, 2014                 [Page 1]
Internet-Draft              SFC Architecture                January 2014

   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.  Definition of Terms  . . . . . . . . . . . . . . . . . . .  3
     1.3.  Service Function Chaining  . . . . . . . . . . . . . . . .  4
   2.  Architectural Concepts . . . . . . . . . . . . . . . . . . . .  6
     2.1.  Service Function Chains  . . . . . . . . . . . . . . . . .  6
     2.2.  Service Function Chain Symmetry  . . . . . . . . . . . . .  7
     2.3.  Service Function Paths . . . . . . . . . . . . . . . . . .  7
   3.  Service Function Chaining Architecture . . . . . . . . . . . .  8
     3.1.  Architecture Principles  . . . . . . . . . . . . . . . . .  8
     3.2.  Fundamental Components . . . . . . . . . . . . . . . . . .  8
   4.  Summary  . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   6.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 14
   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 16
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 17
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 18
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 18
   Appendix A.  Existing Service Deployments  . . . . . . . . . . . . 19
   Appendix B.  Issues with Existing Deployments  . . . . . . . . . . 20
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21

Quinn & Beliveau         Expires August 1, 2014                 [Page 2]
Internet-Draft              SFC Architecture                January 2014

1.  Introduction

   This document describes an architecture used for the creation of
   Service Function Chains (SFC).  It includes architectural concepts,
   principles, and components to provide SFCs in a network.

1.1.  Scope

   The architecture described herein is assumed to be applicable to a
   single network administrative domain.  While it is possible for the
   principles and architectural components to be applied to inter-domain
   SFCs, these are left for future study.

1.2.  Definition of Terms

   Classification:  Locally instantiated policy and customer/network/
      service profile matching of traffic flows for identification of
      appropriate outbound forwarding actions.

   SFC Network Forwarder:  SFC network forwarders provide network
      connectivity for service functions forwarders and service
Show full document text