I2NSF Consumer-Facing Interface YANG Data Model
draft-ietf-i2nsf-consumer-facing-interface-dm-07
|
| Document |
Type |
|
Active Internet-Draft (i2nsf WG)
|
|
Last updated |
|
2019-11-04
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized
bibtex
|
|
Yang Validation |
|
☯
0 errors, 0 warnings.
draft-ietf-i2nsf-consumer-facing-interface-dm-07.txt:
xym 0.4:
Extracting 'ietf-i2nsf-cfi-policy@2019-11-04.yang'
Removed 3 empty lines
ietf-i2nsf-cfi-policy@2019-11-04.yang:
pyang 2.1.1: pyang --verbose --ietf -p {libs} {model}:
# read ietf-i2nsf-cfi-policy@2019-11-04.yang (CL)
# read /a/www/ietf-datatracker/6.118.0/env/share/yang/modules/ietf/ietf-yang-types.yang
# read /a/www/ietf-ftp/yang/draftmod/ietf-yang-types@2019-11-04.yang
# read /a/www/ietf-datatracker/6.118.0/env/share/yang/modules/ietf/ietf-inet-types.yang
# read /a/www/ietf-ftp/yang/draftmod/ietf-inet-types@2019-11-04.yang
# read /a/www/ietf-datatracker/6.118.0/env/share/yang/modules/ietf/ietf-netconf-acm.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-netconf-acm@2018-02-14.yang
yanglint 0.14.80: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors
|
|
Reviews |
|
|
|
Additional URLs |
|
|
| 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 C. Chung
Intended status: Standards Track Sungkyunkwan University
Expires: May 7, 2020 T. Ahn
Korea Telecom
R. Kumar
Juniper Networks
S. Hares
Huawei
November 4, 2019
I2NSF Consumer-Facing Interface YANG Data Model
draft-ietf-i2nsf-consumer-facing-interface-dm-07
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 May 7, 2020.
Jeong, et al. Expires May 7, 2020 [Page 1]
Internet-Draft Consumer-Facing Interface YANG Data Model November 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 Policy Endpoint Groups . . . . . . . . 10
5.1. User Group . . . . . . . . . . . . . . . . . . . . . . . 10
5.2. Device Group . . . . . . . . . . . . . . . . . . . . . . 11
5.3. Location Group . . . . . . . . . . . . . . . . . . . . . 12
6. Information Model for Threat Prevention . . . . . . . . . . . 13
6.1. Threat Feed . . . . . . . . . . . . . . . . . . . . . . . 13
6.2. Payload Content . . . . . . . . . . . . . . . . . . . . . 14
7. Network Configuration Access Control Model (NACM) . . . . . . 15
8. YANG Data Model of Consumer-Facing Interface . . . . . . . . 15
9. XML Configuration Examples of High-Level Security Policy
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
9.1. Database Registration: Information of Positions and
Devices (Endpoint Group) . . . . . . . . . . . . . 36
9.2. Scenario 1: Block SNS Access during Business Hours . . . 37
9.3. Scenario 2: Block Malicious VoIP/VoLTE Packets Coming to
a Company . . . . . . . . . . . . . . . . . . . . . . . . 39
9.4. Scenario 3: Mitigate HTTP and HTTPS Flood Attacks on a
Company Web Server . . . . . . . . . . . . . . . . . . . 40
Show full document text