Service Function Chaining Use Cases In Data Centers
draft-ietf-sfc-dc-use-cases-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06

Service Function Chaining                                       S. Kumar
Internet-Draft                                              C. Obediente
Intended status: Informational                       Cisco Systems, Inc.
Expires: November 5, 2014                                      M. Tufail
                                                                    Citi
                                                                S. Majee
                                                             F5 Networks
                                                              C. Captari
                                                     Telstra Corporation
                                                             May 4, 2014

          Service Function Chaining Use Cases In Data Centers
                     draft-ietf-sfc-dc-use-cases-00

Abstract

   Data center operators deploy a variety of layer 4 through layer 7
   service functions in both physical and virtual form factors.  Most
   traffic originating, transiting, or terminating in the data center is
   subject to treatment by multiple service functions.

   This document describes use cases that demonstrate the applicability
   of Service Function Chaining (SFC) within a data center environment
   and provides SFC requirements for data center centric use cases, with
   primary focus on Enterprise data centers.

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 November 5, 2014.

Copyright Notice

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

Kumar, et al.           Expires November 5, 2014                [Page 1]
Internet-Draft              SFC DC Use Cases                    May 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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Requirements Language  . . . . . . . . . . . . . . . . . .  4
   2.  Definition Of Terms  . . . . . . . . . . . . . . . . . . . . .  4
   3.  Use Cases  . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     3.1.  Traffic Types  . . . . . . . . . . . . . . . . . . . . . .  6
     3.2.  North-South Traffic  . . . . . . . . . . . . . . . . . . .  6
       3.2.1.  Sample north-south service function chains . . . . . .  8
       3.2.2.  Sample north-south SFC description . . . . . . . . . .  8
     3.3.  East-West Traffic  . . . . . . . . . . . . . . . . . . . .  9
       3.3.1.  Sample east-west service function chains . . . . . . . 10
       3.3.2.  Sample east-west SFC description . . . . . . . . . . . 10
     3.4.  Multi-tenancy  . . . . . . . . . . . . . . . . . . . . . . 11
     3.5.  SFCs in data centers . . . . . . . . . . . . . . . . . . . 12
   4.  Drawbacks Of Existing Service Chaining Methods . . . . . . . . 13
   5.  General Requirements . . . . . . . . . . . . . . . . . . . . . 16
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 17
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 17
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 17
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 17
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18

Kumar, et al.           Expires November 5, 2014                [Page 2]
Internet-Draft              SFC DC Use Cases                    May 2014

1.  Introduction

   Data centers -- enterprise, cloud or service provider -- deploy
   service nodes at various points in the network topology.  These nodes
   provide a range of service functions and the set of service functions
   hosted at a given service node may overlap with service functions