idnits 2.17.1 draft-bryskin-netconf-automation-framework-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 16, 2017) is 2377 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC7950' is defined on line 209, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-supa-generic-policy-data-model' is defined on line 213, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-supa-generic-policy-info-model' is defined on line 219, but no explicit reference was found in the text == Outdated reference: A later version (-26) exists of draft-ietf-netconf-subscribed-notifications-05 == Outdated reference: A later version (-25) exists of draft-ietf-netconf-yang-push-10 Summary: 0 errors (**), 0 flaws (~~), 6 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group I. Bryskin 3 Internet-Draft Huawei Technologies 4 Intended status: Informational X. Liu 5 Expires: April 19, 2018 Jabil 6 A. Clemm 7 Huawei 8 H. Birkholz 9 Fraunhofer SIT 10 T. Zhou 11 Huawei 12 October 16, 2017 14 YANG PUSH Based Generalized Network Control Automation Problem Statement 15 draft-bryskin-netconf-automation-framework-00 17 Abstract 19 This document describes the objective of the YANG PUSH based 20 generalized network control automation framework. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on April 19, 2018. 39 Copyright Notice 41 Copyright (c) 2017 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Objective . . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 59 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 60 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 61 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 63 6.2. Informative References . . . . . . . . . . . . . . . . . 5 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 66 1. Introduction 68 YANG "Custom Subscription to Event Notifications" model 69 [I-D.ietf-netconf-subscribed-notifications] allows for a network 70 client automation of network remote monitoring. Specifically, using 71 this model, a network client can subscribe on and receive one or more 72 data streams, each associated with one or more events defined by YANG 73 model(s) governing the network's YANG data store(s). The client can 74 also tailor said streams to its needs by specifying filters on the 75 streams contents, but, otherwise, the client has no control on the 76 stream contents. For example, the client has no way of expanding a 77 stream to carry additional information that was not defined to be a 78 part of said stream. 80 YANG "Subscribing to YANG datastore push updates" model 81 [I-D.ietf-netconf-yang-push], which is an augmentation of the "Custom 82 Subscription to Event Notifications" model, defines a higher level of 83 network remote monitoring automation - it allows for the client 84 itself to define the origins, trigger/maintain conditions and 85 contents of data streams to be sent by the network to the client. 86 This capability is modeled via target-trigger-notify constructs, 87 which allow for the client to specify data store nodes of interest 88 and, possibly, sub-trees rooted by them (targets), conditions to 89 trigger and maintain associated with them streams (e.g. particular 90 change(s) in one or more of the nodes attributes), the contents of 91 the streams and filters to further fine-tune the streams according to 92 the client's needs. 94 It could be observed that the notify part of the target-trigger- 95 notify construct stands for "send me notification', which is one of, 96 generally speaking, many actions the client might want the network to 97 perform, provided that the target-trigger condition holds. For 98 example, instead of sending a notification with some pre-denied 99 content, the client might want the network to perform: 101 a. immediate network re-configuration (e.g. modification of one or 102 more attributes of one or more CONFIG=TRUE data store nodes); 104 b. scheduling one time or periodic such reconfigurations in the 105 future; 107 c. calling an RPC defined by one of the YANG models supported by the 108 network ( e.g. calling network's path computer to evaluate 109 whether an alternative/more optimal path is available for a given 110 connection); 112 d. Dynamic linking/unlinking parent and child data stores supported 113 by the network; 115 e. etc. 117 It could also be observed that "periodic" and "on-change" are two of 118 the conditions that the client might want. The conditions can be 119 expanded to be a logical expression of other event states and some 120 operational data states of the network., as well, as outputs of RPCs. 122 2. Objective 124 The main objective of the YANG PUSH Based Generalized Network Control 125 Automation framework is to generalize the target-trigger-notify 126 construct into event-condition-action construct, where: 128 event 129 a particular change in the network state explicitly defined by one 130 of the YANG models supported by the network or implicitly defined 131 by the client, which is constantly monitored by the network; 133 condition 134 a logical expression that is evaluated only once after the 135 associated event is detected; 137 action 138 an operation (non-exhaustive list of which is described above) to 139 be carried out by the network when the associated event is 140 detected and the associated condition is met. 142 The client will be able to describe the desired network behavior by 143 configuring with the network event-condition-action triplets as rules 144 prior to any services provided by the network to the client. Such an 145 approach will take the client out of the network control loop, thus, 146 changing the client's role from being network's "micro-manager" to 147 being network's "police officer", which interferes into network 148 operations only in exceptional/unpredicted situations. 150 There are numerous benefits to such paradigm, including: 152 o lower latency, faster responsiveness of the network to various 153 events/conditions; 155 o better scale (e.g. the client may control more networks because it 156 does not have to monitor/micro-manage any of them); 158 o CPU and bandwidth savings due to the reduced amount of 159 communication between the client and the network. 161 It is envisioned that the YANG PUSH Based Generalized Network Control 162 Automation framework will fit well within "SUPA Policy-based 163 Management Framework" 164 [I-D.ietf-supa-policy-based-management-framework], which will 165 inherently provide a higher level of automation, for example, by: 167 a. combining multiple micro-conditions into a single macro-condition 168 via a number of logical operations; 170 b. combining multiple micro-actions into a single transaction with a 171 possibility of specifying policies with respect to handling 172 errors/exceptions of each of the transaction components. 174 3. IANA Considerations 176 This document has no actions for IANA. 178 4. Security Considerations 180 This document does not define networking protocols and data, hence 181 are not directly responsible for security risks. 183 5. Acknowledgements 185 6. References 187 6.1. Normative References 189 [I-D.ietf-netconf-subscribed-notifications] 190 Voit, E., Clemm, A., Prieto, A., Nilsen-Nygaard, E., and 191 A. Tripathy, "Custom Subscription to Event Notifications", 192 draft-ietf-netconf-subscribed-notifications-05 (work in 193 progress), October 2017. 195 [I-D.ietf-netconf-yang-push] 196 Clemm, A., Voit, E., Prieto, A., Tripathy, A., Nilsen- 197 Nygaard, E., Bierman, A., and B. Lengyel, "Subscribing to 198 YANG datastore push updates", draft-ietf-netconf-yang- 199 push-10 (work in progress), October 2017. 201 [I-D.ietf-supa-policy-based-management-framework] 202 LIU, W., Xie, C., Strassner, J., Karagiannis, G., Klyus, 203 M., and J. Bi, "SUPA Policy-based Management Framework", 204 draft-ietf-supa-policy-based-management-framework-03 (work 205 in progress), July 2017. 207 6.2. Informative References 209 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 210 RFC 7950, DOI 10.17487/RFC7950, August 2016, 211 . 213 [I-D.ietf-supa-generic-policy-data-model] 214 Halpern, J. and J. Strassner, "Generic Policy Data Model 215 for Simplified Use of Policy Abstractions (SUPA)", draft- 216 ietf-supa-generic-policy-data-model-04 (work in progress), 217 June 2017. 219 [I-D.ietf-supa-generic-policy-info-model] 220 Strassner, J., Halpern, J., and S. Meer, "Generic Policy 221 Information Model for Simplified Use of Policy 222 Abstractions (SUPA)", draft-ietf-supa-generic-policy-info- 223 model-03 (work in progress), May 2017. 225 Authors' Addresses 227 Igor Bryskin 228 Huawei Technologies 230 EMail: Igor.Bryskin@huawei.com 232 Xufeng Liu 233 Jabil 235 EMail: Xufeng_Liu@jabil.com 236 Alexander Clemm 237 Huawei 239 EMail: ludwig@clemm.org 241 Henk Birkholz 242 Fraunhofer SIT 244 EMail: henk.birkholz@sit.fraunhofer.de 246 Tianran Zhou 247 Huawei 249 EMail: zhoutianran@huawei.com