I2NSF Registration Interface YANG Data Model
Department of Computer Engineering
Myongji University116 Myongji-ro, Cheoin-guYonginGyeonggi-do17058Republic of Koreashyun@mju.ac.kr
Department of Computer Science and Engineering
Sungkyunkwan University2066 Seobu-Ro, Jangan-GuSuwonGyeonggi-Do16419Republic of Korea+82 31 299 4957+82 31 290 7996pauljeong@skku.eduhttp://iotlab.skku.edu/people-jaehoon-jeong.php
Department of Electronic, Electrical and Computer Engineering
Sungkyunkwan University2066 Seobu-Ro, Jangan-GuSuwonGyeonggi-Do16419Republic of Korea+82 31 290 7222+82 31 299 6673tkroh0198@skku.edu
Department of Electronic, Electrical and Computer Engineering
Sungkyunkwan University2066 Seobu-Ro, Jangan-GuSuwonGyeonggi-Do16419Republic of Korea+82 31 290 7222+82 31 299 6673dnl9795@skku.edu
Electronics and Telecommunications Research Institute
218 Gajeong-Ro, Yuseong-GuDaejeon305-700Republic of Korea+82 42 860 6514pjs@etri.re.kr
Security
I2NSF Working GroupInternet-Draft
This document defines an information model and a YANG data model for Registration Interface between Security Controller and Developer's Management System (DMS) in the Interface to Network Security Functions (I2NSF) framework to register Network Security Functions (NSF) of the DMS with the Security Controller. The objective of these information and data models is to support NSF capability registration and query via I2NSF Registration Interface.
A number of Network Security Functions (NSF) may exist in the Interface to Network Security Functions (I2NSF) framework . Since each of these NSFs likely has different security capabilities from each other, it is important to register the security capabilities of the NSF with the security controller. In addition, it is required to search NSFs of some required security capabilities on demand. As an example, if additional security capabilities are required to serve some security service request(s) from an I2NSF user, the security controller should be able to request the DMS for NSFs that have the required security capabilities.
This document describes an information model (see ) and a YANG data model (see ) for the I2NSF Registration Interface between the security controller and the developer's management system (DMS) to support NSF capability registration and query via the registration interface. It also describes the operations which should be performed by the security controller and the DMS via the Registration Interface using the defined model.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in when, and only when, they appear in all capitals, as shown here.
This document uses the following terms defined in and .
Network Security Function (NSF): A function that is responsible for a specific treatment of received packets. A Network Security Function can act at various layers of a protocol stack (e.g., at the network layer or other OSI layers). Sample Network Security Service Functions are as follows: Firewall, Intrusion Prevention/Detection System (IPS/IDS), Deep Packet Inspection (DPI), Application Visibility and Control (AVC), network virus and malware scanning, sandbox, Data Loss Prevention (DLP), Distributed Denial of Service (DDoS) mitigation and TLS proxy.
Data Model: A data model is a representation of concepts of interest to an environment in a form that is dependent on data repository, data definition language, query language, implementation language, and protocol.
Information Model: An information model is a representation of concepts of interest to an environment in a form that is independent of data repository, data definition language, query language, implementation language, and protocol.
YANG: This document follows the guidelines of , uses the common YANG types defined in , and adopts the Network Management Datastore
Architecture (NMDA). The meaning of the symbols in tree diagrams is
defined in .
Registering NSFs to I2NSF framework: Developer's Management System (DMS) in I2NSF framework is typically run by an NSF vendor, and uses Registration Interface to provide NSFs developed by the NSF vendor to Security Controller. DMS registers NSFs and their capabilities to I2NSF framework through Registration Interface. For the registered NSFs, Security Controller maintains a catalog of the capabilities of those NSFs.
Updating the capabilities of registered NSFs: After an NSF is registered into Security Controller, some modifications on the capability of the NSF may be required later. In this case, DMS uses Registration Interface to update the capability of the NSF, and this update should be reflected in the catalog of NSFs.
Asking DMS about some required capabilities: In cases that some security capabilities are required to serve the security service request from an I2NSF user, Security Controller searches through the registered NSFs to find ones that can provide the required capabilities. But Security Controller might fail to find any NSFs having the required capabilities among the registered NSFs. In this case, Security Controller needs to request DMS for additional NSF(s) that can provide the required security capabilities via Registration Interface.
The I2NSF registration interface is used by Security Controller and Developer's Management System (DMS) in I2NSF framework. The following summarizes the operations done through the registration interface:
DMS registers NSFs and their capabilities to Security Controller via the registration interface. DMS also uses the registration interface to update the capabilities of the NSFs registered previously.
In case that Security Controller fails to find some required capabilities from any registered NSF that can provide , Security Controller queries DMS about NSF(s) having the required capabilities via the registration interface.
shows the information model of the I2NSF registration interface, which consists of two submodels: NSF capability registration and NSF capability query. Each submodel is used for the operations listed above. The remainder of this section will provide in-depth explanations of each submodel.
This submodel is used by DMS to register an NSF with Security Controller. shows how this submodel is constructed. The most important part in is the NSF capability, and this specifies the set of capabilities that the NSF to be registered can offer. The NSF Name contains a unique name of this NSF with the specified set of capabilities. When registering the NSF, DMS additionally includes the network access information of the NSF which is required to enable network communications with the NSF.
The following will further explain the NSF capability information and the NSF access information in more detail.
NSF Capability Information basically describes the security capabilities of an NSF. In , we show capability objects of an NSF. Following the information model of NSF capabilities defined in , we share the same I2NSF security capabilities: Time Capabilities, Event Capabilities, Condition Capabilities, Action Capabilities, Resolution Strategy Capabilities, Default Action Capabilities, and IPsec Method . Also, NSF Capability Information additionally contains the performance capabilities of an NSF as shown in .
This information represents the processing capability of an NSF. Assuming that the current workload status of each NSF is being collected through NSF monitoring , this capability information of the NSF can be used to determine whether the NSF is in congestion by comparing it with the current workload of the NSF. Moreover, this information can specify an available amount of each type of resource, such as processing power which are available on the NSF. (The registration interface can control the usages and limitations of the created instance and make the appropriate request according to the status.) As illustrated in , this information consists of two items: Processing and Bandwidth. Processing information describes the NSF's available processing power. Bandwidth describes the information about available network amount in two cases, outbound, inbound. These two information can be used for the NSF's instance request.
NSF Access Information contains the followings that are required to communicate with an NSF: IPv4 address, IPv6 address, port number, and supported transport protocol(s) (e.g., Virtual Extensible LAN (VXLAN) , Generic Protocol Extension for VXLAN (VXLAN-GPE) , Generic Route Encapsulation (GRE), Ethernet etc.).
In this document, NSF Access Information is used to identify a specific NSF instance (i.e. NSF Access Information is the signature(unique identifier) of an NSF instance in the overall system).
Security Controller may require some additional capabilities to serve the security service request from an I2NSF user, but none of the registered NSFs has the required capabilities. In this case, Security Controller makes a description of the required capabilities by using the NSF capability information sub-model in , and sends DMS a query about which NSF(s) can provide these capabilities.
This section provides the YANG Tree diagram of the I2NSF registration interface.
A simplified graphical representation of the data model is used in this section. The meaning of the symbols used in the following diagrams is as follows:
Brackets "[" and "]" enclose list keys.
Abbreviations before data node names: "rw" means configuration (read-write) and "ro" state data (read-only).
Symbols after data node names: "?" means an optional node and "*" denotes a "list" and "leaf-list".
Parentheses enclose choice and case nodes, and case nodes are also marked with a colon (":").
Ellipsis ("...") stands for contents of subtrees that are not shown.
The I2NSF registration interface is used for the following purposes.
Developer's Management System (DMS) registers NSFs and their capabilities into Security Controller
via the registration interface. In case that Security Controller fails to find any NSF among the registered
NSFs which can provide some required capabilities, Security Controller uses the registration interface
to query DMS about NSF(s) having the required capabilities.
The following sections describe the YANG data models to support these operations.
This section expands the i2nsf-nsf-registrations in .
When registering an NSF to Security Controller, DMS uses this module to describe what capabilities the NSF can offer.
DMS includes the network access information of the NSF which is required to make a network connection with the NSF as
well as the capability description of the NSF.
This section expands the nsf-capability-query in .
Security Controller may require some additional capabilities to provide the security service requested by an I2NSF user,
but none of the registered NSFs has the required capabilities. In this case, Security Controller makes a description of
the required capabilities using this module and then queries DMS about which NSF(s) can provide these capabilities.
Use NETCONF RPCs to send a NSF capability query. Input data is query-i2nsf-capability-info and output data is nsf-access-info.
In , the ietf-i2nsf-capability refers to the module defined in .
This section expands the nsf-capability-info in and .
In , the ietf-i2nsf-capability refers to the module defined in . The performance-capability is used to specify the performance capability of an NSF.
This section expands the nsf-performance-capability in .
This module is used to specify the performance capabilities of an NSF when registering or initiating the NSF.
This section expands the nsf-access-info in .
This module contains the network access information of an NSF that is required to enable network communications with the NSF.
The field of ip can have either an IPv4 address or an IPv6 address.
This section provides a YANG module of the data model for the registration interface between Security Controller and Developer's Management System, as defined in .
This YANG module imports from , and makes a reference
to .
file "ietf-i2nsf-reg-interface@2020-08-29.yang"
module ietf-i2nsf-reg-interface {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-i2nsf-reg-interface";
prefix nsfreg;
// RFC Ed.: replace occurences of XXXX with actual RFC number and
// remove this note
import ietf-inet-types {
prefix inet;
reference "RFC 6991";
}
import ietf-i2nsf-capability {
prefix cap;
// RFC Ed.: replace YYYY with actual RFC number of
// draft-ietf-i2nsf-capability-data-model and remove this note.
reference "RFC YYYY: I2NSF Capability YANG Data Model";
}
organization
"IETF I2NSF (Interface to Network Security Functions)
Working Group";
contact
"WG Web:
WG List:
Editor: Sangwon Hyun
Editor: Jaehoon Paul Jeong
";
description
"This module defines a YANG data model for I2NSF
Registration Interface.
Copyright (c) 2020 IETF Trust and the persons
identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove
// this note
revision "2020-08-29" {
description "Initial revision";
reference
"RFC XXXX: I2NSF Registration Interface YANG Data Model";
// RFC Ed.: replace XXXX with actual RFC number and remove
// this note
}
grouping nsf-performance-capability {
description
"Description of the performance capabilities of an NSF";
container processing {
description
"Processing power of an NSF in the unit of GHz (gigahertz)";
leaf processing-average {
type uint16;
units "GHz";
description
"Average processing power";
}
leaf processing-peak {
type uint16;
units "GHz";
description
"Peak processing power";
}
}
container bandwidth {
description
"Network bandwidth available on an NSF
in the unit of Mbps (megabits per second)";
container outbound {
description
"Outbound network bandwidth";
leaf outbound-average {
type uint32;
units "Mbps";
description
"Average outbound bandwidth";
}
leaf outbound-peak {
type uint32;
units "Mbps";
description
"Peak outbound bandwidth";
}
}
container inbound {
description
"Inbound network bandwidth";
leaf inbound-average {
type uint32;
units "Mbps";
description
"Average inbound bandwidth";
}
leaf inbound-peak {
type uint32;
units "Mbps";
description
"Peak inbound bandwidth";
}
}
}
}
grouping nsf-capability-info {
description
"Capability description of an NSF";
container security-capability {
description
"Description of the security capabilities of an NSF";
uses cap:nsf-capabilities;
// RFC Ed.: replace YYYY with actual RFC number of
// draft-ietf-i2nsf-capability-data-model and remove this note.
reference "RFC YYYY: I2NSF Capability YANG Data Model";
}
container performance-capability {
description
"Description of the performance capabilities of an NSF";
uses nsf-performance-capability;
}
}
grouping nsf-access-info {
description
"Information required to access an NSF";
leaf capability-name {
type string;
description
"Unique name of this NSF's capability";
}
leaf ip {
type inet:ip-address;
description
"Either an IPv4 address or an IPv6 address of this NSF";
}
leaf port {
type inet:port-number;
description
"Port available on this NSF";
}
}
container nsf-registrations {
description
"Information of an NSF that DMS registers
to Security Controller";
list nsf-information {
key "capability-name";
description
"Required information for registration";
leaf capability-name {
type string;
mandatory true;
description
"Unique name of this registered NSF";
}
container nsf-capability-info {
description
"Capability description of this NSF";
uses nsf-capability-info;
}
container nsf-access-info {
description
"Network access information of this NSF";
uses nsf-access-info;
}
}
}
rpc nsf-capability-query {
description
"Description of the capabilities that the
Security Controller requests to the DMS";
input {
container query-nsf-capability {
description
"Description of the capabilities to request";
uses cap:nsf-capabilities;
// RFC Ed.: replace YYYY with actual RFC number of
// draft-ietf-i2nsf-capability-data-model and remove this note.
reference "RFC YYYY: I2NSF Capability YANG Data Model";
}
}
output {
container nsf-access-info {
description
"Network access information of an NSF
with the requested capabilities";
uses nsf-access-info;
}
}
}
}
]]>This document requests IANA to register the following URI in the
"IETF XML Registry" :
This document requests IANA to register the following YANG
module in the "YANG Module Names" registry
:
The YANG module specified in this document defines a data schema designed to be accessed through network management protocols such as NETCONF or RESTCONF . The lowest NETCONF layer is the secure transport layer, and the required secure transport is Secure Shell (SSH) . The lowest RESTCONF layer is HTTPS, and the required secure transport is TLS .
The NETCONF access control model provides a means of restricting access to specific NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content.
There are a number of data nodes defined in this YANG module that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and their sensitivity/vulnerability:
nsf-registrations: The attacker may exploit this to register a compromised or malicious NSF instead of a legitimate NSF with the Security Controller.
nsf-performance-capability: The attacker may provide incorrect information of the performance capability of any target NSF by illegally modifying this.
nsf-capability-info: The attacker may provide incorrect information of the security capability of any target NSF by illegally modifying this.
nsf-access-info: The attacker may provide incorrect network access information of any target NSF by illegally modifying this.
Some of the readable data nodes in this YANG module may be considered sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. These are the subtrees and data nodes and their sensitivity/vulnerability:
nsf-registrations: The attacker may try to gather some sensitive information of a registered NSF by sniffing this.
nsf-performance-capability: The attacker may gather the performance capability information of any target NSF and misuse the information for subsequent attacks.
nsf-capability-info: The attacker may gather the security capability information of any target NSF and misuse the information for subsequent attacks.
nsf-access-info: The attacker may gather the network access information of any target NSF and misuse the information for subsequent attacks.
The RPC operation in this YANG module may be considered sensitive or vulnerable in some network environments. It is thus important to control access to this operation. The following is the operation and its sensitivity/vulnerability:
nsf-capability-query: The attacker may exploit this RPC operation to deteriorate the availability of the DMS and/or gather the information of some interested NSFs from the DMS.
Network Functions Virtualisation (NFV); Architectureal Framework
This section describes XML examples of the I2NSF Registration Interface data model under the assumption of registering several types of NSFs and querying NSF capability.
This section shows an XML example for registering the capabilities of a general firewall
in either IPv4 networks or IPv6 networks .
general_firewall_capabilitycap:ipv4-protocolcap:exact-ipv4-addresscap:range-ipv4-addresscap:exact-tcp-port-numcap:range-tcp-port-numcap:passcap:dropcap:alertcap:passcap:dropcap:alertcap:ikeless100050001000500010005000general_firewall192.0.2.113000
]]> shows the configuration XML for registering a general firewall in an IPv4 network and its capabilities as follows.
The instance name of the NSF is general_firewall.
The NSF can inspect a protocol, an exact IPv4 address, and a range of IPv4 addresses for IPv4 packets.
The NSF can inspect an exact port number and a range of port numbers for TCP packets.
The NSF can determine whether the packets are allowed to pass, drop, or alert.
The NSF can support IPsec not through IKEv2, but through a Security Controller .
The NSF can have processing power and bandwidth.
The IPv4 address of the NSF is 192.0.2.11.
The port of the NSF is 3000.
general_firewall_capabilitycap:ipv6-protocolcap:exact-ipv6-addresscap:range-ipv6-addresscap:exact-tcp-port-numcap:range-tcp-port-numcap:passcap:dropcap:alertcap:passcap:dropcap:alertcap:ikeless100050001000500010005000general_firewall2001:DB8:0:1::113000
]]>
In addition, shows the configuration XML for registering a general firewall in an IPv6 network and its capabilities as follows.
The instance name of the NSF is general_firewall.
The NSF can inspect a protocol, an exact IPv6 address, and a range of IPv6 addresses for IPv6 packets.
The NSF can inspect an exact port number and a range of port numbers for TCP packets.
The NSF can determine whether the packets are allowed to pass, drop, or alert.
The NSF can support IPsec not through IKEv2, but through a Security Controller .
The NSF can have processing power and bandwidth.
The IPv6 address of the NSF is 2001:DB8:0:1::11.
The port of the NSF is 3000.
This section shows an XML example for registering the capabilities of a time-based firewall
in either IPv4 networks or IPv6 networks .
time_based_firewall_capabilityabsolute-timeperiodic-timecap:ipv4-protocolcap:exact-ipv4-addresscap:range-ipv4-addresscap:exact-tcp-port-numcap:range-tcp-port-numcap:passcap:dropcap:alertcap:passcap:dropcap:alertcap:ike100050001000500010005000time_based_firewall192.0.2.113000
]]> shows the configuration XML for registering a time-based firewall in an IPv4 network and its capabilities as follows.
The instance name of the NSF is time_based_firewall.
The NSF can enforce the security policy rule according to absolute time and periodic time.
The NSF can inspect a protocol, an exact IPv4 address, and a range of IPv4 addresses for IPv4 packets.
The NSF can determine whether the packets are allowed to pass, drop, or alert.
The NSF can support IPsec through IKEv2 .
The NSF can have processing power and bandwidth.
The IPv4 address of the NSF is 192.0.2.11.
The port of the NSF is 3000.
time_based_firewall_capabilityabsolute-timeperiodic-timecap:ipv6-protocolcap:exact-ipv6-addresscap:range-ipv6-addresscap:exact-tcp-port-numcap:range-tcp-port-numcap:passcap:dropcap:alertcap:passcap:dropcap:alertcap:ike100050001000500010005000time_based_firewall2001:DB8:0:1::113000
]]>
In addition, shows the configuration XML for registering a time-based firewall in an IPv6 network and its capabilities as follows.
The instance name of the NSF is time_based_firewall.
The NSF can enforce the security policy rule according to absolute time and periodic time.
The NSF can inspect a protocol, an exact IPv6 address, and a range of IPv6 addresses for IPv6 packets.
The NSF can determine whether the packets are allowed to pass, drop, or alert.
The NSF can support IPsec through IKEv2 .
The NSF can have processing power and bandwidth.
The IPv6 address of the NSF is 2001:DB8:0:1::11.
The port of the NSF is 3000.
This section shows an XML example for registering the capabilities of a web filter
in either IPv4 networks or IPv6 networks .
web_filtercap:user-definedcap:passcap:dropcap:alertcap:passcap:dropcap:alertcap:ikeless100050001000500010005000web_filter192.0.2.113000
]]> shows the configuration XML for registering a web filter in an IPv4 network and its capabilities are as follows.
The instance name of the NSF is web_filter.
The NSF can inspect URL for HTTP and HTTPS packets.
The NSF can determine whether the packets are allowed to pass, drop, or alert.
The NSF can support IPsec not through IKEv2, but through a Security Controller .
The NSF can have processing power and bandwidth.
The IPv4 address of the NSF is 192.0.2.11.
The port of the NSF is 3000.
web_filtercap:user-definedcap:passcap:dropcap:alertcap:passcap:dropcap:alertcap:ikeless100050001000500010005000web_filter2001:DB8:0:1::113000
]]>
In addition, shows the configuration XML for registering a web filter in an IPv6 network and its capabilities are as follows.
The instance name of the NSF is web_filter.
The NSF can inspect URL for HTTP and HTTPS packets.
The NSF can determine whether the packets are allowed to pass, drop, or alert.
The NSF can support IPsec not through IKEv2, but through a Security Controller .
The NSF can have processing power and bandwidth.
The IPv6 address of the NSF is 2001:DB8:0:1::11.
The port of the NSF is 3000.
This section shows an XML example for registering the capabilities of a VoIP/VoLTE filter
in either IPv4 networks or IPv6 networks .
voip_volte_filtercap:voice-idcap:passcap:dropcap:alertcap:passcap:dropcap:alertcap:ikeless100050001000500010005000voip_volte_filter192.0.2.113000
]]> shows the configuration XML for registering a VoIP/VoLTE filter in an IPv4 network and its capabilities are as follows.
The instance name of the NSF is voip_volte_filter.
The NSF can inspect a voice id for VoIP/VoLTE packets.
The NSF can determine whether the packets are allowed to pass, drop, or alert.
The NSF can support IPsec not through IKEv2, but through a Security Controller .
The NSF can have processing power and bandwidth.
The IPv4 address of the NSF is 192.0.2.11.
The port of the NSF is 3000.
voip_volte_filtercap:voice-idcap:passcap:dropcap:alertcap:passcap:dropcap:alertcap:ikeless100050001000500010005000voip_volte_filter2001:DB8:0:1::113000
]]> shows the configuration XML for registering a VoIP/VoLTE filter in an IPv6 network and its capabilities are as follows.
The instance name of the NSF is voip_volte_filter.
The NSF can inspect a voice id for VoIP/VoLTE packets.
The NSF can determine whether the packets are allowed to pass, drop, or alert.
The NSF can support IPsec not through IKEv2, but through a Security Controller .
The NSF can have processing power and bandwidth.
The IPv6 address of the NSF is 2001:DB8:0:1::11.
The port of the NSF is 3000.
This section shows an XML example for registering the capabilities of an HTTP and HTTPS flood mitigator in either IPv4 networks or IPv6 networks .
http_and_https_flood_mitigator
cap:http-flood-action
cap:https-flood-action
cap:passcap:dropcap:alertcap:passcap:dropcap:alertcap:ike100050001000500010005000
http_and_https_flood_mitigation
192.0.2.113000
]]> shows the configuration XML for registering an HTTP and HTTPS flood mitigator in an IPv4 network and its capabilities are as follows.
The instance name of the NSF is http_and_https_flood_mitigator.
The NSF can control the amount of packets for HTTP and HTTPS packets.
The NSF can determine whether the packets are allowed to pass, drop, or alert.
The NSF can support IPsec through IKEv2 .
The NSF can have processing power and bandwidth.
The IPv4 address of the NSF is 192.0.2.11.
The port of the NSF is 3000.
http_and_https_flood_mitigator
cap:http-flood-action
cap:https-flood-action
cap:passcap:dropcap:alertcap:passcap:dropcap:alertcap:ike100050001000500010005000
http_and_https_flood_mitigation
2001:DB8:0:1::113000
]]>
In addition, shows the configuration XML for registering an HTTP and HTTPS flood mitigator in an IPv6 network and its capabilities are as follows.
The instance name of the NSF is http_and_https_flood_mitigator.
The NSF can control the amount of packets for HTTP and HTTPS packets.
The NSF can determine whether the packets are allowed to pass, drop, or alert.
The NSF can support IPsec through IKEv2 .
The NSF can have processing power and bandwidth.
The IPv6 address of the NSF is 2001:DB8:0:1::11.
The port of the NSF is 3000.
This section shows an XML example for querying the capabilities of a time-based firewall
in either IPv4 networks or IPv6 networks .
absolute-timeperiodic-timecap:ipv4-protocolcap:exact-ipv4-addresscap:range-ipv4-addresscap:passcap:dropcap:alertcap:passcap:dropcap:alertcap:ikelesstime-based-firewall192.0.2.113000
]]> shows the XML configuration for querying the capabilities of a time-based firewall in an IPv4 network .
The access information of the announced time-based firewall has the IPv4 address of
192.0.2.11 and the port number of 3000.
absolute-timeperiodic-timecap:ipv6-protocolcap:exact-ipv6-addresscap:range-ipv6-addresscap:passcap:dropcap:alertcap:passcap:dropcap:alertcap:ikelesstime-based-firewall2001:DB8:0:1::113000
]]>
In addition, shows the XML configuration for querying the capabilities of a time-based firewall in an IPv6 network .
The access information of the announced time-based firewall has the IPv6 address of
2001:DB8:0:1::11 and the port number of 3000.
Network Functions Virtualization (NFV) can be used to implement I2NSF framework. In NFV environments, NSFs are deployed as virtual network functions (VNFs). Security Controller can be implemented as an Element Management (EM) of the NFV architecture, and is connected with the VNF Manager (VNFM) via the Ve-Vnfm interface . Security Controller can use this interface for the purpose of the lifecycle management of NSFs. If some NSFs need to be instantiated to enforce security policies in the I2NSF framework, Security Controller could request the VNFM to instantiate them through the Ve-Vnfm interface. Or if an NSF, running as a VNF, is not used by any traffic flows for a time period, Security Controller may request deinstantiating it through the interface for efficient resource utilization.
This work was supported by Institute of Information &
Communications Technology Planning & Evaluation (IITP) grant funded by
the Korea MSIT (Ministry of Science and ICT) (No. 2016-0-00078, Cloud Based
Security Intelligence Technology Development for the Customized
Security Service Provisioning).
This document is made by the group effort of I2NSF working group.
Many people actively contributed to this document, such as Reshad Rahman.
The authors sincerely appreciate their contributions.
The following are co-authors of this document:
Jinyong Tim Kim
Department of Electronic, Electrical and Computer Engineering
Sungkyunkwan University
2066 Seo-ro Jangan-gu
Suwon, Gyeonggi-do 16419
Republic of Korea
EMail: timkim@skku.edu
Chaehong Chung
Department of Electronic, Electrical and Computer Engineering
Sungkyunkwan University
2066 Seo-ro Jangan-gu
Suwon, Gyeonggi-do 16419
Republic of Korea
EMail: darkhong@skku.edu
Susan Hares
Huawei
7453 Hickory Hill
Saline, MI 48176
USA
EMail: shares@ndzh.com
Diego R. Lopez
Telefonica I+D
Jose Manuel Lara, 9
Seville, 41013
Spain
EMail: diego.r.lopez@telefonica.com