Service Function Chaining-Enabled I2NSF Architecture
draft-hyun-i2nsf-sfc-enabled-i2nsf-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-07-04
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                                            S. Hyun
Internet-Draft                                                    S. Woo
Intended status: Standards Track                                  Y. Yeo
Expires: January 5, 2017                                        J. Jeong
                                                 Sungkyunkwan University
                                                                 J. Park
                                                                    ETRI
                                                            July 4, 2016

          Service Function Chaining-Enabled I2NSF Architecture
                 draft-hyun-i2nsf-sfc-enabled-i2nsf-00

Abstract

   This document describes an architecture of the I2NSF framework using
   security function chaining for securiy policy enforcement.  Security
   function chaining enables composite inspection of network traffic by
   steering the traffic through multiple types of security functions
   according to the information model for the capability layer interface
   in the I2NSF framework.  This document explains the additional
   components integrated into the I2NSF framework and their
   functionalities to achieve security function chaining.  It also
   describes representative use cases to address major benefits from the
   proposed architecture.

Status of This Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on January 5, 2017.

Hyun, et al.             Expires January 5, 2017                [Page 1]
Internet-Draft       SFC-enabled I2NSF Architecture            July 2016

Copyright Notice

   Copyright (c) 2016 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Objective  . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Architecture . . . . . . . . . . . . . . . . . . . . . . . . .  6
     4.1.  SFC Policy Manager . . . . . . . . . . . . . . . . . . . .  8
     4.2.  SFC Catalog Manager  . . . . . . . . . . . . . . . . . . .  8
     4.3.  Developer's Management System  . . . . . . . . . . . . . .  9
     4.4.  Classifier . . . . . . . . . . . . . . . . . . . . . . . .  9
     4.5.  Service Function Forwarder (SFF) . . . . . . . . . . . . .  9
   5.  Use Cases  . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     5.1.  Dynamic Path Alternation . . . . . . . . . . . . . . . . . 10
     5.2.  Enforcing Different SFPs Depending on Trust Levels . . . . 11
     5.3.  Effective Load Balancing with Dynamic SF Instantiation . . 12
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 13
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 14

Hyun, et al.             Expires January 5, 2017                [Page 2]
Internet-Draft       SFC-enabled I2NSF Architecture            July 2016

1.  Introduction

   To effectively cope with emerging sophisticated network attacks, it
   is necessary that various security functions cooperatively analyze
   network traffic [sfc-ns-use-cases] [RFC7498]
Show full document text