idnits 2.17.1 draft-liu-netmod-yang-schedule-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 : ---------------------------------------------------------------------------- ** 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 (March 20, 2016) is 2952 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 86, but not defined == Unused Reference: 'RFC6021' is defined on line 200, but no explicit reference was found in the text == Unused Reference: 'RFC2234' is defined on line 207, but no explicit reference was found in the text == Unused Reference: 'RFC6087' is defined on line 213, 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) -- Obsolete informational reference (is this intentional?): RFC 6087 (Obsoleted by RFC 8407) Summary: 3 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: September 20, 2016 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 March 20, 2016 15 A YANG Data Model for Configuration Scheduling 16 draft-liu-netmod-yang-schedule-00 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 September 20, 2015. 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. Configuration Scheduling YANG Data Model Overview..............3 66 3. Configuration Scheduling YANG Module...........................3 67 4. Security Considerations........................................5 68 5. References.....................................................5 69 5.1. Normative References......................................5 70 5.2. Informative References....................................5 72 1. Introduction 74 This document introduces a YANG [RFC6020] data model grouping for 75 configuration scheduling. This grouping can be used in other YANG 76 data models to specify a schedule applied on a configuration schema 77 node, so that the schema node can take effect according to the 78 schedule. 80 1.1. Terminology 82 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 84 "OPTIONAL" in this document are to be interpreted as described in BCP 85 14, [RFC2119]. 87 The following terms are defined in [RFC6020] and are not redefined 88 here: 90 o augment 91 o data model 93 o data node 95 2. Configuration Scheduling YANG Data Model Overview 97 This document defines a grouping "schedules" in the YANG module 98 "ietf-schedule". Specifying this grouping for a YANG schema node 99 allows to specify configuration schedules for the data objects 100 modeled by this schema node. When such a schedule exists, system will 101 configure the specified object according to the specified schedule. 102 The grouping has the following structure: 104 module: ietf-schedule 105 grouping schedules: 106 +--rw schedules 107 +--rw schedule* [schedule-id] 108 +--rw schedule-id uint32 109 +--rw start? yang:date-and-time 110 +--rw schedule-duration? string 111 +--rw repeat-interval? string 113 3. Configuration Scheduling YANG Module 115 file "ietf-schedule@2016-03-01.yang" 116 module ietf-schedule { 117 yang-version 1; 118 namespace "urn:ietf:params:xml:ns:yang:ietf-schedule"; 119 // replace with IANA namespace when assigned 121 prefix "sch"; 123 import ietf-yang-types { 124 prefix "yang"; 125 } 127 organization "TBD"; 128 contact "TBD"; 129 description 130 "The model allows time scheduling parameters to be specified."; 132 revision "2016-03-01" { 133 description "Initial revision"; 134 reference "TBD"; 135 } 137 /* 138 * Groupings 139 */ 141 grouping schedules { 142 description 143 "A list of schedules defining when a particular 144 configuration takes effect."; 145 container schedules { 146 description 147 "Container of a schedule list defining when a particular 148 configuration takes effect."; 149 list schedule { 150 key "schedule-id"; 151 description "A list of schedule elements."; 153 leaf schedule-id { 154 type uint32; 155 description "Identifies the schedule element."; 156 } 157 leaf start { 158 type yang:date-and-time; 159 description "Start time."; 160 } 161 leaf schedule-duration { 162 type string { 163 pattern 164 'P(\d+Y)?(\d+M)?(\d+W)?(\d+D)?T(\d+H)?(\d+M)?(\d+S)?'; 165 } 166 description "Schedule duration in ISO 8601 format."; 167 } 168 leaf repeat-interval { 169 type string { 170 pattern 171 'R\d*/P(\d+Y)?(\d+M)?(\d+W)?(\d+D)?T(\d+H)?(\d+M)?' 172 + '(\d+S)?'; 173 } 174 description "Repeat interval in ISO 8601 format."; 176 } 177 } 178 } 179 } // schedules 180 } 181 183 4. Security Considerations 185 The configuration, state, action and notification data defined in 186 this document are designed to be accessed via the NETCONF protocol 187 [RFC6241]. The data-model by itself does not create any security 188 implications. The security considerations for the NETCONF protocol 189 are applicable. The NETCONF protocol used for sending the data 190 supports authentication and encryption. 192 5. References 194 5.1. Normative References 196 [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the 197 Network Configuration Protocol (NETCONF)", RFC 6020, 198 October 2010. 200 [RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021, 201 October 2010. 203 [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. Bierman, 204 "Network Configuration Protocol (NETCONF)", RFC 6241, June 205 2011. 207 [RFC2234] Crocker, D. and Overell, P.(Editors), "Augmented BNF for 208 Syntax Specifications: ABNF", RFC 2234, Internet Mail 209 Consortium and Demon Internet Ltd., November 1997. 211 5.2. Informative References 213 [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG 214 Data Model Documents", RFC 6087, January 2011. 216 Authors' Addresses 218 Xufeng Liu 219 Ericsson / Kuatro Technologies Inc. 220 8281 Greensboro Drive, Suite 200 221 McLean, VA 22102 222 USA 224 Email: xliu@kuatrotech.com 226 Igor Bryskin 227 Huawei Technologies 228 Email: Igor.Bryskin@huawei.com 230 Vishnu Pavan Beeram 231 Juniper Networks 232 Email: vbeeram@juniper.net 234 Tarek Saad 235 Cisco Systems Inc 236 Email: tsaad@cisco.com 238 Himanshu Shah 239 Ciena 240 Email: hshah@ciena.com 242 Oscar Gonzalez de Dios 243 Telefonica 244 Email: oscar.gonzalezdedios@telefonica.com