Service Function Chaining Use Cases for Network Security
draft-wang-sfc-ns-use-cases-03

Document Type Active Internet-Draft (individual)
Last updated 2017-06-28
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                        E. Wang
Internet-Draft                                                  K. Leung
Intended status: Informational                                  J. Felix
Expires: December 30, 2017                                       J. Iyer
                                                      Cisco Systems Inc.
                                                                P. Patel
                                                             F5 Networks
                                                           June 28, 2017

        Service Function Chaining Use Cases for Network Security
                     draft-wang-sfc-ns-use-cases-03

Abstract

   Enterprise networks deploy a variety of security devices to protect
   the network, hosts and endpoints.  Network security devices, both
   hardware and virtual, operate at all OSI layers with scanning and
   analysis capabilities for application content.  Multiple specific
   devices are often deployed together for breadth and depth of defense.
   This document describes use cases of Service Function Chaining (SFC)
   when deploying network security devices in the manner described above
   and also puts forth requirements for their effective operation.

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 December 30, 2017.

Copyright Notice

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

Wang, et al.            Expires December 30, 2017               [Page 1]
Internet-Draft       SFC Network Security Use Cases            June 2017

   (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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Definition Of Terms . . . . . . . . . . . . . . . . . . . . .   3
   3.  Characteristics of Security Service Functions . . . . . . . .   4
   4.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Service Classification Use Cases  . . . . . . . . . . . .   5
       4.1.1.  Service classification for bi-directional traffic . .   5
       4.1.2.  Service Classifier to distinguish initiator and
               responder . . . . . . . . . . . . . . . . . . . . . .   6
       4.1.3.  Service Classification based on network and
               application criteria  . . . . . . . . . . . . . . . .   7
       4.1.4.  Switching Service Function Paths based on inspection
               and scanning results  . . . . . . . . . . . . . . . .   8
     4.2.  Service Function Use Cases  . . . . . . . . . . . . . . .  10
       4.2.1.  Service Classifier-capable Service Function . . . . .  10
       4.2.2.  Service Functions operating on L5 or L7 data  . . . .  10
       4.2.3.  Service Function mid-stream pick-up . . . . . . . . .  11
       4.2.4.  Bypassing a particular Service Function . . . . . . .  11
       4.2.5.  Receive-only Service Functions  . . . . . . . . . . .  13
     4.3.  Service Data Handling Use Cases . . . . . . . . . . . . .  14
       4.3.1.  Service Function injected new packet  . . . . . . . .  14
       4.3.2.  Service Function initiated connections  . . . . . . .  14
       4.3.3.  Security classification results . . . . . . . . . . .  15
   5.  General Requirements  . . . . . . . . . . . . . . . . . . . .  17
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  18
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
Show full document text