draft-ietf-lmap-yang-01.txt   draft-ietf-lmap-yang-02.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: January 4, 2016 July 3, 2015 Expires: May 4, 2016 November 1, 2015
A YANG Data Model for LMAP Measurement Agents A YANG Data Model for LMAP Measurement Agents
draft-ietf-lmap-yang-01.txt draft-ietf-lmap-yang-02.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 January 4, 2016. This Internet-Draft will expire on May 4, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 13 skipping to change at page 2, line 13
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 2 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 2
2. Data Model Overview . . . . . . . . . . . . . . . . . . . . . 3 2. Data Model Overview . . . . . . . . . . . . . . . . . . . . . 3
3. Relationship to the Information Model . . . . . . . . . . . . 6 3. Relationship to the Information Model . . . . . . . . . . . . 6
4. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 7 4. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 28 5. Security Considerations . . . . . . . . . . . . . . . . . . . 33
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 29 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 34
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 29 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.1. Normative References . . . . . . . . . . . . . . . . . . 29 8.1. Normative References . . . . . . . . . . . . . . . . . . 34
8.2. Informative References . . . . . . . . . . . . . . . . . 29 8.2. Informative References . . . . . . . . . . . . . . . . . 35
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 30 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 35
Appendix B. Non-editorial Changes since -06 . . . . . . . . . . 30 Appendix B. Non-editorial Changes since -01 . . . . . . . . . . 36
Appendix C. Example Configuration (XML) . . . . . . . . . . . . 30 Appendix C. Non-editorial Changes since -00 . . . . . . . . . . 36
Appendix D. Example Configuration (JSON) . . . . . . . . . . . . 34 Appendix D. Example Configuration (XML) . . . . . . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38 Appendix E. Example Configuration (JSON) . . . . . . . . . . . . 40
Appendix F. Example State (XML) . . . . . . . . . . . . . . . . 44
Appendix G. Example State (JSON) . . . . . . . . . . . . . . . . 45
Appendix H. Example Report (XML) . . . . . . . . . . . . . . . . 47
Appendix I. Example Report (JSON) . . . . . . . . . . . . . . . 50
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 54
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) [I-D.ietf-lmap-framework]. The data model is Platforms (LMAP) [RFC7594]. The data model is defined using the YANG
defined using the YANG [RFC6020] data modeling language. It aims to [RFC6020] data modeling language. It aims to be consistent with the
be consistent with the LMAP Information Model LMAP Information Model [I-D.ietf-lmap-information-model].
[I-D.ietf-lmap-information-model].
1.1. Terminology 1.1. Terminology
This document uses the LMAP terminology defined in This document uses the LMAP terminology defined in [RFC7594].
[I-D.ietf-lmap-framework].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
1.2. Tree Diagrams 1.2. Tree Diagrams
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in these diagrams is as this document. The meaning of the symbols in these diagrams is as
follows: follows:
o Brackets "[" and "]" enclose list keys. o Brackets "[" and "]" enclose list keys.
o Abbreviations before data node names: "rw" means configuration o Abbreviations before data node names: "rw" means configuration
(read-write), and "ro" means state data (read-only). (read-write), "ro" means state data (read-only), and "w" means RPC
input date (write-only).
o Symbols after data node names: "?" means an optional node, "!" o Symbols after data node names: "?" means an optional node, "!"
means a presence container, and "*" denotes a list and leaf-list. means a presence container, and "*" denotes a list and leaf-list.
o Parentheses enclose choice and case nodes, and case nodes are also o Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":"). marked with a colon (":").
o Ellipsis ("...") stands for contents of subtrees that are not o Ellipsis ("...") stands for contents of subtrees that are not
shown. shown.
2. Data Model Overview 2. Data Model Overview
The tree diagram below shows the structure of the configuration The tree diagram below shows the structure of the configuration data
model. model.
module: ietf-lmap-control module: ietf-lmap-control
+--rw lmap +--rw lmap
+--rw agent +--rw agent
| +--rw agent-id? yang:uuid | +--rw agent-id? yang:uuid
| +--rw device-id? inet:uri | +--rw device-id? inet:uri
| +--rw group-id? string | +--rw group-id? string
| +--rw report-agent-id? boolean | +--rw measurement-point? string
| +--rw controller-timeout? uint32 | +--rw report-agent-id? boolean
+--rw schedules | +--rw report-measurement-point? boolean
| +--rw schedule* [name] | +--rw controller-timeout? uint32
| +--rw name string +--rw schedules
| +--rw event -> /lmap/events/event/name | +--rw schedule* [name]
| +--rw action* [name] | +--rw name string
| | +--rw name string | +--rw event -> /lmap/events/event/name
| | +--rw task -> /lmap/tasks/task/name | +--rw action* [name]
| | +--rw option* [name] | | +--rw name string
| | | +--rw name string | | +--rw task -> /lmap/tasks/task/name
| | | +--rw value? string | | +--rw option* [name]
| | +--rw destination* -> /lmap/schedules/schedule/name | | | +--rw name string
| +--rw execution-mode enumeration | | | +--rw value? string
+--rw suppression | | +--rw destination* -> /lmap/schedules/schedule/name
| +--rw enabled? boolean | | +--rw suppression-tag* lmap-common:tag-type
| +--rw stop-running? boolean | +--rw execution-mode? enumeration
| +--rw start? yang:date-and-time | +--rw suppression-tag* lmap-common:tag-type
| +--rw end? yang:date-and-time +--rw suppressions
| +--rw task* -> /lmap/tasks/task/name | +--rw suppression* [name]
| +--rw schedule* -> /lmap/schedules/schedule/name | +--rw name string
+--rw tasks | +--rw start? -> /lmap/events/event/name
| +--rw task* [name] | +--rw end? -> /lmap/events/event/name
| +--rw name string | +--rw tag* union
| +--rw (task-identification) | +--rw stop-running? boolean
| | +--:(registry) +--rw tasks
| | | +--rw registry* inet:uri | +--rw task* [name]
| | +--:(program) | +--rw name string
| | +--rw program? string | +--rw metric* [uri]
| +--rw option* [name] | | +--rw uri inet:uri
| | +--rw name string | | +--rw role* string
| | +--rw value? string | +--rw program? string
| +--rw tag* string | +--rw option* [name]
| +--rw suppress-by-default? boolean | | +--rw name string
+--rw events | | +--rw value? string
+--rw event* [name] | +--rw tag* string
+--rw name string | +--rw suppress-by-default? boolean
+--rw (event-type)? +--rw events
| +--:(periodic) +--rw event* [name]
| | +--rw periodic +--rw name string
| | +--rw interval uint32 +--rw (event-type)?
| | +--rw start? yang:date-and-time | +--:(periodic)
| | +--rw end? yang:date-and-time | | +--rw periodic
| +--:(calendar) | | +--rw interval uint32
| | +--rw calendar | | +--rw start? yang:date-and-time
| | +--rw month* union | | +--rw end? yang:date-and-time
| | +--rw weekday* union | +--:(calendar)
| | +--rw day-of-month* union | | +--rw calendar
| | +--rw hour* union | | +--rw month* union
| | +--rw minute* union | | +--rw weekday* union
| | +--rw second* union | | +--rw day-of-month* union
| | +--rw timezone-offset? timezone-offset | | +--rw hour* union
| | +--rw start? yang:date-and-time | | +--rw minute* union
| | +--rw end? yang:date-and-time | | +--rw second* union
| +--:(one-off) | | +--rw timezone-offset? lmap-common:timezone-offset
| | +--rw one-off-time yang:date-and-time | | +--rw start? yang:date-and-time
| +--:(immediate) | | +--rw end? yang:date-and-time
| | +--rw immediate empty | +--:(one-off)
| +--:(startup) | | +--rw one-off-time yang:date-and-time
| +--rw startup empty | +--:(immediate)
+--rw random-spread? int32 | | +--rw immediate empty
| +--:(startup)
| | +--rw startup empty
| +--:(controller-lost)
| | +--rw controller-lost empty
| +--:(controller-ok)
| +--rw controller-ok empty
+--rw random-spread? int32
The tree diagram below shows the structure of the state model. The tree diagram below shows the structure of the state data model.
module: ietf-lmap-control module: ietf-lmap-control
+--ro lmap-state +--ro lmap-state
+--ro agent +--ro agent
| +--ro agent-id yang:uuid | +--ro agent-id yang:uuid
| +--ro device-id inet:uri | +--ro device-id inet:uri
| +--ro hardware string | +--ro hardware string
| +--ro firmware string | +--ro firmware string
| +--ro version string | +--ro version string
| +--ro last-started yang:date-and-time | +--ro last-started yang:date-and-time
+--ro tasks +--ro tasks
+--ro task* [name] | +--ro task* [name]
+--ro name string | +--ro name string
+--ro (task-identification) | +--ro metric* [uri]
| +--:(registry) | | +--ro uri inet:uri
| | +--ro registry* inet:uri | | +--ro role* string
| +--:(program) | +--ro version? string
| +--ro program? string | +--ro program? string
+--ro last-completion? yang:date-and-time +--ro schedules
+--ro last-status? status-code +--ro schedule* [name]
+--ro last-message? string +--ro name string
+--ro last-failed-completion? yang:date-and-time +--ro state? enumeration
+--ro last-failed-status? status-code +--ro last-invocation? yang:date-and-time
+--ro last-failed-message? string +--ro action* [name]
+--ro name string
+--ro state? enumeration
+--ro last-invocation? yang:date-and-time
+--ro last-completion? yang:date-and-time
+--ro last-status? lmap-common:status-code
+--ro last-message? string
+--ro last-failed-completion? yang:date-and-time
+--ro last-failed-status? lmap-common:status-code
+--ro last-failed-message? string
The tree diagram below shows the structure of the notification The tree diagram below shows the structure of the reporting data
(reporting) model. model.
module: ietf-lmap-report module: ietf-lmap-report
notifications: rpcs:
+---n report +---x report
+--ro date yang:date-and-time +---w input
+--ro agent-id? yang:uuid +---w date yang:date-and-time
+--ro group-id? string +---w agent-id? yang:uuid
+--ro task* [name] +---w group-id? string
| +--ro name string +---w measurement-point? string
| +--ro (task-identification) +---w task* [name]
| | +--:(registry) +---w name string
| | | +--ro registry? inet:uri +---w metric* [uri]
| | +--:(program) | +---w uri inet:uri
| | +--ro program? string | +---w role* string
| +--ro option* [name] +---w option* [name]
| | +--ro name string | +---w name string
| | +--ro value? string | +---w value? string
| +--ro tag* string +---w tag* string
| +--ro suppress-by-default? boolean +---w header
+--ro header | +---w column* string
| +--ro column* string +---w row*
+--ro row* +---w start yang:date-and-time
+--ro start yang:date-and-time +---w end? yang:date-and-time
+--ro end? yang:date-and-time +---w conflict* string
+--ro conflict* string +---w value* string
+--ro value* string
3. Relationship to the Information Model 3. Relationship to the Information Model
The LMAP information model [I-D.ietf-lmap-information-model] is The LMAP information model [I-D.ietf-lmap-information-model] is
devided into six sections. They are mapped into the YANG data model devided into six sections. They are mapped into the YANG data model
as explained below: as explained below:
o Pre-Configuration Information: This is not modeled explicitly o Pre-Configuration Information: This is not modeled explicitly
since it is a subset of the configuration information. since it is a subset of the configuration information.
o Configuration Information: This is modeled in the /lmap/agent o Configuration Information: This is modeled in the /lmap/agent
subtree and the /lmap/schedules and /lmap/tasks subtrees described subtree, the /lmap/schedules subtree, and the /lmap/tasks subtree
below. Some items have been left out because they are expected to described below. Some items have been left out because they are
be dealt with by the underlying protocol. expected to be dealt with by the underlying protocol.
o Instruction Information: This is modeled in the /lmap/suppression o Instruction Information: This is modeled in the /lmap/suppressions
subtree and the /lmap/schedules and /lmap/tasks subtrees described subtree, the /lmap/schedules subtree, and the /lmap/tasks subtree
below. described below.
o Logging Information: Some of the logging information, in o Logging Information: Some of the logging information, in
particular 'success/failure/warning messages in response to particular 'success/failure/warning messages in response to
information updates from the Controller', will be handled by the information updates from the Controller', will be handled by the
protocol used to manipulate the lmap specific configuration. protocol used to manipulate the lmap specific configuration.
[[CREF1: It needs to be discussed whether we can rely on informal [[CREF1: It needs to be discussed whether we can rely on informal
syslog messages that can be accessed via protocols such RFC 5277 syslog messages that can be accessed via protocols such RFC 5277
or whether we want to define specific notifications in the YANG or whether we want to define specific notifications in the YANG
data model. --JS]] data model. --JS]]
o Capability and Status Information: Some of the status information o Capability and Status Information: Some of the status information
is modeled in the /lmap-state/agent subtree. Information about is modeled in the /lmap-state/agent subtree and teh /lmap-state/
network interfaces can be obtained from the interfaces YANG data schedules subtree. Information about network interfaces can be
model [RFC7223]. The list of supported tasks is modeled in the obtained from the interfaces YANG data model [RFC7223]. The list
/lmap-state/tasks subtree including information about the last of supported tasks is modeled in the /lmap-state/tasks subtree.
execution and the last failed execution.
o Reporting Information: This is modeled by the report notification. o Reporting Information: This is modeled by the report data model to
be implemented by the Collector. Measurement Agents send results
to the Collector via an RPC operation.
These six sections are build on the following common information These six sections are build on the following common information
objects: objects:
o Schedules: This is modeled in the /lmap/schedules subtree. o Schedules: This is modeled in the /lmap/schedules subtree.
o Channels: Channels are not modeled since the NETCONF and RESTCONF o Channels: Channels are not modeled since the NETCONF and RESTCONF
server configuration data model [I-D.ietf-netconf-server-model] server configuration data model [I-D.ietf-netconf-server-model]
already provides a mechanism to configure NETCONF and RESTCONF already provides a mechanism to configure NETCONF and RESTCONF
server channels. server channels.
o Task Configurations: This is modeled in the /lmap/tasks subtree. o Task Configurations: This is modeled in the /lmap/tasks subtree.
o Event Information: This is modeled in the /lmap/events subtree. o Event Information: This is modeled in the /lmap/events subtree.
4. YANG Modules 4. YANG Modules
The modules import definitions from [RFC6991] and [RFC7223]. The modules import definitions from [RFC6991] and [RFC7223] and they
reference [RFC7398].
<CODE BEGINS> file "ietf-lmap-control@2015-07-03.yang" <CODE BEGINS> file "ietf-lmap-common@2015-10-28.yang"
module ietf-lmap-control { module ietf-lmap-common {
namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-control"; namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-common";
prefix "lmapc"; prefix "lmap-common";
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
} }
organization organization
"IETF Large-Scale Measurement Platforms Working Group"; "IETF Large-Scale Measurement Platforms Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/lmap/> "WG Web: <http://tools.ietf.org/wg/lmap/>
WG List: <mailto:lmap@ietf.org> WG List: <mailto:lmap@ietf.org>
Editor: Juergen Schoenwaelder Editor: Juergen Schoenwaelder
<j.schoenwaelder@jacobs-university.de> <j.schoenwaelder@jacobs-university.de>
skipping to change at page 8, line 17 skipping to change at page 8, line 18
"WG Web: <http://tools.ietf.org/wg/lmap/> "WG Web: <http://tools.ietf.org/wg/lmap/>
WG List: <mailto:lmap@ietf.org> WG List: <mailto:lmap@ietf.org>
Editor: Juergen Schoenwaelder Editor: Juergen Schoenwaelder
<j.schoenwaelder@jacobs-university.de> <j.schoenwaelder@jacobs-university.de>
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 provides common definitions used by the data
agents that are part of a Large-Scale Measurement Platform models written for Large-Scale Measurement Platforms (LMAP).
(LMAP)."; This module defines typedefs and groupings but no schema
tree elements.";
revision "2015-07-03" { revision "2015-10-28" {
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
*/ */
typedef tag-type {
type string {
length "1..max";
pattern '[^\*].*';
}
description
"A tag consists of at least one character and a tag is
not allowed to start with an asterisk '*'.";
// XXX: Does it make sense to have stricter rules,
// XXX: e.g., disallow white space?
}
typedef tag-matchall-type {
type string {
pattern '\*';
}
description
"The string containing a single asterisk '*' is used
to match all tags.";
// XXX: Allow glob-style matching, turning this into a
// XXX: tag-match-type?
}
typedef wildcard {
type string {
pattern '\*';
}
description
"A wildcard for calendar scheduling entries.";
}
typedef weekday { typedef weekday {
type enumeration { type enumeration {
enum sunday { enum sunday {
value 0; value 0;
description "Sunday of the week"; description "Sunday of the week";
} }
enum monday { enum monday {
value 1; value 1;
description "Monday of the week"; description "Monday of the week";
} }
skipping to change at page 10, line 28 skipping to change at page 11, line 12
enum december { enum december {
value 12; value 12;
description "December of the Julian and Gregorian calendar"; description "December of the Julian and Gregorian calendar";
} }
} }
description description
"A type modeling the month in the Julian and Gregorian "A type modeling the month in the Julian and Gregorian
tradition."; tradition.";
} }
typedef wildcard {
type string { pattern '\*'; }
description
"A wildcard for calendar scheduling entries.";
}
typedef status-code { typedef status-code {
type int32; type int32;
description description
"A status code returned by the execution of a task. Note that "A status code returned by the execution of a task. Note that
the actual range is implementation dependent but it should the actual range is implementation dependent but it should
be portable to use values in the range 0..127 for regular be portable to use values in the range 0..127 for regular
exit codes. By convention, 0 indicates successful termination. exit codes. By convention, 0 indicates successful termination.
Negative values may be used to indicate abnormal termination Negative values may be used to indicate abnormal termination
due to a signal; the absolute value may identify the signal due to a signal; the absolute value may identify the signal
number in this case."; number in this case.";
skipping to change at page 11, line 12 skipping to change at page 11, line 38
description description
"A timezone-offset as it is use in the yang:date-and-time "A timezone-offset as it is use in the yang:date-and-time
type. The value Z is equivalent to +00:00. The value -00:00 type. The value Z is equivalent to +00:00. The value -00:00
indicates and unknown time-offset."; indicates and unknown time-offset.";
} }
/* /*
* Groupings * Groupings
*/ */
grouping timing-start-end-grouping { grouping metrics-grouping {
description description
"A grouping that provides start and end times for "This grouping models a list of entry in a metrics registry.";
timing objects.";
leaf start { list metric {
type yang:date-and-time; key uri;
description
"The date and time when the timing object
starts to create triggers.";
}
leaf end {
type yang:date-and-time;
description description
"The date and time when the timing object "A list of entries in a metrics registry.";
stops to create triggers.
It is generally a good idea to always configure leaf uri {
an end time and to refresh the configuration type inet:uri;
of timing object as needed to ensure that agents description
that loose connectivity to their controller "A URI identifying an entry in a metrics registry.";
do not continue their tasks forever."; }
leaf-list role {
type string;
description
"A set of roles for this metrics.";
}
} }
} }
grouping task-options-grouping { grouping task-options-grouping {
description description
"A list of options of a task. Each option is a name/value "A list of options of a task. Each option is a name/value
pair (where the value may be absent)."; pair (where the value may be absent).";
list option { list option {
key "name"; key "name";
skipping to change at page 12, line 23 skipping to change at page 12, line 47
"The name of the option."; "The name of the option.";
} }
leaf value { leaf value {
type string; type string;
description description
"The value of the option."; "The value of the option.";
} }
} }
} }
}
<CODE ENDS>
<CODE BEGINS> file "ietf-lmap-control@2015-10-28.yang"
module ietf-lmap-control {
grouping task-grouping { namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-control";
description prefix "lmap-control";
"A grouping that defines the configuration of a task.";
list task { import ietf-yang-types {
key name; prefix yang;
description }
"The list of tasks configured on the LMAP agent."; import ietf-inet-types {
prefix inet;
}
import ietf-lmap-common {
prefix lmap-common;
}
leaf name { organization
type string; "IETF Large-Scale Measurement Platforms Working Group";
description
"The unique name of a task.";
}
choice task-identification { contact
mandatory true; "WG Web: <http://tools.ietf.org/wg/lmap/>
description WG List: <mailto:lmap@ietf.org>
"Information that identifies the task.";
leaf-list registry { Editor: Juergen Schoenwaelder
type inet:uri; <j.schoenwaelder@jacobs-university.de>
description
"A registry entry identifying the metrics a measurement
task supports.";
}
leaf program { Editor: Vaibhav Bajpai
type string; <v.bajpai@jacobs-university.de>";
description
"The (local) program to invoke in order to execute
the task.";
}
}
uses task-options-grouping { description
description "This module defines a data model for controlling measurement
"The list of task specific options."; agents that are part of a Large-Scale Measurement Platform
} (LMAP). This data model is expected to be implemented by a
measurement agent.";
leaf-list tag { revision "2015-10-28" {
type string; description
description "Initial version";
"A tag contains additional information that is passed reference
with the result record to the collector. A tag can be "RFC XXX: A YANG Data Model for LMAP Measurement Agents";
used to carry the Measurement Cycle ID."; }
}
leaf suppress-by-default { /*
type boolean; * Groupings
default true; */
description
"Indicates whether the task will be suppressed by grouping timing-start-end-grouping {
a default supression."; description
} "A grouping that provides start and end times for
timing objects.";
leaf start {
type yang:date-and-time;
description
"The date and time when the timing object
starts to create triggers.";
}
leaf end {
type yang:date-and-time;
description
"The date and time when the timing object
stops to create triggers.
It is generally a good idea to always configure
an end time and to refresh the configuration
of timing object as needed to ensure that agents
that loose connectivity to their controller
do not continue their tasks forever.";
} }
} }
/* /*
* Configuration data nodes * Configuration data nodes
*/ */
container lmap { container lmap {
description description
"Configuration of the LMAP agent."; "Configuration of the LMAP agent.";
skipping to change at page 14, line 30 skipping to change at page 15, line 22
leaf group-id { leaf group-id {
type string; type string;
description description
"The group-id identifies a group of measurement "The group-id identifies a group of measurement
agents. In certain deployments, the group-id agents. In certain deployments, the group-id
may be considered less sensitive than the may be considered less sensitive than the
agent-id."; agent-id.";
} }
leaf measurement-point {
type string;
description
"The measurement point indicating where the
measurement agent is located on a path.";
reference
"RFC 7398: A Reference Path and Measurement Points
for Large-Scale Measurement of Broadband
Performance";
}
leaf report-agent-id { leaf report-agent-id {
type boolean; type boolean;
default false; must "../agent-id" {
// XXX: write a must expression that requires description
// group-id to be configured when this is true? "An agent-id must exist for this to be set.";
}
description description
"The 'report-agent-id' controls whether the "The 'report-agent-id' controls whether the
'agent-id' is reported to collectors if the 'agent-id' is reported to collectors if the
'group-id' is configured. If the 'group-id' 'group-id' is configured. If the 'group-id'
is not configured, the agent-id is always is not configured, the agent-id is always
reported."; reported.";
} }
leaf report-measurement-point {
type boolean;
must "../measurement-point" {
description
"A measurement-point must exist for this to be set.";
}
description
"The 'report-measurement-point' controls whether
the 'measurement-point' is reported to collectors
if the 'measurement-point' is configured.";
}
leaf controller-timeout { leaf controller-timeout {
type uint32; type uint32;
units "seconds"; units "seconds";
description description
"A timer is started after each successful contact "A timer is started after each successful contact
with a controller. When the timer reaches the with a controller. When the timer reaches the
controller-timeout, all schedules will be controller-timeout, an event is raised indicating
disabled, i.e., no new actions will be executed that connectivity to the controller has been lost.";
(and hence no new tasks started). The disabled
schedules will be reenabled automatically once
contact with a controller has been established
successfully again. Note that this will not affect
the execution of actions that are essential to
establish contact with the controller or that
perform critical housekeeping functions.";
} }
} }
/* /*
* Common Information Objects: Schedules * Common Information Objects: Schedules
*/ */
container schedules { container schedules {
description description
"Configuration of LMAP schedules. Schedules control with "Configuration of LMAP schedules. Schedules control which
tasks are executed by the LMAP implementation."; tasks are executed by the LMAP implementation.";
list schedule { list schedule {
key name; key name;
description description
"Configuration of a particular schedule."; "Configuration of a particular schedule.";
leaf name { leaf name {
type string; type string;
description description
"The locally-unique, administratively assigned name for "The locally-unique, administratively assigned name for
this scheduled task."; this schedule.";
} }
leaf event { leaf event {
type leafref { type leafref {
path "/lmap/events/event/name"; path "/lmap/events/event/name";
} }
mandatory true; mandatory true;
description description
"The event source controlling the start of the scheduled "The event source controlling the start of the scheduled
tasks."; tasks.";
skipping to change at page 16, line 17 skipping to change at page 17, line 25
leaf task { leaf task {
type leafref { type leafref {
path "/lmap/tasks/task/name"; path "/lmap/tasks/task/name";
} }
mandatory true; mandatory true;
description description
"The tasks invoked by this action."; "The tasks invoked by this action.";
} }
uses task-options-grouping { uses lmap-common:task-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 leafref { type leafref {
path "/lmap/schedules/schedule/name"; path "/lmap/schedules/schedule/name";
} }
description description
"A schedule of receiving the output produced by "A schedule of receiving the output produced by
this action. A queue is internally used to pass this action. A queue is internally used to pass
results to another schedule. The behaviour of results to another schedule. The behaviour of
an action passing data to its own schedule is an action passing data to its own schedule is
implementation specific."; implementation specific.
Data passed to a sequential or pipelined schedule
is consumed by the schedule's first action. Data
passed to a parallel schedule is consumed by all
actions of the schedule.";
}
leaf-list suppression-tag {
type lmap-common:tag-type;
description
"A list of suppression tags.";
} }
} }
leaf execution-mode { leaf execution-mode {
type enumeration { type enumeration {
enum sequential { enum sequential {
value 1; value 1;
description description
"The actions of the schedule are executed "The actions of the schedule are executed
sequentially."; sequentially.";
} }
enum parallel { enum parallel {
value 2; value 2;
description description
"The actions of the schedule are executed "The actions of the schedule are executed
concurrently"; concurrently";
} }
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.";
} }
} }
mandatory true; default pipelined;
description description
"The execution mode of this schedule determins in "The execution mode of this schedule determins in
which order the actions of the schedule are executed."; which order the actions of the schedule are executed.";
} }
leaf-list suppression-tag {
type lmap-common:tag-type;
description
"A list of suppression tags.";
}
} }
} }
/* /*
* Suppression * Suppression
*/ */
container suppression { container suppressions {
description description
"Suppression information to prevent schedules to start "Suppression information to prevent schedules or
certain tasks."; certain actions from starting.";
leaf enabled { list suppression {
type boolean; key name;
default false;
description description
"Setting 'enabled' to true will suppress all tasks for "Configuration of a particular suppression.";
which suppress-by-default is true.";
}
leaf stop-running { leaf name {
type boolean; type string;
default false; description
description "The locally-unique, administratively assigned name for
"Setting 'stop-running' to true will cause running this suppression.";
tasks to be terminated if suppression is enabled }
(the 'enabled' leaf is set to true). Otherwise,
running tasks will not be affected if suppression
is enabled.";
}
leaf start { leaf start {
type yang:date-and-time; type leafref {
description path "/lmap/events/event/name";
"The date and time when supression starts to }
become effective. If not present, supression description
becomes effective immeditately when 'enabled' "The event source controlling the start of the
is set to true."; suppression period.";
} }
leaf end { leaf end {
type yang:date-and-time; type leafref {
description path "/lmap/events/event/name";
"The date and time when supression stops to }
be effective. If not present, supression description
continues indefinite until 'enabled' is set "The event source controlling the end of the
to false."; suppression period. If not present, supression
} continues indefinitely.";
}
leaf-list task { leaf-list tag {
type leafref { type union {
path "/lmap/tasks/task/name"; type lmap-common:tag-type;
type lmap-common:tag-matchall-type;
}
description
"A list of suppression tags. The suppression will
apply to all schedules (and their actions) that have
a matching value in their suppression-tags and to
all actions that have a matching value in their
suppression-tags.";
} }
description
"A specific task to suppress. If no tasks are
listed, then all tasks will be suppressed.";
}
leaf-list schedule { leaf stop-running {
type leafref { type boolean;
path "/lmap/schedules/schedule/name"; default false;
description
"Setting 'stop-running' to true will cause running
tasks to be terminated if suppression is activated.
Otherwise, running tasks will not be affected if
suppression is activated.";
} }
description
"A specific schedule to suppress. If no schedules
are listed, then all schedules will be suppressed.";
} }
} }
/* /*
* Common Information Objects: Task Configurations * Common Information Objects: Task Configurations
*/ */
container tasks { container tasks {
description description
"Configuration of LMAP tasks."; "Configuration of LMAP tasks.";
skipping to change at page 18, line 44 skipping to change at page 20, line 20
} }
/* /*
* Common Information Objects: Task Configurations * Common Information Objects: Task Configurations
*/ */
container tasks { container tasks {
description description
"Configuration of LMAP tasks."; "Configuration of LMAP tasks.";
uses task-grouping; list task {
key name;
description
"The list of tasks configured on the LMAP agent.";
leaf name {
type string;
description
"The unique name of a task.";
}
uses lmap-common:metrics-grouping;
leaf program {
type string;
description
"The (local) program to invoke in order to execute
the task.";
}
uses lmap-common:task-options-grouping {
description
"The list of task specific options.";
}
leaf-list tag {
type string;
description
"A tag contains additional information that is passed
with the result record to the collector. A tag can be
used to carry the Measurement Cycle ID.";
}
leaf suppress-by-default {
type boolean;
default true;
description
"Indicates whether the task will be suppressed by
a default supression.";
}
}
} }
/* /*
* Common Information Objects: Event Information * Common Information Objects: Event Information
*/ */
container events { container events {
description description
"Configuration of LMAP events. "Configuration of LMAP events.
skipping to change at page 20, line 16 skipping to change at page 22, line 31
} }
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 union { type union {
type month; type lmap-common:month;
type wildcard; type lmap-common:wildcard;
} }
description description
"A month at which this calendar timing will "A month at which this calendar timing will
trigger. The wildcard means all months."; trigger. The wildcard means all months.";
} }
leaf-list weekday { leaf-list weekday {
type union { type union {
type weekday; type lmap-common:weekday;
type wildcard; type lmap-common:wildcard;
} }
description description
"A weekday at which this calendar timing will "A weekday at which this calendar timing will
trigger. The wildcard means all weekdays."; trigger. The wildcard means all weekdays.";
} }
leaf-list day-of-month { leaf-list day-of-month {
type union { type union {
type int8 { range "-31..-1 | 1..31"; } type int8 { range "-31..-1 | 1..31"; }
type wildcard; type lmap-common:wildcard;
} }
description description
"A day in the month at which this calendar "A day in the month at which this calendar
timing will trigger. Negative numbers indicate timing will trigger. Negative numbers indicate
days counted backwards from the end of the days counted backwards from the end of the
months. The wildcard means all days of a month."; months. The wildcard means all days of a month.";
} }
leaf-list hour { leaf-list hour {
type union { type union {
type int8 { range "0..23"; } type int8 { range "0..23"; }
type wildcard; type lmap-common:wildcard;
} }
description description
"An hour at which this calendar timing will "An hour at which this calendar timing will
trigger. The wildcard means all hours of a day."; trigger. The wildcard means all hours of a day.";
} }
leaf-list minute { leaf-list minute {
type union { type union {
type int8 { range "0..59"; } type int8 { range "0..59"; }
type wildcard; type lmap-common:wildcard;
} }
description description
"A minute at which this calendar timing will "A minute at which this calendar timing will
trigger. The wildcard means all minutes of trigger. The wildcard means all minutes of
an hour."; an hour.";
} }
leaf-list second { leaf-list second {
type union { type union {
type int8 { range "0..59"; } type int8 { range "0..59"; }
type wildcard; type lmap-common:wildcard;
} }
description description
"A second at which this calendar timing will "A second at which this calendar timing will
trigger. The wildcard means all seconds of trigger. The wildcard means all seconds of
a minute."; a minute.";
} }
leaf timezone-offset { leaf timezone-offset {
type timezone-offset; type lmap-common:timezone-offset;
description description
"The timezone in which this calendar timing "The timezone in which this calendar timing
object will be evaluated."; object will be evaluated.";
} }
uses timing-start-end-grouping; uses timing-start-end-grouping;
} }
} }
case one-off { case one-off {
leaf one-off-time { leaf one-off-time {
type yang:date-and-time; type yang:date-and-time;
mandatory true; mandatory true;
description description
"This one-off timing object triggers once at the "This one-off timing object triggers once at the
configured one-off-time."; configured one-off-time.";
} }
skipping to change at page 22, line 20 skipping to change at page 24, line 36
case startup { case startup {
leaf startup { leaf startup {
type empty; type empty;
mandatory true; mandatory true;
description description
"This startup event object triggers whenever the "This startup event object triggers whenever the
LMAP agent (re)starts."; LMAP agent (re)starts.";
} }
} }
case controller-lost {
leaf controller-lost {
type empty;
mandatory true;
description
"The controller-lost event object triggers when
the connectivity to the controller has been lost
for at least 'controller-timeout' seconds.";
}
}
case controller-ok {
leaf controller-ok {
type empty;
mandatory true;
description
"The controller-ok event object triggers when
the connectivity to the controller has been
restored after it was lost for at least
'controller-timeout' seconds.";
}
}
} }
leaf random-spread { leaf random-spread {
type int32; type int32;
units milliseconds; units milliseconds;
description description
"This optional leaf adds a random spread to the "This optional leaf adds a random spread to the
computation of the trigger."; computation of the trigger.";
} }
} }
skipping to change at page 24, line 18 skipping to change at page 27, line 8
key name; key name;
description description
"The list of tasks available on the LMAP agent."; "The list of tasks available on the LMAP agent.";
leaf name { leaf name {
type string; type string;
description description
"The unique name of a task."; "The unique name of a task.";
} }
choice task-identification { uses lmap-common:metrics-grouping;
mandatory true;
description
"Information that identifies the task.";
leaf-list registry {
type inet:uri;
description
"The registry entry identifying the configured task.";
}
leaf program {
type string;
description
"The (local) program to invoke in order to execute
the task.";
}
}
leaf last-completion { leaf version {
type yang:date-and-time; type string;
description description
"The date and time of the last completion of this task."; "A short description of the software implementing
the task. This should include the version
number of the measurement task software.";
} }
leaf last-status { leaf program {
type status-code; type string;
description description
"The status code returned by the last execution of "The (local) program to invoke in order to execute
this task."; the task.";
} }
}
}
leaf last-message { container schedules {
description
"State of LMAP schedules.";
list schedule {
key name;
description
"State of a particular schedule.";
leaf name {
type string; type string;
description description
"The status message produced by the last execution "The locally-unique, administratively assigned name for
of this task."; this schedule.";
} }
leaf last-failed-completion { leaf state {
type yang:date-and-time; type enumeration {
enum enabled {
value 1;
description
"The value 'enabled' indicates that the
schedule is currently enabled.";
}
enum disabled {
value 2;
description
"The value 'disabled' indicates that the
schedule is currently disabled.";
}
enum suppressed {
value 3;
description
"The value 'suppressed' indicates that the
schedule is currently suppressed.";
}
}
description description
"The date and time of the last failed invocation "The current state of the schedule.";
of this task.";
} }
leaf last-failed-status { leaf last-invocation {
type status-code; type yang:date-and-time;
description description
"The status code returned by the last failed execution "The date and time of the last invocation of
of this task. "; this schedule.";
} }
leaf last-failed-message { list action {
type string; key name;
description description
"The status message produced by the last failed "The state of the actions associated with this
execution of this task."; schedule entry.";
leaf name {
type string;
description
"The unique identifier for this action.";
}
leaf state {
type enumeration {
enum enabled {
value 1;
description
"The value 'enabled' indicates that the
action is currently enabled.";
}
enum disabled {
value 2;
description
"The value 'disabled' indicates that the
action is currently disabled.";
}
enum suppressed {
value 3;
description
"The value 'suppressed' indicates that the
action is currently suppressed.";
}
}
description
"The current state of the action.";
}
leaf last-invocation {
type yang:date-and-time;
description
"The date and time of the last invocation of
this action.";
}
leaf last-completion {
type yang:date-and-time;
description
"The date and time of the last completion of
this action.";
}
leaf last-status {
type lmap-common:status-code;
description
"The status code returned by the last execution of
this action.";
}
leaf last-message {
type string;
description
"The status message produced by the last execution
of this action.";
}
leaf last-failed-completion {
type yang:date-and-time;
description
"The date and time of the last failed completion
of this action.";
}
leaf last-failed-status {
type lmap-common:status-code;
description
"The status code returned by the last failed execution
of this action.";
}
leaf last-failed-message {
type string;
description
"The status message produced by the last failed
execution of this action.";
}
} }
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
<CODE BEGINS> file "ietf-lmap-report@2015-07-03.yang" <CODE BEGINS> file "ietf-lmap-report@2015-10-28.yang"
module ietf-lmap-report { module 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 "lmap-report";
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
import ietf-lmap-control { import ietf-lmap-common {
prefix lmapc; prefix lmap-common;
} }
organization organization
"IETF Large-Scale Measurement Platforms Working Group"; "IETF Large-Scale Measurement Platforms Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/lmap/> "WG Web: <http://tools.ietf.org/wg/lmap/>
WG List: <mailto:lmap@ietf.org> WG List: <mailto:lmap@ietf.org>
Editor: Juergen Schoenwaelder Editor: Juergen Schoenwaelder
<j.schoenwaelder@jacobs-university.de> <j.schoenwaelder@jacobs-university.de>
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 that are part of a Large-Scale Measurement measurement agents, which are part of a Large-Scale Measurement
Platform (LMAP)."; Platform (LMAP), to result data collectors. This data model is
expected to be implemented by a collector.";
revision "2015-04-10" { revision "2015-10-28" {
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";
} }
notification report { rpc report {
description description
"The result record produced by a certain task."; "The report operation is used by an LMAP measurement agent to
submit measurement results produced by measurement tasks to
a collector.";
leaf date { input {
type yang:date-and-time;
mandatory true;
description
"The date and time when this report was sent.";
// XXX It is unclear why this is useful. The receiver can
// XXX easily timestamp when data was received.
}
leaf agent-id { leaf date {
type yang:uuid; type yang:date-and-time;
description mandatory true;
"The agent-id of the agent from which this description
report originates."; "The date and time when this result report was sent to
} a collector.";
}
leaf group-id { leaf agent-id {
type string; type yang:uuid;
description description
"The group-id of the agent from which this "The agent-id of the agent from which this
report originates."; report originates.";
} }
uses lmapc:task-grouping;
// XXX We would prefer to just send a configuration version
// XXX number such that the configuration can be identified
// XXX that was active XXX when the report was generated. It
// XXX would be nice to have a generic configuration version
// XXX number that we could reuse. If this works out, we can
// XXX inline the grouping as well.
// XXX Note that task-grouping contains stuff that is not leaf group-id {
// XXX relevant here, perhaps using a grouping is not helpful type string;
// XXX here. It is also missing stuff, such as the options description
// XXX in the schedule entry. "The group-id of the agent from which this
report originates.";
}
container header { leaf measurement-point {
description type string;
"The header of the result records."; description
"The measurement-point of the agent from which this
report originates.";
}
list task {
key name;
description
"The list of tasks for which results are reported.";
leaf-list column { leaf name {
type string; type string;
description description
"A header of a column in the result rows."; "The unique name of the task.";
} }
}
list row { uses lmap-common:metrics-grouping;
description
"The rows of the result record.";
leaf start { uses lmap-common:task-options-grouping {
type yang:date-and-time; description
mandatory true; "The list of task options there were in use then the
description measurement was performed. This list must include
"The date and time when the measurement producing both the task specific options as well as the action
this result row started."; specific options.";
} }
leaf end { leaf-list tag {
type yang:date-and-time; type string;
description description
"The date and time when the measurement producing "A tag contains additional information that is passed
this result row stopped."; with the result record to the collector. A tag can be
} used to carry the Measurement Cycle ID.";
}
leaf-list conflict { container header {
type string; description
description "This container lists the column labels. It does not
"The name of a task overlapping with the execution really serve a purpose other than making the result
of the task that has produced this result record."; data look nicely structured.";
} leaf-list column {
type string;
description
"An ordered list of column labels. The order is determined
by the system and must match the order of the columns in
the result rows.";
}
}
leaf-list value { list row {
type string; description
description "The rows of the result record.";
"The value of a cell in the result.";
// XXX We could make this a union / choice in order to a leaf start {
// XXX more compact encoding of numbers in certain encodings type yang:date-and-time;
// XXX (e.g. JSON) mandatory true;
} description
} "The date and time when the measurement producing
} this result row started.";
} }
<CODE ENDS>
leaf end {
type yang:date-and-time;
description
"The date and time when the measurement producing
this result row stopped.";
}
leaf-list conflict {
type string;
description
"The name of a task overlapping with the execution
of the task that has produced this result record.";
}
leaf-list value {
type string;
description
"The value of a cell in the result row.";
}
}
}
}
}
}
<CODE ENDS>
5. Security Considerations 5. Security Considerations
TBD TBD
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.
skipping to change at page 29, line 5 skipping to change at page 34, line 16
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.
URI: urn:ietf:params:xml:ns:yang:ietf-lmap-report URI: urn:ietf:params:xml:ns:yang:ietf-lmap-report
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.
This document registers a YANG module in the "YANG Module Names" This document registers a YANG module in the "YANG Module Names"
registry [RFC6020]. registry [RFC6020].
name: ietf-lmap-common
namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-common
prefix: lmap-common
reference: RFC XXXX
name: ietf-lmap-control name: ietf-lmap-control
namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-control namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-control
prefix: lmapc prefix: lmap-control
reference: RFC XXXX reference: RFC XXXX
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: lmap-report
reference: RFC XXXX reference: RFC XXXX
7. Acknowledgements 7. Acknowledgements
Juergen Schoenwaelder and Vaibhav Bajpai work in part on the Leone Juergen Schoenwaelder and Vaibhav Bajpai worked in part on the Leone
research project, which receives 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
Flamingo, a Network of Excellence project (ICT-318488) supported by
the European Commission under its Seventh Framework Programme.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997,
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the <http://www.rfc-editor.org/info/rfc2119>.
Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010.
[RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
July 2013. the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>.
[RFC7223] Bjorklund, M., "A YANG Data Model for Interface [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC
Management", RFC 7223, May 2014. 6991, DOI 10.17487/RFC6991, July 2013,
<http://www.rfc-editor.org/info/rfc6991>.
8.2. Informative References 8.2. Informative References
[I-D.ietf-lmap-framework]
Eardley, P., Morton, A., Bagnulo, M., Burbridge, T.,
Aitken, P., and A. Akhter, "A framework for Large-Scale
Measurement of Broadband Performance (LMAP)", draft-ietf-
lmap-framework-12 (work in progress), March 2015.
[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-06 (work in progress), July 2015. information-model-06 (work in progress), July 2015.
[I-D.ietf-netconf-server-model] [I-D.ietf-netconf-server-model]
Watsen, K. and J. Schoenwaelder, "NETCONF Server and Watsen, K. and J. Schoenwaelder, "NETCONF Server and
RESTCONF Server Configuration Models", draft-ietf-netconf- RESTCONF Server Configuration Models", draft-ietf-netconf-
server-model-06 (work in progress), February 2015. server-model-08 (work in progress), October 2015.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>.
[RFC7223] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 7223, DOI 10.17487/RFC7223, May 2014,
<http://www.rfc-editor.org/info/rfc7223>.
[RFC7398] Bagnulo, M., Burbridge, T., Crawford, S., Eardley, P., and
A. Morton, "A Reference Path and Measurement Points for
Large-Scale Measurement of Broadband Performance", RFC
7398, DOI 10.17487/RFC7398, February 2015,
<http://www.rfc-editor.org/info/rfc7398>.
[RFC7594] Eardley, P., Morton, A., Bagnulo, M., Burbridge, T.,
Aitken, P., and A. Akhter, "A Framework for Large-Scale
Measurement of Broadband Performance (LMAP)", RFC 7594,
DOI 10.17487/RFC7594, September 2015,
<http://www.rfc-editor.org/info/rfc7594>.
Appendix A. Open Issues Appendix A. Open Issues
o The task-options-grouping needs fixing, see the comments inline. o The task-options-grouping needs fixing, see the comments inline.
o Should results be shipped via notifications or would it be more Appendix B. Non-editorial Changes since -01
practical to have a collector provding a RESTCONF server and data
is simply written via posts to suitable resources? This seems to
be the way current platforms work. If we do this, we also need to
think about how RESTCONF client credentials are configured.
Appendix B. Non-editorial Changes since -06 o Updated and split examples (config vs state vs report).
o Refactored the definitions so that common definitions used by both
the control and report data models are in the new module ietf-
lmap-common.
o A report is submitted via an RPC operation instead of using a
notification.
o The default execution mode is pipelined.
o Clarified which action consumes data in sequential, pipelines, and
parallel execution mode.
o Added /lmap/agent/measurement-point, /lmap/agent/report-
measurement-point, and /report/measurement-point to configure and
report the measurement point.
o Turned /lmap/suppression into a list /lmap/suppressions/
suppression that uses a start and stop event to define the
beginning and end of a suppression period.
o Added controller-lost an controller-ok event choices to /lmap/
events/event.
o Added a metrics-grouping to identify entries in a metric registry
and associated roles.
o Added /lmap-state/schedules to report the status of schedules and
their actions. Refactored /lmap-state/tasks to only report the
task capabilities.
Appendix C. Non-editorial Changes since -00
o A task can now reference multiply registry entries. o A task can now reference multiply registry entries.
o Schedules are triggered by Events instead of Timings; Timings are o Schedules are triggered by Events instead of Timings; Timings are
just one of many possible event sources. just one of many possible event sources.
o Actions feed into other Schedules (instead of Actions within other o Actions feed into other Schedules (instead of Actions within other
Schedules). Schedules).
o Removed the notion of multiple task outputs. o Removed the notion of multiple task outputs.
o Support for sequential, parallel, and pipelined execution of o Support for sequential, parallel, and pipelined execution of
Actions. Actions.
Appendix C. Example Configuration (XML) Appendix D. Example Configuration (XML)
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<lmap xmlns="urn:ietf:params:xml:ns:yang:ietf-lmap-control">
<agent>
<agent-id>550e8400-e29b-41d4-a716-446655440000</agent-id>
<device-id>urn:dev:mac:0024befffe804ff1</device-id>
<group-id>wireless measurement at the north-pole</group-id>
<report-agent-id>true</report-agent-id>
</agent>
<schedules>
<schedule>
<name>hourly-schedule</name>
<event>hourly</event>
<action>
<name>icmp-latency-hourly</name>
<task>icmp-latency-measurement</task>
<destination>daily</destination>
</action>
<action>
<name>udp-latency-weekdays-hourly</name>
<task>udp-latency-measurement</task>
<destination>daily</destination>
</action>
<execution-mode>sequential</execution-mode>
</schedule>
<schedule>
<name>daily-schedule</name>
<event>daily</event>
<action>
<name>report-daily</name>
<task>lmap-reporting-task</task>
<option>
<name>channel</name>
<value>http://collector.example.org/</value>
</option>
</action>
<execution-mode>sequential</execution-mode>
</schedule>
<schedule>
<name>immediate-schedule</name>
<event>immediate</event>
<action>
<name>icmp-latency-immediate</name>
<task>icmp-latency-measurement</task>
</action>
<action>
<name>report-immediate</name>
<task>lmap-reporting-task</task>
<option>
<name>channel</name>
<value>http://collector.example.org/</value>
</option>
</action>
<execution-mode>pipelined</execution-mode>
</schedule>
</schedules>
<suppression>
<enabled>true</enabled>
<start>2015-09-02T14:06:11+02:00</start>
<task>iperf-server</task>
<schedule>hourly</schedule>
<schedule>weekdays-hourly</schedule>
</suppression>
<tasks> <config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<task> <lmap xmlns="urn:ietf:params:xml:ns:yang:ietf-lmap-control">
<name>udp-latency-measurement</name>
<registry>urn:....</registry>
</task>
<task>
<name>icmp-latency-measurement</name>
<registry>urn:....</registry>
</task>
<task>
<name>iperf-server</name>
<program>/usr/bin/iperf</program>
<option>
<name>role</name>
<value>server</value>
</option>
<suppress-by-default>false</suppress-by-default>
</task>
<task>
<name>lmap-reporting-task</name>
<program>/usr/bin/lmap-reporter</program>
</task>
</tasks>
<events> <agent>
<event> <agent-id>550e8400-e29b-41d4-a716-446655440000</agent-id>
<name>hourly</name> <device-id>urn:dev:mac:0024befffe804ff1</device-id>
<periodic> <group-id>wireless measurement at the north-pole</group-id>
<interval>3600000</interval> <report-agent-id>true</report-agent-id>
<start>2014-09-01T17:44:00+02:00</start> </agent>
<end>2015-09-30T00:00:00+02:00</end>
</periodic>
</event>
<event>
<name>daily</name>
<calendar>
<hour>4</hour>
</calendar>
</event>
<event>
<name>once-every-six-hours</name>
<calendar>
<hour>0</hour>
<hour>6</hour>
<hour>12</hour>
<hour>18</hour>
<minute>0</minute>
<second>0</second>
<end>2014-09-30T00:00:00+02:00</end>
</calendar>
<random-spread>21600000</random-spread>
</event>
<event>
<name>immediate</name>
<immediate/>
</event>
<event>
<name>startup</name>
<startup/>
<random-spread>12345</random-spread>
</event>
</events>
</lmap> <schedules>
<lmap-state xmlns="urn:ietf:params:xml:ns:yang:ietf-lmap-control"> <schedule>
<name>hourly-schedule</name>
<event>hourly</event>
<action>
<name>icmp-latency-hourly</name>
<task>icmp-latency-measurement</task>
<destination>daily-schedule</destination>
</action>
<action>
<name>udp-latency-weekdays-hourly</name>
<task>udp-latency-measurement</task>
<destination>daily-schedule</destination>
</action>
<execution-mode>sequential</execution-mode>
</schedule>
<agent> <schedule>
<agent-id>550e8400-e29b-41d4-a716-446655440000</agent-id> <name>daily-schedule</name>
<device-id>urn:dev:mac:0024befffe804ff1</device-id> <event>daily</event>
<hardware>ACME home router</hardware> <action>
<firmware>OpenWrt version 10.03.1</firmware> <name>report-daily</name>
<version>Measurement Agent Daemon (MAD) 4.2</version> <task>lmap-reporting-task</task>
<last-started>2015-04-10T17:24:42+02:00</last-started> <option>
</agent> <name>channel</name>
<value>http://collector.example.org/</value>
</option>
</action>
<execution-mode>sequential</execution-mode>
</schedule>
<tasks> <schedule>
<task> <name>immediate-schedule</name>
<name>udp-latency-measurement</name> <event>immediate</event>
<registry>urn:....</registry> <action>
</task> <name>icmp-latency-immediate</name>
<task>icmp-latency-measurement</task>
</action>
<action>
<name>report-immediate</name>
<task>lmap-reporting-task</task>
<option>
<name>channel</name>
<value>http://collector.example.org/</value>
</option>
</action>
<execution-mode>pipelined</execution-mode>
</schedule>
</schedules>
<task> <suppressions>
<name>icmp-latency-measurement</name> <suppression>
<registry>urn:....</registry> <name>controller-lost-suppression</name>
</task> <start>controller-lost</start>
<end>controller-ok</end>
<tag>*</tag>
</suppression>
</suppressions>
<task> <tasks>
<name>iperf</name> <task>
<program>iperf</program> <name>udp-latency-measurement</name>
</task> <metric>
<uri>urn:....</uri>
<role>source</role>
</metric>
</task>
<task>
<name>icmp-latency-measurement</name>
<metric>
<uri>urn:....</uri>
</metric>
</task>
<task>
<name>iperf-server</name>
<program>/usr/bin/iperf</program>
<option>
<name>role</name>
<value>server</value>
</option>
<suppress-by-default>false</suppress-by-default>
</task>
<task>
<name>lmap-reporting-task</name>
<program>/usr/bin/lmap-reporter</program>
</task>
</tasks>
<task> <events>
<name>lmap-reporting-task</name> <event>
<program>lmap-reportd</program> <name>hourly</name>
<last-completion>2015-01-23T12:00:00+01:00</last-completion> <periodic>
<last-status>0</last-status> <interval>3600000</interval>
<last-message>OK</last-message> <start>2014-09-01T17:44:00+02:00</start>
<last-failed-completion>2015-01-23T03:00:00+01:00</last-failed-completion> <end>2015-09-30T00:00:00+02:00</end>
<last-failed-status>42</last-failed-status> </periodic>
<last-failed-message>connection timed out</last-failed-message> </event>
</task> <event>
</tasks> <name>daily</name>
<calendar>
<hour>4</hour>
</calendar>
</event>
<event>
<name>once-every-six-hours</name>
<calendar>
<hour>0</hour>
<hour>6</hour>
<hour>12</hour>
<hour>18</hour>
<minute>0</minute>
<second>0</second>
<end>2014-09-30T00:00:00+02:00</end>
</calendar>
<random-spread>21600000</random-spread>
</event>
<event>
<name>immediate</name>
<immediate/>
</event>
<event>
<name>startup</name>
<startup/>
<random-spread>12345</random-spread>
</event>
<event>
<name>controller-lost</name>
<controller-lost/>
</event>
<event>
<name>controller-ok</name>
<controller-ok/>
</event>
</events>
</lmap-state> </lmap>
</data> </config>
Appendix D. Example Configuration (JSON) Appendix E. Example Configuration (JSON)
{ {
"ietf-lmap-control:lmap": { "ietf-lmap-control:lmap": {
"agent": { "agent": {
"agent-id": "550e8400-e29b-41d4-a716-446655440000", "agent-id": "550e8400-e29b-41d4-a716-446655440000",
"device-id": "urn:dev:mac:0024befffe804ff1", "device-id": "urn:dev:mac:0024befffe804ff1",
"group-id": "wireless measurement at the north-pole", "group-id": "wireless measurement at the north-pole",
"report-agent-id": true "report-agent-id": true
}, },
"schedules": { "schedules": {
"schedule": [ "schedule": [
{ {
"name": "hourly-schedule", "name": "hourly-schedule",
"event": "hourly", "event": "hourly",
"action": [ "action": [
{ {
"name": "icmp-latency-hourly", "name": "icmp-latency-hourly",
"task": "icmp-latency-measurement", "task": "icmp-latency-measurement",
"destination": [ "destination": [
"daily" "daily-schedule"
] ]
}, },
{ {
"name": "udp-latency-weekdays-hourly", "name": "udp-latency-weekdays-hourly",
"task": "udp-latency-measurement", "task": "udp-latency-measurement",
"destination": [ "destination": [
"daily" "daily-schedule"
] ]
} }
], ],
"execution-mode": "sequential" "execution-mode": "sequential"
}, },
{ {
"name": "daily-schedule", "name": "daily-schedule",
"event": "daily", "event": "daily",
"action": [ "action": [
{ {
skipping to change at page 35, line 50 skipping to change at page 41, line 39
"name": "channel", "name": "channel",
"value": "http://collector.example.org/" "value": "http://collector.example.org/"
} }
] ]
} }
], ],
"execution-mode": "pipelined" "execution-mode": "pipelined"
} }
] ]
}, },
"suppression": { "suppressions": {
"enabled": true, "suppression": [
"start": "2015-09-02T14:06:11+02:00", {
"task": [ "name": "controller-lost-suppression",
"iperf-server" "start": "controller-lost",
], "end": "controller-ok",
"schedule": [ "tag": [
"hourly", "*"
"weekdays-hourly" ]
}
] ]
}, },
"tasks": { "tasks": {
"task": [ "task": [
{ {
"name": "udp-latency-measurement", "name": "udp-latency-measurement",
"registry": [ "metric": [
"urn:...." {
"uri": "urn:....",
"role": [
"source"
]
}
] ]
}, },
{ {
"name": "icmp-latency-measurement", "name": "icmp-latency-measurement",
"registry": [ "metric": [
"urn:...." {
"uri": "urn:...."
}
] ]
}, },
{ {
"name": "iperf-server", "name": "iperf-server",
"program": "/usr/bin/iperf", "program": "/usr/bin/iperf",
"option": [ "option": [
{ {
"name": "role", "name": "role",
"value": "server" "value": "server"
} }
skipping to change at page 37, line 42 skipping to change at page 43, line 38
"random-spread": 21600000 "random-spread": 21600000
}, },
{ {
"name": "immediate", "name": "immediate",
"immediate": [null] "immediate": [null]
}, },
{ {
"name": "startup", "name": "startup",
"startup": [null], "startup": [null],
"random-spread": 12345 "random-spread": 12345
},
{
"name": "controller-lost",
"controller-lost": [null]
},
{
"name": "controller-ok",
"controller-ok": [null]
} }
] ]
} }
}, }
}
Appendix F. Example State (XML)
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<lmap-state xmlns="urn:ietf:params:xml:ns:yang:ietf-lmap-control">
<agent>
<agent-id>550e8400-e29b-41d4-a716-446655440000</agent-id>
<device-id>urn:dev:mac:0024befffe804ff1</device-id>
<hardware>ACME home router</hardware>
<firmware>OpenWrt version 10.03.1</firmware>
<version>Measurement Agent Daemon (MAD) 4.2</version>
<last-started>2015-04-10T17:24:42+02:00</last-started>
</agent>
<tasks>
<task>
<name>udp-latency-measurement</name>
<metric>
<uri>urn:....</uri>
<role>source</role>
<role>target</role>
</metric>
</task>
<task>
<name>icmp-latency-measurement</name>
<metric>
<uri>urn:....</uri>
</metric>
</task>
<task>
<name>iperf</name>
<program>iperf</program>
</task>
<task>
<name>lmap-reporting-task</name>
<program>lmap-reportd</program>
</task>
</tasks>
<schedules>
<schedule>
<name>hourly-schedule</name>
<state>enabled</state>
<last-invocation>2015-01-23T12:00:00+01:00</last-invocation>
<action>
<name>icmp-latency-hourly</name>
<state>enabled</state>
<last-invocation>2015-01-23T12:00:00+01:00</last-invocation>
<last-completion>2015-01-23T12:00:01+01:00</last-completion>
<last-status>0</last-status>
<last-message>OK</last-message>
<last-failed-completion>2015-01-23T03:00:00+01:00</last-failed-completion>
<last-failed-status>42</last-failed-status>
<last-failed-message>connection timed out</last-failed-message>
</action>
<action>
<name>udp-latency-weekdays-hourly</name>
<last-invocation>2015-01-23T12:00:01+01:00</last-invocation>
<last-completion>2015-01-23T12:00:02+01:00</last-completion>
<last-status>0</last-status>
<last-message>OK</last-message>
<last-failed-completion>2015-01-23T03:00:00+01:00</last-failed-completion>
<last-failed-status>42</last-failed-status>
<last-failed-message>connection timed out</last-failed-message>
</action>
</schedule>
</schedules>
</lmap-state>
</data>
Appendix G. Example State (JSON)
{
"ietf-lmap-control:lmap-state": { "ietf-lmap-control:lmap-state": {
"agent": { "agent": {
"agent-id": "550e8400-e29b-41d4-a716-446655440000", "agent-id": "550e8400-e29b-41d4-a716-446655440000",
"device-id": "urn:dev:mac:0024befffe804ff1", "device-id": "urn:dev:mac:0024befffe804ff1",
"hardware": "ACME home router", "hardware": "ACME home router",
"firmware": "OpenWrt version 10.03.1", "firmware": "OpenWrt version 10.03.1",
"version": "Measurement Agent Daemon (MAD) 4.2", "version": "Measurement Agent Daemon (MAD) 4.2",
"last-started": "2015-04-10T17:24:42+02:00" "last-started": "2015-04-10T17:24:42+02:00"
}, },
"tasks": { "tasks": {
"task": [ "task": [
{ {
"name": "udp-latency-measurement", "name": "udp-latency-measurement",
"registry": [ "metric": [
"urn:...." {
"uri": "urn:....",
"role": [
"source",
"target"
]
}
] ]
}, },
{ {
"name": "icmp-latency-measurement", "name": "icmp-latency-measurement",
"registry": [ "metric": [
"urn:...." {
"uri": "urn:...."
}
] ]
}, },
{ {
"name": "iperf", "name": "iperf",
"program": "iperf" "program": "iperf"
}, },
{ {
"name": "lmap-reporting-task", "name": "lmap-reporting-task",
"program": "lmap-reportd", "program": "lmap-reportd"
"last-completion": "2015-01-23T12:00:00+01:00", }
"last-status": 0, ]
"last-message": "OK", },
"last-failed-completion": "2015-01-23T03:00:00+01:00", "schedules": {
"last-failed-status": 42, "schedule": [
"last-failed-message": "connection timed out" {
"name": "hourly-schedule",
"state": "enabled",
"last-invocation": "2015-01-23T12:00:00+01:00",
"action": [
{
"name": "icmp-latency-hourly",
"state": "enabled",
"last-invocation": "2015-01-23T12:00:00+01:00",
"last-completion": "2015-01-23T12:00:01+01:00",
"last-status": 0,
"last-message": "OK",
"last-failed-completion": "2015-01-23T03:00:00+01:00",
"last-failed-status": 42,
"last-failed-message": "connection timed out"
},
{
"name": "udp-latency-weekdays-hourly",
"last-invocation": "2015-01-23T12:00:01+01:00",
"last-completion": "2015-01-23T12:00:02+01:00",
"last-status": 0,
"last-message": "OK",
"last-failed-completion": "2015-01-23T03:00:00+01:00",
"last-failed-status": 42,
"last-failed-message": "connection timed out"
}
]
} }
] ]
} }
} }
} }
Appendix H. Example Report (XML)
<?xml version="1.0" encoding="utf-8"?>
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
message-id="1">
<report xmlns="urn:ietf:params:xml:ns:yang:ietf-lmap-report">
<date>2015-10-28T13:27:42+02:00</date>
<agent-id>550e8400-e29b-41d4-a716-446655440000</agent-id>
<group-id>wireless measurement at the north-pole</group-id>
<task>
<name>icmp-latency-measurement</name>
<!-- fping -A -d -C 5 -q www.ietf.org www.google.com -->
<header>
<column>target</column>
<column>ip</column>
<column>rtt-1</column>
<column>rtt-2</column>
<column>rtt-3</column>
<column>rtt-4</column>
<column>rtt-5</column>
</header>
<row>
<start>2015-03-25T00:00:55+00:00</start>
<value>www.ietf.org</value>
<value>104.20.0.85</value>
<value>14.15</value>
<value>14.14</value>
<value>14.09</value>
<value>14.17</value>
<value>14.51</value>
</row>
<row>
<start>2015-03-25T00:00:56+00:00</start>
<value>www.google.com</value>
<value>216.58.213.36</value>
<value>12.24</value>
<value>11.99</value>
<value>12.49</value>
<value>11.87</value>
<value>12.45</value>
</row>
</task>
<task>
<name>happy-dns-measurement</name>
<!-- happy -m -a www.ietf.org www.google.com -->
<header>
<column>target</column>
<column>ip</column>
<column>name</column>
</header>
<row>
<start>2015-03-25T00:00:56+00:00</start>
<value>www.ietf.org</value>
<value>2400:cb00:2048:1::6814:55</value>
<value>www.ietf.org.cdn.cloudflare-dnssec.net</value>
</row>
<row>
<start>2015-03-25T00:00:56+00:00</start>
<value>www.ietf.org</value>
<value>2400:cb00:2048:1::6814:155</value>
<value>www.ietf.org.cdn.cloudflare-dnssec.net</value>
</row>
<row>
<start>2015-03-25T00:00:56+00:00</start>
<value>www.ietf.org</value>
<value>104.20.1.85</value>
<value>www.ietf.org.cdn.cloudflare-dnssec.net</value>
</row>
<row>
<start>2015-03-25T00:00:56+00:00</start>
<value>www.ietf.org</value>
<value>104.20.0.85</value>
<value>www.ietf.org.cdn.cloudflare-dnssec.net</value>
</row>
<row>
<start>2015-03-25T00:00:56+00:00</start>
<value>www.google.com</value>
<value>2a00:1450:4008:800::1012</value>
<!-- <value>www.google.com</value> xxx leaflist sucks -->
<value>ber01s08-in-x12.1e100.net</value>
</row>
<row>
<start>2015-03-25T00:00:56+00:00</start>
<value>www.google.com</value>
<value>216.58.213.36</value>
<!-- <value>www.google.com</value> xxx leaflist sucks -->
<value>ber01s15-in-f36.1e100.net</value>
</row>
</task>
<task>
<name>happy-connect-measurement</name>
<!-- happy -m -a www.ietf.org www.google.com -->
<header>
<column>target</column>
<column>port</column>
<column>ip</column>
<column>time-1</column>
<column>time-2</column>
<column>time-3</column>
</header>
<row>
<start>2015-03-25T00:00:56+00:00</start>
<value>www.ietf.org</value>
<value>80</value>
<value>2400:cb00:2048:1::6814:55</value>
<value>8164</value>
<value>8019</value>
<value>14066</value>
</row>
<row>
<start>2015-03-25T00:00:56+00:00</start>
<value>www.ietf.org</value>
<value>80</value>
<value>2400:cb00:2048:1::6814:155</value>
<value>14131</value>
<value>14029</value>
<value>7984</value>
</row>
<row>
<start>2015-03-25T00:00:56+00:00</start>
<value>www.ietf.org</value>
<value>80</value>
<value>104.20.1.85</value>
<value>13821</value>
<value>13736</value>
<value>7995</value>
</row>
<row>
<start>2015-03-25T00:00:56+00:00</start>
<value>www.ietf.org</value>
<value>80</value>
<value>104.20.0.85</value>
<value>14024</value>
<value>13756</value>
<value>8589</value>
</row>
<row>
<start>2015-03-25T00:00:56+00:00</start>
<value>www.google.com</value>
<value>80</value>
<value>2a00:1450:4008:800::1012</value>
<value>19246</value>
<value>19416</value>
<value>19443</value>
</row>
<row>
<start>2015-03-25T00:00:56+00:00</start>
<value>www.google.com</value>
<value>80</value>
<value>216.58.213.36</value>
<value>11692</value>
<value>11668</value>
<value>11933</value>
</row>
</task>
</report>
</rpc>
Appendix I. Example Report (JSON)
{
"report": {
"date": "2015-10-28T13:27:42+02:00",
"agent-id": "550e8400-e29b-41d4-a716-446655440000",
"group-id": "wireless measurement at the north-pole",
"task": [
{
"name": "icmp-latency-measurement",
"header": {
"column": [
"target",
"ip",
"rtt-1",
"rtt-2",
"rtt-3",
"rtt-4",
"rtt-5"
]
},
"row": [
{
"start": "2015-03-25T00:00:55+00:00",
"value": [
"www.ietf.org",
"104.20.0.85",
"14.15",
"14.14",
"14.09",
"14.17",
"14.51"
]
},
{
"start": "2015-03-25T00:00:56+00:00",
"value": [
"www.google.com",
"216.58.213.36",
"12.24",
"11.99",
"12.49",
"11.87",
"12.45"
]
}
]
},
{
"name": "happy-dns-measurement",
"header": {
"column": [
"target",
"ip",
"name"
]
},
"row": [
{
"start": "2015-03-25T00:00:56+00:00",
"value": [
"www.ietf.org",
"2400:cb00:2048:1::6814:55",
"www.ietf.org.cdn.cloudflare-dnssec.net"
]
},
{
"start": "2015-03-25T00:00:56+00:00",
"value": [
"www.ietf.org",
"2400:cb00:2048:1::6814:155",
"www.ietf.org.cdn.cloudflare-dnssec.net"
]
},
{
"start": "2015-03-25T00:00:56+00:00",
"value": [
"www.ietf.org",
"104.20.1.85",
"www.ietf.org.cdn.cloudflare-dnssec.net"
]
},
{
"start": "2015-03-25T00:00:56+00:00",
"value": [
"www.ietf.org",
"104.20.0.85",
"www.ietf.org.cdn.cloudflare-dnssec.net"
]
},
{
"start": "2015-03-25T00:00:56+00:00",
"value": [
"www.google.com",
"2a00:1450:4008:800::1012",
"ber01s08-in-x12.1e100.net"
]
},
{
"start": "2015-03-25T00:00:56+00:00",
"value": [
"www.google.com",
"216.58.213.36",
"ber01s15-in-f36.1e100.net"
]
}
]
},
{
"name": "happy-connect-measurement",
"header": {
"column": [
"target",
"port",
"ip",
"time-1",
"time-2",
"time-3"
]
},
"row": [
{
"start": "2015-03-25T00:00:56+00:00",
"value": [
"www.ietf.org",
"80",
"2400:cb00:2048:1::6814:55",
"8164",
"8019",
"14066"
]
},
{
"start": "2015-03-25T00:00:56+00:00",
"value": [
"www.ietf.org",
"80",
"2400:cb00:2048:1::6814:155",
"14131",
"14029",
"7984"
]
},
{
"start": "2015-03-25T00:00:56+00:00",
"value": [
"www.ietf.org",
"80",
"104.20.1.85",
"13821",
"13736",
"7995"
]
},
{
"start": "2015-03-25T00:00:56+00:00",
"value": [
"www.ietf.org",
"80",
"104.20.0.85",
"14024",
"13756",
"8589"
]
},
{
"start": "2015-03-25T00:00:56+00:00",
"value": [
"www.google.com",
"80",
"2a00:1450:4008:800::1012",
"19246",
"19416",
"19443"
]
},
{
"start": "2015-03-25T00:00:56+00:00",
"value": [
"www.google.com",
"80",
"216.58.213.36",
"11692",
"11668",
"11933"
]
}
]
}
]
}
}
Authors' Addresses Authors' Addresses
Juergen Schoenwaelder Juergen Schoenwaelder
Jacobs University Bremen Jacobs University Bremen
Email: j.schoenwaelder@jacobs-university.de Email: j.schoenwaelder@jacobs-university.de
Vaibhav Bajpai Vaibhav Bajpai
Jacobs University Bremen Jacobs University Bremen
 End of changes. 145 change blocks. 
675 lines changed or deleted 1461 lines changed or added

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