draft-ietf-lmap-yang-10.txt   draft-ietf-lmap-yang-11.txt 
Network Working Group J. Schoenwaelder Network Working Group J. Schoenwaelder
Internet-Draft V. Bajpai Internet-Draft V. Bajpai
Intended status: Standards Track Jacobs University Bremen Intended status: Standards Track Jacobs University Bremen
Expires: July 15, 2017 January 11, 2017 Expires: August 26, 2017 February 22, 2017
A YANG Data Model for LMAP Measurement Agents A YANG Data Model for LMAP Measurement Agents
draft-ietf-lmap-yang-10.txt draft-ietf-lmap-yang-11.txt
Abstract Abstract
This document defines a data model for Large-Scale Measurement This document defines a data model for Large-Scale Measurement
Platforms (LMAP). The data model is defined using the YANG data Platforms (LMAP). The data model is defined using the YANG data
modeling language. modeling language.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 15, 2017. This Internet-Draft will expire on August 26, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 19 skipping to change at page 2, line 19
1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3
2. Data Model Overview . . . . . . . . . . . . . . . . . . . . . 3 2. Data Model Overview . . . . . . . . . . . . . . . . . . . . . 3
3. Relationship to the Information Model . . . . . . . . . . . . 8 3. Relationship to the Information Model . . . . . . . . . . . . 8
4. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 10 4. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 10
4.1. LMAP Common YANG Module . . . . . . . . . . . . . . . . . 10 4.1. LMAP Common YANG Module . . . . . . . . . . . . . . . . . 10
4.2. LMAP Control YANG Module . . . . . . . . . . . . . . . . 18 4.2. LMAP Control YANG Module . . . . . . . . . . . . . . . . 18
4.3. LMAP Report YANG Module . . . . . . . . . . . . . . . . . 39 4.3. LMAP Report YANG Module . . . . . . . . . . . . . . . . . 39
5. Security Considerations . . . . . . . . . . . . . . . . . . . 44 5. Security Considerations . . . . . . . . . . . . . . . . . . . 44
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 47 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 47
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 47 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 48
8.1. Normative References . . . . . . . . . . . . . . . . . . 47 8.1. Normative References . . . . . . . . . . . . . . . . . . 48
8.2. Informative References . . . . . . . . . . . . . . . . . 48 8.2. Informative References . . . . . . . . . . . . . . . . . 48
Appendix A. Example Parameter Extension Module . . . . . . . . . 49 Appendix A. Example Parameter Extension Module . . . . . . . . . 49
Appendix B. Example Configuration . . . . . . . . . . . . . . . 51 Appendix B. Example Configuration . . . . . . . . . . . . . . . 52
Appendix C. Example Report . . . . . . . . . . . . . . . . . . . 54 Appendix C. Example Report . . . . . . . . . . . . . . . . . . . 55
Appendix D. Change History . . . . . . . . . . . . . . . . . . . 57 Appendix D. Change History . . . . . . . . . . . . . . . . . . . 57
D.1. Non-editorial Changes since -07 . . . . . . . . . . . . . 57 D.1. Non-editorial Changes since -07 . . . . . . . . . . . . . 57
D.2. Non-editorial Changes since -06 . . . . . . . . . . . . . 57 D.2. Non-editorial Changes since -06 . . . . . . . . . . . . . 57
D.3. Non-editorial Changes since -05 . . . . . . . . . . . . . 57 D.3. Non-editorial Changes since -05 . . . . . . . . . . . . . 58
D.4. Non-editorial Changes since -04 . . . . . . . . . . . . . 58 D.4. Non-editorial Changes since -04 . . . . . . . . . . . . . 58
D.5. Non-editorial Changes since -03 . . . . . . . . . . . . . 58 D.5. Non-editorial Changes since -03 . . . . . . . . . . . . . 59
D.6. Non-editorial Changes since -02 . . . . . . . . . . . . . 58 D.6. Non-editorial Changes since -02 . . . . . . . . . . . . . 59
D.7. Non-editorial Changes since -01 . . . . . . . . . . . . . 59 D.7. Non-editorial Changes since -01 . . . . . . . . . . . . . 59
D.8. Non-editorial Changes since -00 . . . . . . . . . . . . . 59 D.8. Non-editorial Changes since -00 . . . . . . . . . . . . . 60
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 60 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 60
1. Introduction 1. Introduction
This document defines a data model for Large-Scale Measurement This document defines a data model for Large-Scale Measurement
Platforms (LMAP) [RFC7594]. The data model is defined using the YANG Platforms (LMAP) [RFC7594]. The data model is defined using the YANG
[RFC7950] data modeling language. It aims to be consistent with the [RFC7950] data modeling language. It aims to be consistent with the
LMAP Information Model [I-D.ietf-lmap-information-model]. LMAP Information Model [I-D.ietf-lmap-information-model].
1.1. Terminology 1.1. Terminology
skipping to change at page 10, line 9 skipping to change at page 10, line 9
o Task Configurations: Configured tasks are modeled in the /lmap/ o Task Configurations: Configured tasks are modeled in the /lmap/
tasks subtree. tasks subtree.
o Event Information: Event definitions are modeled in the /lmap/ o Event Information: Event definitions are modeled in the /lmap/
events subtree. events subtree.
4. YANG Modules 4. YANG Modules
4.1. LMAP Common YANG Module 4.1. LMAP Common YANG Module
This module imports definitions from [RFC6536]. This module imports definitions from [RFC6536] and it references
[ISO-8601].
<CODE BEGINS> file "ietf-lmap-common@2017-01-11.yang" <CODE BEGINS> file "ietf-lmap-common@2017-02-22.yang"
module ietf-lmap-common { module ietf-lmap-common {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-common"; namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-common";
prefix "lmap"; prefix "lmap";
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
} }
skipping to change at page 10, line 41 skipping to change at page 10, line 42
Editor: Vaibhav Bajpai Editor: Vaibhav Bajpai
<v.bajpai@jacobs-university.de>"; <v.bajpai@jacobs-university.de>";
description description
"This module provides common definitions used by the data "This module provides common definitions used by the data
models written for Large-Scale Measurement Platforms (LMAP). models written for Large-Scale Measurement Platforms (LMAP).
This module defines typedefs and groupings but no schema This module defines typedefs and groupings but no schema
tree elements."; tree elements.";
revision "2017-01-11" { revision "2017-02-22" {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXX: A YANG Data Model for LMAP Measurement Agents"; "RFC XXX: A YANG Data Model for LMAP Measurement Agents";
} }
/* /*
* Typedefs * Typedefs
*/ */
skipping to change at page 14, line 51 skipping to change at page 15, line 4
"Saturday of the Gregorian calendar."; "Saturday of the Gregorian calendar.";
} }
enum sunday { enum sunday {
value 7; value 7;
description description
"Sunday of the Gregorian calendar."; "Sunday of the Gregorian calendar.";
} }
} }
description description
"A type modeling the weekdays in the Gregorian calendar. "A type modeling the weekdays in the Gregorian calendar.
The numbering follows the ISO 8601 scheme.";
The numbering follows the ISO 8601 scheme.";
reference
"ISO 8601:2004: Data elements and interchange formats --
Information interchange -- Representation
of dates and times";
} }
typedef weekday-or-all { typedef weekday-or-all {
type union { type union {
type weekday; type weekday;
type wildcard; type wildcard;
} }
description description
"A weekday or a wildcard indicating all seven weekdays."; "A weekday or a wildcard indicating all seven weekdays.";
} }
skipping to change at page 18, line 15 skipping to change at page 18, line 22
} }
} }
} }
<CODE ENDS> <CODE ENDS>
4.2. LMAP Control YANG Module 4.2. LMAP Control YANG Module
This module imports definitions from [RFC6536], [RFC6991] and the This module imports definitions from [RFC6536], [RFC6991] and the
common LMAP module and it references [RFC7398]. common LMAP module and it references [RFC7398].
<CODE BEGINS> file "ietf-lmap-control@2017-01-11.yang" <CODE BEGINS> file "ietf-lmap-control@2017-02-22.yang"
module ietf-lmap-control { module ietf-lmap-control {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-control"; namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-control";
prefix "lmapc"; prefix "lmapc";
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
import ietf-netconf-acm { import ietf-netconf-acm {
skipping to change at page 18, line 51 skipping to change at page 19, line 11
Editor: Vaibhav Bajpai Editor: Vaibhav Bajpai
<v.bajpai@jacobs-university.de>"; <v.bajpai@jacobs-university.de>";
description description
"This module defines a data model for controlling measurement "This module defines a data model for controlling measurement
agents that are part of a Large-Scale Measurement Platform agents that are part of a Large-Scale Measurement Platform
(LMAP). This data model is expected to be implemented by a (LMAP). This data model is expected to be implemented by a
measurement agent."; measurement agent.";
revision "2017-01-11" { revision "2017-02-22" {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXX: A YANG Data Model for LMAP Measurement Agents"; "RFC XXX: A YANG Data Model for LMAP Measurement Agents";
} }
/* /*
* Typedefs * Typedefs
*/ */
skipping to change at page 20, line 14 skipping to change at page 20, line 22
"The date and time when the event object "The date and time when the event object
starts to create triggers."; starts to create triggers.";
} }
leaf end { leaf end {
type yang:date-and-time; type yang:date-and-time;
description description
"The date and time when the event object "The date and time when the event object
stops to create triggers. stops to create triggers.
It is generally a good idea to always configure It is generally a good idea to always configure
an end time and to refresh the configuration an end time and to refresh the end time as needed
of event object as needed to ensure that agents to ensure that agents that lose connectivity to
that loose connectivity to their controller their controller do not continue executing schedules
do not continue their tasks forever."; forever.";
} }
} }
/* /*
* Capability, configuration and state data nodes * Capability, configuration and state data nodes
*/ */
container lmap { container lmap {
description description
"Configuration and control of an LMAP agent."; "Configuration and control of an LMAP agent.";
skipping to change at page 21, line 4 skipping to change at page 21, line 11
} }
leaf-list tag { leaf-list tag {
type lmap:tag; type lmap:tag;
config false; config false;
description description
"An optional unordered set of tags that provide "An optional unordered set of tags that provide
additional information about the capabilities of additional information about the capabilities of
the measurement agent."; the measurement agent.";
} }
container tasks { container tasks {
description description
"A list of tasks that the measurement agent supports."; "A list of tasks that the measurement agent supports.";
list task { list task {
key name; key name;
description description
"The list of tasks supportined by the LMAP agent."; "The list of tasks supported by the LMAP agent.";
leaf name { leaf name {
type lmap:identifier; type lmap:identifier;
description description
"The unique name of a task capability."; "The unique name of a task capability.";
} }
uses lmap:registry-grouping; uses lmap:registry-grouping;
leaf version { leaf version {
skipping to change at page 23, line 51 skipping to change at page 24, line 12
* Task Configuration * Task Configuration
*/ */
container tasks { container tasks {
description description
"Configuration of LMAP tasks."; "Configuration of LMAP tasks.";
list task { list task {
key name; key name;
description description
"The list of tasks configured on the LMAP agent."; "The list of tasks configured on the LMAP agent. Note
that a configured task MUST resolve to a task listed
in the capabilities. Attempts to execute a configured
task that is not listed in the capabilities result in
a runtime execution error.";
leaf name { leaf name {
type lmap:identifier; type lmap:identifier;
description description
"The unique name of a task."; "The unique name of a task.";
} }
uses lmap:registry-grouping; uses lmap:registry-grouping;
leaf program { leaf program {
skipping to change at page 26, line 22 skipping to change at page 26, line 34
enum pipelined { enum pipelined {
value 3; value 3;
description description
"The actions of the schedule are executed in a "The actions of the schedule are executed in a
pipelined mode. Output created by an action is pipelined mode. Output created by an action is
passed as input to the subsequent action."; passed as input to the subsequent action.";
} }
} }
default pipelined; default pipelined;
description description
"The execution mode of this schedule determins in "The execution mode of this schedule determines in
which order the actions of the schedule are executed."; which order the actions of the schedule are executed.";
} }
leaf-list tag { leaf-list tag {
type lmap:tag; type lmap:tag;
description description
"A set of schedule specific tags that are reported "A set of schedule specific tags that are reported
together with the measurement results to a collector."; together with the measurement results to a collector.";
} }
skipping to change at page 28, line 39 skipping to change at page 29, line 4
config false; config false;
description description
"The date and time of the last invocation of "The date and time of the last invocation of
this schedule."; this schedule.";
} }
list action { list action {
key name; key name;
description description
"An action describes a task that is invoked by the "An action describes a task that is invoked by the
schedule. Multiple actions are invoked sequentially."; schedule. Multiple actions are invoked according to
the execution-mode of the schedule.";
leaf name { leaf name {
type lmap:identifier; type lmap:identifier;
description description
"The unique identifier for this action."; "The unique identifier for this action.";
} }
leaf task { leaf task {
type task-ref; type task-ref;
mandatory true; mandatory true;
skipping to change at page 29, line 30 skipping to change at page 29, line 43
uses lmap:options-grouping { uses lmap:options-grouping {
description description
"The list of action specific options that are "The list of action specific options that are
appended to the list of task specific options."; appended to the list of task specific options.";
} }
leaf-list destination { leaf-list destination {
type schedule-ref; type schedule-ref;
description description
"A set of schedules receiving the output produced "A set of schedules receiving the output produced
by this action. A queue is internally used to pass by this action. The output is stored temporarily
results to another schedule. The behaviour of since the destination schedules will in general
an action passing data to its own schedule is not be running when output is passed to them. The
implementation specific. behaviour of an action passing data to its own
schedule is implementation specific.
Data passed to a sequential or pipelined schedule Data passed to a sequential or pipelined schedule
is received by the schedule's first action. Data is received by the schedule's first action. Data
passed to a parallel schedule is received by all passed to a parallel schedule is received by all
actions of the schedule."; actions of the schedule.";
} }
leaf-list tag { leaf-list tag {
type lmap:tag; type lmap:tag;
description description
skipping to change at page 36, line 35 skipping to change at page 36, line 49
case calendar { case calendar {
container calendar { container calendar {
description description
"A calendar timing object triggers based on the "A calendar timing object triggers based on the
current calendar date and time."; current calendar date and time.";
leaf-list month { leaf-list month {
type lmap:month-or-all; type lmap:month-or-all;
min-elements 1; min-elements 1;
description description
"A set of month at which this calendar timing "A set of months at which this calendar timing
will trigger. The wildcard means all months."; will trigger. The wildcard means all months.";
} }
leaf-list day-of-month { leaf-list day-of-month {
type lmap:day-of-months-or-all; type lmap:day-of-months-or-all;
min-elements 1; min-elements 1;
description description
"A set of days of the month at which this "A set of days of the month at which this
calendar timing will trigger. The wildcard means calendar timing will trigger. The wildcard means
all days of a month."; all days of a month.";
} }
leaf-list day-of-week { leaf-list day-of-week {
skipping to change at page 37, line 28 skipping to change at page 37, line 42
description description
"A set of minutes at which this calendar timing "A set of minutes at which this calendar timing
will trigger. The wildcard means all minutes of will trigger. The wildcard means all minutes of
an hour."; an hour.";
} }
leaf-list second { leaf-list second {
type lmap:second-or-all; type lmap:second-or-all;
min-elements 1; min-elements 1;
description description
"A set of second at which this calendar timing "A set of seconds at which this calendar timing
will trigger. The wildcard means all seconds of will trigger. The wildcard means all seconds of
a minute."; a minute.";
} }
leaf timezone-offset { leaf timezone-offset {
type lmap:timezone-offset; type lmap:timezone-offset;
description description
"The timezone in which this calendar timing "The timezone in which this calendar timing
object will be evaluated. If not present, object will be evaluated. If not present,
the systems' local timezone will be used."; the systems' local timezone will be used.";
skipping to change at page 39, line 19 skipping to change at page 39, line 32
} }
} }
} }
<CODE ENDS> <CODE ENDS>
4.3. LMAP Report YANG Module 4.3. LMAP Report YANG Module
This module imports definitions from [RFC6536] and the common LMAP This module imports definitions from [RFC6536] and the common LMAP
module. module.
<CODE BEGINS> file "ietf-lmap-report@2017-01-11.yang" <CODE BEGINS> file "ietf-lmap-report@2017-02-22.yang"
module ietf-lmap-report { module ietf-lmap-report {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-report"; namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-report";
prefix "lmapr"; prefix "lmapr";
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
import ietf-lmap-common { import ietf-lmap-common {
skipping to change at page 40, line 5 skipping to change at page 40, line 18
Editor: Vaibhav Bajpai Editor: Vaibhav Bajpai
<v.bajpai@jacobs-university.de>"; <v.bajpai@jacobs-university.de>";
description description
"This module defines a data model for reporting results from "This module defines a data model for reporting results from
measurement agents, which are part of a Large-Scale Measurement measurement agents, which are part of a Large-Scale Measurement
Platform (LMAP), to result data collectors. This data model is Platform (LMAP), to result data collectors. This data model is
expected to be implemented by a collector."; expected to be implemented by a collector.";
revision "2017-01-11" { revision "2017-02-22" {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXX: A YANG Data Model for LMAP Measurement Agents"; "RFC XXX: A YANG Data Model for LMAP Measurement Agents";
} }
rpc report { rpc report {
description description
"The report operation is used by an LMAP measurement agent to "The report operation is used by an LMAP measurement agent to
submit measurement results produced by measurement tasks to submit measurement results produced by measurement tasks to
skipping to change at page 46, line 14 skipping to change at page 46, line 28
used to predict time periods where measurements used to predict time periods where measurements
take place (or do not take place). take place (or do not take place).
Some of the RPC operations in this YANG module may be considered Some of the RPC operations in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control access to these operations. These are the important to control access to these operations. These are the
operations and their sensitivity/vulnerability: operations and their sensitivity/vulnerability:
/report The report operation is used to send locally collected /report The report operation is used to send locally collected
measurement results to a remote collector. Unauthorized measurement results to a remote collector. Unauthorized
access may leak measurement results. access may leak measurement results, including from passive
measurements.
The data model uses a number of identifiers that are set by the The data model uses a number of identifiers that are set by the
controller. Implementors may find these identifiers useful for the controller. Implementors may find these identifiers useful for the
identification of resources, e.g., to identify objects in a identification of resources, e.g., to identify objects in a
filesystem providing temporary storage. Since the identifiers used filesystem providing temporary storage. Since the identifiers used
by the YANG data model may allow characters that may be given special by the YANG data model may allow characters that may be given special
interpretation in a specific context, implementations MUST ensure interpretation in a specific context, implementations must ensure
that identifiers are properly mapped into safe identifiers. that identifiers are properly mapped into safe identifiers.
The data model allows to specify options in the form of name value The data model allows to specify options in the form of name value
pairs that are passed to programs. Implementers MUST taken care that pairs that are passed to programs. Implementers ought to take care
option names and values are passed literally to programs. In that option names and values are passed literally to programs. In
particular, it MUST be avoided that any shell expansions are particular, shell expansions that may alter option names and values
performed that may alter the option names and values. must not be performed.
6. IANA Considerations 6. IANA Considerations
This document registers a URI in the "IETF XML Registry" [RFC3688]. This document registers a URI in the "IETF XML Registry" [RFC3688].
Following the format in RFC 3688, the following registrations have Following the format in RFC 3688, the following registrations have
been made. been made.
URI: urn:ietf:params:xml:ns:yang:ietf-lmap-common URI: urn:ietf:params:xml:ns:yang:ietf-lmap-common
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
skipping to change at page 47, line 25 skipping to change at page 47, line 40
name: ietf-lmap-report name: ietf-lmap-report
namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-report namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-report
prefix: lmapr prefix: lmapr
reference: RFC XXXX reference: RFC XXXX
7. Acknowledgements 7. Acknowledgements
Several people contributed to this specification by reviewing early Several people contributed to this specification by reviewing early
versions and actively participating in the LMAP working group versions and actively participating in the LMAP working group
(apologies to those unintentionally omitted): Marcelo Bagnulo, Martin (apologies to those unintentionally omitted): Marcelo Bagnulo, Martin
Bjorklund, Trevor Burbridge, Timothy Carey, Philip Eardley, Al Bjorklund, Trevor Burbridge, Timothy Carey, Alissa Cooper, Philip
Morton, Dan Romascanu, Andrea Soppera, and Barbara Stark. Eardley, Al Morton, Dan Romascanu, Andrea Soppera, and Barbara Stark.
Juergen Schoenwaelder and Vaibhav Bajpai worked in part on the Leone Juergen Schoenwaelder and Vaibhav Bajpai worked in part on the Leone
research project, which received funding from the European Union research project, which received funding from the European Union
Seventh Framework Programme [FP7/2007-2013] under grant agreement Seventh Framework Programme [FP7/2007-2013] under grant agreement
number 317647. number 317647.
Juergen Schoenwaelder and Vaibhav Bajpai were partly funded by Juergen Schoenwaelder and Vaibhav Bajpai were partly funded by
Flamingo, a Network of Excellence project (ICT-318488) supported by Flamingo, a Network of Excellence project (ICT-318488) supported by
the European Commission under its Seventh Framework Programme. the European Commission under its Seventh Framework Programme.
skipping to change at page 48, line 19 skipping to change at page 48, line 33
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<http://www.rfc-editor.org/info/rfc7950>. <http://www.rfc-editor.org/info/rfc7950>.
8.2. Informative References 8.2. Informative References
[I-D.ietf-lmap-information-model] [I-D.ietf-lmap-information-model]
Burbridge, T., Eardley, P., Bagnulo, M., and J. Burbridge, T., Eardley, P., Bagnulo, M., and J.
Schoenwaelder, "Information Model for Large-Scale Schoenwaelder, "Information Model for Large-Scale
Measurement Platforms (LMAP)", draft-ietf-lmap- Measurement Platforms (LMAP)", draft-ietf-lmap-
information-model-13 (work in progress), November 2016. information-model-16 (work in progress), January 2017.
[I-D.ietf-netconf-netconf-client-server] [I-D.ietf-netconf-netconf-client-server]
Watsen, K., Wu, G., and J. Schoenwaelder, "NETCONF Client Watsen, K., Wu, G., and J. Schoenwaelder, "NETCONF Client
and Server Models", draft-ietf-netconf-netconf-client- and Server Models", draft-ietf-netconf-netconf-client-
server-01 (work in progress), November 2016. server-01 (work in progress), November 2016.
[I-D.ietf-netmod-entity] [I-D.ietf-netmod-entity]
Bierman, A., Bjorklund, M., Dong, J., and D. Romascanu, "A Bierman, A., Bjorklund, M., Dong, J., and D. Romascanu, "A
YANG Data Model for Hardware Management", draft-ietf- YANG Data Model for Hardware Management", draft-ietf-
netmod-entity-01 (work in progress), October 2016. netmod-entity-02 (work in progress), January 2017.
[ISO-8601]
International Organization for Standardization, "Data
elements and interchange formats -- Information
interchange -- Representation of dates and times", ISO
Standard 8601:2004, 2004.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>. <http://www.rfc-editor.org/info/rfc3688>.
[RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, DOI 10 [RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, DOI 10
.17487/RFC5424, March 2009, .17487/RFC5424, March 2009,
<http://www.rfc-editor.org/info/rfc5424>. <http://www.rfc-editor.org/info/rfc5424>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
skipping to change at page 53, line 16 skipping to change at page 53, line 41
<start>controller-lost</start> <start>controller-lost</start>
<end>controller-connected</end> <end>controller-connected</end>
<match>measurement:*</match> <match>measurement:*</match>
</suppression> </suppression>
</suppressions> </suppressions>
<tasks> <tasks>
<!-- configuration of an update-ping-targets task --> <!-- configuration of an update-ping-targets task -->
<task> <task>
<name>update-ping-targets</name> <name>update-ping-targets</name>
<program>/usr/bin/fping-update-targets</program> <program>fping-update-targets</program>
</task> </task>
<!-- configuration of a ping-all-targets task --> <!-- configuration of a ping-all-targets task -->
<task> <task>
<name>ping-all-targets</name> <name>ping-all-targets</name>
<program>/usr/bin/fping</program> <program>fping</program>
</task> </task>
<!-- configuration of a traceroute task --> <!-- configuration of a traceroute task -->
<task> <task>
<name>traceroute</name> <name>traceroute</name>
<program>/usr/bin/mtr</program> <program>mtr</program>
<option> <option>
<id>csv</id> <id>csv</id>
<name>--csv</name> <name>--csv</name>
</option> </option>
</task> </task>
<!-- configuration of a reporter task --> <!-- configuration of a reporter task -->
<task> <task>
<name>report</name> <name>report</name>
<program>/usr/bin/lmap-report</program> <program>lmap-report</program>
</task> </task>
<task> <task>
<name>ippm-udp-latency-client</name> <name>ippm-udp-latency-client</name>
<program>/usr/bin/ippm-udp-latency</program> <program>ippm-udp-latency</program>
<function> <function>
<uri>urn:example:tbd</uri> <uri>urn:example:tbd</uri>
<role>client</role> <role>client</role>
</function> </function>
<tag>active</tag> <tag>active</tag>
</task> </task>
</tasks> </tasks>
<events> <events>
<!-- The event E1 triggers every hour during September 2016 <!-- The event E1 triggers every hour during September 2016
 End of changes. 38 change blocks. 
49 lines changed or deleted 67 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/