Network Working Group X. Liu
Internet-Draft Ericsson
Intended status: Standards Track I. Bryskin
Expires: March 17, 2017 Huawei Technologies
V. Beeram
Juniper Networks
T. Saad
Cisco Systems Inc
H. Shah
Ciena
O. Gonzalez de Dios
Telefonica
September 17, 2016
A YANG Data Model for Configuration Scheduling
draft-liu-netmod-yang-schedule-01
Abstract
This document describes a data model grouping for configuration
scheduling.
Status of this Memo
This Internet-Draft is submitted 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
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on March 17, 2017.
Liu, et al. Expires March 17, 2016 [Page 1]
Internet-Draft draft-liu-netmod-yang-schedule-01 September 2017
Copyright Notice
Copyright (c) 2016 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...................................................2
1.1. Terminology...............................................2
2. Motivation.....................................................3
3. Configuration Scheduling YANG Data Model Overview..............3
4. Usage Example..................................................3
5. Configuration Scheduling YANG Module...........................4
6. Security Considerations........................................6
7. References.....................................................7
7.1. Normative References......................................7
7.2. Informative References....................................7
1. Introduction
This document introduces a YANG [RFC6020] data model grouping for
configuration scheduling. This grouping can be used in other YANG
data models to specify a schedule applied on a configuration schema
node, so that the schema node can take effect according to the
schedule.
1.1. Terminology
The keywords "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 BCP
14, [RFC2119].
The following terms are defined in [RFC6020] and are not redefined
here:
Liu, et al. Expires March 17, 2017 [Page 2]
Internet-Draft draft-liu-netmod-yang-schedule-01 September 2017
o augment
o data model
o data node
2. Motivation
Some applications benefit from resource scheduling to allow operators
to plan ahead of time. Traffic engineering is one of such examples
[RFC7399]. When configuration and state models are designed for such
applications, it has been considered that certain data objects need
to be configured according to predefined schedules. In other
situations, operators need to de-configure certain data objects at
predefined schedules for the purposes such as maintenance. These data
objects are interpreted and implemented by the applicable
applications.
3. Configuration Scheduling YANG Data Model Overview
This document defines a grouping "schedules" in the YANG module
"ietf-schedule". Specifying this grouping for a YANG schema node
allows to specify configuration schedules for the data objects
modeled by this schema node. When such a schedule exists, system will
configure the specified object according to the specified schedule.
The grouping has the following structure:
module: ietf-schedule
grouping schedules:
+--rw schedules
+--rw schedule* [schedule-id]
+--rw schedule-id uint32
+--rw inclusive-exclusive? enumeration
+--rw start? yang:date-and-time
+--rw schedule-duration? string
+--rw repeat-interval? string
4. Usage Example
The following model defines a list of TE (Traffic Engineering) links
which can be configured with specified schedules:
+--rw te-link* [id]
+--rw id string
+--rw schedules
Liu, et al. Expires March 17, 2017 [Page 3]
Internet-Draft draft-liu-netmod-yang-schedule-01 September 2017
+--rw schedule* [schedule-id]
+--rw schedule-id uint32
+--rw inclusive-exclusive? enumeration
+--rw start? yang:date-and-time
+--rw schedule-duration? string
+--rw repeat-interval? String
The following configuration requests that
o link-1 is configured weekly for five one-day periods, starting
from 2016-09-12T23:20:50.52Z.
o link-1 is de-configured for two hours, starting from 2016-09-
15T01:00:00.00Z.
<te-link>
<id>link-1</id>
<schedules>
<schedule>
<schedule-id>11<schedule-id>
<start>2016-09-12T23:20:50.52Z</start>
<schedule-duration>P1D</schedule-duration>
<repeat-interval>R5/P1W</repeat-interval>
<schedule>
</schedules>
</te-link>
<te-link>
<id>link-2</id>
<schedules>
<schedule-id>12<schedule-id>
<inclusive-exclusive>exclusive</inclusive-exclusive>
<start>2016-09-15T01:00:00.00Z</start>
<schedule-duration>P2H</schedule-duration>
</schedules>
</te-link>
5. Configuration Scheduling YANG Module
<CODE BEGINS> file "ietf-schedule@2016-08-28.yang"
module ietf-schedule {
yang-version 1;
namespace "urn:ietf:params:xml:ns:yang:ietf-schedule";
Liu, et al. Expires March 17, 2017 [Page 4]
Internet-Draft draft-liu-netmod-yang-schedule-01 September 2017
// replace with IANA namespace when assigned
prefix "sch";
import ietf-yang-types {
prefix "yang";
}
organization "TBD";
contact "TBD";
description
"The model allows time scheduling parameters to be specified.";
revision "2016-08-28" {
description "Initial revision";
reference "TBD";
}
/*
* Groupings
*/
grouping schedules {
description
"A list of schedules defining when a particular
configuration takes effect.";
container schedules {
description
"Container of a schedule list defining when a particular
configuration takes effect.";
list schedule {
key "schedule-id";
description "A list of schedule elements.";
leaf schedule-id {
type uint32;
description "Identifies the schedule element.";
}
leaf inclusive-exclusive {
type enumeration {
enum inclusive {
Liu, et al. Expires March 17, 2017 [Page 5]
Internet-Draft draft-liu-netmod-yang-schedule-01 September 2017
description "The schedule element is inclusive.";
}
enum exclusive {
description "The schedule element is exclusive.";
}
}
default "inclusive";
description
"Whether the list item is inclusive or exclusive.";
}
leaf start {
type yang:date-and-time;
description "Start time.";
}
leaf schedule-duration {
type string {
pattern
'P(\d+Y)?(\d+M)?(\d+W)?(\d+D)?T(\d+H)?(\d+M)?(\d+S)?';
}
description "Schedule duration in ISO 8601 format.";
}
leaf repeat-interval {
type string {
pattern
'R\d*/P(\d+Y)?(\d+M)?(\d+W)?(\d+D)?T(\d+H)?(\d+M)?'
+ '(\d+S)?';
}
description "Repeat interval in ISO 8601 format.";
}
}
}
} // schedules
}
<CODE ENDS>
6. Security Considerations
The configuration, state, action and notification data defined in
this document are designed to be accessed via the NETCONF protocol
[RFC6241]. The data-model by itself does not create any security
implications. The security considerations for the NETCONF protocol
Liu, et al. Expires March 17, 2017 [Page 6]
Internet-Draft draft-liu-netmod-yang-schedule-01 September 2017
are applicable. The NETCONF protocol used for sending the data
supports authentication and encryption.
7. References
7.1. Normative References
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010.
[RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021,
October 2010.
[RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. Bierman,
"Network Configuration Protocol (NETCONF)", RFC 6241, June
2011.
[RFC2234] Crocker, D. and Overell, P.(Editors), "Augmented BNF for
Syntax Specifications: ABNF", RFC 2234, Internet Mail
Consortium and Demon Internet Ltd., November 1997.
[RFC7399] Farrel, A. and King, D., "Unanswered Questions in the Path
Computation Element Architecture", RFC 7399, October 2014.
7.2. Informative References
[RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG
Data Model Documents", RFC 6087, January 2011.
Liu, et al. Expires March 17, 2017 [Page 7]
Internet-Draft draft-liu-netmod-yang-schedule-01 September 2017
Authors' Addresses
Xufeng Liu
Ericsson / Kuatro Technologies Inc.
8281 Greensboro Drive, Suite 200
McLean, VA 22102
USA
Email: xliu@kuatrotech.com
Igor Bryskin
Huawei Technologies
Email: Igor.Bryskin@huawei.com
Vishnu Pavan Beeram
Juniper Networks
Email: vbeeram@juniper.net
Tarek Saad
Cisco Systems Inc
Email: tsaad@cisco.com
Himanshu Shah
Ciena
Email: hshah@ciena.com
Oscar Gonzalez de Dios
Telefonica
Email: oscar.gonzalezdedios@telefonica.com
Liu, et al. Expires March 17, 2017 [Page 8]