idnits 2.17.1 draft-liu-netmod-yang-schedule-01.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 : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 17, 2016) is 2750 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2119' is mentioned on line 88, but not defined == Unused Reference: 'RFC6021' is defined on line 272, but no explicit reference was found in the text == Unused Reference: 'RFC2234' is defined on line 279, but no explicit reference was found in the text == Unused Reference: 'RFC6087' is defined on line 288, but no explicit reference was found in the text ** Obsolete normative reference: RFC 6021 (Obsoleted by RFC 6991) ** Obsolete normative reference: RFC 2234 (Obsoleted by RFC 4234) ** Downref: Normative reference to an Informational RFC: RFC 7399 -- Obsolete informational reference (is this intentional?): RFC 6087 (Obsoleted by RFC 8407) Summary: 4 errors (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group X. Liu 2 Internet-Draft Ericsson 3 Intended status: Standards Track I. Bryskin 4 Expires: March 17, 2017 Huawei Technologies 5 V. Beeram 6 Juniper Networks 7 T. Saad 8 Cisco Systems Inc 9 H. Shah 10 Ciena 11 O. Gonzalez de Dios 12 Telefonica 13 September 17, 2016 15 A YANG Data Model for Configuration Scheduling 16 draft-liu-netmod-yang-schedule-01 18 Abstract 20 This document describes a data model grouping for configuration 21 scheduling. 23 Status of this Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF), its areas, and its working groups. Note that 30 other groups may also distribute working documents as Internet- 31 Drafts. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 The list of current Internet-Drafts can be accessed at 39 http://www.ietf.org/ietf/1id-abstracts.txt 41 The list of Internet-Draft Shadow Directories can be accessed at 42 http://www.ietf.org/shadow.html 44 This Internet-Draft will expire on March 17, 2017. 46 Copyright Notice 48 Copyright (c) 2016 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction...................................................2 64 1.1. Terminology...............................................2 65 2. Motivation.....................................................3 66 3. Configuration Scheduling YANG Data Model Overview..............3 67 4. Usage Example..................................................3 68 5. Configuration Scheduling YANG Module...........................4 69 6. Security Considerations........................................6 70 7. References.....................................................7 71 7.1. Normative References......................................7 72 7.2. Informative References....................................7 74 1. Introduction 76 This document introduces a YANG [RFC6020] data model grouping for 77 configuration scheduling. This grouping can be used in other YANG 78 data models to specify a schedule applied on a configuration schema 79 node, so that the schema node can take effect according to the 80 schedule. 82 1.1. Terminology 84 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 85 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 86 "OPTIONAL" in this document are to be interpreted as described in BCP 87 14, [RFC2119]. 89 The following terms are defined in [RFC6020] and are not redefined 90 here: 92 o augment 94 o data model 96 o data node 98 2. Motivation 100 Some applications benefit from resource scheduling to allow operators 101 to plan ahead of time. Traffic engineering is one of such examples 102 [RFC7399]. When configuration and state models are designed for such 103 applications, it has been considered that certain data objects need 104 to be configured according to predefined schedules. In other 105 situations, operators need to de-configure certain data objects at 106 predefined schedules for the purposes such as maintenance. These data 107 objects are interpreted and implemented by the applicable 108 applications. 110 3. Configuration Scheduling YANG Data Model Overview 112 This document defines a grouping "schedules" in the YANG module 113 "ietf-schedule". Specifying this grouping for a YANG schema node 114 allows to specify configuration schedules for the data objects 115 modeled by this schema node. When such a schedule exists, system will 116 configure the specified object according to the specified schedule. 117 The grouping has the following structure: 119 module: ietf-schedule 120 grouping schedules: 121 +--rw schedules 122 +--rw schedule* [schedule-id] 123 +--rw schedule-id uint32 124 +--rw inclusive-exclusive? enumeration 125 +--rw start? yang:date-and-time 126 +--rw schedule-duration? string 127 +--rw repeat-interval? string 129 4. Usage Example 131 The following model defines a list of TE (Traffic Engineering) links 132 which can be configured with specified schedules: 134 +--rw te-link* [id] 135 +--rw id string 136 +--rw schedules 137 +--rw schedule* [schedule-id] 138 +--rw schedule-id uint32 139 +--rw inclusive-exclusive? enumeration 140 +--rw start? yang:date-and-time 141 +--rw schedule-duration? string 142 +--rw repeat-interval? String 144 The following configuration requests that 146 o link-1 is configured weekly for five one-day periods, starting 147 from 2016-09-12T23:20:50.52Z. 149 o link-1 is de-configured for two hours, starting from 2016-09- 150 15T01:00:00.00Z. 152 153 link-1 154 155 156 11 157 2016-09-12T23:20:50.52Z 158 P1D 159 R5/P1W 160 161 162 163 164 link-2 165 166 12 167 exclusive 168 2016-09-15T01:00:00.00Z 169 P2H 170 171 173 5. Configuration Scheduling YANG Module 175 file "ietf-schedule@2016-08-28.yang" 176 module ietf-schedule { 177 yang-version 1; 178 namespace "urn:ietf:params:xml:ns:yang:ietf-schedule"; 179 // replace with IANA namespace when assigned 181 prefix "sch"; 183 import ietf-yang-types { 184 prefix "yang"; 185 } 187 organization "TBD"; 188 contact "TBD"; 189 description 190 "The model allows time scheduling parameters to be specified."; 192 revision "2016-08-28" { 193 description "Initial revision"; 194 reference "TBD"; 195 } 197 /* 198 * Groupings 199 */ 201 grouping schedules { 202 description 203 "A list of schedules defining when a particular 204 configuration takes effect."; 205 container schedules { 206 description 207 "Container of a schedule list defining when a particular 208 configuration takes effect."; 209 list schedule { 210 key "schedule-id"; 211 description "A list of schedule elements."; 213 leaf schedule-id { 214 type uint32; 215 description "Identifies the schedule element."; 216 } 217 leaf inclusive-exclusive { 218 type enumeration { 219 enum inclusive { 220 description "The schedule element is inclusive."; 221 } 222 enum exclusive { 223 description "The schedule element is exclusive."; 224 } 225 } 226 default "inclusive"; 227 description 228 "Whether the list item is inclusive or exclusive."; 229 } 230 leaf start { 231 type yang:date-and-time; 232 description "Start time."; 233 } 234 leaf schedule-duration { 235 type string { 236 pattern 237 'P(\d+Y)?(\d+M)?(\d+W)?(\d+D)?T(\d+H)?(\d+M)?(\d+S)?'; 238 } 239 description "Schedule duration in ISO 8601 format."; 240 } 241 leaf repeat-interval { 242 type string { 243 pattern 244 'R\d*/P(\d+Y)?(\d+M)?(\d+W)?(\d+D)?T(\d+H)?(\d+M)?' 245 + '(\d+S)?'; 246 } 247 description "Repeat interval in ISO 8601 format."; 248 } 249 } 250 } 251 } // schedules 252 } 253 255 6. Security Considerations 257 The configuration, state, action and notification data defined in 258 this document are designed to be accessed via the NETCONF protocol 259 [RFC6241]. The data-model by itself does not create any security 260 implications. The security considerations for the NETCONF protocol 261 are applicable. The NETCONF protocol used for sending the data 262 supports authentication and encryption. 264 7. References 266 7.1. Normative References 268 [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the 269 Network Configuration Protocol (NETCONF)", RFC 6020, 270 October 2010. 272 [RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021, 273 October 2010. 275 [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. Bierman, 276 "Network Configuration Protocol (NETCONF)", RFC 6241, June 277 2011. 279 [RFC2234] Crocker, D. and Overell, P.(Editors), "Augmented BNF for 280 Syntax Specifications: ABNF", RFC 2234, Internet Mail 281 Consortium and Demon Internet Ltd., November 1997. 283 [RFC7399] Farrel, A. and King, D., "Unanswered Questions in the Path 284 Computation Element Architecture", RFC 7399, October 2014. 286 7.2. Informative References 288 [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG 289 Data Model Documents", RFC 6087, January 2011. 291 Authors' Addresses 293 Xufeng Liu 294 Ericsson / Kuatro Technologies Inc. 295 8281 Greensboro Drive, Suite 200 296 McLean, VA 22102 297 USA 299 Email: xliu@kuatrotech.com 301 Igor Bryskin 302 Huawei Technologies 303 Email: Igor.Bryskin@huawei.com 305 Vishnu Pavan Beeram 306 Juniper Networks 307 Email: vbeeram@juniper.net 309 Tarek Saad 310 Cisco Systems Inc 311 Email: tsaad@cisco.com 313 Himanshu Shah 314 Ciena 315 Email: hshah@ciena.com 317 Oscar Gonzalez de Dios 318 Telefonica 319 Email: oscar.gonzalezdedios@telefonica.com