draft-ietf-i2nsf-capability-data-model-05.txt   draft-ietf-i2nsf-capability-data-model-06.txt 
I2NSF Working Group S. Hares I2NSF Working Group S. Hares, Ed.
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track J. Jeong Intended status: Standards Track J. Jeong, Ed.
Expires: January 26, 2020 J. Kim Expires: January 14, 2021 J. Kim
Sungkyunkwan University Sungkyunkwan University
R. Moskowitz R. Moskowitz
HTT Consulting HTT Consulting
Q. Lin Q. Lin
Huawei Huawei
July 25, 2019 July 13, 2020
I2NSF Capability YANG Data Model I2NSF Capability YANG Data Model
draft-ietf-i2nsf-capability-data-model-05 draft-ietf-i2nsf-capability-data-model-06
Abstract Abstract
This document defines a YANG data model for the capabilities of This document defines a YANG data model for the capabilities of
various Network Security Functions (NSFs) in the Interface to Network various Network Security Functions (NSFs) in the Interface to Network
Security Functions (I2NSF) framework to centrally manage the Security Functions (I2NSF) framework to centrally manage the
capabilities of the various NSFs. capabilities of the various NSFs.
Status of This Memo Status of This Memo
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 January 26, 2020. This Internet-Draft will expire on January 14, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 21 skipping to change at page 2, line 21
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. Network Security Function (NSF) Capabilities . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . 39
8. Security Considerations . . . . . . . . . . . . . . . . . . . 38 8. Security Considerations . . . . . . . . . . . . . . . . . . . 39
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 39 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 40
9.1. Normative References . . . . . . . . . . . . . . . . . . 39 9.1. Normative References . . . . . . . . . . . . . . . . . . 40
9.2. Informative References . . . . . . . . . . . . . . . . . 41 9.2. Informative References . . . . . . . . . . . . . . . . . 43
Appendix A. Configuration Examples . . . . . . . . . . . . . . . 43 Appendix A. Configuration Examples . . . . . . . . . . . . . . . 44
A.1. Example 1: Registration for Capabilities of General A.1. Example 1: Registration for Capabilities of General
Firewall . . . . . . . . . . . . . . . . . . . . . . . . 43
A.2. Example 2: Registration for Capabilities of Time based
Firewall . . . . . . . . . . . . . . . . . . . . . . . . 44 Firewall . . . . . . . . . . . . . . . . . . . . . . . . 44
A.3. Example 3: Registration for Capabilities of Web Filter . 45 A.2. Example 2: Registration for Capabilities of Time based
Firewall . . . . . . . . . . . . . . . . . . . . . . . . 45
A.3. Example 3: Registration for Capabilities of Web Filter . 46
A.4. Example 4: Registration for Capabilities of VoIP/VoLTE A.4. Example 4: Registration for Capabilities of VoIP/VoLTE
Filter . . . . . . . . . . . . . . . . . . . . . . . . . 45 Filter . . . . . . . . . . . . . . . . . . . . . . . . . 46
A.5. Example 5: Registration for Capabilities of HTTP and A.5. Example 5: Registration for Capabilities of HTTP and
HTTPS Flood Mitigation . . . . . . . . . . . . . . . . . 46 HTTPS Flood Mitigation . . . . . . . . . . . . . . . . . 47
Appendix B. Changes from draft-ietf-i2nsf-capability-data- Appendix B. Changes from draft-ietf-i2nsf-capability-data-
model-04 . . . . . . . . . . . . . . . . . . . . . . 47 model-05 . . . . . . . . . . . . . . . . . . . . . . 48
Appendix C. Acknowledgments . . . . . . . . . . . . . . . . . . 47 Appendix C. Acknowledgments . . . . . . . . . . . . . . . . . . 48
Appendix D. Contributors . . . . . . . . . . . . . . . . . . . . 48 Appendix D. Contributors . . . . . . . . . . . . . . . . . . . . 49
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 48 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 49
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 described in smartphones), service providers have a lot of problems described in
[RFC8192]. To resolve these problems, [draft-ietf-i2nsf-capability] [RFC8192]. To resolve these problems, [draft-ietf-i2nsf-capability]
specifies the information model of the capabilities of Network specifies the information model of the capabilities of Network
Security Functions (NSFs). Security Functions (NSFs).
This document provides a YANG data model [RFC6020][RFC7950] that This document provides a YANG data model [RFC6020][RFC7950] that
defines the capabilities of NSFs to centrally manage the capabilities defines the capabilities of NSFs to centrally manage the capabilities
of those security devices. The security devices can register their of those security devices. The security devices can register their
own capabilities into a Network Operator Management (Mgmt) System own capabilities into a Network Operator Management (Mgmt) System
(i.e., Security Controller) with this YANG data model through the (i.e., Security Controller) with this YANG data model through the
registration interface [RFC8329]. With the capabilities of those registration interface [RFC8329]. With the capabilities of those
security devices maintained centrally, those security devices can be security devices maintained centrally, those security devices can be
easily managed [RFC8329]. This YANG data model is based on the more easily managed [RFC8329]. This YANG data model is based on the
information model for I2NSF NSF capabilities information model for I2NSF NSF capabilities
[draft-ietf-i2nsf-capability]. [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 as model that is used as the basis for the design of I2NSF Policy as
described in [RFC8329] and [draft-ietf-i2nsf-capability].. The described in [RFC8329] and [draft-ietf-i2nsf-capability]. The "ietf-
"ietf-i2nsf-capability" YANG module defined in this document provides i2nsf-capability" YANG module defined in this document provides the
the following features: 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
functions. functions.
o Definition for condition capabilities of generic network security o Definition for condition capabilities of generic network security
functions. functions.
o Definition for condition capabilities of advanced network security o Definition for condition capabilities of advanced network security
skipping to change at page 3, line 51 skipping to change at page 3, line 51
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
[draft-ietf-i2nsf-terminology][draft-ietf-i2nsf-capability] [draft-ietf-i2nsf-capability][RFC8431]. Especially, the following
[RFC8431][draft-ietf-supa-generic-policy-info-model]. Especially, terms are from [RFC3444]:
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.
skipping to change at page 4, line 27 skipping to change at page 4, line 25
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 is this document. The meaning of the symbols in these diagrams is
referred from [RFC8340]. referred from [RFC8340].
4. Overview 4. Overview
This section provides as overview of how the YANG data model can be This section provides as overview of how the YANG data model can be
used in the I2NSF framework described in [RFC8329]. Figure 1 shows used in the I2NSF framework described in [RFC8329]. Figure 1 shows
the capabilities of NSFs in I2NSF Framework. As shown in this the capabilities (e.g., firewall and web filter) of NSFs in the I2NSF
figure, an NSF Developer's Mgmt System can register NSFs and the Framework. As shown in this figure, an NSF Developer's Management
capabilities that the network security device can support. To System can register NSFs and the capabilities that the network
register NSFs in this way, the Developer's Mgmt System utilizes this security device can support. To register NSFs in this way, the
standardized capabilities YANG data model through its registration Developer's Management System utilizes this standardized capability
interface. With the capabilities of those network security devices YANG data model through the I2NSF Registration Interface
maintained centrally, those security devices can be easily managed, [draft-ietf-i2nsf-registration-interface-dm]. That is, this
which can resolve many of the problems described in [RFC8192]. The Registration Interface uses the YANG module described in this
use cases are described below. document to describe the capability of a network security function
that is registered with the Security Controller. With the
capabilities of those network security devices maintained centrally,
those security devices can be more easily managed, which can resolve
many of the problems described in [RFC8192].
In Figure 1, a new NSF at a Developer's Management Systems has
capabilities of Firewall (FW) and Web Filter (WF), which are denoted
as (Cap = {FW, WF}), to support Event-Condition-Action (ECA) policy
rules where 'E', 'C', and 'A' mean "Event", "Condition", and
"Action", respectively. The condition involves IPv4 or IPv6
datagrams, and the action includes "Allow" and "Deny" for those
datagrams.
Note that the NSF-Facing Interface is used to configure the security Note that the NSF-Facing Interface is used to configure the security
policy rules of the generic network security functions policy rules of the generic network security functions
[draft-ietf-i2nsf-nsf-facing-interface-dm], and the NSF Monitoring [draft-ietf-i2nsf-nsf-facing-interface-dm], and The configuration of
Interface is used to configure the security policy rules of advanced advanced security functions over the NSF-Facing Interface is used to
network security functions [draft-dong-i2nsf-asf-config], configure the security policy rules of advanced network security
respectively, according to the capabilities of NSFs registered with functions (e.g., anti-virus and anti-DDoS attack)
the I2NSF Framework.
+-------------------------------------------------------+ [draft-dong-i2nsf-asf-config], respectively, according to the
| I2NSF User (e.g., Overlay Network Mgmt, Enterprise | capabilities of NSFs registered with the I2NSF Framework.
| Network Mgmt, another network domain's mgmt, etc.) |
+--------------------+----------------------------------+ +------------------------------------------------------+
| | I2NSF User (e.g., Overlay Network Mgmt, Enterprise |
| Network Mgmt, another network domain's mgmt, etc.) |
+--------------------+---------------------------------+
I2NSF ^
Consumer-Facing Interface | Consumer-Facing Interface |
| |
| v 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 = {} | Cap = {FW, WF}
NSF-Facing Interface | C = {IPv4, IPv6} I2NSF | E = {}
| A = {Allow, Deny} NSF-Facing Interface | C = {IPv4, IPv6}
| | A = {Allow, Deny}
v
+---------------+----+------------+-----------------+ +---------------+----+------------+-----------------+
| | | | | | | |
+---+---+ +---+---+ +---+---+ +---+---+ +---+---+ +---+---+ +---+---+ +---+---+
| 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
Cap = {FW, WF} Cap = {FW, WF} Cap = {FW, WF} Cap = {FW, WF}
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's Mgmt System A Developer's 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
A use case of an NSF with the capabilities of firewall and web filter
is described as follows.
o If a network manager wants to apply security policy rules to block o If a network manager wants to apply security policy rules to block
malicious users, it is a tremendous burden to apply all of the malicious users with firewall and web filter, it is a tremendous
needed rules to NSFs one-by-one. This problem can be resolved by burden for a network administrator to apply all of the needed
managing the capabilities of NSFs. If network manager wants to rules to NSFs one by one. This problem can be resolved by
block malicious users with IPv6, the network manager sends the managing the capabilities of NSFs in this document.
security policy rules to block the users to the Network Operator
Mgmt System using I2NSF user (i.e., a web browser or a software).
When the Network Operator Mgmt System receives the security policy
rules, it automatically sends that security policy rules to
appropriate NSFs (i.e., NSF-m in Developer's Mgmt System A and
NSF-1 in Developer's Mgmt System B) which can support the
capabilities (i.e., IPv6). Therefore, an I2NSF User need not
consider NSFs where to which NSFs the rules apply.
o If NSFs encounter the malicious packets, it is a tremendous burden o If a network administrator wants to block malicious users for IPv6
for the network manager to apply the rule to block the malicious traffic, he sends a security policy rule to block the users to the
packets to NSFs one-by-one. This problem can be resolved by Network Operator Management System using the I2NSF User (i.e., web
managing the capabilities of NSFs. If NSFs encounter the application).
suspicious IPv4 packets, they can ask the Network Operator Mgmt
System for information about the suspicious IPv4 packets in order o When the Network Operator Management System receives the security
to alter specific rules and/or configurations. When the Network policy rule, it automatically sends that security policy rules to
Operator Mgmt System receives information, it inspects the appropriate NSFs (i.e., NSF-m in Developer's Management System A
information about the suspiciou IPv4 packets. If the suspicious and NSF-1 in Developer's Management System B) which can support
packets are determined to be malicious packets, the Network the capabilities (i.e., IPv6). This lets an I2NSF User not
Operator Mgmt System creates and sends the security policy rules consider NSFs where the rule is applied.
blocking malicious packets to appropriate NSFs (i.e., NSF-1 in
Developer's Mgmt System A and NSF-1 and NSF-n in Developer's Mgmt o If NSFs encounter the suspicious IPv6 packets of malicious users,
System B) which can support the capabilities (i.e., IPv4). they can filter the packets out according to the configured
Therefore, the new security policy rules blocking malicious security policy rule. Therefore, the security policy rule against
packets can be applied to appropriate NSFs without humans the malicious users' packets can be automatically applied to
intervention. appropriate NSFs without human intervention.
5. YANG Tree Diagram 5. YANG Tree Diagram
This section shows an YANG tree diagram of capabilities for network This section shows a YANG tree diagram of capabilities of network
security functions, as defined in the [draft-ietf-i2nsf-capability]. security functions, as defined in the [draft-ietf-i2nsf-capability].
5.1. Network Security Function (NSF) Capabilities 5.1. Network Security Function (NSF) Capabilities
This section shows YANG tree diagram for NSF capabilities. This section explains a YANG tree diagram of NSF capabilities and its
features. Figure 2 shows a YANG tree diagram of NSF capabilities.
The NSF capabilities in the tree include time capabilities, event
capabilities, condition capabilities, action capabilities, resolution
strategy capabilities, and default action capabilities. Those
capabilities can be tailored or extended according to a vendor's
specific requirements. Refer to the NSF capabilities information
model for detailed discussion [draft-ietf-i2nsf-capability].
module: ietf-i2nsf-capability module: ietf-i2nsf-capability
+--rw nsf* [nsf-name] +--rw nsf* [nsf-name]
+--rw nsf-name string +--rw nsf-name string
+--rw time-capabilities* enumeration +--rw time-capabilities* enumeration
+--rw event-capabilities +--rw event-capabilities
| +--rw system-event-capability* identityref | +--rw system-event-capability* identityref
| +--rw system-alarm-capability* identityref | +--rw system-alarm-capability* identityref
+--rw condition-capabilities +--rw condition-capabilities
| +--rw generic-nsf-capabilities | +--rw generic-nsf-capabilities
| | +--rw ipv4-capability* identityref | | +--rw ipv4-capability* identityref
| | +--rw icmp-capability* identityref
| | +--rw ipv6-capability* identityref | | +--rw ipv6-capability* identityref
| | +--rw icmpv6-capability* identityref
| | +--rw tcp-capability* identityref | | +--rw tcp-capability* identityref
| | +--rw udp-capability* identityref | | +--rw udp-capability* identityref
| | +--rw icmp-capability* identityref
| +--rw advanced-nsf-capabilities | +--rw advanced-nsf-capabilities
| | +--rw anti-virus-capability* identityref | | +--rw anti-virus-capability* identityref
| | +--rw anti-ddos-capability* identityref | | +--rw anti-ddos-capability* identityref
| | +--rw ips-capability* identityref | | +--rw ips-capability* identityref
| | +--rw url-capability* identityref | | +--rw url-capability* identityref
| | +--rw voip-volte-capability* identityref | | +--rw voip-volte-capability* identityref
| +--rw context-capabilities* identityref | +--rw context-capabilities* identityref
+--rw action-capabilities +--rw action-capabilities
| +--rw ingress-action-capability* identityref | +--rw ingress-action-capability* identityref
| +--rw egress-action-capability* identityref | +--rw egress-action-capability* identityref
| +--rw log-action-capability* 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 of Capabilities of Network Security
Functions Functions
This YANG tree diagram shows NSF capabilities. Time capabilities are used to specify the capabilities which describe
The model includes NSF capabilities. The NSF capabilities include
time capabilities, event capabilities, condition capabilities, action
capabilities, resolution strategy capabilities, and default action
capabilities.
Time capabilities are used to specify the capabilities to specify
when to execute the I2NSF policy rule. The time capabilities are when to execute the I2NSF policy rule. The time capabilities are
defined in terms of absolute time and periodic time. The absolute defined in terms of absolute time and periodic time. The absolute
time means the exact time to start or end. The periodic time means time means the exact time to start or end. The periodic time means
repeated time like day, week, or month. repeated time like day, week, or month. See Section 3.4.6
(Capability Algebra) in [draft-ietf-i2nsf-capability] for more
information about the time-based condition (e.g., time period) in the
capability algebra.
Event capabilities are used to specify capabilities how to trigger Event capabilities are used to specify the capabilities that describe
the evaluation of the condition clause of the I2NSF Policy Rule. The the event that would trigger the evaluation of the condition clause
defined event capabilities are defined as system event and system of the I2NSF Policy Rule. The defined event capabilities are system
alarm. The event capability can be extended according to specific event and system alarm. See Section 3.1 (Design Principles and ECA
vendor condition features. The event capability is described in Policy Model Overview) in [draft-ietf-i2nsf-capability] for more
detail in [draft-ietf-i2nsf-capability]. information about the event in the ECA policy model.
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. The condition capabilities are I2NSF policy rule can be executed. The condition capabilities are
classified in terms of generic network security functions and classified in terms of generic network security functions and
advanced network security functions. The condition capabilities of advanced network security functions. The condition capabilities of
generic network security functions are defined as IPv4 capability, generic network security functions are defined as IPv4 capability,
IPv6 capability, TCP capability, UDP capability, and ICMP capability. IPv6 capability, TCP capability, UDP capability, and ICMP capability.
The condition capabilities of advanced network security functions are The condition capabilities of advanced network security functions are
defined as anti-virus capability, anti-ddos capability, IPS defined as anti-virus capability, anti-DDoS capability, IPS
capability, HTTP capability, and VoIP/VoLTE capability. The capability, HTTP capability, and VoIP/VoLTE capability. See
condition capability can be extended according to specific vendor Section 3.1 (Design Principles and ECA Policy Model Overview) in
condition features. The condition capability is described in detail [draft-ietf-i2nsf-capability] for more information about the
in [draft-ietf-i2nsf-capability]. condition in the ECA policy model. Also, see Section 3.4.3 (I2NSF
Condition Clause Operator Types) in [draft-ietf-i2nsf-capability] for
more information about the operator types in an I2NSF condition
clause.
Action capabilities are used to specify capabilities of how to Action capabilities are used to specify the capabilities that
control and monitor aspects of flow-based NSFs when the event and describe the control and monitoring aspects of flow-based NSFs when
condition clauses are satisfied. The action capabilities are defined the event and condition clauses are satisfied. The action
as ingress-action capability, egress-action capability, and log- capabilities are defined as ingress-action capability, egress-action
action capability. The action capability can be extended according capability, and log-action capability. See Section 3.1 (Design
to specific vendor action features. The action capability is Principles and ECA Policy Model Overview) in
described in detail in [draft-ietf-i2nsf-capability]. [draft-ietf-i2nsf-capability] for more information about the action
in the ECA policy model. Also, see Section 7.2 (NSF-Facing Flow
Security Policy Structure) in [RFC8329] for more information about
the ingress and egress actions. In addition, see Section 9.1 (Flow-
Based NSF Capability Characterization) for more information about
logging at NSFs.
Resolution strategy capabilities are used to specify capabilities of Resolution strategy capabilities are used to specify the capabilities
how to resolve conflicts that occur between the actions of the same that describe conflicts that occur between the actions of the same or
or different policy rules that are matched and contained in this 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), Prioritized Matching Rule with Errors (PMRE), Matching Rule (PMR), Prioritized Matching Rule with Errors (PMRE),
and Prioritized Matching Rule with No Errors (PMRN). The resolution and Prioritized Matching Rule with No Errors (PMRN). See
strategy capabilities can be extended according to specific vendor Section 3.4.2 (Conflict, Resolution Strategy and Default Action) in
action features. The resolution strategy capability is described in [draft-ietf-i2nsf-capability] for more information about the
detail in [draft-ietf-i2nsf-capability]. resolution strategy.
Default action capabilities are used to specify capabilities of how Default action capabilities are used to specify the capabilities that
to execute I2NSF policy rules when no rule matches a packet. The describe how to execute I2NSF policy rules when no rule matches a
default action capabilities are defined as pass, drop, reject, alert, packet. The default action capabilities are defined as pass, drop,
and mirror. The default action capability can be extended according alert, and mirror. See Section 3.4.2 (Conflict, Resolution Strategy
to specific vendor action features. The default action capability is and Default Action) in [draft-ietf-i2nsf-capability] for more
described in detail in [draft-ietf-i2nsf-capability]. information about the default action.
IPsec method capabilities are used to specify capabilities of how to IPsec method capabilities are used to specify capabilities of how to
support an Internet Key Exchange (IKE) for the security support an Internet Key Exchange (IKE) for the security
communication. The default action capabilities are defined as IKE communication. The default action capabilities are defined as IKE or
and IKE-less. The default action capability can be extended IKE-less. See [draft-ietf-i2nsf-sdn-ipsec-flow-protection] for more
according to specific vendor action features. The default action information about the SDN-based IPsec flow protection in I2NSF.
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 a YANG data module for network security This section introduces a YANG data module for network security
functions capabilities, as defined in the functions capabilities, as defined in the
[draft-ietf-i2nsf-capability]. [draft-ietf-i2nsf-capability].
<CODE BEGINS> file "ietf-i2nsf-capability@2019-07-24.yang" <CODE BEGINS> file "ietf-i2nsf-capability@2020-07-13.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
nsfcap; nsfcap;
organization organization
"IETF I2NSF (Interface to Network Security Functions) "IETF I2NSF (Interface to Network Security Functions)
skipping to change at page 9, line 49 skipping to change at page 10, line 4
<mailto:ldunbar@futurewei.com> <mailto:ldunbar@futurewei.com>
WG Chair: Yoav Nir WG Chair: Yoav Nir
<mailto:ynir.ietf@gmail.com> <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>";
description description
"This module describes a capability model "This module describes a capability model for I2NSF devices.
for I2NSF devices.
Copyright (c) 2018 IETF Trust and the persons Copyright (c) 2020 IETF Trust and the persons identified as
identified as authors of the code. All rights reserved. authors of the code. All rights reserved.
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-07-24"{ revision "2020-07-13"{
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 I2NSF policy events."; "Base identity for I2NSF policy events.";
reference reference
"draft-ietf-i2nsf-nsf-monitoring-data-model-01 "draft-ietf-i2nsf-nsf-monitoring-data-model-03
- Event"; - Event";
} }
identity system-event-capability { identity system-event-capability {
base event; base event;
description description
"Identity for system events"; "Identity for system events";
reference reference
"draft-ietf-i2nsf-nsf-monitoring-data-model-01 "draft-ietf-i2nsf-nsf-monitoring-data-model-03
- System alarm"; - System alarm";
} }
identity system-alarm-capability { identity system-alarm-capability {
base event; base event;
description description
"Identity for system alarms"; "Identity for system alarms";
reference reference
"draft-ietf-i2nsf-nsf-monitoring-data-model-01 "draft-ietf-i2nsf-nsf-monitoring-data-model-03
- System alarm"; - System alarm";
} }
identity access-violation { identity access-violation {
base system-event-capability; base system-event-capability;
description description
"Identity for access violation events"; "Identity for access violation events";
reference reference
"draft-ietf-i2nsf-nsf-monitoring-data-model-01 "draft-ietf-i2nsf-nsf-monitoring-data-model-03
- System event"; - System event";
} }
identity configuration-change { identity configuration-change {
base system-event-capability; base system-event-capability;
description description
"Identity for configuration change events"; "Identity for configuration change events";
reference reference
"draft-ietf-i2nsf-nsf-monitoring-data-model-01 "draft-ietf-i2nsf-nsf-monitoring-data-model-03
- System event"; - System event";
} }
identity memory-alarm { identity memory-alarm {
base system-alarm-capability; base system-alarm-capability;
description description
"Identity for memory alarm events"; "Identity for memory alarm events";
reference reference
"draft-ietf-i2nsf-nsf-monitoring-data-model-01 "draft-ietf-i2nsf-nsf-monitoring-data-model-03
- System alarm"; - System alarm";
} }
identity cpu-alarm { identity cpu-alarm {
base system-alarm-capability; base system-alarm-capability;
description description
"Identity for CPU alarm events"; "Identity for CPU alarm events";
reference reference
"draft-ietf-i2nsf-nsf-monitoring-data-model-01 "draft-ietf-i2nsf-nsf-monitoring-data-model-03
- System alarm"; - System alarm";
} }
identity disk-alarm { identity disk-alarm {
base system-alarm-capability; base system-alarm-capability;
description description
"Identity for disk alarm events"; "Identity for disk alarm events";
reference reference
"draft-ietf-i2nsf-nsf-monitoring-data-model-01 "draft-ietf-i2nsf-nsf-monitoring-data-model-03
- System alarm"; - System alarm";
} }
identity hardware-alarm { identity hardware-alarm {
base system-alarm-capability; base system-alarm-capability;
description description
"Identity for hardware alarm events"; "Identity for hardware alarm events";
reference reference
"draft-ietf-i2nsf-nsf-monitoring-data-model-01 "draft-ietf-i2nsf-nsf-monitoring-data-model-03
- System alarm"; - System alarm";
} }
identity interface-alarm { identity interface-alarm {
base system-alarm-capability; base system-alarm-capability;
description description
"Identity for interface alarm events"; "Identity for interface alarm events";
reference reference
"draft-ietf-i2nsf-nsf-monitoring-data-model-01 "draft-ietf-i2nsf-nsf-monitoring-data-model-03
- System alarm"; - System alarm";
} }
identity condition { identity condition {
description description
"Base identity for policy conditions"; "Base identity for policy conditions";
} }
identity context-capability { identity context-capability {
base condition; base condition;
skipping to change at page 15, line 49 skipping to change at page 16, line 4
} }
identity exact-ipv4-address { identity exact-ipv4-address {
base ipv4-capability; base ipv4-capability;
description description
"Identity for exact-match IPv4 address "Identity for exact-match IPv4 address
condition capability"; condition capability";
reference reference
"RFC 791: Internet Protocol - Address"; "RFC 791: Internet Protocol - Address";
} }
identity range-ipv4-address { identity range-ipv4-address {
base ipv4-capability; base ipv4-capability;
description description
"Identity for range-match IPv4 address "Identity for range-match IPv4 address condition
condition capability"; capability";
reference reference
"RFC 791: Internet Protocol - Address"; "RFC 791: Internet Protocol - Address";
} }
identity ipv4-ip-opts { identity ipv4-ip-opts {
base ipv4-capability; base ipv4-capability;
description description
"Identity for IPv4 option condition capability"; "Identity for IPv4 option condition capability";
reference reference
"RFC 791: Internet Protocol - Options"; "RFC 791: Internet Protocol - Options";
} }
identity ipv4-geo-ip { identity ipv4-geo-ip {
base ipv4-capability; base ipv4-capability;
description description
"Identity for geography condition capability"; "Identity for geography condition capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-05: Information Model
of NSFs Capabilities - Geo-IP"; of NSFs Capabilities - Geo-IP";
} }
identity ipv6-capability { identity ipv6-capability {
base condition; base condition;
description description
"Identity for IPv6 condition capabilities"; "Identity for IPv6 condition capabilities";
reference reference
"RFC 8200: Internet Protocol, Version 6 (IPv6) "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification"; Specification";
skipping to change at page 17, line 52 skipping to change at page 18, line 5
description description
"Identity for IPv6 next header condition capability"; "Identity for IPv6 next header condition capability";
reference reference
"RFC 8200: 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-capability; base ipv6-capability;
description description
"Identity for exact-match IPv6 hop limit "Identity for exact-match IPv6 hop limit condition
condition capability"; capability";
reference reference
"RFC 8200: 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-capability; base ipv6-capability;
description description
"Identity for range-match IPv6 hop limit "Identity for range-match IPv6 hop limit condition
condition capability"; capability";
reference reference
"RFC 8200: 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-capability; base ipv6-capability;
description description
"Identity for exact-match IPv6 address "Identity for exact-match IPv6 address condition
condition capability"; capability";
reference reference
"RFC 8200: 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-capability; base ipv6-capability;
description description
"Identity for range-match IPv6 address "Identity for range-match IPv6 address condition
condition capability"; capability";
reference reference
"RFC 8200: Internet Protocol, Version 6 (IPv6) "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification - Address"; Specification - Address";
} }
identity tcp-capability { identity tcp-capability {
base condition; base condition;
description description
"Identity for TCP condition capabilities"; "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-capability; base tcp-capability;
description description
"Identity for exact-match TCP port number "Identity for exact-match TCP port number condition
condition capability"; 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-capability; base tcp-capability;
description description
"Identity for range-match TCP port number "Identity for range-match TCP port number condition
condition capability"; 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-capability; base tcp-capability;
description description
"Identity for exact-match TCP sequence number "Identity for exact-match TCP sequence number condition
condition capability"; 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-capability; base tcp-capability;
description description
"Identity for range-match TCP sequence number "Identity for range-match TCP sequence number condition
condition capability"; 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-capability; base tcp-capability;
description description
"Identity for exact-match TCP acknowledgement number "Identity for exact-match TCP acknowledgement number condition
condition capability"; 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-capability; base tcp-capability;
description description
"Identity for range-match TCP acknowledgement number "Identity for range-match TCP acknowledgement number condition
condition capability"; 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-capability; base tcp-capability;
description description
"Identity for exact-match TCP window size "Identity for exact-match TCP window size condition capability";
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-capability; base tcp-capability;
description description
"Identity for range-match TCP window size "Identity for range-match TCP window size condition capability";
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-capability; base tcp-capability;
description description
"Identity for TCP flags condition capability"; "Identity for TCP flags condition capability";
reference reference
"RFC 793: Transmission Control Protocol - Flags"; "RFC 793: Transmission Control Protocol - Flags";
skipping to change at page 20, line 44 skipping to change at page 20, line 44
base condition; base condition;
description description
"Identity for UDP condition capabilities"; "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-capability; base udp-capability;
description description
"Identity for exact-match UDP port number "Identity for exact-match UDP port number condition capability";
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-capability; base udp-capability;
description description
"Identity for range-match UDP port number "Identity for range-match UDP port number condition capability";
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-capability; base udp-capability;
description description
"Identity for exact-match UDP total-length "Identity for exact-match UDP total-length condition capability";
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-capability; base udp-capability;
description description
"Identity for range-match UDP total-length "Identity for range-match UDP total-length condition capability";
condition capability";
reference reference
"RFC 768: User Datagram Protocol - Total Length"; "RFC 768: User Datagram Protocol - Total Length";
} }
identity icmp-capability { identity icmp-capability {
base condition; base condition;
description description
"Identity for ICMP condition capabilities"; "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-capability; base icmp-capability;
description description
"Identity for ICMP type condition capability"; "Identity for ICMP type condition capability";
reference reference
"RFC 792: Internet Control Message Protocol"; "RFC 792: Internet Control Message Protocol";
} }
identity icmpv6-capability {
base condition;
description
"Identity for ICMPv6 condition capabilities";
reference
"RFC 4443: Internet Control Message Protocol (ICMPv6)
for the Internet Protocol Version 6 (IPv6) Specification
- ICMPv6";
}
identity icmpv6-type {
base icmpv6-capability;
description
"Identity for ICMPv6 type condition capability";
reference
"RFC 4443: Internet Control Message Protocol (ICMPv6)
for the Internet Protocol Version 6 (IPv6) Specification
- ICMPv6";
}
identity url-capability { identity url-capability {
base condition; base condition;
description description
"Identity for URL condition capabilities"; "Identity for URL condition capabilities";
} }
identity pre-defined { identity pre-defined {
base url-capability; base url-capability;
description description
"Identity for URL pre-defined condition capabilities"; "Identity for URL pre-defined condition capabilities";
skipping to change at page 22, line 35 skipping to change at page 22, line 51
identity session-log { identity session-log {
base log-action-capability; base log-action-capability;
description description
"Identity for session log log-action capability"; "Identity for session log log-action capability";
} }
identity ingress-action-capability { identity ingress-action-capability {
description description
"Identity for ingress-action capabilities"; "Identity for ingress-action capabilities";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "RFC 8329: Framework for Interface to Network Security
of NSFs Capabilities - Action"; Functions - Ingress action";
} }
identity egress-action-capability { identity egress-action-capability {
description description
"Base identity for egress-action capabilities"; "Base identity for egress-action capabilities";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "RFC 8329: Framework for Interface to Network Security
of NSFs Capabilities - Egress action"; Functions - Egress action";
} }
identity default-action-capability { identity default-action-capability {
description description
"Identity for default-action capabilities"; "Identity for default-action capabilities";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-05: Information Model of
of NSFs Capabilities - Default action"; NSFs Capabilities - Default action";
} }
identity pass { identity pass {
base ingress-action-capability; base ingress-action-capability;
base egress-action-capability; base egress-action-capability;
base default-action-capability; base default-action-capability;
description description
"Identity for pass action capability"; "Identity for pass action capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "RFC 8329: Framework for Interface to Network Security
of NSFs Capabilities - Actions and Functions - Ingress, egress, and pass actions
default action"; draft-ietf-i2nsf-capability-05: Information Model of
NSFs Capabilities - Actions and default action";
} }
identity drop { identity drop {
base ingress-action-capability; base ingress-action-capability;
base egress-action-capability; base egress-action-capability;
base default-action-capability; base default-action-capability;
description description
"Identity for drop action capability"; "Identity for drop action capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "RFC 8329: Framework for Interface to Network Security
of NSFs Capabilities - Actions and Functions - Ingress, egress, and drop actions
default action"; draft-ietf-i2nsf-capability-05: Information Model of
} NSFs Capabilities - Actions and default action";
identity reject {
base ingress-action-capability;
base egress-action-capability;
base default-action-capability;
description
"Identity for reject action capability";
reference
"draft-ietf-i2nsf-capability-04: Information Model
of NSFs Capabilities - Actions and
default action";
} }
identity alert { identity alert {
base ingress-action-capability; base ingress-action-capability;
base egress-action-capability; base egress-action-capability;
base default-action-capability; base default-action-capability;
description description
"Identity for alert action capability"; "Identity for alert action capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "RFC 8329: Framework for Interface to Network Security
of NSFs Capabilities - Actions and Functions - Ingress, egress, and alert actions
default action"; draft-ietf-i2nsf-nsf-monitoring-data-model-03: I2NSF
NSF Monitoring YANG Data Model - Alarm (i.e., alert)
draft-ietf-i2nsf-capability-05: Information Model of
NSFs Capabilities - Actions and default action";
} }
identity mirror { identity mirror {
base ingress-action-capability; base ingress-action-capability;
base egress-action-capability; base egress-action-capability;
base default-action-capability; base default-action-capability;
description description
"Identity for mirror action capability"; "Identity for mirror action capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "RFC 8329: Framework for Interface to Network Security
of NSFs Capabilities - Actions and Functions - Ingress, egress, and mirror actions
default action"; draft-ietf-i2nsf-capability-05: Information Model of
NSFs Capabilities - Actions and default action";
} }
identity invoke-signaling { identity invoke-signaling {
base egress-action-capability; base egress-action-capability;
description description
"Identity for invoke signaling action capability"; "Identity for invoke signaling action capability";
reference
"RFC 8329: Framework for Interface to Network Security
Functions - Invoke-signaling action";
} }
identity tunnel-encapsulation { identity tunnel-encapsulation {
base egress-action-capability; base egress-action-capability;
description description
"Identity for tunnel encapsulation action capability"; "Identity for tunnel encapsulation action capability";
reference
"RFC 8329: Framework for Interface to Network Security
Functions - Tunnel-encapsulation action";
} }
identity forwarding { identity forwarding {
base egress-action-capability; base egress-action-capability;
description description
"Identity for forwarding action capability"; "Identity for forwarding action capability";
reference
"RFC 8329: Framework for Interface to Network Security
Functions - Forwarding action";
} }
identity redirection { identity redirection {
base egress-action-capability; base egress-action-capability;
description description
"Identity for redirection action capability"; "Identity for redirection action capability";
reference
"RFC 8329: Framework for Interface to Network Security
Functions - Redirection action";
} }
identity resolution-strategy-capability { identity resolution-strategy-capability {
description description
"Base identity for resolution strategy capability"; "Base identity for resolution strategy capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-05: Information Model of
of NSFs Capabilities - Resolution Strategy"; NSFs Capabilities - Resolution Strategy";
} }
identity fmr { identity fmr {
base resolution-strategy-capability; base resolution-strategy-capability;
description description
"Identity for First Matching Rule (FMR) "Identity for First Matching Rule (FMR) resolution
resolution strategy capability"; strategy capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-05: Information Model of
of NSFs Capabilities - Resolution Strategy"; NSFs Capabilities - Resolution Strategy";
} }
identity lmr { identity lmr {
base resolution-strategy-capability; base resolution-strategy-capability;
description description
"Identity for Last Matching Rule (LMR) "Identity for Last Matching Rule (LMR) resolution
resolution strategy capability"; strategy capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-05: Information Model of
of NSFs Capabilities - Resolution Strategy"; NSFs Capabilities - Resolution Strategy";
} }
identity pmr { identity pmr {
base resolution-strategy-capability; base resolution-strategy-capability;
description description
"Identity for Prioritized Matching Rule (PMR) "Identity for Prioritized Matching Rule (PMR) resolution
resolution strategy capability"; strategy capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-05: Information Model of
of NSFs Capabilities - Resolution Strategy"; NSFs Capabilities - Resolution Strategy";
} }
identity pmre { identity pmre {
base resolution-strategy-capability; 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"; resolution strategy capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-05: Information Model of NSFs
of NSFs Capabilities - Resolution Strategy"; Capabilities - Resolution Strategy";
} }
identity pmrn { identity pmrn {
base resolution-strategy-capability; 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"; resolution strategy capability";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-05: Information Model of NSFs
of NSFs Capabilities - Resolution Strategy"; Capabilities - Resolution Strategy";
} }
identity advanced-nsf-capability { identity advanced-nsf-capability {
description description
"Base identity for advanced "Base identity for advanced network security function (NSF)
network security function (NSF) capabilities"; 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
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller"; Advanced NSF Capability";
} }
identity anti-virus-capability { identity anti-virus-capability {
base advanced-nsf-capability; base advanced-nsf-capability;
description description
"Identity for advanced NSF anti-virus 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
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-virus"; Anti-Virus";
} }
identity anti-ddos-capability { identity anti-ddos-capability {
base advanced-nsf-capability; base advanced-nsf-capability;
description description
"Identity for advanced NSF anti-ddos 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
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-ddos"; Anti-DDoS";
} }
identity ips-capability { identity ips-capability {
base advanced-nsf-capability; base advanced-nsf-capability;
description description
"Identity for advanced NSF Intrusion Prevention System "Identity for advanced NSF Intrusion Prevention System
(IPS) capabilities"; (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
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Intrusion Prevention System"; Intrusion Prevention System";
} }
identity voip-volte-capability { identity voip-volte-capability {
base advanced-nsf-capability; base advanced-nsf-capability;
description description
"Identity for advanced NSF 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
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller";
Controller";
} }
identity detect { identity detect {
base anti-virus-capability; base anti-virus-capability;
description description
"Identity for advanced NSF anti-virus detect capability"; "Identity for advanced NSF Anti-Virus detection capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-virus"; Anti-Virus";
} }
identity exception-application { identity exception-application {
base anti-virus-capability; base anti-virus-capability;
description description
"Identity for advanced NSF anti-virus exception "Identity for advanced NSF Anti-Virus exception application
application capability"; capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-virus"; Anti-Virus";
} }
identity exception-signature { identity exception-signature {
base anti-virus-capability; base anti-virus-capability;
description description
"Identity for advanced NSF anti-virus exception "Identity for advanced NSF Anti-Virus exception signature
signature capability"; capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-virus"; Anti-Virus";
} }
identity whitelists { identity whitelists {
base anti-virus-capability; base anti-virus-capability;
description description
"Identity for advanced NSF anti-virus whitelists "Identity for advanced NSF Anti-Virus whitelists capability";
capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-virus"; Anti-virus";
} }
identity syn-flood-action { identity syn-flood-action {
base anti-ddos-capability; base anti-ddos-capability;
description description
"Identity for advanced NSF anti-DDoS syn flood "Identity for advanced NSF Anti-DDoS syn flood action
action capability"; capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-DDoS"; Anti-DDoS";
} }
identity udp-flood-action { identity udp-flood-action {
base anti-ddos-capability; base anti-ddos-capability;
description description
"Identity for advanced NSF anti-DDoS UDP flood "Identity for advanced NSF anti-DDoS UDP flood action
action capability"; capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-DDoS"; Anti-DDoS";
} }
identity http-flood-action { identity http-flood-action {
base anti-ddos-capability; base anti-ddos-capability;
description description
"Identity for advanced NSF anti-DDoS http flood "Identity for advanced NSF anti-DDoS http flood action
action capability"; capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-DDoS"; Anti-DDoS";
} }
identity https-flood-action { identity https-flood-action {
base anti-ddos-capability; base anti-ddos-capability;
description description
"Identity for advanced NSF anti-DDoS https flood "Identity for advanced NSF Anti-DDoS https flood action
action capability"; capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-DDoS"; Anti-DDoS";
} }
identity dns-request-flood-action { identity dns-request-flood-action {
base anti-ddos-capability; base anti-ddos-capability;
description description
"Identity for advanced NSF anti-DDoS dns request "Identity for advanced NSF anti-DDoS dns request
flood action capability"; flood action capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-DDoS"; Anti-DDoS";
} }
identity dns-reply-flood-action { identity dns-reply-flood-action {
base anti-ddos-capability; base anti-ddos-capability;
description description
"Identity for advanced NSF anti-DDoS dns reply flood "Identity for advanced NSF Anti-DDoS DNS reply flood action
action capability"; capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-DDoS"; Anti-DDoS";
} }
identity icmp-flood-action { identity icmp-flood-action {
base anti-ddos-capability; base anti-ddos-capability;
description description
"Identity for advanced NSF anti-DDoS icmp flood "Identity for advanced NSF Anti-DDoS ICMP flood action
action capability"; capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-DDoS"; Anti-DDoS";
}
identity icmpv6-flood-action {
base anti-ddos-capability;
description
"Identity for advanced NSF Anti-DDoS ICMPv6 flood action
capability";
reference
"draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Security Functions with I2NSF Security Controller -
Anti-DDoS";
} }
identity sip-flood-action { identity sip-flood-action {
base anti-ddos-capability; base anti-ddos-capability;
description description
"Identity for advanced NSF anti-DDoS sip flood "Identity for advanced NSF Anti-DDoS SIP flood action
action capability"; capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-DDoS"; Anti-DDoS";
} }
identity detect-mode { identity detect-mode {
base anti-ddos-capability; base anti-ddos-capability;
description description
"Identity for advanced NSF anti-DDoS detect "Identity for advanced NSF Anti-DDoS detection mode
mode capability"; capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-DDoS"; Anti-DDoS";
} }
identity baseline-learning { identity baseline-learning {
base anti-ddos-capability; base anti-ddos-capability;
description description
"Identity for advanced NSF anti-DDoS baseline "Identity for advanced NSF Anti-DDoS baseline learning
learning capability"; capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Anti-DDoS"; Anti-DDoS";
} }
identity signature-set { identity signature-set {
base ips-capability; base ips-capability;
description description
"Identity for advanced NSF IPS signature set "Identity for advanced NSF IPS signature set capability";
capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Intrusion Prevention System"; Intrusion Prevention System";
} }
identity ips-exception-signature { identity ips-exception-signature {
base ips-capability; base ips-capability;
description description
"Identity for advanced NSF IPS exception signature "Identity for advanced NSF IPS exception signature
capability"; capability";
reference reference
"draft-dong-i2nsf-asf-config-01: Configuration of "draft-dong-i2nsf-asf-config-01: Configuration of Advanced
Advanced Security Functions with I2NSF Security Security Functions with I2NSF Security Controller -
Controller - Intrusion Prevention System"; Intrusion Prevention System";
} }
identity voice-id { identity voice-id {
base voip-volte-capability; base voip-volte-capability;
description description
"Identity for advanced NSF VoIP/VoLTE voice-id "Identity for advanced NSF VoIP/VoLTE voice-id capability";
capability";
reference reference
"RFC 3261: SIP: Session Initiation Protocol"; "RFC 3261: SIP: Session Initiation Protocol";
} }
identity user-agent { identity user-agent {
base voip-volte-capability; base voip-volte-capability;
description description
"Identity for advanced NSF VoIP/VoLTE user agent "Identity for advanced NSF VoIP/VoLTE user agent capability";
capability";
reference reference
"RFC 3261: SIP: Session Initiation Protocol"; "RFC 3261: SIP: Session Initiation Protocol";
} }
identity ipsec-capability { identity ipsec-capability {
description description
"Base identity for an IPsec capabilities"; "Base identity for an IPsec capabilities";
} }
identity ike { identity ike {
base ipsec-capability; base ipsec-capability;
description description
"Identity for an IPSec Internet Key Exchange (IKE) "Identity for an IPSec Internet Key Exchange (IKE)
capability"; capability";
} }
identity ikeless { identity ikeless {
base ipsec-capability; base ipsec-capability;
description description
skipping to change at page 31, line 43 skipping to change at page 32, line 24
"Identity for an IPSec without Internet Key Exchange (IKE) "Identity for an IPSec without Internet Key Exchange (IKE)
capability"; capability";
} }
/* /*
* Grouping * Grouping
*/ */
grouping nsf-capabilities { grouping nsf-capabilities {
description description
"Network Security Funtion (NSF) 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 - I2NSF Flow Security Policy Structure Functions - I2NSF Flow Security Policy Structure
draft-ietf-i2nsf-capability-04: Information Model draft-ietf-i2nsf-capability-05: Information Model of
of NSFs Capabilities - Capability Information Model Design"; 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
"absolute time capabilities. "absolute time capabilities.
If network security function has the absolute time If a network security function has the absolute time
capability, the network security function capability, the network security function supports
supports rule execution according to absolute time."; rule execution according to absolute time.";
} }
enum periodic-time { enum periodic-time {
description description
"periodic time capabilities. "periodic time capabilities.
If network security function has the periodic time If a network security function has the periodic time
capability, the network security function capability, the network security function supports
supports rule execution according to periodic time."; rule execution according to periodic time.";
} }
} }
description description
"Time capabilities"; "Time capabilities";
} }
container event-capabilities { container event-capabilities {
description description
"Capabilities of events. "Capabilities of events.
If network security function has If a network security function has the event capabilities,
the event capabilities, the network security functions the network security function supports rule execution
supports rule execution according to system event 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-05: Information Model of
of NSFs Capabilities - Design Principles and ECA NSFs Capabilities - Design Principles and ECA Policy
Policy Model Overview Model Overview
draft-ietf-i2nsf-nsf-monitoring-data-model-01: A YANG draft-ietf-i2nsf-nsf-monitoring-data-model-03: I2NSF
Data Model for Monitoring I2NSF Network Security NSF Monitoring YANG Data Model - System Alarm and
Functions - System Alarm and System Events"; System Events";
leaf-list system-event-capability { leaf-list system-event-capability {
type identityref { type identityref {
base system-event-capability; base system-event-capability;
} }
description description
"System event capabilities"; "System event capabilities";
} }
leaf-list system-alarm-capability { leaf-list system-alarm-capability {
skipping to change at page 33, line 19 skipping to change at page 33, line 45
} }
} }
container condition-capabilities { container condition-capabilities {
description description
"Conditions capabilities."; "Conditions capabilities.";
container generic-nsf-capabilities { container generic-nsf-capabilities {
description description
"Conditions capabilities. "Conditions capabilities.
If a network security function has If a network security function has the condition
the condition capabilities, the network security function capabilities, the network security function
supports rule execution according to conditions of IPv4, supports rule execution according to conditions of
IPv6, TCP, UDP, ICMP, and payload."; IPv4, IPv6, TCP, UDP, ICMP, ICMPv6, and payload.";
reference reference
"RFC 791: Internet Protocol "RFC 791: Internet Protocol - IPv4
RFC 792: Internet Control Message Protocol RFC 792: Internet Control Message Protocol - ICMP
RFC 793: Transmission Control Protocol RFC 793: Transmission Control Protocol - TCP
RFC 768: User Datagram Protocol - UDP
RFC 8200: Internet Protocol, Version 6 (IPv6) RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification - Next Header Specification - IPv6
RFC 4443: Internet Control Message Protocol (ICMPv6)
for the Internet Protocol Version 6 (IPv6) Specification
- ICMPv6
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-05: Information Model of
of NSFs Capabilities - Design Principles and ECA Policy NSFs Capabilities - Design Principles and ECA Policy
Model Overview"; Model Overview";
leaf-list ipv4-capability { leaf-list ipv4-capability {
type identityref { type identityref {
base ipv4-capability; base ipv4-capability;
} }
description description
"IPv4 packet capabilities"; "IPv4 packet capabilities";
reference reference
"RFC 791: Internet Protocol"; "RFC 791: Internet Protocol";
} }
leaf-list icmp-capability {
type identityref {
base icmp-capability;
}
description
"ICMP packet capabilities";
reference
"RFC 792: Internet Control Message Protocol - ICMP";
}
leaf-list ipv6-capability { leaf-list ipv6-capability {
type identityref { type identityref {
base ipv6-capability; base ipv6-capability;
} }
description description
"IPv6 packet capabilities"; "IPv6 packet capabilities";
reference reference
"RFC 8200: Internet Protocol, Version 6 (IPv6) "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification - Next Header"; Specification - IPv6";
} }
leaf-list tcp-capability { leaf-list icmpv6-capability {
type identityref { type identityref {
base tcp-capability; base icmpv6-capability;
} }
description description
"TCP packet capabilities"; "ICMPv6 packet capabilities";
reference reference
"RFC 793: Transmission Control Protocol"; "RFC 4443: Internet Control Message Protocol (ICMPv6)
for the Internet Protocol Version 6 (IPv6) Specification
- ICMPv6";
} }
leaf-list udp-capability { leaf-list tcp-capability {
type identityref { type identityref {
base udp-capability; base tcp-capability;
} }
description description
"UDP packet capabilities"; "TCP packet capabilities";
reference reference
"RFC 768: User Datagram Protocol"; "RFC 793: Transmission Control Protocol - TCP";
} }
leaf-list icmp-capability { leaf-list udp-capability {
type identityref { type identityref {
base icmp-capability; base udp-capability;
} }
description description
"ICMP packet capabilities"; "UDP packet capabilities";
reference reference
"RFC 8200: Internet Protocol, Version 6 (IPv6)"; "RFC 768: User Datagram Protocol - UDP";
} }
} }
container advanced-nsf-capabilities { container advanced-nsf-capabilities {
description description
"Advanced Network Security Function (NSF) capabilities, "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 anti-virus-capability { leaf-list anti-virus-capability {
type identityref { type identityref {
base anti-virus-capability; base anti-virus-capability;
skipping to change at page 36, line 22 skipping to change at page 37, line 16
} }
} }
leaf-list context-capabilities { leaf-list context-capabilities {
type identityref { type identityref {
base context-capability; base context-capability;
} }
description description
"Security context capabilities"; "Security context capabilities";
} }
} }
container action-capabilities { container action-capabilities {
description description
"Action capabilities. "Action capabilities.
If network security function has If a network security function has the action
the action capabilities, it supports capabilities, the network security function supports
the attendant actions for policy rules."; the attendant actions for policy rules.";
leaf-list ingress-action-capability { leaf-list ingress-action-capability {
type identityref { type identityref {
base ingress-action-capability; base ingress-action-capability;
} }
description description
"Ingress-action capabilities"; "Ingress-action capabilities";
} }
skipping to change at page 37, line 14 skipping to change at page 38, line 8
"Log-action capabilities"; "Log-action capabilities";
} }
} }
leaf-list resolution-strategy-capabilities { leaf-list resolution-strategy-capabilities {
type identityref { type identityref {
base resolution-strategy-capability; base resolution-strategy-capability;
} }
description description
"Resolution strategy capabilities. "Resolution strategy capabilities.
The resolution strategies can be used to The resolution strategies can be used to specify how
specify how to resolve conflicts that occur between to resolve conflicts that occur between the actions
the actions of the same or different policy rules that of the same or different policy rules that are matched
are matched for the smae packet and by particular NSF"; for the same packet and by particular NSF";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "draft-ietf-i2nsf-capability-05: Information Model of
of NSFs Capabilities - Resolution strategy"; NSFs Capabilities - Resolution strategy";
} }
leaf-list default-action-capabilities { leaf-list default-action-capabilities {
type identityref { type identityref {
base default-action-capability; base default-action-capability;
} }
description description
"Default action capabilities. "Default action capabilities.
A default action is used to execute I2NSF policy rules 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, or mirror."; defined as pass, drop, alert, or mirror.";
reference reference
"draft-ietf-i2nsf-capability-04: Information Model "RFC 8329: Framework for Interface to Network Security
of NSFs Capabilities - Default action"; Functions - Ingress and egress actions
draft-ietf-i2nsf-capability-05: Information Model of
NSFs Capabilities - Default action";
} }
leaf-list ipsec-method { leaf-list ipsec-method {
type identityref { type identityref {
base ipsec-capability; base ipsec-capability;
} }
description description
"IPsec method capabilities"; "IPsec method capabilities";
reference reference
" draft-ietf-i2nsf-sdn-ipsec-flow-protection-04"; "draft-ietf-i2nsf-sdn-ipsec-flow-protection-08:
Software-Defined Networking (SDN)-based IPsec Flow
Protection - IPsec methods such as IKE and IKE-less";
} }
} }
/* /*
* Data nodes * Data nodes
*/ */
list nsf { list nsf {
key "nsf-name"; key "nsf-name";
description description
"The list of Network security Function (NSF) "The list of Network Security Function (NSF) capabilities";
capabilities";
leaf nsf-name { leaf nsf-name {
type string; type string;
mandatory true; mandatory true;
description description
"The name of network security function"; "The name of network security function";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
skipping to change at page 39, line 13 skipping to change at page 40, line 11
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 There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., config true, which is the writable, creatable, and deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config) in some network environments. Write operations to these data nodes
to these data nodes without proper protection can have a negative could have a negative effect on network and security operations.
effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability:
o ietf-i2nsf-capability: The attacker may provide incorrect o ietf-i2nsf-capability: An attacker could alter the security
information of the security capability of any target NSF by capabilities associated with an NSF whereby disabling or enabling
illegally modifying this. the evasion of security mitigations.
Some of the readable data nodes in this YANG module may be considered Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability: nodes and their sensitivity/vulnerability:
o ietf-i2nsf-capability: The attacker may gather the security o ietf-i2nsf-capability: An attacker could gather the security
capability information of any target NSF and misuse the capability information of any NSF and use this information to
information for subsequent attacks. evade detection or filtering.
9. References 9. References
9.1. Normative References 9.1. Normative References
[draft-dong-i2nsf-asf-config]
Pan, W. and L. Xia, "Configuration of Advanced Security
Functions with I2NSF Security Controller", draft-dong-
i2nsf-asf-config-01 (work in progress), October 2018.
[draft-ietf-i2nsf-capability]
Xia, L., Strassner, J., Basile, C., and D. Lopez,
"Information Model of NSFs Capabilities", draft-ietf-
i2nsf-capability-05 (work in progress), April 2019.
[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-03 (work in progress), May 2020.
[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-08 (work in progress), June 2020.
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
DOI 10.17487/RFC3261, June 2002, DOI 10.17487/RFC3261, June 2002,
<https://www.rfc-editor.org/info/rfc3261>. <https://www.rfc-editor.org/info/rfc3261>.
[RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between
Information Models and Data Models", RFC 3444,
DOI 10.17487/RFC3444, January 2003,
<https://www.rfc-editor.org/info/rfc3444>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>. <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>.
skipping to change at page 41, line 35 skipping to change at page 43, line 7
S., and N. Bahadur, "A YANG Data Model for the Routing S., and N. Bahadur, "A YANG Data Model for the Routing
Information Base (RIB)", RFC 8431, DOI 10.17487/RFC8431, Information Base (RIB)", RFC 8431, DOI 10.17487/RFC8431,
September 2018, <https://www.rfc-editor.org/info/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-dong-i2nsf-asf-config]
Pan, W. and L. Xia, "Configuration of Advanced Security
Functions with I2NSF Security Controller", draft-dong-
i2nsf-asf-config-01 (work in progress), October 2018.
[draft-ietf-i2nsf-capability]
Xia, L., Strassner, J., Basile, C., and D. Lopez,
"Information Model of NSFs Capabilities", draft-ietf-
i2nsf-capability-05 (work in progress), April 2019.
[draft-ietf-i2nsf-nsf-facing-interface-dm] [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-07 Data Model", draft-ietf-i2nsf-nsf-facing-interface-dm-09
(work in progress), July 2019. (work in progress), May 2020.
[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.
Birkholz, "Interface to Network Security Functions (I2NSF)
Terminology", draft-ietf-i2nsf-terminology-08 (work in
progress), July 2019.
[draft-ietf-supa-generic-policy-info-model] [draft-ietf-i2nsf-registration-interface-dm]
Strassner, J., Halpern, J., and S. Meer, "Generic Policy Hyun, S., Jeong, J., Roh, T., Wi, S., and J. Park, "I2NSF
Information Model for Simplified Use of Policy Registration Interface YANG Data Model", draft-ietf-i2nsf-
Abstractions (SUPA)", draft-ietf-supa-generic-policy-info- registration-interface-dm (work in progress), March 2020.
model-03 (work in progress), May 2017.
Appendix A. Configuration Examples Appendix A. Configuration Examples
This section shows configuration examples of "ietf-i2nsf-capability" This section shows configuration examples of "ietf-i2nsf-capability"
module for capabilities registration of general firewall. module for capabilities registration of general firewall.
A.1. Example 1: Registration for Capabilities of General Firewall A.1. Example 1: Registration for Capabilities of General Firewall
This section shows a configuration example for capabilities This section shows a configuration example for capabilities
registration of general firewall. registration of general firewall.
skipping to change at page 47, line 39 skipping to change at page 48, line 39
1. The name of the NSF is http_and_https_flood_mitigation. 1. The name of the NSF is http_and_https_flood_mitigation.
2. The location of the NSF is 221.159.112.140. 2. The location of the NSF is 221.159.112.140.
3. The NSF can control the amount of packets for http and https 3. The NSF can control the amount of packets for http and https
packets. packets.
4. The NSF can control whether the packets are allowed to pass, 4. The NSF can control whether the packets are allowed to pass,
drop, or alert. drop, or alert.
Appendix B. Changes from draft-ietf-i2nsf-capability-data-model-04 Appendix B. Changes from draft-ietf-i2nsf-capability-data-model-05
The following changes are made from draft-ietf-i2nsf-capability-data- The following changes are made from draft-ietf-i2nsf-capability-data-
model-04: model-05:
o The version is revised according to the comments from Acee Lindem o The version is revised according to the comments from Romans
and Carl Moberg who are YANG doctors for review. Danyliw for his AD review.
Appendix C. Acknowledgments Appendix C. Acknowledgments
This work was supported by Institute of Information & Communications This work was supported by Institute of Information & Communications
Technology Planning & Evaluation (IITP) grant funded by the Korea Technology Planning & Evaluation (IITP) grant funded by the Korea
MSIT (Ministry of Science and ICT) (R-20160222-002755, Cloud based MSIT (Ministry of Science and ICT) (R-20160222-002755, Cloud based
Security Intelligence Technology Development for the Customized Security Intelligence Technology Development for the Customized
Security Service Provisioning). Security Service Provisioning).
Appendix D. Contributors Appendix D. Contributors
skipping to change at page 48, line 29 skipping to change at page 49, line 29
o Liang Xia (Huawei) o Liang Xia (Huawei)
o Jung-Soo Park (ETRI) o Jung-Soo Park (ETRI)
o Tae-Jin Ahn (Korea Telecom) o Tae-Jin Ahn (Korea Telecom)
o Se-Hui Lee (Korea Telecom) o Se-Hui Lee (Korea Telecom)
Authors' Addresses Authors' Addresses
Susan Hares Susan Hares (editor)
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 (editor)
Department of Computer Science and Engineering 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
 End of changes. 192 change blocks. 
456 lines changed or deleted 510 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/