Registration Interface Information Model
draft-hyun-i2nsf-registration-interface-im-06

Document Type Active Internet-Draft (individual)
Last updated 2018-07-17
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)
Network Working Group                                            S. Hyun
Internet-Draft                                         Chosun University
Intended status: Standards Track                                J. Jeong
Expires: January 18, 2019                                         T. Roh
                                                                   S. Wi
                                                 Sungkyunkwan University
                                                                 J. Park
                                                                    ETRI
                                                           July 17, 2018

                Registration Interface Information Model
             draft-hyun-i2nsf-registration-interface-im-06

Abstract

   This document describes an information model for Interface to Network
   Security Functions (I2NSF) Registration Interface between Security
   Controller and Developer's Management System (DMS).  The information
   model is required to support NSF instance via the registration
   interface.  This document explains the procedures over I2NSF
   registration interface for these functionalities.  It also describes
   the detailed information which should be exchanged via I2NSF
   registration interface.

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 https://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 January 18, 2019.

Copyright Notice

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

Hyun, et al.            Expires January 18, 2019                [Page 1]
Internet-Draft  Registration Interface Information Model       July 2018

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://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
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Objectives  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Information Model . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  NSF Instance Managment Mechanism  . . . . . . . . . . . .   5
     5.2.  NSF Registration Mechanism  . . . . . . . . . . . . . . .   6
     5.3.  NSF Access Information  . . . . . . . . . . . . . . . . .   6
     5.4.  NSF Capability Information (Capabilities of an NSF
           instance) . . . . . . . . . . . . . . . . . . . . . . . .   7
       5.4.1.  Performance Capabilities  . . . . . . . . . . . . . .   7
     5.5.  Role-based Access Control List  . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Appendix A.  Lifecycle Managmenet Mechanism . . . . . . . . . . .  12
   Appendix B.  Changes from draft-hyun-i2nsf-registration-
                interface-im-05  . . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   A number of virtual network security function instances typically
   exist in Interface to Network Security Functions (I2NSF) framework
   [RFC8329].  Since these NSF instances may have different security
   capabilities, it is important to register the security capabilities
   of each NSF instance into the security controller after they have
   been created.  In addition, it is required to instantiate NSFs of
   some required security capabilities on demand.  As an example, if
   additional security capabilities are required to meet the new
   security requirements that an I2NSF user requests, the security
Show full document text