Network Working Group J. Jeong Internet-Draft D. Daghmehchi Intended status: Standards Track Sungkyunkwan University Expires: September 14, 2017 T. Ahn Korea Telecom R. Kumar Juniper Networks S. Hares Huawei March 13, 2017 Consumer-Facing Interface YANG Data Model for Interface to Network Security Functions draft-jeong-i2nsf-consumer-facing-interface-dm-01 Abstract This document describes a YANG data model for security management that is based on Interface to Network Security Functions (I2NSF) by using Network Functions Virtualization (NFV). This document proposes a security management architecture based on I2NSF framework. Note that the I2NSF framework consists of I2NSF User, Security Management System (i.e., Security Controller and Developer's Management System), and the instances of Network Security Functions (NSFs) in the lowest layer of the framework. I2NSF User consists of Application Logic, Policy Updater, and Event Collector. Security Controller consists of Security Policy Manager and NSF Capability Manager. This document explains a data model to perform the missions for a security service (i.e., VoIP-VoLTE) in I2NSF security management system. Status of This Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. Jeong, et al. Expires September 14, 2017 [Page 1] Internet-Draft Consumer-Facing Interface Data Model March 2017 The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on September 14, 2017. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Architecture of Security Management . . . . . . . . . . . . . 5 5.1. I2NSF User . . . . . . . . . . . . . . . . . . . . . . . . 6 5.2. Security Management System . . . . . . . . . . . . . . . . 7 5.3. NSF Instances . . . . . . . . . . . . . . . . . . . . . . 7 6. Use Case: VoIP-VoLTE Security Service . . . . . . . . . . . . 7 6.1. Security Management for VoIP-VoLTE Security Service . . . 8 6.2. Data Modeling for VoIP-VoLTE Security Service . . . . . . 8 6.3. YANG Data Model for VoIP-VoLTE Security Service . . . . . 11 7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 9.1. Normative References . . . . . . . . . . . . . . . . . . . 19 9.2. Informative References . . . . . . . . . . . . . . . . . . 19 Appendix A. Changes from draft-jeong-i2nsf-consumer-facing-interface-dm-00 . . 19 Jeong, et al. Expires September 14, 2017 [Page 2] Internet-Draft Consumer-Facing Interface Data Model March 2017 1. Introduction Basically, information model and data model are used to defining the managed objects in the network management. Despite of some overlapped details, they have different characters in the view of network management. Generally, the main purpose of information model is to model managed objects at a conceptual level, with no dependent of any specific implementations or protocols. To make a clear overall design, the information model should hide all protocol and implementation details defining relationships between managed objects. Based on this, the information models can be implemented in different ways and mapped on different protocols. They are neutral to protocols. In general, information models can be defined in an informal way, using natural languages such as English. Furthermore, it seems advisable to use object-oriented techniques to describe an information model. Data models are defined at a lower level of abstraction and provide many details. They provide details about the implementation and protocols' specification, e.g., rules that explain how to map managed objects onto lower-level protocol constructs. Since conceptual models can be implemented in different ways, multiple data models can be derived by a single information model. The impressive role of the network functions virtualization (NFV) in the network management leads to a rapid advent of NFV in this industry. As practical applications, network security functions (NSFs), such as firewall, intrusion detection system (IDS) and intrusion protection system (IPS), can also be provided as virtual network functions (VNF). By virtual technology, these VNFs might be automatically provisioned and dynamically migrated based on real-time security requirements. This document presents an information model to implement security functions based on NFV. This document proposes a data modeling in an architecture for security management [i2nsf-security-mgnt], which is based on I2NSF framework [i2nsf-framework], the requirements and information model for I2NSF consumer-facing interface (i.e., client-facing interface) to security controller [client-facing-inf-req] [client-facing-inf-im]. This I2NSF framework contains I2NSF User, Security Management System (i.e., Security Controller and Developer's Management System), and NSFs in the NSF instance layer. The security management architecture has more detailed structures for core components in the I2NSF framework. I2NSF User includes Application Logic, Policy Updater, and Event Collector. Security Controller contains Security Policy Manager and NSF Capability Manager. Application Logic generates a high-level policy and Policy Updater Jeong, et al. Expires September 14, 2017 [Page 3] Internet-Draft Consumer-Facing Interface Data Model March 2017 sends it to Security Policy Manager via Consumer-Facing Interface. Security Policy Manager maps the high-level policy into several low- level policies in Security Controller. After mapping, the low-level policies are distributed to NSF(s) via NSF-Facing Interface so that they can be enforced in them. When an event occurs for NSF to change a low-level policy, NSF sends the event to Security Controller via NSF-Facing Interface. Security Controller then forwards it to Event Collector via Consumer-Facing Interface. Next, Event Collector sends it to Application Logic. Application Logic then updates the current policies in accordance with the event. This document proposes a data model for security services in the security management architecture in [i2nsf-security-mgnt] so that the security management architecture can support flexible and effective security policies. 2. Objectives The two main objectives for security management architecture in this document are as follows: o High-level security management: To propose the design of a generic security management architecture to support the enforcement of flexible and effective security policies in NSFs. o Automatic update of security policies: To provide the reflection of the updated low-level security policies for new security attacks on the corresponding high-level security policies. 3. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC3444]. 4. Terminology This document uses the terminology described in [i2nsf-framework][i2nsf-security-mgnt]. In addition, the following terms are defined below: o Application Logic: It is a component in the security management architecture which generates high-level security policies to block or mitigate security attacks. o Policy Updater: It is a component which forwards a high-level security policy to Security Controller. The high-level policy is received from Application Logic. Jeong, et al. Expires September 14, 2017 [Page 4] Internet-Draft Consumer-Facing Interface Data Model March 2017 o Security Policy Manager: It maps a high-level security policy received from Policy Updater into low-level security policies, and vice versa. o NSF Capability Manager: It is a component which stores the NSF capability registered by Developer's Management System via Registration Interface and shares it with Security Policy Manger to generate the corresponding low-level security policies. o Event Collector: It is a component which receives an event from Security Controller, which should be reflected by updating (or generating) a high-level policy in Application Logic. 5. Architecture of Security Management Generally, Data models are often represented in formal data definition languages that are specific to the management protocol being used. Based on NFV, the structure of the proposed model is based on VNFs to provide a flexible and effective security policies. Figure 1 illustrates the structure of the suggested model. The architecture is designed based on three layers: I2NSF user, security management system, and NSF instances. The high level security policies are defined and distributed in the I2NSF user layer. Translating the high level security policies relevant to NSF capability and delivering them to NSF interfaces are performed in the security management system. Jeong, et al. Expires September 14, 2017 [Page 5] Internet-Draft Consumer-Facing Interface Data Model March 2017 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | I2NSF User | | +-+-+-+-+-+-+-+-+-+-+-+ | | ---| Application Logic |<-- | | | +-+-+-+-+-+-+-+-+-+-+-+ | | | | | | | | | | | +-+-+-+v+-+-+-+-+-+ +-+-+-+v+-+-+-+ | | | Policy Updater | | Event | | | +-+-+-+-+-+-+-+-+-+ | Collector | | | | +-+-+-+^+-+-+-+ | | | | | | | | | | | ------------------- | +-+-+-+-+-+-+-+-+-+-+-+-+-+|+-+-|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Consumer-Facing Interface | | Consumer-Facing Interface +-+-+-+-+-+-+-+-+-+-+-+-+-+|+-+-|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Security Management System| | | | +-+-+-+-+-+-+-+-+-+v+-+-+-+-+ | | |Security Controller | | | | +-+-+-+-+-+ +-+-+-+-+-+-+ | Registration | | | |Security | |NSF | | Interface +-+-+-+-+-+-+-+ | | | |Policy | |Capability | |<----------->| Developer's | | | | |Manager | |Manager | | | Mgnt System | | | | +-+-+-+-+-+ +-+-+-+-+-+-+ | +-+-+-+-+-+-+-+ | | +-+-+-+-+-+-^-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |--------------------------------- NSF-Facing Interface +-+-+-+-+-+-+-|-+-+-+-+-+-+|+-+-+-+-+-+-+-+-+-+|+-+-+-+-+-+-+-+-+-+-+ |NSF Instances| | | | | +-+-+v+-+-+ +-+-+v+-+-+ +-+-+v+-+-+ | | | NSF-1 | | NSF-2 | . . . | NSF-n | | | +-+-+-+-+-+ +-+-+-+-+-+ +-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: Security Management Architecture in I2NSF 5.1. I2NSF User I2NSF User layer consists of three components; Application logic, Policy Updater, and Event Collector. The Application logic is a component which generates high level security policies. To this end, it receives the event for updating (or generating) a high level policy from Event collector and updates (or generates) a high level policy based on the collected events. After that, the high level policy is sent to Policy updater in order to distribute it to Security controller(s). In order to update (or generate) a high level policy, Event collector receives the events sent by Security Jeong, et al. Expires September 14, 2017 [Page 6] Internet-Draft Consumer-Facing Interface Data Model March 2017 controller and sends them to Application logic. Based on these feedbacks, the Application logic can update (or generate) high level security policies. 5.2. Security Management System In the security management system layer, the Security policy manager receives a high level policy from Policy updater via Consumer-Facing Interface and maps this policy into several low level policies. These low level policies are relevant to a given NSF capability that is registered into NSF capability manager. Moreover, Security policy manager delivers those policies to NSF(s) via NSF-Facing Interface. To generate low level policies relevant to a given NSF capability, the NSF capability manager stores an NSF's capability registered by Developer's management system and shares it with Security policy manager. Whenever a new NSF is registered, NSF capability manager requests Developer's management system to register the NSF's capability into the management table of NSF capability manager via Registration Interface. Developer's management system is another part of security management system to registers a new NSF's capability into NSF capability manager. 5.3. NSF Instances All NSFs are located at this layer. After mapping the high level policies to low level policies, the Security policy manager delivers those policies to NSF(s) through NSF-Facing Interface. 6. Use Case: VoIP-VoLTE Security Service As a use case for implementation, VoIP-VoLTE security management is considered to develop a data model. Based on this, the VoIP-VoLTE security manager acts as Application logic for VoIP-VoLTE security services and defines the security conditions. Based on VoIP-VoLTE security management, the list of illegal devices information is stored in VoIP-VoLTE database and can be updated either manually or automatically by VoIP-VoLTE security manager. To define the policies, information of dangerous domain blacklists (e.g., IP addresses and source ports), time management (e.g., access time and expire time), user-agent (e.g., priority levels), and Session Initiation Protocol (SIP) URIs of an SIP device that are suspicious of illegal call or authentication is published by VoIP-VoLTE security manager. Accordingly, ahe list of illegal devices, which is automatically (or manually) updated, is stored in VoIP-VoLTE database. The VoIP-VoLTE security manager periodically loads this list to generate a new high level security policy (e.g., the blocking list of illegal devices using IP address, source ports, etc) to Jeong, et al. Expires September 14, 2017 [Page 7] Internet-Draft Consumer-Facing Interface Data Model March 2017 prevent the delivery of packets from/to those newly added VoIP-VoLTE attackers. When the NSF detects an anomalous message or call delivered from a domain, the information of the domain such as an IP address, user- agents and expire time values is sent by an NSF to Security controller via NSF-Facing Interface. Security controller delivers it to Event collector. Event collector forwards the detected domain information to VoIP-VoLTE security manager, and then VoIP-VoLTE security manager updates the VoIP-VoLTE database. 6.1. Security Management for VoIP-VoLTE Security Service VoIP-VoLTE security management maintains and publishes the blacklists of IP addresses, source ports, expire time, user-agents, and Session Initiation Protocol (SIP) URIs of SIP device that are suspicious of illegal call and authentication. In our generic security management architecture, VoIP-VoLTE Security Manager is plays the role of Application Logic for VoIP-VoLTE security services in Figure 1. Based on VoIP-VoLTE security management, the list of illegal devices information can be updated either manually or automatically by VoIP- VoLTE Security Manager as Application Logic. Also, VoIP-VoLTE Security Manager periodically generates a new high-level security policy to prevent the delivery of packets from/to those newly added VoIP-VoLTE attackers and enforce the low-level security policies in NSF. It sends the new high-level security policy to Policy Updater, which forwards it to Security Controller. When the NSF detects an anomalous message or call delivered from a domain, the domain information such as an IP address, user-agents and expire time values is sent by an NSF to Security Controller via NSF Facing Interface. Security Controller delivers it to Event Collector. Event Collector forwards the detected domain information to VoIP-VoLTE Security Manager, and then VoIP-VoLTE Security Manager updates the VoIP-VoLTE database. 6.2. Data Modeling for VoIP-VoLTE Security Service The data model for VoIP-VoLTE Security Service is derived from i2nsf consumer-facing interface information model. The main objective of this data model is to fully transform the information model into a YANG data model that can be used for delivering security policies to successfully orchestrate control or management messages between the components in the proposed security management architecture. The sementics of the data model must align with those of client- facing interface to security controller information model. The Jeong, et al. Expires September 14, 2017 [Page 8] Internet-Draft Consumer-Facing Interface Data Model March 2017 transformation of the information model was done by hand, and thus, certain changes were made to reflect the fact that this is a YANG data model. This data model is a framework that can be extended according to the security needs. In other words, the model design is independent of the content and meaning of specific policies, as well as the implementation approach. Here, the volte/voip security service is used as an example case for policy rule generation. To implement the model, three parameters have been considered to define the high level policies; blacklisting countries, time interval specification, and caller's priority levels. If the administrator sets a new high-level security policy, a data model parser in I2NSF User interprets the policy and generates an XML file in accordance with a YANG data model. In order to enable interaction between I2NSF User and Security management system, a communication channel based on RESTCONF is implemented. Basically, the data model is defined based on the security policy requirements to detect the suspicious calls in VoIP-VoLTE service. Figure 2 shows a generic data model of VoIP- VoLTE security service. +--: (ieft-i2nsf-policy) +--rw policy-lifecycle-list | +--rw policy-lifecycle-container *(policy-lifecycle-id) | +--rw expiration-event | | +--rw enabled boolean | | +--rw event-id uint 16 | | +--rw event-date date-and-time | +--rw expiration-time | +--rw enabled boolean | +--rw time date-and-time +--rw policy-rule-list | +--rw policy-rule-container *[policy-rule-id] | +--rw policy-rule-id uint 16 | +--rw policy-name string | +--rw policy-date date-and-time | +--rw service | | +--voip-handling boolean | | +--volte-handling boolean | +--rw condition *[condition-id] | +--rw caller | | +--rw caller-id uint 16 | | +--rw caller-location | | +--rw country string | | +--rw city string | +--rw callee | | +--rw callee-id uint 16 Jeong, et al. Expires September 14, 2017 [Page 9] Internet-Draft Consumer-Facing Interface Data Model March 2017 | | +--rw callee-location | | +--rw country string | | +--rw city string | +--rw valid-time-interval | +--rw start-time data-and-time | +--rw end-time data-and-time +--rw action-list | +--rw action-container | +--rw action-date date-and-time | +--rw action-name string | +--: (action-name-ingress) | | +--rw permit? boolean | | +--rw mirror? boolean | | +--rw log? boolean | +--: (action-name-engress) | +--rw redirection? boolean | +--rw update-list +--rw update-container *(update-id) +--rw update-event | +--rw update-event-id uint 16 | +--rw update-enabled boolean | +--rw update-event-date date-and-time | +--rw update-log string +--rw update-time date-and-time Figure 2: Generic Data Model for VoIP-VoLTE Security Service The data model consists of policy life cycle management, policy rule, and action. The policy life cycle field specifies an expiration time and/or a set of expiration events to determine the life-time of the policy itself. The policy rule field represents the specific information about a high-level policy such as service types, conditions and valid time interval. The action field specifies which actions should be taken. For example, call traffic from a blacklisted caller location at an unusual time of day (included in the valid-time-interval) could be blocked and sequentially forwarded to a pre-defined host for Deep Packet Inspection (DPI) when both permit and mirror are assigned true. To translate a high level policy into a set of low level policies, the security management system is implemented. After translating the high-level security policy, Security management system generates low- level security policies to specify the actions network traffic from and/or to those IP addresses. The data model parser generates an XML _le for a low-level security policy and delivers it to proper NSF instances. Security management system also interprets security events generated by NSF into a high-level log message in a YANG data Jeong, et al. Expires September 14, 2017 [Page 10] Internet-Draft Consumer-Facing Interface Data Model March 2017 model and delivers it to I2NSF Users in the opposite direction. In this case, we select a firewall application as an NSF instance to determine whether a VoIP-VoLTE call is suspicious or not by checking the caller's and callee's locations and call time. When a call has suspicious behavior patterns, its network traffic could be effectively blocked by the firewall application according to the low- level security policy. The results for the firewall application would be delivered in a YANG data model to the Security management system through the RESTCONF protocol. Multiple NSF instances can be considered depending on specific situations. For example, additionally DPI can be used for analyzing the network traffic from suspicious callers. 6.3. YANG Data Model for VoIP-VoLTE Security Service This section describes a YANG data model for VoIP-VoLTE security service, which is based on the information of consumer-facing interface to security controller [client-facing-inf-im]. file "ietf-i2nsf-consumer-facing-interface.yang" module ietf-i2nsf-consumer-facing-interface { namespace "urn:ietf:params:xml:ns:yang:ietf-i2nsf-consumer-facing-interface"; prefix capability-interface; import ietf-yang-types { prefix yang; } organization "IETF I2NSF (Interface to Network Security Functions) Working Group"; contact "WG Web: WG List: WG Chair: Adrian Farrel WG Chair: Linda Dunbar Editor: Jaehoon Paul Jeong "; Jeong, et al. Expires September 14, 2017 [Page 11] Internet-Draft Consumer-Facing Interface Data Model March 2017 description "This module defines a YANG data module for consumer-facing interface to security controller."; revision "2016-11-13"{ description "Initial revision"; reference "draft-kumar-i2nsf-client-facing-interface-im-01"; } //Groupings grouping policy { description "policy is a grouping including a set of security rules according to certain logic, i.e., their similarity or mutual relations, etc. The network security policy is able to apply over both the unidirectional and bidirectional traffic across the NSF."; list policy-lifecycle { key "policy-lifecycle-id"; description "The ID of the policy lifecycle for each policy. This must be unique."; leaf policy-lifecycle-id { type uint16; mandatory true; description "This is policy lifecycle-id."; } container expiration-event { description "The event which makes the policy expired."; leaf enabled { type boolean; mandatory true; description "This represents whether the policy is enabled or disabled."; } leaf event-id { type uint16; mandatory true; description "The ID of the event. This must be unique."; Jeong, et al. Expires September 14, 2017 [Page 12] Internet-Draft Consumer-Facing Interface Data Model March 2017 } leaf event-date { type yang:date-and-time; mandatory true; description "The date when the event is triggered."; } } container expiration-time { description "The time when the policy is expired."; leaf enabled { type boolean; mandatory true; description "This represents whether the policy is enabled or disabled."; } leaf time { type yang:date-and-time; mandatory true; description "The time when the policy is enabled."; } } } list policy-rule { key "policy-rule-id"; description "The ID of the policy rule. This is key for policy-rule-list. This must be unique."; leaf policy-name { type string; mandatory true; description "The name of the policy. This must be unique."; } leaf policy-rule-id { type uint16; mandatory true; Jeong, et al. Expires September 14, 2017 [Page 13] Internet-Draft Consumer-Facing Interface Data Model March 2017 description "The ID of the policy rule. This must be unique."; } leaf policy-rule-date { type yang:date-and-time; mandatory true; description "The date when the date-and-time when the policy is created."; } container service { description "The services which NSFs could perform to manage the security attacks. This consists of voip-handling and volte-handling. This will be extended in later version."; leaf voip-handling { type boolean; mandatory true; description "This field represents whether the policy contains handling the voip packet flow."; } leaf volte-handling { type boolean; mandatory true; description "This field represents whether the policy contains handling the volte packet flow."; } } list condition { key "condition-id"; description "The ID of the condition. This must be unique."; leaf condition-id { type uint16; mandatory true; description "This is condition id"; } Jeong, et al. Expires September 14, 2017 [Page 14] Internet-Draft Consumer-Facing Interface Data Model March 2017 container caller { description "The caller of VoIP-VoLTE call"; leaf caller-id { type uint16; mandatory true; description "The ID of the caller. This must be unique."; } container caller-location { description "The location of the caller."; leaf country { type string; mandatory true; description "The country of the caller."; } leaf city { type string; mandatory true; description "The city of the caller."; } } } container callee { description "The callee of VoIP-VoLTE call."; leaf callee-id { type uint16; mandatory true; description "The ID of the callee. This must be unique."; } container callee-location { description "The location of the callee."; leaf country { type string; Jeong, et al. Expires September 14, 2017 [Page 15] Internet-Draft Consumer-Facing Interface Data Model March 2017 mandatory true; description "The country of the callee."; } leaf city { type string; mandatory true; description "The city of the callee."; } } } container valid-time-interval { description "The time when the policy starts or ends to be valid."; leaf start-time { type yang:date-and-time; mandatory true; description "The time when the policy starts to be valid."; } leaf end-time { type yang:date-and-time; mandatory true; description "The time when the policy ends to be valid."; } } } } container action { description "TBD"; choice action-type { description "The flow-based NSFs realize the network security functions by executing various Actions, which at least includes ingress-action, egress-action, and advanced-action."; case ingress-action { description Jeong, et al. Expires September 14, 2017 [Page 16] Internet-Draft Consumer-Facing Interface Data Model March 2017 "The ingress actions consist of permit, mirror and log."; leaf permit { type boolean; mandatory true; description "Packet flow is permitted or denyed."; } leaf mirror { type boolean; mandatory true; description "Packet flow is mirroried."; } leaf log { type boolean; mandatory true; description "Packet flow is logged."; } } case engress-type { description "The egress action consists of redirection. TBD"; leaf redirection { type boolean; mandatory true; description "Packet flow is redireted."; } } container update { description "The event which makes the policy expired."; leaf update-id { type uint16; mandatory true; description "The policy update-id to distingush each update. This must be unique."; } Jeong, et al. Expires September 14, 2017 [Page 17] Internet-Draft Consumer-Facing Interface Data Model March 2017 leaf update-event-id { type uint16; mandatory true; description "The ID of the event. This must be unique."; } leaf update-enabled { type boolean; mandatory true; description "The update is enabled or disabled."; } leaf update-event-date { type yang:date-and-time; mandatory true; description "The date when the update-event is triggered."; } leaf update-log { type boolean; mandatory true; description "To log update and its description"; } } } } } } Figure 3: YANG Data Model for VoIP-VoLTE Security Service 7. Security Considerations The security management architecture is derived from the I2NSF framework [i2nsf-framework], so the security considerations of the I2NSF framework should be included in this document. Especially, proper secure communication channels should be used for the delivery of control or management messages amongst the components in the proposed architecture. 8. Acknowledgements This work was supported by Institute for Information & communications Technology Promotion(IITP) grant funded by the Korea government(MSIP) Jeong, et al. Expires September 14, 2017 [Page 18] Internet-Draft Consumer-Facing Interface Data Model March 2017 (No.R-20160222-002755, Cloud based Security Intelligence Technology Development for the Customized Security Service Provisioning). This document has greatly benefited from inputs by Hyoungshick Kim, Hoon Ko, Sanghak Oh, Eunsoo Kim, Jinyong Tim Kim, Daeyoung Hyun, and Se- Hui Lee. 9. References 9.1. Normative References [RFC3444] Pras, A., "On the Difference between Information Models and Data Models", RFC 3444, January 2003. 9.2. Informative References [i2nsf-framework] Lopez, D., Lopez, E., Dunbar, L., Strassner, J., and R. Kumar, "Framework for Interface to Network Security Functions", draft-ietf-i2nsf-framework-04 (work in progress), October 2016. [i2nsf-security-mgnt] Kim, H., Ko, H., Oh, S., Jeong, J., and S. Lee, "An Architecture for Security Management in I2NSF Framework", draft-kim- i2nsf-security-management-architecture-03 (work in progress), October 2016. [client-facing-inf-req] Kumar, R., Lohiya, A., Qi, D., Bitar, N., Palislamovic, S., and L. Xia, "Requirements for Client-Facing Interface to Security Controller", draft-ietf-i2nsf-client-facing- interface-req-00 (work in progress), October 2016. [client-facing-inf-im] Kumar, R., Lohiya, A., Qi, D., Bitar, N., Palislamovic, S., and L. Xia, "Information model for Client-Facing Interface to Security Controller", draft-kumar-i2nsf- client-facing-interface-im-01 (work in progress), October 2016. Appendix A. Changes from draft-jeong-i2nsf-consumer-facing-interface-dm-00 The following changes are made from draft-jeong-i2nsf-consumer-facing-interface-dm-00: Jeong, et al. Expires September 14, 2017 [Page 19] Internet-Draft Consumer-Facing Interface Data Model March 2017 o Miscellaneous expressions in the whole descriptions are corrected. o A YANG data model is clarified to efficiently support VoIP-VoLTE security services. Authors' Addresses Jaehoon Paul Jeong Department of Software Sungkyunkwan University 2066 Seobu-Ro, Jangan-Gu Suwon, Gyeonggi-Do 16419 Republic of Korea Phone: +82 31 299 4957 Fax: +82 31 290 7996 EMail: pauljeong@skku.edu URI: http://iotlab.skku.edu/people-jaehoon-jeong.php Mahdi Daghmehchi Firoozjaei Department of Electical and Computer Enginering Sungkyunkwan University 2066 Seobu-Ro, Jangan-Gu Suwon, Gyeonggi-Do 16419 Republic of Korea Phone: +82-31-299-4104 EMail: mdaghmechi@skku.edu Tae-Jin Ahn Korea Telecom 70 Yuseong-Ro, Yuseong-Gu Daejeon 305-811 Republic of Korea Phone: +82 42 870 8409 EMail: taejin.ahn@kt.com Jeong, et al. Expires September 14, 2017 [Page 20] Internet-Draft Consumer-Facing Interface Data Model March 2017 Rakesh Kumar Juniper Networks 1133 Innovation Way Sunnyvale, CA 94089 USA Phone: EMail: rkkumar@juniper.net Susan Hares Huawei 7453 Hickory Hill Saline, MI 48176 USA Phone: +1-734-604-0332 EMail: shares@ndzh.com Jeong, et al. Expires September 14, 2017 [Page 21]