draft-ietf-i2nsf-capability-data-model-04.txt   draft-ietf-i2nsf-capability-data-model-05.txt 
I2NSF Working Group S. Hares I2NSF Working Group S. Hares
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track J. Jeong Intended status: Standards Track J. Jeong
Expires: September 29, 2019 J. Kim Expires: January 26, 2020 J. Kim
Sungkyunkwan University Sungkyunkwan University
R. Moskowitz R. Moskowitz
HTT Consulting HTT Consulting
Q. Lin Q. Lin
Huawei Huawei
March 28, 2019 July 25, 2019
I2NSF Capability YANG Data Model I2NSF Capability YANG Data Model
draft-ietf-i2nsf-capability-data-model-04 draft-ietf-i2nsf-capability-data-model-05
Abstract Abstract
This document defines a YANG data model for capabilities of various This document defines a YANG data model for the capabilities of
Network Security Functions (NSFs) in Interface to Network Security various Network Security Functions (NSFs) in the Interface to Network
Functions (I2NSF) framework to cetrally manage capabilities of varios Security Functions (I2NSF) framework to centrally manage the
NSFs. capabilities of the various NSFs.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 29, 2019. This Internet-Draft will expire on January 26, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 18 skipping to change at page 2, line 18
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. YANG Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 6 5. YANG Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Capabilities of Network Security Function . . . . . . . . 6 5.1. Network Security Function (NSF) Capabilities . . . . . . 6
6. YANG Data Modules . . . . . . . . . . . . . . . . . . . . . . 9 6. YANG Data Modules . . . . . . . . . . . . . . . . . . . . . . 9
6.1. I2NSF Capability YANG Data Module . . . . . . . . . . . . 9 6.1. I2NSF Capability YANG Data Module . . . . . . . . . . . . 9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38
8. Security Considerations . . . . . . . . . . . . . . . . . . . 39 8. Security Considerations . . . . . . . . . . . . . . . . . . . 38
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 39 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.1. Normative References . . . . . . . . . . . . . . . . . . 39 9.1. Normative References . . . . . . . . . . . . . . . . . . 39
9.2. Informative References . . . . . . . . . . . . . . . . . 40 9.2. Informative References . . . . . . . . . . . . . . . . . 41
Appendix A. Changes from draft-ietf-i2nsf-capability-data- Appendix A. Configuration Examples . . . . . . . . . . . . . . . 43
model-03 . . . . . . . . . . . . . . . . . . . . . . 42 A.1. Example 1: Registration for Capabilities of General
Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . 42 Firewall . . . . . . . . . . . . . . . . . . . . . . . . 43
Appendix C. Contributors . . . . . . . . . . . . . . . . . . . . 42 A.2. Example 2: Registration for Capabilities of Time based
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42 Firewall . . . . . . . . . . . . . . . . . . . . . . . . 44
A.3. Example 3: Registration for Capabilities of Web Filter . 45
A.4. Example 4: Registration for Capabilities of VoIP/VoLTE
Filter . . . . . . . . . . . . . . . . . . . . . . . . . 45
A.5. Example 5: Registration for Capabilities of HTTP and
HTTPS Flood Mitigation . . . . . . . . . . . . . . . . . 46
Appendix B. Changes from draft-ietf-i2nsf-capability-data-
model-04 . . . . . . . . . . . . . . . . . . . . . . 47
Appendix C. Acknowledgments . . . . . . . . . . . . . . . . . . 47
Appendix D. Contributors . . . . . . . . . . . . . . . . . . . . 48
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 48
1. Introduction 1. Introduction
As the industry becomes more sophisticated and network devices (e.g., As the industry becomes more sophisticated and network devices (e.g.,
Internet of Things, Self-driving vehicles, and VoIP/VoLTE Internet of Things, Self-driving vehicles, and VoIP/VoLTE
smartphones), service providers have a lot of problems mentioned in smartphones), service providers have a lot of problems described in
[RFC8192]. To resolve these problems, [i2nsf-nsf-cap-im] specifies [RFC8192]. To resolve these problems, [draft-ietf-i2nsf-capability]
the information model of the capabilities of Network Security specifies the information model of the capabilities of Network
Functions (NSFs). Security Functions (NSFs).
This document provides a data model using YANG [RFC6020][RFC7950] This document provides a YANG data model [RFC6020][RFC7950] that
that defines the capabilities of NSFs to centrally manage defines the capabilities of NSFs to centrally manage the capabilities
capabilities of those security devices. The security devices can of those security devices. The security devices can register their
register their own capabilities into Network Operator Management own capabilities into a Network Operator Management (Mgmt) System
(Mgmt) System (i.e., Security Controller) with this YANG data model (i.e., Security Controller) with this YANG data model through the
through the registration interface [RFC8329]. With the capabilities registration interface [RFC8329]. With the capabilities of those
of those security devices registered centrally, those security security devices maintained centrally, those security devices can be
devices can be easily managed [RFC8329]. This YANG data model is easily managed [RFC8329]. This YANG data model is based on the
based on the information model for I2NSF NSF capabilities information model for I2NSF NSF capabilities
[i2nsf-nsf-cap-im]. [draft-ietf-i2nsf-capability].
This YANG data model uses an "Event-Condition-Action" (ECA) policy This YANG data model uses an "Event-Condition-Action" (ECA) policy
model that is used as the basis for the design of I2NSF Policy model that is used as the basis for the design of I2NSF Policy as
described in [RFC8329] and [i2nsf-nsf-cap-im]. Rules. The "ietf- described in [RFC8329] and [draft-ietf-i2nsf-capability].. The
i2nsf-capability" YANG module defined in this document provides the "ietf-i2nsf-capability" YANG module defined in this document provides
following features: the following features:
o Definition for general capabilities of network security functions. o Definition for general capabilities of network security functions.
o Definition for event capabilities of generic network security o Definition for event capabilities of generic network security
function. functions.
o Definition for condition capabilities of generic network security o Definition for condition capabilities of generic network security
function. functions.
o Definition for condition capabilities of advanced network security o Definition for condition capabilities of advanced network security
function. functions.
o Definition for action capabilities of generic network security o Definition for action capabilities of generic network security
function. functions.
o Definition for resolution strategy capabilities of generic network o Definition for resolution strategy capabilities of generic network
security function. security functions.
o Definition for default action capabilities of generic network o Definition for default action capabilities of generic network
security function. security functions.
2. Requirements Language 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119][RFC8174]. document are to be interpreted as described in [RFC2119][RFC8174].
3. Terminology 3. Terminology
This document uses the terminology described in This document uses the terminology described in
[i2nsf-terminology][i2nsf-nsf-cap-im] [draft-ietf-i2nsf-terminology][draft-ietf-i2nsf-capability]
[RFC8431][supa-policy-info-model]. Especially, the following terms [RFC8431][draft-ietf-supa-generic-policy-info-model]. Especially,
are from [supa-policy-info-model]: the following terms are from
[draft-ietf-supa-generic-policy-info-model]:
o Data Model: A data model is a representation of concepts of o Data Model: A data model is a representation of concepts of
interest to an environment in a form that is dependent on data interest to an environment in a form that is dependent on data
repository, data definition language, query language, repository, data definition language, query language,
implementation language, and protocol. implementation language, and protocol.
o Information Model: An information model is a representation of o Information Model: An information model is a representation of
concepts of interest to an environment in a form that is concepts of interest to an environment in a form that is
independent of data repository, data definition language, query independent of data repository, data definition language, query
language, implementation language, and protocol. language, implementation language, and protocol.
3.1. Tree Diagrams 3.1. Tree Diagrams
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in these diagrams this document. The meaning of the symbols in these diagrams is
[RFC8340] is as follows: referred from [RFC8340].
o Brackets "[" and "]" enclose list keys.
o Abbreviations before data node names: "rw" means configuration
(read-write) and "ro" state data (read-only).
o Symbols after data node names: "?" means an optional node and "*"
denotes a "list" and "leaf-list".
o Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":").
o Ellipsis ("...") stands for contents of subtrees that are not
shown.
4. Overview 4. Overview
This section explains overview how the YANG data model can be used in This section provides as overview of how the YANG data model can be
I2NSF framework described in [RFC8329]. Figure 1 shows capabilities used in the I2NSF framework described in [RFC8329]. Figure 1 shows
of NSFs in I2NSF Framework. As shown in this figure, Developer's the capabilities of NSFs in I2NSF Framework. As shown in this
Mgmt System can register NSFs with capabilities that the network figure, an NSF Developer's Mgmt System can register NSFs and the
security device can support. To register NSFs in this way, the capabilities that the network security device can support. To
Developer's Mgmt System utilizes this standardized capabilities YANG register NSFs in this way, the Developer's Mgmt System utilizes this
data model through registration interface. With the capabilities of standardized capabilities YANG data model through its registration
those network security devices registered centrally, those security interface. With the capabilities of those network security devices
devices can be easily managed, which can resolve the a lot of maintained centrally, those security devices can be easily managed,
problems described in [RFC8192]. The following shows use cases. which can resolve many of the problems described in [RFC8192]. The
use cases are described below.
Note [i2nsf-nsf-yang] is used to configure security policy rules of Note that the NSF-Facing Interface is used to configure the security
generic network security functions and [i2nsf-advanced-nsf-dm] is policy rules of the generic network security functions
used to configure security policy rules of advanced network security [draft-ietf-i2nsf-nsf-facing-interface-dm], and the NSF Monitoring
functions according to the capabilities of network security devices Interface is used to configure the security policy rules of advanced
registed in I2NSF Framework. network security functions [draft-dong-i2nsf-asf-config],
respectively, according to the capabilities of NSFs registered with
the I2NSF Framework.
+-------------------------------------------------------+ +-------------------------------------------------------+
| I2NSF User (e.g., Overlay Network Mgmt, Enterprise | | I2NSF User (e.g., Overlay Network Mgmt, Enterprise |
| Network Mgmt, another network domain's mgmt, etc.) | | Network Mgmt, another network domain's mgmt, etc.) |
+--------------------+----------------------------------+ +--------------------+----------------------------------+
| |
Consumer-Facing Interface | Consumer-Facing Interface |
| |
| I2NSF |
+-----------------+------------+ Registration +-------------+ +-----------------+------------+ Registration +-------------+
| Network Operator Mgmt System | Interface | Developer's | | Network Operator Mgmt System | Interface | Developer's |
| (i.e., Security Controller) | < --------- > | Mgmt System | | (i.e., Security Controller) | < --------- > | Mgmt System |
+-----------------+------------+ +-------------+ +-----------------+------------+ +-------------+
| New NSF | New NSF
| E = {} | E = {}
NSF-Facing Interface | C = {IPv4, IPv6} NSF-Facing Interface | C = {IPv4, IPv6}
| A = {Allow, Deny} | A = {Allow, Deny}
| |
+---------------+----+------------+-----------------+ +---------------+----+------------+-----------------+
| | | | | | | |
+---+---+ +---+---+ +---+---+ +---+---+ +---+---+ +---+---+ +---+---+ +---+---+
| NSF-1 | ... | NSF-m | | NSF-1 | ... | NSF-n | ... | NSF-1 | ... | NSF-m | | NSF-1 | ... | NSF-n | ...
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+ +-------+ +-------+
NSF-1 NSF-m NSF-1 NSF-n NSF-1 NSF-m NSF-1 NSF-n
E = {} E = {user} E = {dev} E = {time} E = {} E = {user} E = {dev} E = {time}
C = {IPv4} C = {IPv6} C = {IPv4, IPv6} C = {IPv4} C = {IPv4} C = {IPv6} C = {IPv4, IPv6} C = {IPv4}
A = {Allow, Deny} A = {Allow, Deny} A = {Allow, Deny} A = {Allow, Deny} A = {Allow, Deny} A = {Allow, Deny} A = {Allow, Deny} A = {Allow, Deny}
Developer Mgmt System A Developer Mgmt System B Developer's Mgmt System A Developer's Mgmt System B
Figure 1: Capabilities of NSFs in I2NSF Framework Figure 1: Capabilities of NSFs in I2NSF Framework
o If network manager wants to apply security policy rules about o If a network manager wants to apply security policy rules to block
blocking malicious users, it is a tremendous burden to apply all malicious users, it is a tremendous burden to apply all of the
of these rules to NSFs one by one. This problem can be resolved needed rules to NSFs one-by-one. This problem can be resolved by
by managing the capabilities of NSFs. If network manager wants to managing the capabilities of NSFs. If network manager wants to
block malicious users with IPv6, network manager sends the block malicious users with IPv6, the network manager sends the
security policy rules about blocking the users to Network Operator security policy rules to block the users to the Network Operator
Mgmt System using I2NSF user (i.e., a web browser or a software). Mgmt System using I2NSF user (i.e., a web browser or a software).
When the Network Operator Mgmt System receives the security policy When the Network Operator Mgmt System receives the security policy
rules, it automatically sends that security policy rules to rules, it automatically sends that security policy rules to
appropriate NSFs (i.e., NSF-m in Developer Mgmt System A and NSF-1 appropriate NSFs (i.e., NSF-m in Developer's Mgmt System A and
in Developer Mgmt System B) which can support the capabilities NSF-1 in Developer's Mgmt System B) which can support the
(i.e., IPv6). Therefore, I2NSF User need not consider NSFs where capabilities (i.e., IPv6). Therefore, an I2NSF User need not
to apply the rules. consider NSFs where to which NSFs the rules apply.
o If NSFs find the malicious packets, it is a tremendous burden for o If NSFs encounter the malicious packets, it is a tremendous burden
network manager to apply the rule about blocking the malicious for the network manager to apply the rule to block the malicious
packets to NSFs one by one. This problem can be resolved by packets to NSFs one-by-one. This problem can be resolved by
managing the capabilities of NSFs. If NSFs find the suspicious managing the capabilities of NSFs. If NSFs encounter the
packets with IPv4, they can ask the Network Operator Mgmt System suspicious IPv4 packets, they can ask the Network Operator Mgmt
for information about the suspicious packets with IPv4. to alter System for information about the suspicious IPv4 packets in order
specific rules and/or configurations. When the Network Operator to alter specific rules and/or configurations. When the Network
Mgmt System receives information, it inspects the information Operator Mgmt System receives information, it inspects the
about the suspicious packets with IPv4. If the suspicious packets information about the suspiciou IPv4 packets. If the suspicious
are determined to be malicious packets, the Network Operator Mgmt packets are determined to be malicious packets, the Network
System creates and sends the security policy rule against Operator Mgmt System creates and sends the security policy rules
malicious packets to appropriate NSFs (i.e., NSF-1 in Developer blocking malicious packets to appropriate NSFs (i.e., NSF-1 in
Mgmt System A and NSF-1 and NSF-n in Developer Mgmt System B) Developer's Mgmt System A and NSF-1 and NSF-n in Developer's Mgmt
which can support the capabilities (i.e., IPv4). Therefore, the System B) which can support the capabilities (i.e., IPv4).
new security policy rule against malicious packets can be applied Therefore, the new security policy rules blocking malicious
to appropriate NSFs without intervention of humans. packets can be applied to appropriate NSFs without humans
intervention.
5. YANG Tree Diagram 5. YANG Tree Diagram
This section shows an YANG tree diagram of capabilities for network This section shows an YANG tree diagram of capabilities for network
security functions, as defined in the [i2nsf-nsf-cap-im]. security functions, as defined in the [draft-ietf-i2nsf-capability].
5.1. Capabilities of Network Security Function 5.1. Network Security Function (NSF) Capabilities
This section shows YANG tree diagram for capabilities of network This section shows YANG tree diagram for NSF capabilities.
security functions.
module: ietf-i2nsf-capability module: ietf-i2nsf-capability
+--rw nsf +--rw nsf* [nsf-name]
+--rw nsf-name string
+--rw time-capabilities* enumeration +--rw time-capabilities* enumeration
+--rw event-capabilities +--rw event-capabilities
| +--rw system-event-capa* identityref | +--rw system-event-capability* identityref
| +--rw system-alarm-capa* identityref | +--rw system-alarm-capability* identityref
+--rw condition-capabilities +--rw condition-capabilities
| +--rw generic-nsf-capabilities | +--rw generic-nsf-capabilities
| | +--rw ipv4-capa* identityref | | +--rw ipv4-capability* identityref
| | +--rw ipv6-capa* identityref | | +--rw ipv6-capability* identityref
| | +--rw tcp-capa* identityref | | +--rw tcp-capability* identityref
| | +--rw udp-capa* identityref | | +--rw udp-capability* identityref
| | +--rw icmp-capa* identityref | | +--rw icmp-capability* identityref
| +--rw advanced-nsf-capabilities | +--rw advanced-nsf-capabilities
| | +--rw antivirus-capa* identityref | | +--rw anti-virus-capability* identityref
| | +--rw antiddos-capa* identityref | | +--rw anti-ddos-capability* identityref
| | +--rw ips-capa* identityref | | +--rw ips-capability* identityref
| | +--rw url-capa* identityref | | +--rw url-capability* identityref
| | +--rw voip-volte-capa* identityref | | +--rw voip-volte-capability* identityref
| +--rw context-capabilities* identityref | +--rw context-capabilities* identityref
+--rw action-capabilities +--rw action-capabilities
| +--rw ingress-action-capa* identityref | +--rw ingress-action-capability* identityref
| +--rw egress-action-capa* identityref | +--rw egress-action-capability* identityref
| +--rw log-action-capa* identityref | +--rw log-action-capability* identityref
+--rw resolution-strategy-capabilities* identityref +--rw resolution-strategy-capabilities* identityref
+--rw default-action-capabilities* identityref +--rw default-action-capabilities* identityref
+--rw ipsec-method* identityref +--rw ipsec-method* identityref
Figure 2: YANG Tree Diagram for Capabilities of Network Security Figure 2: YANG Tree Diagram for Capabilities of Network Security
Functions Functions
This YANG tree diagram shows capabilities of network security This YANG tree diagram shows NSF capabilities.
functions.
The NSF includes NSF capabilities. The NSF capabilities include time The model includes NSF capabilities. The NSF capabilities include
capabilities, event capabilities, condition capabilities, action time capabilities, event capabilities, condition capabilities, action
capabilities, resolution strategy capabilities, and default action capabilities, resolution strategy capabilities, and default action
capabilities. capabilities.
Time capabilities are used to specify capabilities when to execute Time capabilities are used to specify the capabilities to specify
the I2NSF policy rule. The time capabilities are defined as absolute when to execute the I2NSF policy rule. The time capabilities are
time and periodic time. defined in terms of absolute time and periodic time. The absolute
time means the exact time to start or end. The periodic time means
repeated time like day, week, or month.
Event capabilities are used to specify capabilities how to trigger Event capabilities are used to specify capabilities how to trigger
the evaluation of the condition clause of the I2NSF Policy Rule. The the evaluation of the condition clause of the I2NSF Policy Rule. The
event capabilities are defined as system event and system alarm. The defined event capabilities are defined as system event and system
event capability can be extended according to specific vendor alarm. The event capability can be extended according to specific
condition features. The event capability is described in detail in vendor condition features. The event capability is described in
[i2nsf-nsf-cap-im]. detail in [draft-ietf-i2nsf-capability].
Condition capabilities are used to specify capabilities of a set of Condition capabilities are used to specify capabilities of a set of
attributes, features, and/or values that are to be compared with a attributes, features, and/or values that are to be compared with a
set of known attributes, features, and/or values in order to set of known attributes, features, and/or values in order to
determine whether or not the set of actions in that (imperative) determine whether or not the set of actions in that (imperative)
I2NSF policy rule can be executed or not. The condition capability I2NSF policy rule can be executed. The condition capabilities are
is classified as condition capabilities of generic network security classified in terms of generic network security functions and
functions and advanced network security functions. The condition advanced network security functions. The condition capabilities of
capabilities of generic network security functions are defined as generic network security functions are defined as IPv4 capability,
IPv4 capability, IPv6 capability, tcp capability, udp capability, and IPv6 capability, TCP capability, UDP capability, and ICMP capability.
icmp capability. The condition capabilities of advanced network The condition capabilities of advanced network security functions are
security functions are defined as antivirus capability, antiddos defined as anti-virus capability, anti-ddos capability, IPS
capability, ips capability, http capability, and VoIP/VoLTE capability, HTTP capability, and VoIP/VoLTE capability. The
capability. The condition capability can be extended according to condition capability can be extended according to specific vendor
specific vendor condition features. The condition capability is condition features. The condition capability is described in detail
described in detail in [i2nsf-nsf-cap-im]. in [draft-ietf-i2nsf-capability].
Action capabilities is used to specify capabilities how to control Action capabilities are used to specify capabilities of how to
and monitor aspects of flow-based NSFs when the event and condition control and monitor aspects of flow-based NSFs when the event and
clauses are satisfied. The action capabilities are defined as condition clauses are satisfied. The action capabilities are defined
ingress action capability, egress action capability, and log action as ingress-action capability, egress-action capability, and log-
capability. The action capability can be extended according to action capability. The action capability can be extended according
specific vendor action features. The action capability is described to specific vendor action features. The action capability is
in detail in [i2nsf-nsf-cap-im]. described in detail in [draft-ietf-i2nsf-capability].
Resolution strategy capabilities are used to specify capabilities how Resolution strategy capabilities are used to specify capabilities of
to resolve conflicts that occur between the actions of the same or how to resolve conflicts that occur between the actions of the same
different policy rules that are matched and contained in this or different policy rules that are matched and contained in this
particular NSF. The resolution strategy capabilities are defined as particular NSF. The resolution strategy capabilities are defined as
First Matching Rule (FMR), Last Matching Rule (LMR), Prioritized First Matching Rule (FMR), Last Matching Rule (LMR), Prioritized
Matching Rule (PMR) with Errors (PMRE), and Prioritized Matching Rule Matching Rule (PMR), Prioritized Matching Rule with Errors (PMRE),
with No Errors (PMRN). The resolution strategy capability can be and Prioritized Matching Rule with No Errors (PMRN). The resolution
extended according to specific vendor action features. The strategy capabilities can be extended according to specific vendor
resolution strategy capability is described in detail in action features. The resolution strategy capability is described in
[i2nsf-nsf-cap-im]. detail in [draft-ietf-i2nsf-capability].
Default action capabilities are used to specify capabilities how to Default action capabilities are used to specify capabilities of how
execute I2NSF policy rule when no rule matches a packet. The default to execute I2NSF policy rules when no rule matches a packet. The
action capabilities are defined as pass, drop, reject, alert, and default action capabilities are defined as pass, drop, reject, alert,
mirror. The default action capability can be extended according to and mirror. The default action capability can be extended according
specific vendor action features. The default action capability is to specific vendor action features. The default action capability is
described in detail in [i2nsf-nsf-cap-im]. described in detail in [draft-ietf-i2nsf-capability].
IPsec method capabilities are used to specify capabilities how to IPsec method capabilities are used to specify capabilities of how to
support an Internet key exchange for the security communication. The support an Internet Key Exchange (IKE) for the security
default action capabilities are defined as ike and ikeless. The communication. The default action capabilities are defined as IKE
default action capability can be extended according to specific and IKE-less. The default action capability can be extended
vendor action features. The default action capability is described according to specific vendor action features. The default action
in detail in [draft-ietf-i2nsf-sdn-ipsec-flow-protection]. capability is described in detail in
[draft-ietf-i2nsf-sdn-ipsec-flow-protection].
6. YANG Data Modules 6. YANG Data Modules
6.1. I2NSF Capability YANG Data Module 6.1. I2NSF Capability YANG Data Module
This section introduces an YANG data module for capabilities of This section introduces a YANG data module for network security
network security functions, as defined in the [i2nsf-nsf-cap-im]. functions capabilities, as defined in the
[draft-ietf-i2nsf-capability].
<CODE BEGINS> file "ietf-i2nsf-capability@2019-03-28.yang" <CODE BEGINS> file "ietf-i2nsf-capability@2019-07-24.yang"
module ietf-i2nsf-capability { module ietf-i2nsf-capability {
yang-version 1.1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability"; "urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability";
prefix prefix
iicapa; nsfcap;
organization organization
"IETF I2NSF (Interface to Network Security Functions) "IETF I2NSF (Interface to Network Security Functions)
Working Group"; Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/i2nsf> "WG Web: <http://tools.ietf.org/wg/i2nsf>
WG List: <mailto:i2nsf@ietf.org> WG List: <mailto:i2nsf@ietf.org>
WG Chair: Adrian Farrel
<mailto:Adrain@olddog.co.uk>
WG Chair: Linda Dunbar WG Chair: Linda Dunbar
<mailto:Linda.duhbar@huawei.com> <mailto:ldunbar@futurewei.com>
WG Chair: Yoav Nir
<mailto:ynir.ietf@gmail.com>
Editor: Susan Hares Editor: Susan Hares
<mailto:shares@ndzh.com> <mailto:shares@ndzh.com>
Editor: Jaehoon Paul Jeong Editor: Jaehoon Paul Jeong
<mailto:pauljeong@skku.edu> <mailto:pauljeong@skku.edu>
Editor: Jinyong Tim Kim Editor: Jinyong Tim Kim
<mailto:timkim@skku.edu>"; <mailto:timkim@skku.edu>";
skipping to change at page 10, line 18 skipping to change at page 10, line 22
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 8341; see This version of this YANG module is part of RFC 8341; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision "2019-03-28"{ revision "2019-07-24"{
description "Initial revision."; description "Initial revision.";
reference reference
"RFC XXXX: I2NSF Capability YANG Data Model"; "RFC XXXX: I2NSF Capability YANG Data Model";
} }
/* /*
* Identities * Identities
*/ */
identity event { identity event {
description description
"Base identity for event of policy."; "Base identity for I2NSF policy events.";
reference reference
"draft-hong-i2nsf-nsf-monitoring-data-model-06 "draft-ietf-i2nsf-nsf-monitoring-data-model-01
- Event"; - Event";
} }
identity system-event-capa { identity system-event-capability {
base event; base event;
description description
"Identity for system event"; "Identity for system events";
reference reference
"draft-hong-i2nsf-nsf-monitoring-data-model-06 "draft-ietf-i2nsf-nsf-monitoring-data-model-01
- System alarm"; - System alarm";
} }
identity system-alarm-capa { identity system-alarm-capability {
base event; base event;
description description
"Identity for system alarm"; "Identity for system alarms";
reference reference
"draft-hong-i2nsf-nsf-monitoring-data-model-06 "draft-ietf-i2nsf-nsf-monitoring-data-model-01
- System alarm"; - System alarm";
} }
identity access-violation { identity access-violation {
base system-event-capa; base system-event-capability;
description description
"Identity for access violation "Identity for access violation events";
among system events";
reference reference
"draft-hong-i2nsf-nsf-monitoring-data-model-06 "draft-ietf-i2nsf-nsf-monitoring-data-model-01
- System event"; - System event";
} }
identity configuration-change { identity configuration-change {
base system-event-capa; base system-event-capability;
description description
"Identity for configuration change "Identity for configuration change events";
among system events";
reference reference
"draft-hong-i2nsf-nsf-monitoring-data-model-06 "draft-ietf-i2nsf-nsf-monitoring-data-model-01
- System event"; - System event";
} }
identity memory-alarm { identity memory-alarm {
base system-alarm-capa; base system-alarm-capability;
description description
"Identity for memory alarm "Identity for memory alarm events";
among system alarms";
reference reference
"draft-hong-i2nsf-nsf-monitoring-data-model-06 "draft-ietf-i2nsf-nsf-monitoring-data-model-01
- System alarm"; - System alarm";
} }
identity cpu-alarm { identity cpu-alarm {
base system-alarm-capa; base system-alarm-capability;
description description
"Identity for cpu alarm "Identity for CPU alarm events";
among system alarms";
reference reference
"draft-hong-i2nsf-nsf-monitoring-data-model-06 "draft-ietf-i2nsf-nsf-monitoring-data-model-01
- System alarm"; - System alarm";
} }
identity disk-alarm { identity disk-alarm {
base system-alarm-capa; base system-alarm-capability;
description description
"Identity for disk alarm "Identity for disk alarm events";
among system alarms";
reference reference
"draft-hong-i2nsf-nsf-monitoring-data-model-06 "draft-ietf-i2nsf-nsf-monitoring-data-model-01
- System alarm"; - System alarm";
} }
identity hardware-alarm { identity hardware-alarm {
base system-alarm-capa; base system-alarm-capability;
description description
"Identity for hardware alarm "Identity for hardware alarm events";
among system alarms";
reference reference
"draft-hong-i2nsf-nsf-monitoring-data-model-06 "draft-ietf-i2nsf-nsf-monitoring-data-model-01
- System alarm"; - System alarm";
} }
identity interface-alarm { identity interface-alarm {
base system-alarm-capa; base system-alarm-capability;
description description
"Identity for interface alarm "Identity for interface alarm events";
among system alarms";
reference reference
"draft-hong-i2nsf-nsf-monitoring-data-model-06 "draft-ietf-i2nsf-nsf-monitoring-data-model-01
- System alarm"; - System alarm";
} }
identity condition { identity condition {
description description
"Base identity for conditions of policy"; "Base identity for policy conditions";
} }
identity context-capa { identity context-capability {
base condition; base condition;
description description
"Identity for capabilities of context condition"; "Identity for context condition capabilities";
} }
identity acl-number { identity acl-number {
base context-capa; base context-capability;
description description
"Identity for acl number capability "Identity for ACL number condition capability";
of context condition";
} }
identity application { identity application {
base context-capa; base context-capability;
description description
"Identity for application capability "Identity for application condition capability";
of context condition";
} }
identity target { identity target {
base context-capa; base context-capability;
description description
"Identity for target capability "Identity for target condition capability";
of context condition";
} }
identity user { identity user {
base context-capa; base context-capability;
description description
"Identity for user capability "Identity for user condition capability";
of context condition";
} }
identity group { identity group {
base context-capa; base context-capability;
description description
"Identity for group capability "Identity for group condition capability";
of context condition";
} }
identity geography { identity geography {
base context-capa; base context-capability;
description description
"Identity for geography capability "Identity for geography condition capability";
of context condition";
} }
identity ipv4-capa { identity ipv4-capability {
base condition; base condition;
description description
"Identity for capabilities of IPv4 condition"; "Identity for IPv4 condition capabilities";
reference reference
"RFC 791: Internet Protocol"; "RFC 791: Internet Protocol";
} }
identity exact-ipv4-header-length { identity exact-ipv4-header-length {
base ipv4-capa; base ipv4-capability;
description description
"Identity for exact header length capability "Identity for exact-match IPv4 header-length
of IPv4 condition"; condition capability";
reference reference
"RFC 791: Internet Protocol - Header Length"; "RFC 791: Internet Protocol - Header Length";
} }
identity range-ipv4-header-length { identity range-ipv4-header-length {
base ipv4-capa; base ipv4-capability;
description description
"Identity for range header length capability "Identity for range-match IPv4 header-length
of IPv4 condition"; condition capability";
reference reference
"RFC 791: Internet Protocol - Header Length"; "RFC 791: Internet Protocol - Header Length";
} }
identity ipv4-tos { identity ipv4-tos {
base ipv4-capa; base ipv4-capability;
description description
"Identity for type of service capability "Identity for IPv4 Type-Of-Service (TOS)
of IPv4 condition"; condition capability";
reference reference
"RFC 791: Internet Protocol - Type of Service"; "RFC 791: Internet Protocol - Type of Service";
} }
identity exact-ipv4-total-length { identity exact-ipv4-total-length {
base ipv4-capa; base ipv4-capability;
description description
"Identity for exact total length capability "Identity for exact-match IPv4 total length
of IPv4 condition"; condition capability";
reference reference
"RFC 791: Internet Protocol - Total Length"; "RFC 791: Internet Protocol - Total Length";
} }
identity range-ipv4-total-length { identity range-ipv4-total-length {
base ipv4-capa; base ipv4-capability;
description description
"Identity for range total length capability "Identity for range-match IPv4 total length
of IPv4 condition"; condition capability";
reference reference
"RFC 791: Internet Protocol - Total Length"; "RFC 791: Internet Protocol - Total Length";
} }
identity ipv4-id { identity ipv4-id {
base ipv4-capa; base ipv4-capability;
description description
"Identity for identification capability "Identity for identification condition capability";
of IPv4 condition";
reference reference
"RFC 791: Internet Protocol - Identification"; "RFC 791: Internet Protocol - Identification";
} }
identity ipv4-fragment-flags { identity ipv4-fragment-flags {
base ipv4-capa; base ipv4-capability;
description description
"Identity for fragment flags capability "Identity for IPv4 fragment flags condition capability";
of IPv4 condition";
reference reference
"RFC 791: Internet Protocol - Fragmentation Flags"; "RFC 791: Internet Protocol - Fragmentation Flags";
} }
identity exact-ipv4-fragment-offset { identity exact-ipv4-fragment-offset {
base ipv4-capa; base ipv4-capability;
description description
"Identity for exact fragment offset capability "Identity for exact-match IPv4 fragment offset
of IPv4 condition"; condition capability";
reference reference
"RFC 791: Internet Protocol - Fragmentation Offset"; "RFC 791: Internet Protocol - Fragmentation Offset";
} }
identity range-ipv4-fragment-offset { identity range-ipv4-fragment-offset {
base ipv4-capa; base ipv4-capability;
description description
"Identity for range fragment offset capability "Identity for range-match IPv4 fragment offset
of IPv4 condition"; condition capability";
reference reference
"RFC 791: Internet Protocol - Fragmentation Offset"; "RFC 791: Internet Protocol - Fragmentation Offset";
} }
identity exact-ipv4-ttl { identity exact-ipv4-ttl {
base ipv4-capa; base ipv4-capability;
description description
"Identity for exact time to live capability "Identity for exact-match IPv4 Time-To-Live (TTL)
of IPv4 condition"; condition capability";
reference reference
"RFC 791: Internet Protocol - Time To Live (TTL)"; "RFC 791: Internet Protocol - Time To Live (TTL)";
} }
identity range-ipv4-ttl { identity range-ipv4-ttl {
base ipv4-capa; base ipv4-capability;
description description
"Identity for range time to live capability "Identity for range-match IPv4 Time-To-Live (TTL)
of IPv4 condition"; condition capability";
reference reference
"RFC 791: Internet Protocol - Time To Live (TTL)"; "RFC 791: Internet Protocol - Time To Live (TTL)";
} }
identity ipv4-protocol { identity ipv4-protocol {
base ipv4-capa; base ipv4-capability;
description description
"Identity for protocol capability "Identity for IPv4 protocol condition capability";
of IPv4 condition";
reference reference
"RFC 790: Assigned numbers - Assigned Internet "RFC 790: Assigned numbers - Assigned Internet
Protocol Number Protocol Number
RFC 791: Internet Protocol - Protocol"; RFC 791: Internet Protocol - Protocol";
} }
identity exact-ipv4-address { identity exact-ipv4-address {
base ipv4-capa; base ipv4-capability;
description description
"Identity for exact address capability "Identity for exact-match IPv4 address
of IPv4 condition"; condition capability";
reference reference
"RFC 791: Internet Protocol - Address"; "RFC 791: Internet Protocol - Address";
} }
identity range-ipv4-address { identity range-ipv4-address {
base ipv4-capa; base ipv4-capability;
description description
"Identity for range-address capability "Identity for range-match IPv4 address
of IPv4 condition"; condition capability";
reference reference
"RFC 791: Internet Protocol - Address"; "RFC 791: Internet Protocol - Address";
} }
identity ipv4-ipopts { identity ipv4-ip-opts {
base ipv4-capa; base ipv4-capability;
description description
"Identity for option capability "Identity for IPv4 option condition capability";
of IPv4 condition";
reference reference
"RFC 791: Internet Protocol - Options"; "RFC 791: Internet Protocol - Options";
} }
identity ipv4-sameip { identity ipv4-geo-ip {
base ipv4-capa; base ipv4-capability;
description
"Identity for sameIP capability
of IPv4 condition";
}
identity ipv4-geoip {
base ipv4-capa;
description description
"Identity for geography capability "Identity for geography condition capability";
of IPv4 condition"; reference
"draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Geo-IP";
} }
identity ipv6-capa { identity ipv6-capability {
base condition; base condition;
description description
"Identity for capabilities of IPv6 condition"; "Identity for IPv6 condition capabilities";
reference reference
"RFC 2460: Internet Protocol, Version 6 (IPv6) "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification"; Specification";
} }
identity ipv6-traffic-class { identity ipv6-traffic-class {
base ipv6-capa; base ipv6-capability;
description description
"Identity for traffic class capability "Identity for IPv6 traffic class
of IPv6 condition"; condition capability";
reference reference
"RFC 2460: Internet Protocol, Version 6 (IPv6) "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification - Traffic Class"; Specification - Traffic Class";
} }
identity exact-ipv6-flow-label { identity exact-ipv6-flow-label {
base ipv6-capa; base ipv6-capability;
description description
"Identity for exact flow label capability "Identity for exact-match IPv6 flow label
of IPv6 condition"; condition capability";
reference reference
"RFC 2460: Internet Protocol, Version 6 (IPv6) "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification - Flow Label"; Specification - Flow Label";
} }
identity range-ipv6-flow-label { identity range-ipv6-flow-label {
base ipv6-capa; base ipv6-capability;
description description
"Identity for range flow label capability "Identity for range-match IPv6 flow label
of IPv6 condition"; condition capability";
reference reference
"RFC 2460: Internet Protocol, Version 6 (IPv6) "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification - Flow Label"; Specification - Flow Label";
} }
identity exact-ipv6-payload-length { identity exact-ipv6-payload-length {
base ipv6-capa; base ipv6-capability;
description description
"Identity for exact payload length capability "Identity for exact-match IPv6 payload length
of IPv6 condition"; condition capability";
reference reference
"RFC 2460: Internet Protocol, Version 6 (IPv6) "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification - Payload Length"; Specification - Payload Length";
} }
identity range-ipv6-payload-length { identity range-ipv6-payload-length {
base ipv6-capa; base ipv6-capability;
description description
"Identity for range payload length capability "Identity for range-match IPv6 payload length
of IPv6 condition"; condition capability";
reference reference
"RFC 2460: Internet Protocol, Version 6 (IPv6) "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification - Payload Length"; Specification - Payload Length";
} }
identity ipv6-next-header { identity ipv6-next-header {
base ipv6-capa; base ipv6-capability;
description description
"Identity for next header capability "Identity for IPv6 next header condition capability";
of IPv6 condition";
reference reference
"RFC 2460: Internet Protocol, Version 6 (IPv6) "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification - Next Header"; Specification - Next Header";
} }
identity exact-ipv6-hop-limit { identity exact-ipv6-hop-limit {
base ipv6-capa; base ipv6-capability;
description description
"Identity for exact hop limit capability "Identity for exact-match IPv6 hop limit
of IPv6 condition"; condition capability";
reference reference
"RFC 2460: Internet Protocol, Version 6 (IPv6) "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification - Hop Limit"; Specification - Hop Limit";
} }
identity range-ipv6-hop-limit { identity range-ipv6-hop-limit {
base ipv6-capa; base ipv6-capability;
description description
"Identity for range hop limit capability "Identity for range-match IPv6 hop limit
of IPv6 condition"; condition capability";
reference reference
"RFC 2460: Internet Protocol, Version 6 (IPv6) "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification - Hop Limit"; Specification - Hop Limit";
} }
identity exact-ipv6-address { identity exact-ipv6-address {
base ipv6-capa; base ipv6-capability;
description description
"Identity for exact address capability "Identity for exact-match IPv6 address
of IPv6 condition"; condition capability";
reference reference
"RFC 2460: Internet Protocol, Version 6 (IPv6) "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification - Address"; Specification - Address";
} }
identity range-ipv6-address { identity range-ipv6-address {
base ipv6-capa; base ipv6-capability;
description description
"Identity for range address capability "Identity for range-match IPv6 address
of IPv6 condition"; condition capability";
reference reference
"RFC 2460: Internet Protocol, Version 6 (IPv6) "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification - Address"; Specification - Address";
} }
identity tcp-capa { identity tcp-capability {
base condition; base condition;
description description
"Identity for capabilities of tcp condition"; "Identity for TCP condition capabilities";
reference reference
"RFC 793: Transmission Control Protocol"; "RFC 793: Transmission Control Protocol";
} }
identity exact-tcp-port-num { identity exact-tcp-port-num {
base tcp-capa; base tcp-capability;
description description
"Identity for exact port number capability "Identity for exact-match TCP port number
of tcp condition"; condition capability";
reference reference
"RFC 793: Transmission Control Protocol - Port Number"; "RFC 793: Transmission Control Protocol - Port Number";
} }
identity range-tcp-port-num { identity range-tcp-port-num {
base tcp-capa; base tcp-capability;
description description
"Identity for range port number capability "Identity for range-match TCP port number
of tcp condition"; condition capability";
reference reference
"RFC 793: Transmission Control Protocol - Port Number"; "RFC 793: Transmission Control Protocol - Port Number";
} }
identity exact-tcp-seq-num { identity exact-tcp-seq-num {
base tcp-capa; base tcp-capability;
description description
"Identity for exact sequence number capability "Identity for exact-match TCP sequence number
of tcp condition"; condition capability";
reference reference
"RFC 793: Transmission Control Protocol - Sequence Number"; "RFC 793: Transmission Control Protocol - Sequence Number";
} }
identity range-tcp-seq-num { identity range-tcp-seq-num {
base tcp-capa; base tcp-capability;
description description
"Identity for range sequence number capability "Identity for range-match TCP sequence number
of tcp condition"; condition capability";
reference reference
"RFC 793: Transmission Control Protocol - Sequence Number"; "RFC 793: Transmission Control Protocol - Sequence Number";
} }
identity exact-tcp-ack-num { identity exact-tcp-ack-num {
base tcp-capa; base tcp-capability;
description description
"Identity for exact acknowledgement number capability "Identity for exact-match TCP acknowledgement number
of tcp condition"; condition capability";
reference reference
"RFC 793: Transmission Control Protocol - Acknowledgement Number"; "RFC 793: Transmission Control Protocol - Acknowledgement Number";
} }
identity range-tcp-ack-num { identity range-tcp-ack-num {
base tcp-capa; base tcp-capability;
description description
"Identity for range acknowledgement number capability "Identity for range-match TCP acknowledgement number
of tcp condition"; condition capability";
reference reference
"RFC 793: Transmission Control Protocol - Acknowledgement Number"; "RFC 793: Transmission Control Protocol - Acknowledgement Number";
} }
identity exact-tcp-window-size { identity exact-tcp-window-size {
base tcp-capa; base tcp-capability;
description description
"Identity for exact window size capability "Identity for exact-match TCP window size
of tcp condition"; condition capability";
reference reference
"RFC 793: Transmission Control Protocol - Window Size"; "RFC 793: Transmission Control Protocol - Window Size";
} }
identity range-tcp-window-size { identity range-tcp-window-size {
base tcp-capa; base tcp-capability;
description description
"Identity for range window size capability "Identity for range-match TCP window size
of tcp condition"; condition capability";
reference reference
"RFC 793: Transmission Control Protocol - Window Size"; "RFC 793: Transmission Control Protocol - Window Size";
} }
identity tcp-flags { identity tcp-flags {
base tcp-capa; base tcp-capability;
description description
"Identity for flags capability "Identity for TCP flags condition capability";
of tcp condition";
reference reference
"RFC 793: Transmission Control Protocol - Flags"; "RFC 793: Transmission Control Protocol - Flags";
} }
identity udp-capa { identity udp-capability {
base condition; base condition;
description description
"Identity for capabilities of udp condition"; "Identity for UDP condition capabilities";
reference reference
"RFC 768: User Datagram Protocol"; "RFC 768: User Datagram Protocol";
} }
identity exact-udp-port-num { identity exact-udp-port-num {
base udp-capa; base udp-capability;
description description
"Identity for exact port number capability "Identity for exact-match UDP port number
of udp condition"; condition capability";
reference reference
"RFC 768: User Datagram Protocol - Port Number"; "RFC 768: User Datagram Protocol - Port Number";
} }
identity range-udp-port-num { identity range-udp-port-num {
base udp-capa; base udp-capability;
description description
"Identity for range port number capability "Identity for range-match UDP port number
of udp condition"; condition capability";
reference reference
"RFC 768: User Datagram Protocol - Port Number"; "RFC 768: User Datagram Protocol - Port Number";
} }
identity exact-udp-total-length { identity exact-udp-total-length {
base udp-capa; base udp-capability;
description description
"Identity for exact total-length capability "Identity for exact-match UDP total-length
of udp condition"; condition capability";
reference reference
"RFC 768: User Datagram Protocol - Total Length"; "RFC 768: User Datagram Protocol - Total Length";
} }
identity range-udp-total-length { identity range-udp-total-length {
base udp-capa; base udp-capability;
description description
"Identity for range total-length capability "Identity for range-match UDP total-length
of udp condition"; condition capability";
reference reference
"RFC 768: User Datagram Protocol - Total Length"; "RFC 768: User Datagram Protocol - Total Length";
} }
identity icmp-capa { identity icmp-capability {
base condition; base condition;
description description
"Identity for capabilities of icmp condition"; "Identity for ICMP condition capabilities";
reference reference
"RFC 792: Internet Control Message Protocol"; "RFC 792: Internet Control Message Protocol";
} }
identity icmp-type { identity icmp-type {
base icmp-capa; base icmp-capability;
description description
"Identity for icmp type capability "Identity for ICMP type condition capability";
of icmp condition";
reference reference
"RFC 792: Internet Control Message Protocol"; "RFC 792: Internet Control Message Protocol";
} }
identity url-capa { identity url-capability {
base condition; base condition;
description description
"Identity for capabilities of url condition"; "Identity for URL condition capabilities";
} }
identity pre-defined { identity pre-defined {
base url-capa; base url-capability;
description description
"Identity for pre-defined capabilities of "Identity for URL pre-defined condition capabilities";
url condition";
} }
identity user-defined { identity user-defined {
base url-capa; base url-capability;
description description
"Identity for user-defined capabilities of "Identity for URL user-defined condition capabilities";
url condition";
} }
identity log-action-capa { identity log-action-capability {
description description
"Identity for capabilities of log action"; "Identity for log-action capabilities";
} }
identity rule-log { identity rule-log {
base log-action-capa; base log-action-capability;
description description
"Identity for rule log capability "Identity for rule log log-action capability";
of log action";
} }
identity session-log { identity session-log {
base log-action-capa; base log-action-capability;
description description
"Identity for session log capability "Identity for session log log-action capability";
of log action";
} }
identity ingress-action-capa { identity ingress-action-capability {
description description
"Identity for capabilities of ingress action"; "Identity for ingress-action capabilities";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Action"; of NSFs Capabilities - Action";
} }
identity egress-action-capa { identity egress-action-capability {
description description
"Base identity for egress action"; "Base identity for egress-action capabilities";
reference
"draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Egress action";
} }
identity default-action-capa { identity default-action-capability {
description description
"Identity for capabilities of default action"; "Identity for default-action capabilities";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Default action"; of NSFs Capabilities - Default action";
} }
identity pass { identity pass {
base ingress-action-capa; base ingress-action-capability;
base egress-action-capa; base egress-action-capability;
base default-action-capa; base default-action-capability;
description description
"Identity for pass"; "Identity for pass action capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Actions and of NSFs Capabilities - Actions and
default action"; default action";
} }
identity drop { identity drop {
base ingress-action-capa; base ingress-action-capability;
base egress-action-capa; base egress-action-capability;
base default-action-capa; base default-action-capability;
description description
"Identity for drop"; "Identity for drop action capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Actions and of NSFs Capabilities - Actions and
default action"; default action";
} }
identity reject { identity reject {
base ingress-action-capa; base ingress-action-capability;
base egress-action-capa; base egress-action-capability;
base default-action-capa; base default-action-capability;
description description
"Identity for reject"; "Identity for reject action capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Actions and of NSFs Capabilities - Actions and
default action"; default action";
} }
identity alert { identity alert {
base ingress-action-capa; base ingress-action-capability;
base egress-action-capa; base egress-action-capability;
base default-action-capa; base default-action-capability;
description description
"Identity for alert"; "Identity for alert action capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Actions and of NSFs Capabilities - Actions and
default action"; default action";
} }
identity mirror { identity mirror {
base ingress-action-capa; base ingress-action-capability;
base egress-action-capa; base egress-action-capability;
base default-action-capa; base default-action-capability;
description description
"Identity for mirror"; "Identity for mirror action capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Actions and of NSFs Capabilities - Actions and
default action"; default action";
} }
identity invoke-signaling { identity invoke-signaling {
base egress-action-capa; base egress-action-capability;
description description
"Identity for invoke signaling"; "Identity for invoke signaling action capability";
} }
identity tunnel-encapsulation { identity tunnel-encapsulation {
base egress-action-capa; base egress-action-capability;
description description
"Identity for tunnel encapsulation"; "Identity for tunnel encapsulation action capability";
} }
identity forwarding { identity forwarding {
base egress-action-capa; base egress-action-capability;
description description
"Identity for forwarding"; "Identity for forwarding action capability";
} }
identity redirection { identity redirection {
base egress-action-capa; base egress-action-capability;
description description
"Identity for redirection"; "Identity for redirection action capability";
} }
identity resolution-strategy-capa { identity resolution-strategy-capability {
description description
"Base identity for resolution strategy"; "Base identity for resolution strategy capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Resolution Strategy"; of NSFs Capabilities - Resolution Strategy";
} }
identity fmr { identity fmr {
base resolution-strategy-capa; base resolution-strategy-capability;
description description
"Identity for First Matching Rule (FMR)"; "Identity for First Matching Rule (FMR)
resolution strategy capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Resolution Strategy"; of NSFs Capabilities - Resolution Strategy";
} }
identity lmr { identity lmr {
base resolution-strategy-capa; base resolution-strategy-capability;
description description
"Identity for Last Matching Rule (LMR)"; "Identity for Last Matching Rule (LMR)
resolution strategy capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Resolution Strategy"; of NSFs Capabilities - Resolution Strategy";
} }
identity pmr { identity pmr {
base resolution-strategy-capa; base resolution-strategy-capability;
description description
"Identity for Prioritized Matching Rule (PMR)"; "Identity for Prioritized Matching Rule (PMR)
resolution strategy capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Resolution Strategy"; of NSFs Capabilities - Resolution Strategy";
} }
identity pmre { identity pmre {
base resolution-strategy-capa; base resolution-strategy-capability;
description description
"Identity for Prioritized Matching Rule "Identity for Prioritized Matching Rule
with Errors (PMRE)"; with Errors (PMRE) resolution strategy capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Resolution Strategy"; of NSFs Capabilities - Resolution Strategy";
} }
identity pmrn { identity pmrn {
base resolution-strategy-capa; base resolution-strategy-capability;
description description
"Identity for Prioritized Matching Rule "Identity for Prioritized Matching Rule
with No Errors (PMRN)"; with No Errors (PMRN) resolution strategy capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Resolution Strategy"; of NSFs Capabilities - Resolution Strategy";
} }
identity advanced-nsf-capability {
identity advanced-nsf-capa {
description description
"Base identity for advanced "Base identity for advanced
network security function capabilities"; network security function (NSF) capabilities";
reference reference
"RFC 8329: Framework for Interface to Network Security "RFC 8329: Framework for Interface to Network Security
Functions - Differences from ACL Data Models Functions - Differences from ACL Data Models
draft-dong-i2nsf-asf-config-01: Configuration of draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller"; Controller";
} }
identity antivirus-capa { identity anti-virus-capability {
base advanced-nsf-capa; base advanced-nsf-capability;
description description
"Identity for antivirus capabilities"; "Identity for advanced NSF anti-virus capabilities";
reference reference
"RFC 8329: Framework for Interface to Network Security "RFC 8329: Framework for Interface to Network Security
Functions - Differences from ACL Data Models Functions - Differences from ACL Data Models
draft-dong-i2nsf-asf-config-01: Configuration of draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antivirus"; Controller - Anti-virus";
} }
identity antiddos-capa { identity anti-ddos-capability {
base advanced-nsf-capa; base advanced-nsf-capability;
description description
"Identity for antiddos capabilities"; "Identity for advanced NSF anti-ddos capabilities";
reference reference
"RFC 8329: Framework for Interface to Network Security "RFC 8329: Framework for Interface to Network Security
Functions - Differences from ACL Data Models Functions - Differences from ACL Data Models
draft-dong-i2nsf-asf-config-01: Configuration of draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antiddos"; Controller - Anti-ddos";
} }
identity ips-capa { identity ips-capability {
base advanced-nsf-capa; base advanced-nsf-capability;
description description
"Identity for IPS capabilities"; "Identity for advanced NSF Intrusion Prevention System
(IPS) capabilities";
reference reference
"RFC 8329: Framework for Interface to Network Security "RFC 8329: Framework for Interface to Network Security
Functions - Differences from ACL Data Models Functions - Differences from ACL Data Models
draft-dong-i2nsf-asf-config-01: Configuration of draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Intrusion Prevention System"; Controller - Intrusion Prevention System";
} }
identity voip-volte-capability {
identity voip-volte-capa { base advanced-nsf-capability;
base advanced-nsf-capa;
description description
"Identity for VoIP/VoLTE capabilities"; "Identity for advanced NSF VoIP/VoLTE capabilities";
reference reference
"RFC 3261: SIP: Session Initiation Protocol "RFC 3261: SIP: Session Initiation Protocol
RFC 8329: Framework for Interface to Network Security RFC 8329: Framework for Interface to Network Security
Functions - Differences from ACL Data Models Functions - Differences from ACL Data Models
draft-dong-i2nsf-asf-config-01: Configuration of draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller"; Controller";
} }
identity detect { identity detect {
base antivirus-capa; base anti-virus-capability;
description description
"Identity for detect capabilities "Identity for advanced NSF anti-virus detect capability";
of antivirus";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antivirus"; Controller - Anti-virus";
} }
identity exception-application { identity exception-application {
base antivirus-capa; base anti-virus-capability;
description description
"Identity for exception application capabilities "Identity for advanced NSF anti-virus exception
of antivirus"; application capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antivirus"; Controller - Anti-virus";
} }
identity exception-signature { identity exception-signature {
base antivirus-capa; base anti-virus-capability;
description description
"Identity for exception signature capabilities "Identity for advanced NSF anti-virus exception
of antivirus"; signature capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antivirus"; Controller - Anti-virus";
} }
identity whitelists { identity whitelists {
base antivirus-capa; base anti-virus-capability;
description description
"Identity for whitelists capabilities "Identity for advanced NSF anti-virus whitelists
of antivirus"; capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antivirus"; Controller - Anti-virus";
} }
identity syn-flood-action { identity syn-flood-action {
base antiddos-capa; base anti-ddos-capability;
description description
"Identity for syn flood action capabilities "Identity for advanced NSF anti-DDoS syn flood
of antiddos"; action capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antiddos"; Controller - Anti-DDoS";
} }
identity udp-flood-action { identity udp-flood-action {
base antiddos-capa; base anti-ddos-capability;
description description
"Identity for udp flood action capabilities "Identity for advanced NSF anti-DDoS UDP flood
of antiddos"; action capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antiddos"; Controller - Anti-DDoS";
} }
identity http-flood-action { identity http-flood-action {
base antiddos-capa; base anti-ddos-capability;
description description
"Identity for http flood action capabilities "Identity for advanced NSF anti-DDoS http flood
of antiddos"; action capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antiddos"; Controller - Anti-DDoS";
} }
identity https-flood-action { identity https-flood-action {
base antiddos-capa; base anti-ddos-capability;
description description
"Identity for https flood action capabilities "Identity for advanced NSF anti-DDoS https flood
of antiddos"; action capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antiddos"; Controller - Anti-DDoS";
} }
identity dns-request-flood-action { identity dns-request-flood-action {
base antiddos-capa; base anti-ddos-capability;
description description
"Identity for dns request flood action capabilities "Identity for advanced NSF anti-DDoS dns request
of antiddos"; flood action capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antiddos"; Controller - Anti-DDoS";
} }
identity dns-reply-flood-action { identity dns-reply-flood-action {
base antiddos-capa; base anti-ddos-capability;
description description
"Identity for dns reply flood action capabilities "Identity for advanced NSF anti-DDoS dns reply flood
of antiddos"; action capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antiddos"; Controller - Anti-DDoS";
} }
identity icmp-flood-action { identity icmp-flood-action {
base antiddos-capa; base anti-ddos-capability;
description description
"Identity for icmp flood action capabilities "Identity for advanced NSF anti-DDoS icmp flood
of antiddos"; action capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antiddos"; Controller - Anti-DDoS";
} }
identity sip-flood-action { identity sip-flood-action {
base antiddos-capa; base anti-ddos-capability;
description description
"Identity for sip flood action capabilities "Identity for advanced NSF anti-DDoS sip flood
of antiddos"; action capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antiddos"; Controller - Anti-DDoS";
} }
identity detect-mode { identity detect-mode {
base antiddos-capa; base anti-ddos-capability;
description description
"Identity for detect mode capabilities "Identity for advanced NSF anti-DDoS detect
of antiddos"; mode capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antiddos"; Controller - Anti-DDoS";
} }
identity baseline-learn { identity baseline-learning {
base antiddos-capa; base anti-ddos-capability;
description description
"Identity for baseline learn capabilities "Identity for advanced NSF anti-DDoS baseline
of antiddos"; learning capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Antiddos"; Controller - Anti-DDoS";
} }
identity signature-set { identity signature-set {
base ips-capa; base ips-capability;
description description
"Identity for signature set capabilities "Identity for advanced NSF IPS signature set
of IPS"; capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Intrusion Prevention System"; Controller - Intrusion Prevention System";
} }
identity ips-exception-signature { identity ips-exception-signature {
base ips-capa; base ips-capability;
description description
"Identity for ips exception signature capabilities "Identity for advanced NSF IPS exception signature
of IPS"; capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller - Intrusion Prevention System"; Controller - Intrusion Prevention System";
} }
identity voice-id { identity voice-id {
base voip-volte-capa; base voip-volte-capability;
description description
"Identity for voice-id capabilities "Identity for advanced NSF VoIP/VoLTE voice-id
of VoIP/VoLTE"; capability";
reference reference
"RFC 3261: SIP: Session Initiation Protocol"; "RFC 3261: SIP: Session Initiation Protocol";
} }
identity user-agent { identity user-agent {
base voip-volte-capa; base voip-volte-capability;
description description
"Identity for user agent capabilities "Identity for advanced NSF VoIP/VoLTE user agent
of VoIP/VoLTE"; capability";
reference reference
"RFC 3261: SIP: Session Initiation Protocol"; "RFC 3261: SIP: Session Initiation Protocol";
} }
identity ipsec-capa { identity ipsec-capability {
description description
"Base identity for an IPsec"; "Base identity for an IPsec capabilities";
} }
identity ike { identity ike {
base ipsec-capa; base ipsec-capability;
description description
"Identity for an IKE"; "Identity for an IPSec Internet Key Exchange (IKE)
capability";
} }
identity ikeless { identity ikeless {
base ipsec-capa; base ipsec-capability;
description description
"Identity for an IKEless"; "Identity for an IPSec without Internet Key Exchange (IKE)
capability";
} }
/* /*
* Grouping * Grouping
*/ */
grouping nsf-capabilities { grouping nsf-capabilities {
description description
"Capabilities of network security funtion"; "Network Security Funtion (NSF) Capabilities";
reference reference
"RFC 8329: Framework for Interface to Network Security "RFC 8329: Framework for Interface to Network Security
Functions - I2NSF Flow Security Policy Structure Functions - I2NSF Flow Security Policy Structure
draft-ietf-i2nsf-capability-04: Information Model draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Capability Information Model Design"; of NSFs Capabilities - Capability Information Model Design";
leaf-list time-capabilities { leaf-list time-capabilities {
type enumeration { type enumeration {
enum absolute-time { enum absolute-time {
description description
"Capabilities of absolute time. "absolute time capabilities.
If network security function has the absolute time If network security function has the absolute time
capability, the network security function capability, the network security function
supports rule execution according to absolute time."; supports rule execution according to absolute time.";
} }
enum periodic-time { enum periodic-time {
description description
"Capabilities of periodic time. "periodic time capabilities.
If network security function has the periodic time If network security function has the periodic time
capability, the network security function capability, the network security function
supports rule execution according to periodic time."; supports rule execution according to periodic time.";
} }
} }
description description
"This is capabilities for time"; "Time capabilities";
} }
container event-capabilities { container event-capabilities {
description description
"Capabilities of events. "Capabilities of events.
If network security function has If network security function has
the event capabilities, the network security functions the event capabilities, the network security functions
supports rule execution according to system event supports rule execution according to system event
and system alarm."; and system alarm.";
reference reference
"RFC 8329: Framework for Interface to Network Security "RFC 8329: Framework for Interface to Network Security
Functions - I2NSF Flow Security Policy Structure Functions - I2NSF Flow Security Policy Structure
draft-ietf-i2nsf-capability-04: Information Model draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Design Principles and ECA of NSFs Capabilities - Design Principles and ECA
Policy Model Overview Policy Model Overview
draft-hong-i2nsf-nsf-monitoring-data-model-06: A YANG draft-ietf-i2nsf-nsf-monitoring-data-model-01: A YANG
Data Model for Monitoring I2NSF Network Security Data Model for Monitoring I2NSF Network Security
Functions - System Alarm and System Events"; Functions - System Alarm and System Events";
leaf-list system-event-capa { leaf-list system-event-capability {
type identityref { type identityref {
base system-event-capa; base system-event-capability;
} }
description description
"Capabilities for a system event"; "System event capabilities";
} }
leaf-list system-alarm-capa { leaf-list system-alarm-capability {
type identityref { type identityref {
base system-alarm-capa; base system-alarm-capability;
} }
description description
"Capabilities for a system alarm"; "System alarm Capabilities";
} }
} }
container condition-capabilities { container condition-capabilities {
description description
"Capabilities of conditions."; "Conditions capabilities.";
container generic-nsf-capabilities { container generic-nsf-capabilities {
description description
"Capabilities of conditions. "Conditions capabilities.
If a network security function has If a network security function has
the condition capabilities, the network security function the condition capabilities, the network security function
supports rule execution according to conditions of IPv4, supports rule execution according to conditions of IPv4,
IPv6, foruth layer, ICMP, and payload."; IPv6, TCP, UDP, ICMP, and payload.";
reference reference
"RFC 791: Internet Protocol "RFC 791: Internet Protocol
RFC 792: Internet Control Message Protocol RFC 792: Internet Control Message Protocol
RFC 793: Transmission Control Protocol RFC 793: Transmission Control Protocol
RFC 2460: Internet Protocol, Version 6 (IPv6) RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification - Next Header Specification - Next Header
RFC 8329: Framework for Interface to Network Security RFC 8329: Framework for Interface to Network Security
Functions - I2NSF Flow Security Policy Structure Functions - I2NSF Flow Security Policy Structure
draft-ietf-i2nsf-capability-04: Information Model draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Design Principles and ECA Policy of NSFs Capabilities - Design Principles and ECA Policy
Model Overview"; Model Overview";
leaf-list ipv4-capa { leaf-list ipv4-capability {
type identityref { type identityref {
base ipv4-capa; base ipv4-capability;
} }
description description
"Capabilities for an IPv4 packet"; "IPv4 packet capabilities";
reference reference
"RFC 791: Internet Protocol"; "RFC 791: Internet Protocol";
} }
leaf-list ipv6-capa { leaf-list ipv6-capability {
type identityref { type identityref {
base ipv6-capa; base ipv6-capability;
} }
description description
"Capabilities for an IPv6 packet"; "IPv6 packet capabilities";
reference reference
"RFC 2460: Internet Protocol, Version 6 (IPv6) "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification - Next Header"; Specification - Next Header";
} }
leaf-list tcp-capa { leaf-list tcp-capability {
type identityref { type identityref {
base tcp-capa; base tcp-capability;
} }
description description
"Capabilities for a tcp packet"; "TCP packet capabilities";
reference reference
"RFC 793: Transmission Control Protocol"; "RFC 793: Transmission Control Protocol";
} }
leaf-list udp-capa { leaf-list udp-capability {
type identityref { type identityref {
base udp-capa; base udp-capability;
} }
description description
"Capabilities for an udp packet"; "UDP packet capabilities";
reference reference
"RFC 768: User Datagram Protocol"; "RFC 768: User Datagram Protocol";
} }
leaf-list icmp-capa { leaf-list icmp-capability {
type identityref { type identityref {
base icmp-capa; base icmp-capability;
} }
description description
"Capabilities for an ICMP packet"; "ICMP packet capabilities";
reference reference
"RFC 2460: Internet Protocol, Version 6 (IPv6) "; "RFC 8200: Internet Protocol, Version 6 (IPv6)";
} }
} }
container advanced-nsf-capabilities { container advanced-nsf-capabilities {
description description
"Capabilities of advanced network security functions, "Advanced Network Security Function (NSF) capabilities,
such as anti virus, anti DDoS, IPS, and VoIP/VoLTE."; such as anti-virus, anti-DDoS, IPS, and VoIP/VoLTE.";
reference reference
"RFC 8329: Framework for Interface to Network Security "RFC 8329: Framework for Interface to Network Security
Functions - Differences from ACL Data Models Functions - Differences from ACL Data Models
draft-dong-i2nsf-asf-config-01: Configuration of draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller"; Controller";
leaf-list antivirus-capa { leaf-list anti-virus-capability {
type identityref { type identityref {
base antivirus-capa; base anti-virus-capability;
} }
description description
"Capabilities for an antivirus"; "Anti-virus capabilities";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller"; Controller";
} }
leaf-list antiddos-capa { leaf-list anti-ddos-capability {
type identityref { type identityref {
base antiddos-capa; base anti-ddos-capability;
} }
description description
"Capabilities for an antiddos"; "Anti-ddos capabilities";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller"; Controller";
} }
leaf-list ips-capa { leaf-list ips-capability {
type identityref { type identityref {
base ips-capa; base ips-capability;
} }
description description
"Capabilities for an ips"; "Intrusion Prevention System (IPS) capabilities";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller"; Controller";
} }
leaf-list url-capa { leaf-list url-capability {
type identityref { type identityref {
base url-capa; base url-capability;
} }
description description
"Capabilities for a url category"; "URL capabilities";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller"; Controller";
} }
leaf-list voip-volte-capa { leaf-list voip-volte-capability {
type identityref { type identityref {
base voip-volte-capa; base voip-volte-capability;
} }
description description
"Capabilities for a voip and volte"; "VoIP and VoLTE capabilities";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of
Advanced Security Functions with I2NSF Security Advanced Security Functions with I2NSF Security
Controller"; Controller";
} }
} }
leaf-list context-capabilities { leaf-list context-capabilities {
type identityref { type identityref {
base context-capa; base context-capability;
} }
description description
"Capabilities for a context security"; "Security context capabilities";
} }
} }
container action-capabilities { container action-capabilities {
description description
"Capabilities of actions. "Action capabilities.
If network security function has If network security function has
the action capabilities, the network security function the action capabilities, it supports
supports rule execution according to actions."; the attendant actions for policy rules.";
leaf-list ingress-action-capa { leaf-list ingress-action-capability {
type identityref { type identityref {
base ingress-action-capa; base ingress-action-capability;
} }
description description
"Capabilities for an action"; "Ingress-action capabilities";
} }
leaf-list egress-action-capa { leaf-list egress-action-capability {
type identityref { type identityref {
base egress-action-capa; base egress-action-capability;
} }
description description
"Capabilities for an egress action"; "Egress-action capabilities";
} }
leaf-list log-action-capa { leaf-list log-action-capability {
type identityref { type identityref {
base log-action-capa; base log-action-capability;
} }
description description
"Capabilities for a log action"; "Log-action capabilities";
} }
} }
leaf-list resolution-strategy-capabilities { leaf-list resolution-strategy-capabilities {
type identityref { type identityref {
base resolution-strategy-capa; base resolution-strategy-capability;
} }
description description
"Capabilities for a resolution strategy. "Resolution strategy capabilities.
The resolution strategies can be used to The resolution strategies can be used to
specify how to resolve conflicts that occur between specify how to resolve conflicts that occur between
the actions of the same or different policy rules that the actions of the same or different policy rules that
are matched and contained in this particular NSF"; are matched for the smae packet and by particular NSF";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Resolution strategy"; of NSFs Capabilities - Resolution strategy";
} }
leaf-list default-action-capabilities { leaf-list default-action-capabilities {
type identityref { type identityref {
base default-action-capa; base default-action-capability;
} }
description description
"Capabilities for a default action. "Default action capabilities.
A default action is used to execute I2NSF policy rule A default action is used to execute I2NSF policy rules
when no rule matches a packet. The default action is when no rule matches a packet. The default action is
defined as pass, drop, reject, alert, and mirror."; defined as pass, drop, reject, alert, or mirror.";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Default action"; of NSFs Capabilities - Default action";
} }
leaf-list ipsec-method { leaf-list ipsec-method {
type identityref { type identityref {
base ipsec-capa; base ipsec-capability;
} }
description description
"Capabilities for an IPsec method"; "IPsec method capabilities";
reference reference
" draft-ietf-i2nsf-sdn-ipsec-flow-protection-04"; " draft-ietf-i2nsf-sdn-ipsec-flow-protection-04";
} }
} }
/* /*
* Data nodes * Data nodes
*/ */
container nsf { list nsf {
key "nsf-name";
description description
"The list of capabilities of "The list of Network security Function (NSF)
network security function"; capabilities";
uses nsf-capabilities; leaf nsf-name {
type string;
mandatory true;
description
"The name of network security function";
}
} }
} }
<CODE ENDS> <CODE ENDS>
Figure 3: YANG Data Module of I2NSF Capability Figure 3: YANG Data Module of I2NSF Capability
7. IANA Considerations 7. IANA Considerations
This document requests IANA to register the following URI in the This document requests IANA to register the following URI in the
"IETF XML Registry" [RFC3688]: "IETF XML Registry" [RFC3688]:
URI: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability Uri: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
This document requests IANA to register the following YANG module in This document requests IANA to register the following YANG module in
the "YANG Module Names" registry [RFC7950]. the "YANG Module Names" registry [RFC7950].
name: ietf-i2nsf-capability name: ietf-i2nsf-capability
namespace: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability namespace: urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability
prefix: iicapa
prefix: nsfcap
reference: RFC XXXX reference: RFC XXXX
8. Security Considerations 8. Security Considerations
The YANG module specified in this document defines a data schema The YANG module specified in this document defines a data schema
designed to be accessed through network management protocols such as designed to be accessed through network management protocols such as
NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is
the secure transport layer, and the required transport secure the secure transport layer, and the required transport secure
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
is HTTPS, and the required transport secure transport is TLS is HTTPS, and the required transport secure transport is TLS
[RFC8446]. [RFC8446].
The NETCONF access control model [RFC8341] provides a means of The NETCONF access control model [RFC8341] provides a means of
restricting access to specific NETCONF or RESTCONF users to a restricting access to specific NETCONF or RESTCONF users to a
preconfigured subset of all available NETCONF or RESTCONF protocol preconfigured subset of all available NETCONF or RESTCONF protocol
operations and content. operations and content.
There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability:
o ietf-i2nsf-capability: The attacker may provide incorrect
information of the security capability of any target NSF by
illegally modifying this.
Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability:
o ietf-i2nsf-capability: The attacker may gather the security
capability information of any target NSF and misuse the
information for subsequent attacks.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
Network Configuration Protocol (NETCONF)", RFC 6020, A., Peterson, J., Sparks, R., Handley, M., and E.
October 2010. Schooler, "SIP: Session Initiation Protocol", RFC 3261,
DOI 10.17487/RFC3261, June 2002,
<https://www.rfc-editor.org/info/rfc3261>.
[RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, the Network Configuration Protocol (NETCONF)", RFC 6020,
January 2011, <https://www.rfc-editor.org/info/rfc6087>. DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC768] Postel, J., "User Datagram Protocol", RFC 768, August
RFC 6991, DOI 10.17487/RFC6991, July 2013, 1980.
<https://www.rfc-editor.org/info/rfc6991>.
[RFC7950] Bjorklund, M., "The YANG 1.1 Data Modeling Language", [RFC790] Postel, J., "Assigned Numbers", RFC 790, September 1981.
RFC 7950, August 2016.
[RFC791] Postel, J., "Internet Protocol", RFC 791, September 1981.
[RFC792] Postel, J., "Internet Control Message Protocol", RFC 792,
September 1981.
[RFC793] Postel, J., "Transmission Control Protocol", RFC 793,
September 1981.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8192] Hares, S., Lopez, D., Zarny, M., Jacquenet, C., Kumar, R., [RFC8192] Hares, S., Lopez, D., Zarny, M., Jacquenet, C., Kumar, R.,
and J. Jeong, "Interface to Network Security Functions and J. Jeong, "Interface to Network Security Functions
(I2NSF): Problem Statement and Use Cases", RFC 8192, July (I2NSF): Problem Statement and Use Cases", RFC 8192,
2017. DOI 10.17487/RFC8192, July 2017,
<https://www.rfc-editor.org/info/rfc8192>.
[RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", STD 86, RFC 8200,
DOI 10.17487/RFC8200, July 2017,
<https://www.rfc-editor.org/info/rfc8200>.
[RFC8329] Lopez, D., Lopez, E., Dunbar, L., Strassner, J., and R. [RFC8329] Lopez, D., Lopez, E., Dunbar, L., Strassner, J., and R.
Kumar, "Framework for Interface to Network Security Kumar, "Framework for Interface to Network Security
Functions", RFC 8329, February 2018. Functions", RFC 8329, DOI 10.17487/RFC8329, February 2018,
<https://www.rfc-editor.org/info/rfc8329>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341, Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018, DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>. <https://www.rfc-editor.org/info/rfc8341>.
[RFC8431] Wang, L., Chen, M., Dass, A., Ananthakrishnan, H., Kini, [RFC8431] Wang, L., Chen, M., Dass, A., Ananthakrishnan, H., Kini,
S., and N. Bahadur, "A YANG Data Model for Routing S., and N. Bahadur, "A YANG Data Model for the Routing
Information Base (RIB)", RFC RFC8431, September 2018. Information Base (RIB)", RFC 8431, DOI 10.17487/RFC8431,
September 2018, <https://www.rfc-editor.org/info/rfc8431>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
9.2. Informative References 9.2. Informative References
[draft-ietf-i2nsf-sdn-ipsec-flow-protection] [draft-dong-i2nsf-asf-config]
Marin-Lopez, R., Lopez-Millan, G., and F. Pereniguez-
Garcia, "Software-Defined Networking (SDN)-based IPsec
Flow Protection", draft-ietf-i2nsf-sdn-ipsec-flow-
protection-04 (work in progress), March 2019.
[i2nsf-advanced-nsf-dm]
Pan, W. and L. Xia, "Configuration of Advanced Security Pan, W. and L. Xia, "Configuration of Advanced Security
Functions with I2NSF Security Controller", draft-dong- Functions with I2NSF Security Controller", draft-dong-
i2nsf-asf-config-01 (work in progress), October 2018. i2nsf-asf-config-01 (work in progress), October 2018.
[i2nsf-nsf-cap-im] [draft-ietf-i2nsf-capability]
Xia, L., Strassner, J., Basile, C., and D. Lopez, Xia, L., Strassner, J., Basile, C., and D. Lopez,
"Information Model of NSFs Capabilities", draft-ietf- "Information Model of NSFs Capabilities", draft-ietf-
i2nsf-capability-04 (work in progress), October 2018. i2nsf-capability-05 (work in progress), April 2019.
[i2nsf-nsf-yang] [draft-ietf-i2nsf-nsf-facing-interface-dm]
Kim, J., Jeong, J., Park, J., Hares, S., and Q. Lin, Kim, J., Jeong, J., Park, J., Hares, S., and Q. Lin,
"I2NSF Network Security Function-Facing Interface YANG "I2NSF Network Security Function-Facing Interface YANG
Data Model", draft-ietf-i2nsf-nsf-facing-interface-dm-04 Data Model", draft-ietf-i2nsf-nsf-facing-interface-dm-07
(work in progress), March 2019. (work in progress), July 2019.
[i2nsf-terminology] [draft-ietf-i2nsf-nsf-monitoring-data-model]
Jeong, J., Chung, C., Hares, S., Xia, L., and H. Birkholz,
"I2NSF NSF Monitoring YANG Data Model", draft-ietf-i2nsf-
nsf-monitoring-data-model-01 (work in progress), July
2019.
[draft-ietf-i2nsf-sdn-ipsec-flow-protection]
Marin-Lopez, R., Lopez-Millan, G., and F. Pereniguez-
Garcia, "Software-Defined Networking (SDN)-based IPsec
Flow Protection", draft-ietf-i2nsf-sdn-ipsec-flow-
protection-05 (work in progress), July 2019.
[draft-ietf-i2nsf-terminology]
Hares, S., Strassner, J., Lopez, D., Xia, L., and H. Hares, S., Strassner, J., Lopez, D., Xia, L., and H.
Birkholz, "Interface to Network Security Functions (I2NSF) Birkholz, "Interface to Network Security Functions (I2NSF)
Terminology", draft-ietf-i2nsf-terminology-07 (work in Terminology", draft-ietf-i2nsf-terminology-08 (work in
progress), January 2019. progress), July 2019.
[supa-policy-info-model] [draft-ietf-supa-generic-policy-info-model]
Strassner, J., Halpern, J., and S. Meer, "Generic Policy Strassner, J., Halpern, J., and S. Meer, "Generic Policy
Information Model for Simplified Use of Policy Information Model for Simplified Use of Policy
Abstractions (SUPA)", draft-ietf-supa-generic-policy-info- Abstractions (SUPA)", draft-ietf-supa-generic-policy-info-
model-03 (work in progress), May 2017. model-03 (work in progress), May 2017.
Appendix A. Changes from draft-ietf-i2nsf-capability-data-model-03 Appendix A. Configuration Examples
The following changes are made from draft-ietf-i2nsf-capability-data- This section shows configuration examples of "ietf-i2nsf-capability"
model-03: module for capabilities registration of general firewall.
o We added a leaf-list for IPsec method capabilities (e.g., ike and A.1. Example 1: Registration for Capabilities of General Firewall
ikeless).
o We changed http capa fields to url category capa fields. This section shows a configuration example for capabilities
registration of general firewall.
o We added context capa fields (e.g., acl number, application, <nsf xmlns="urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability">
target, users, group, and geography). <nsf-name>general_firewall</nsf-name>
<condition-capabilities>
<generic-nsf-capabilities>
<ipv4-capability>ipv4-protocol</ipv4-capability>
<ipv4-capability>exact-ipv4-address</ipv4-capability>
<ipv4-capability>range-ipv4-address</ipv4-capability>
<tcp-capability>exact-fourth-layer-port-num</tcp-capability>
<tcp-capability>range-fourth-layer-port-num</tcp-capability>
</generic-nsf-capabilities>
</condition-capabilities>
<action-capabilities>
<ingress-action-capability>pass</ingress-action-capability>
<ingress-action-capability>drop</ingress-action-capability>
<ingress-action-capability>alert</ingress-action-capability>
<egress-action-capability>pass</egress-action-capability>
<egress-action-capability>drop</egress-action-capability>
<egress-action-capability>alert</egress-action-capability>
</action-capabilities>
</nsf>
Appendix B. Acknowledgments Figure 4: Configuration XML for Capabilities Registration of General
Firewall
This work was supported by Institute for Information & communications Figure 4 shows the configuration XML for capabilities registration of
Technology Promotion (IITP) grant funded by the Korea government general firewall and its capabilities are as follows.
(MSIP) (No.R-20160222-002755, Cloud based Security Intelligence
Technology Development for the Customized Security Service
Provisioning).
Appendix C. Contributors 1. The name of the NSF is general_firewall.
2. The NSF can inspect protocol, exact IPv4 address, and range IPv4
address for IPv4 packets.
3. The NSF can inspect exact port number and range port number for
fourth layer packets.
4. The NSF can control whether the packets are allowed to pass,
drop, or alert.
A.2. Example 2: Registration for Capabilities of Time based Firewall
This section shows a configuration example for capabilities
registration of time based firewall.
<nsf xmlns="urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability">
<nsf-name>time_based_firewall</nsf-name>
<time-capabilities>absolute-time</time-capabilities>
<time-capabilities>periodic-time</time-capabilities>
<condition-capabilities>
<generic-nsf-capabilities>
<ipv4-capability>ipv4-protocol</ipv4-capability>
<ipv4-capability>exact-ipv4-address</ipv4-capability>
<ipv4-capability>range-ipv4-address</ipv4-capability>
</generic-nsf-capabilities>
</condition-capabilities>
<action-capabilities>
<ingress-action-capability>pass</ingress-action-capability>
<ingress-action-capability>drop</ingress-action-capability>
<ingress-action-capability>alert</ingress-action-capability>
<egress-action-capability>pass</egress-action-capability>
<egress-action-capability>drop</egress-action-capability>
<egress-action-capability>alert</egress-action-capability>
</action-capabilities>
</nsf>
Figure 5: Configuration XML for Capabilities Registration of Time
based Firewall
Figure 5 shows the configuration XML for capabilities registration of
time based firewall and its capabilities are as follows.
1. The name of the NSF is time_based_firewall.
2. The NSF can execute the security policy rule according to
absolute time and periodic time.
3. The NSF can inspect protocol, exact IPv4 address, and range IPv4
address for IPv4 packets.
4. The NSF can control whether the packets are allowed to pass,
drop, or alert.
A.3. Example 3: Registration for Capabilities of Web Filter
This section shows a configuration example for capabilities
registration of web filter.
<nsf xmlns="urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability">
<nsf-name>web_filter</nsf-name>
<condition-capabilities>
<advanced-nsf-capabilities>
<url-capability>user-defined</url-capability>
</advanced-nsf-capabilities>
</condition-capabilities>
<action-capabilities>
<ingress-action-capability>pass</ingress-action-capability>
<ingress-action-capability>drop</ingress-action-capability>
<ingress-action-capability>alert</ingress-action-capability>
<egress-action-capability>pass</egress-action-capability>
<egress-action-capability>drop</egress-action-capability>
<egress-action-capability>alert</egress-action-capability>
</action-capabilities>
</nsf>
Figure 6: Configuration XML for Capabilities Registration of Web
Filter
Figure 6 shows the configuration XML for capabilities registration of
web filter and its capabilities are as follows.
1. The name of the NSF is web_filter.
2. The NSF can inspect url for http and https packets.
3. The NSF can control whether the packets are allowed to pass,
drop, or alert.
A.4. Example 4: Registration for Capabilities of VoIP/VoLTE Filter
This section shows a configuration example for capabilities
registration of VoIP/VoLTE filter.
<nsf xmlns="urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability">
<nsf-name>voip_volte_filter</nsf-name>
<condition-capabilities>
<advanced-nsf-capabilities>
<voip-volte-capability>voice-id</voip-volte-capability>
</advanced-nsf-capabilities>
</condition-capabilities>
<action-capabilities>
<ingress-action-capability>pass</ingress-action-capability>
<ingress-action-capability>drop</ingress-action-capability>
<ingress-action-capability>alert</ingress-action-capability>
<egress-action-capability>pass</egress-action-capability>
<egress-action-capability>drop</egress-action-capability>
<egress-action-capability>alert</egress-action-capability>
</action-capabilities>
</nsf>
Figure 7: Configuration XML for Capabilities Registration of VoIP/
VoLTE Filter
Figure 7 shows the configuration XML for capabilities registration of
VoIP/VoLTE filter and its capabilities are as follows.
1. The name of the NSF is voip_volte_filter.
2. The NSF can inspect voice id for VoIP/VoLTE packets.
3. The NSF can control whether the packets are allowed to pass,
drop, or alert.
A.5. Example 5: Registration for Capabilities of HTTP and HTTPS Flood
Mitigation
This section shows a configuration example for capabilities
registration of http and https flood mitigation.
<nsf xmlns="urn:ietf:params:xml:ns:yang:ietf-i2nsf-capability">
<nsf-name>http_and_https_flood_mitigation</nsf-name>
<condition-capabilities>
<advanced-nsf-capabilities>
<anti-ddos-capability>http-flood-action</anti-ddos-capability>
<anti-ddos-capability>https-flood-action</anti-ddos-capability>
</advanced-nsf-capabilities>
</condition-capabilities>
<action-capabilities>
<ingress-action-capability>pass</ingress-action-capability>
<ingress-action-capability>drop</ingress-action-capability>
<ingress-action-capability>alert</ingress-action-capability>
<egress-action-capability>pass</egress-action-capability>
<egress-action-capability>drop</egress-action-capability>
<egress-action-capability>alert</egress-action-capability>
</action-capabilities>
</nsf>
Figure 8: Configuration XML for Capabilities Registration of HTTP and
HTTPS Flood Mitigation
Figure 8 shows the configuration XML for capabilities registration of
http and https flood mitigation and its capabilities are as follows.
1. The name of the NSF is http_and_https_flood_mitigation.
2. The location of the NSF is 221.159.112.140.
3. The NSF can control the amount of packets for http and https
packets.
4. The NSF can control whether the packets are allowed to pass,
drop, or alert.
Appendix B. Changes from draft-ietf-i2nsf-capability-data-model-04
The following changes are made from draft-ietf-i2nsf-capability-data-
model-04:
o The version is revised according to the comments from Acee Lindem
and Carl Moberg who are YANG doctors for review.
Appendix C. Acknowledgments
This work was supported by Institute of Information & Communications
Technology Planning & Evaluation (IITP) grant funded by the Korea
MSIT (Ministry of Science and ICT) (R-20160222-002755, Cloud based
Security Intelligence Technology Development for the Customized
Security Service Provisioning).
Appendix D. Contributors
This document is made by the group effort of I2NSF working group. This document is made by the group effort of I2NSF working group.
Many people actively contributed to this document. The following are Many people actively contributed to this document. The following are
considered co-authors: considered co-authors:
o Hyoungshick Kim (Sungkyunkwan University) o Hyoungshick Kim (Sungkyunkwan University)
o Daeyoung Hyun (Sungkyunkwan University) o Daeyoung Hyun (Sungkyunkwan University)
o Dongjin Hong (Sungkyunkwan University) o Dongjin Hong (Sungkyunkwan University)
skipping to change at page 43, line 14 skipping to change at page 48, line 39
Susan Hares Susan Hares
Huawei Huawei
7453 Hickory Hill 7453 Hickory Hill
Saline, MI 48176 Saline, MI 48176
USA USA
Phone: +1-734-604-0332 Phone: +1-734-604-0332
EMail: shares@ndzh.com EMail: shares@ndzh.com
Jaehoon Paul Jeong Jaehoon Paul Jeong
Department of Software Department of Computer Science and Engineering
Sungkyunkwan University Sungkyunkwan University
2066 Seobu-Ro, Jangan-Gu 2066 Seobu-Ro, Jangan-Gu
Suwon, Gyeonggi-Do 16419 Suwon, Gyeonggi-Do 16419
Republic of Korea Republic of Korea
Phone: +82 31 299 4957 Phone: +82 31 299 4957
Fax: +82 31 290 7996 Fax: +82 31 290 7996
EMail: pauljeong@skku.edu EMail: pauljeong@skku.edu
URI: http://iotlab.skku.edu/people-jaehoon-jeong.php URI: http://iotlab.skku.edu/people-jaehoon-jeong.php
Jinyong Tim Kim Jinyong Tim Kim
Department of Computer Engineering Department of Electronic, Electrical and Computer Engineering
Sungkyunkwan University Sungkyunkwan University
2066 Seobu-Ro, Jangan-Gu 2066 Seobu-Ro, Jangan-Gu
Suwon, Gyeonggi-Do 16419 Suwon, Gyeonggi-Do 16419
Republic of Korea Republic of Korea
Phone: +82 10 8273 0930 Phone: +82 10 8273 0930
EMail: timkim@skku.edu EMail: timkim@skku.edu
Robert Moskowitz Robert Moskowitz
HTT Consulting HTT Consulting
 End of changes. 427 change blocks. 
684 lines changed or deleted 916 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/