I2NSF Consumer-Facing Interface YANG Data Model
draft-ietf-i2nsf-consumer-facing-interface-dm-06

Document Type Active Internet-Draft (i2nsf WG)
Last updated 2019-07-24
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Reviews
Additional URLs
- Yang catalog entry for ietf-i2nsf-cfi-policy@2019-06-12.yang
- Yang impact analysis for draft-ietf-i2nsf-consumer-facing-interface-dm
- Mailing list discussion
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
I2NSF Working Group                                             J. Jeong
Internet-Draft                                                    E. Kim
Intended status: Standards Track                 Sungkyunkwan University
Expires: January 25, 2020                                         T. Ahn
                                                           Korea Telecom
                                                                R. Kumar
                                                        Juniper Networks
                                                                S. Hares
                                                                  Huawei
                                                           July 24, 2019

            I2NSF Consumer-Facing Interface YANG Data Model
            draft-ietf-i2nsf-consumer-facing-interface-dm-06

Abstract

   This document describes an information model and a YANG data model
   for the Consumer-Facing Interface between an Interface to Network
   Security Functions (I2NSF) User and Security Controller in an I2NSF
   system in a Network Functions Virtualization (NFV) environment.  The
   information model defines various types of managed objects and the
   relationship among them needed to build the interface.  The
   information model is organized based on the "Event-Condition-Action"
   (ECA) policy model defined by a capability information model for
   I2NSF [i2nsf-capability-im], and the data model is defined for
   enabling different users of a given I2NSF system to define, manage,
   and monitor security policies for specific flows within an
   administrative domain.

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 25, 2020.

Jeong, et al.           Expires January 25, 2020                [Page 1]
Internet-Draft  Consumer-Facing Interface YANG Data Model      July 2019

Copyright Notice

   Copyright (c) 2019 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
   (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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   5
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Information Model for Policy  . . . . . . . . . . . . . . . .   5
     4.1.  Event Sub-model . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  Condition Sub-model . . . . . . . . . . . . . . . . . . .   8
     4.3.  Action Sub-model  . . . . . . . . . . . . . . . . . . . .   9
   5.  Information Model for Multi-Tenancy . . . . . . . . . . . . .  10
     5.1.  Policy Domain . . . . . . . . . . . . . . . . . . . . . .  10
     5.2.  Policy Tenant . . . . . . . . . . . . . . . . . . . . . .  11
     5.3.  Policy Role . . . . . . . . . . . . . . . . . . . . . . .  11
     5.4.  Policy User . . . . . . . . . . . . . . . . . . . . . . .  12
     5.5.  Policy Management Authentication Method . . . . . . . . .  13
   6.  Information Model for Policy Endpoint Groups  . . . . . . . .  14
     6.1.  User Group  . . . . . . . . . . . . . . . . . . . . . . .  15
     6.2.  Device Group  . . . . . . . . . . . . . . . . . . . . . .  16
     6.3.  Location Group  . . . . . . . . . . . . . . . . . . . . .  16
   7.  Information Model for Threat Prevention . . . . . . . . . . .  17
     7.1.  Threat Feed . . . . . . . . . . . . . . . . . . . . . . .  18
     7.2.  Payload Content . . . . . . . . . . . . . . . . . . . . .  18
   8.  Role-based Acess Control (RBAC) . . . . . . . . . . . . . . .  19
   9.  YANG Data Model for Security Policies for Consumer-Facing
       Interface . . . . . . . . . . . . . . . . . . . . . . . . . .  20
   10. Example XML Output for Various Scenarios  . . . . . . . . . .  49
     10.1.  DB Registration: Information of Positions and Devices
Show full document text