NSF-triggered Traffic Steering in I2NSF Framework
draft-hyun-i2nsf-nsf-triggered-steering-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-11-13
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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                                                  J. Jeong
Intended status: Standards Track                                  S. Woo
Expires: May 17, 2017                                             Y. Yeo
                                                 Sungkyunkwan University
                                                                 J. Park
                                                                    ETRI
                                                       November 13, 2016

           NSF-triggered Traffic Steering in I2NSF Framework
               draft-hyun-i2nsf-nsf-triggered-steering-01

Abstract

   This document describes an architecture of the framework for
   Interface to Network Security Functions (I2NSF) which enables traffic
   steering between Network Security Functions (NSFs) for security
   policy enforcement.  Such traffic steering enables composite
   inspection of network traffic by steering the traffic through
   multiple types of NSFs according to the information model for the
   NSF-facing interface in the I2NSF framework.  This document explains
   the additional components integrated into the I2NSF framework and
   their functionalities to achieve NSF-triggered traffic steering.  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.

Hyun, et al.              Expires May 17, 2017                  [Page 1]
Internet-Draft       NSF-triggered Traffic Steering        November 2016

   This Internet-Draft will expire on May 17, 2017.

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 . . . . . . . . . . . . . . . . . . . . . . . . .  5
     4.1.  NSF Operation Manager  . . . . . . . . . . . . . . . . . .  7
     4.2.  Developer's Management System  . . . . . . . . . . . . . .  7
     4.3.  Packet Forwarding Header . . . . . . . . . . . . . . . . .  8
     4.4.  Network Security Function Forwarder (NSFF) . . . . . . . .  8
   5.  Use Cases  . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     5.1.  Enforcing Different NSFs Depending on a Packet
           Source's Trust Level . . . . . . . . . . . . . . . . . . .  9
     5.2.  Effective Load Balancing with Dynamic NSF Instantiation  . 10
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 11
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 11
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 12

Hyun, et al.              Expires May 17, 2017                  [Page 2]
Internet-Draft       NSF-triggered Traffic Steering        November 2016

1.  Introduction

   To effectively cope with emerging sophisticated network attacks, it
   is necessary that various Network Security Functions (NSFs)
   cooperatively analyze network traffic [sfc-ns-use-cases][RFC7498]
   [i2nsf-problem][capability-im].  In addition, depending on the
   characteristics of network traffic and their suspiciousness level,
   the different types of network traffic need to be analyzed through
Show full document text