draft-ietf-lmap-information-model-17.txt   draft-ietf-lmap-information-model-18.txt 
Network Working Group T. Burbridge Network Working Group T. Burbridge
Internet-Draft P. Eardley Internet-Draft P. Eardley
Intended status: Standards Track BT Intended status: Standards Track BT
Expires: August 26, 2017 M. Bagnulo Expires: October 23, 2017 M. Bagnulo
Universidad Carlos III de Madrid Universidad Carlos III de Madrid
J. Schoenwaelder J. Schoenwaelder
Jacobs University Bremen Jacobs University Bremen
February 22, 2017 April 21, 2017
Information Model for Large-Scale Measurement Platforms (LMAP) Information Model for Large-Scale Measurement Platforms (LMAP)
draft-ietf-lmap-information-model-17 draft-ietf-lmap-information-model-18
Abstract Abstract
This Information Model applies to the Measurement Agent within a This Information Model applies to the Measurement Agent within a
Large-Scale Measurement Platform. As such it outlines the Large-Scale Measurement Platform. As such it outlines the
information that is (pre-)configured on the Measurement Agent or information that is (pre-)configured on the Measurement Agent or
exists in communications with a Controller or Collector within an exists in communications with a Controller or Collector within an
LMAP framework. The purpose of such an Information Model is to LMAP framework. The purpose of such an Information Model is to
provide a protocol and device independent view of the Measurement provide a protocol and device independent view of the Measurement
Agent that can be implemented via one or more Control and Report Agent that can be implemented via one or more Control and Report
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 August 26, 2017. This Internet-Draft will expire on October 23, 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 3, line 27 skipping to change at page 3, line 27
3.11.7. Definition of ma-controller-lost-obj . . . . . . . . 46 3.11.7. Definition of ma-controller-lost-obj . . . . . . . . 46
3.11.8. Definition of ma-controller-connected-obj . . . . . 46 3.11.8. Definition of ma-controller-connected-obj . . . . . 46
4. Example Execution . . . . . . . . . . . . . . . . . . . . . . 47 4. Example Execution . . . . . . . . . . . . . . . . . . . . . . 47
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48
6. Security Considerations . . . . . . . . . . . . . . . . . . . 49 6. Security Considerations . . . . . . . . . . . . . . . . . . . 49
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 49 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 49
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 50 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 50
8.1. Normative References . . . . . . . . . . . . . . . . . . 50 8.1. Normative References . . . . . . . . . . . . . . . . . . 50
8.2. Informative References . . . . . . . . . . . . . . . . . 50 8.2. Informative References . . . . . . . . . . . . . . . . . 50
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 51 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 51
A.1. Non-editorial changes since -16 . . . . . . . . . . . . . 51 A.1. Non-editorial changes since -17 . . . . . . . . . . . . . 51
A.2. Non-editorial changes since -15 . . . . . . . . . . . . . 51 A.2. Non-editorial changes since -16 . . . . . . . . . . . . . 51
A.3. Non-editorial changes since -14 . . . . . . . . . . . . . 51 A.3. Non-editorial changes since -15 . . . . . . . . . . . . . 51
A.4. Non-editorial changes since -13 . . . . . . . . . . . . . 51 A.4. Non-editorial changes since -14 . . . . . . . . . . . . . 51
A.5. Non-editorial changes since -12 . . . . . . . . . . . . . 51 A.5. Non-editorial changes since -13 . . . . . . . . . . . . . 52
A.6. Non-editorial changes since -11 . . . . . . . . . . . . . 52 A.6. Non-editorial changes since -12 . . . . . . . . . . . . . 52
A.7. Non-editorial changes since -10 . . . . . . . . . . . . . 52 A.7. Non-editorial changes since -11 . . . . . . . . . . . . . 52
A.8. Non-editorial changes since -09 . . . . . . . . . . . . . 52 A.8. Non-editorial changes since -10 . . . . . . . . . . . . . 52
A.9. Non-editorial changes since -08 . . . . . . . . . . . . . 52 A.9. Non-editorial changes since -09 . . . . . . . . . . . . . 52
A.10. Non-editorial changes since -07 . . . . . . . . . . . . . 53 A.10. Non-editorial changes since -08 . . . . . . . . . . . . . 53
A.11. Non-editorial changes since -06 . . . . . . . . . . . . . 53 A.11. Non-editorial changes since -07 . . . . . . . . . . . . . 53
A.12. Non-editorial changes since -05 . . . . . . . . . . . . . 54 A.12. Non-editorial changes since -06 . . . . . . . . . . . . . 53
A.13. Non-editorial changes since -05 . . . . . . . . . . . . . 54
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 54 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 54
1. Introduction 1. Introduction
A large-scale measurement platform is a collection of components that A large-scale measurement platform is a collection of components that
work in a coordinated fashion to perform measurements from a large work in a coordinated fashion to perform measurements from a large
number of vantage points. The main components of a large-scale number of vantage points. A typical use case is the execution of
measurement platform are the Measurement Agents (hereafter MAs), the broadband measurements [RFC7536]. The main components of a large-
Controller(s) and the Collector(s). scale measurement platform are the Measurement Agents (hereafter
MAs), the Controller(s) and the Collector(s).
The MAs are the elements actually performing the measurements. The The MAs are the elements actually performing the measurements. The
MAs are controlled by exactly one Controller at a time and the MAs are controlled by exactly one Controller at a time and the
Collectors gather the results generated by the MAs. In a nutshell, Collectors gather the results generated by the MAs. In a nutshell,
the normal operation of a large-scale measurement platform starts the normal operation of a large-scale measurement platform starts
with the Controller instructing a set of one or more MAs to perform a with the Controller instructing a set of one or more MAs to perform a
set of one or more Measurement Tasks at a certain point in time. The set of one or more Measurement Tasks at a certain point in time. The
MAs execute the instructions from a Controller, and once they have MAs execute the instructions from a Controller, and once they have
done so, they report the results of the measurements to one or more done so, they report the results of the measurements to one or more
Collectors. The overall framework for a large-scale measurement Collectors. The overall framework for a large-scale measurement
skipping to change at page 6, line 22 skipping to change at page 6, line 24
The information described herein relates to the information stored, The information described herein relates to the information stored,
received or transmitted by a Measurement Agent as described within received or transmitted by a Measurement Agent as described within
the LMAP framework [RFC7594]. As such, some subsets of this the LMAP framework [RFC7594]. As such, some subsets of this
information model are applicable to the measurement Controller, information model are applicable to the measurement Controller,
Collector and any device management system that pre-configures the Collector and any device management system that pre-configures the
Measurement Agent. The information described in these models will be Measurement Agent. The information described in these models will be
transmitted by protocols using interfaces between the Measurement transmitted by protocols using interfaces between the Measurement
Agent and such systems according to a Data Model. Agent and such systems according to a Data Model.
For clarity the information model is divided into six sections: The information model is divided into six aspects. Firstly the
grouping of information facilitates reader understanding. Secondly,
the particular groupings chosen are expected to map to different
protocols or different transmissions within those protocols.
1. Pre-Configuration Information. Information pre-configured on the 1. Pre-Configuration Information. Information pre-configured on the
Measurement Agent prior to any communication with other Measurement Agent prior to any communication with other
components of the LMAP architecture (i.e., the Controller, components of the LMAP architecture (i.e., the Controller,
Collector and Measurement Peers), specifically detailing how to Collector and Measurement Peers), specifically detailing how to
communicate with a Controller and whether the device is enabled communicate with a Controller and whether the device is enabled
to participate as an MA. to participate as an MA.
2. Configuration Information. Update of the pre-configuration 2. Configuration Information. Update of the pre-configuration
information during the registration of the MA or subsequent information during the registration of the MA or subsequent
skipping to change at page 7, line 27 skipping to change at page 7, line 32
extracted by a task and reported by the MA in the reporting extracted by a task and reported by the MA in the reporting
communication to a Collector. communication to a Collector.
It should also be noted that the MA may be in communication with It should also be noted that the MA may be in communication with
other management systems which may be responsible for configuring and other management systems which may be responsible for configuring and
retrieving information from the MA device. Such systems, where retrieving information from the MA device. Such systems, where
available, can perform an important role in transferring the pre- available, can perform an important role in transferring the pre-
configuration information to the MA or enabling/disabling the configuration information to the MA or enabling/disabling the
measurement functionality of the MA. measurement functionality of the MA.
The Information Model is divided into sub-sections for a number of
reasons. Firstly the grouping of information facilitates reader
understanding. Secondly, the particular groupings chosen are
expected to map to different protocols or different transmissions
within those protocols.
The granularity of data transmitted in each operation of the Control The granularity of data transmitted in each operation of the Control
and Report Protocols is not dictated by the Information Model. For and Report Protocols is not dictated by the Information Model. For
example, the Instruction object may be delivered in a single example, the Instruction object may be delivered in a single
operation. Alternatively, Schedules and Task Configurations may be operation. Alternatively, Schedules and Task Configurations may be
separated or even each Schedule/Task Configuration may be delivered separated or even each Schedule/Task Configuration may be delivered
individually. Similarly the Information Model does not dictate individually. Similarly the Information Model does not dictate
whether data is read, write, or read/write. For example, some whether data is read, write, or read/write. For example, some
Control Protocols may have the ability to read back Configuration and Control Protocols may have the ability to read back Configuration and
Instruction information which have been previously set on the MA. Instruction information which have been previously set on the MA.
Lastly, while some protocols may simply overwrite information (for Lastly, while some protocols may simply overwrite information (for
example refreshing the entire Instruction Information), other example refreshing the entire Instruction Information), other
protocols may have the ability to update or delete selected items of protocols may have the ability to update or delete selected items of
information. information.
The information in these six sections is captured by a number of The information modeled by the six aspects of the information model
common information objects. These objects are also described later is supported by a number of common information objects. These
in this document and comprise of: objects are also described later in this document and comprise of:
a. Schedules. A set of Schedules tells the MA to execute Actions. a. Schedules. A set of Schedules tells the MA to execute Actions.
An Action of a Schedule leads to the execution of a Task. An Action of a Schedule leads to the execution of a Task.
Without a Schedule no Task (including measurements or reporting Without a Schedule no Task (including measurements or reporting
or communicating with the Controller) is ever executed. or communicating with the Controller) is ever executed.
Schedules are used within the Instruction to specify what tasks Schedules are used within the Instruction to specify what tasks
should be performed, when, and how to direct their results. A should be performed, when, and how to direct their results. A
Schedule is also used within the pre-Configuration and Schedule is also used within the pre-Configuration and
Configuration information in order to execute the Task or Tasks Configuration information in order to execute the Task or Tasks
required to communicate with the Controller. A specific Schedule required to communicate with the Controller. A specific Schedule
can only be active once. Attempts to start a Schedule while the can only be active once. Attempts to start a Schedule while the
same Schedule is still running will fail. same Schedule is still running will fail.
skipping to change at page 11, line 14 skipping to change at page 11, line 14
It can be seen that these Channels, Schedules and Task Configurations It can be seen that these Channels, Schedules and Task Configurations
for the initial MA-Controller communication are no different in terms for the initial MA-Controller communication are no different in terms
of the Information Model to any other Channel, Schedule or Task of the Information Model to any other Channel, Schedule or Task
Configuration that might execute a Measurement Task or report the Configuration that might execute a Measurement Task or report the
measurement results (as described later). measurement results (as described later).
The MA may be pre-configured with an MA ID, or may use a Device ID in The MA may be pre-configured with an MA ID, or may use a Device ID in
the first Controller contact before it is assigned an MA ID. The the first Controller contact before it is assigned an MA ID. The
Device ID may be a MAC address or some other device identifier Device ID may be a MAC address or some other device identifier
expressed as a URI. If the MA ID is not provided at this stage then expressed as a URI. If the MA ID is not provided at this stage, then
it must be provided by the Controller during Configuration. it must be provided by the Controller during Configuration.
3.1.1. Definition of ma-preconfig-obj 3.1.1. Definition of ma-preconfig-obj
object { object {
[uuid ma-preconfig-agent-id;] [uuid ma-preconfig-agent-id;]
ma-task-obj ma-preconfig-control-tasks<1..*>; ma-task-obj ma-preconfig-control-tasks<1..*>;
ma-channel-obj ma-preconfig-control-channels<1..*>; ma-channel-obj ma-preconfig-control-channels<1..*>;
ma-schedule-obj ma-preconfig-control-schedules<1..*>; ma-schedule-obj ma-preconfig-control-schedules<1..*>;
[uri ma-preconfig-device-id;] [uri ma-preconfig-device-id;]
skipping to change at page 36, line 32 skipping to change at page 36, line 32
ma-action-tags: An optional unordered set of tags that ma-action-tags: An optional unordered set of tags that
are reported together with the are reported together with the
measurement results to a collector. measurement results to a collector.
ma-action-suppression-tags: An optional unordered set of ma-action-suppression-tags: An optional unordered set of
suppression tags that are used to suppression tags that are used to
select actions to be suppressed. select actions to be suppressed.
3.8. Common Objects: Channels 3.8. Common Objects: Channels
A Channel defines a bi-directional communication channel between the A Channel defines a bi-directional communication mechanism between
MA and a Controller or Collector. Multiple Channels can be defined the MA and a Controller or Collector. Multiple Channels can be
to enable results to be split or duplicated across different defined to enable results to be split or duplicated across different
Collectors. Collectors.
Each Channel contains the details of the remote endpoint (including Each Channel contains the details of the remote endpoint (including
location and security credential information such as the location and security credential information such as a certificate).
certificate). The timing of when to communicate over a Channel is The timing of when to communicate over a Channel is specified by the
specified by the Schedule which executes the corresponding Control or Schedule which executes the corresponding Control or Reporting Task.
Reporting Task. The certificate can be the digital certificate The certificate can be the digital certificate associated to the FQDN
associated to the FQDN in the URL or it can be the certificate of the in the URL or it can be the certificate of the Certification
Certification Authority that was used to issue the certificate for Authority that was used to issue the certificate for the FQDN (Fully
the FQDN (Fully Qualified Domain Name) of the target URL (which will Qualified Domain Name) of the target URL (which will be retrieved
be retrieved later on using a communication protocol such as TLS). later on using a communication protocol such as TLS). In order to
In order to establish a secure channel, the MA will use its own establish a secure channel, the MA will use its own security
security credentials (in the Configuration Information) and the given credentials (in the Configuration Information) and the given
credentials for the individual Channel end-point. credentials for the individual Channel end-point.
As with the Task Configurations, each Channel is also given a text As with the Task Configurations, each Channel is also given a text
name by which it can be referenced as a Task Option. name by which it can be referenced as a Task Option.
Although the same in terms of information, Channels used for Although the same in terms of information, Channels used for
communication with the Controller are referred to as Control Channels communication with the Controller are referred to as Control Channels
whereas Channels to Collectors are referred to as Report Channels. whereas Channels to Collectors are referred to as Report Channels.
Hence Control Channels will be referenced from Control Tasks executed Hence Control Channels will be referenced from Control Tasks executed
by a Control Schedule, whereas Report Channels will be referenced by a Control Schedule, whereas Report Channels will be referenced
skipping to change at page 49, line 30 skipping to change at page 49, line 30
The second consideration is that no mandated information items should The second consideration is that no mandated information items should
pose a risk to confidentiality or privacy given such secure pose a risk to confidentiality or privacy given such secure
communication channels. For this latter reason items such as the MA communication channels. For this latter reason items such as the MA
context and MA ID are left optional and can be excluded from some context and MA ID are left optional and can be excluded from some
deployments. This may, for example, allow the MA to remain anonymous deployments. This may, for example, allow the MA to remain anonymous
and for information about location or other context that might be and for information about location or other context that might be
used to identify or track the MA to be omitted or blurred. used to identify or track the MA to be omitted or blurred.
Implementations and deployments should also be careful about exposing Implementations and deployments should also be careful about exposing
device-ids when this is not strictly needed. device-ids when this is not strictly needed.
An implementation of this Information Model should support wherever An implementation of this Information Model should support all the
relevant, all the security and privacy requirements associated with security and privacy requirements associated with the LMAP Framework
the LMAP Framework. In addition, users of this Information Model are [RFC7594]. In addition, users of this Information Model are advised
advised to choose identifiers for Group IDs, tags or names of to choose identifiers for Group IDs, tags or names of information
information model objects (e.g., configured tasks, schedules or model objects (e.g., configured tasks, schedules or actions) that do
actions) that do not reveal any sensitive information to people not reveal any sensitive information to people authorized to process
authorized to process measurement results but who are not authorized measurement results but who are not authorized to know details about
to know details about the Measurement Agents that were used to the Measurement Agents that were used to perform the measurement.
perform the measurement.
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): Vaibhav Bajpai, Michael (apologies to those unintentionally omitted): Vaibhav Bajpai, Michael
Bugenhagen, Timothy Carey, Alissa Cooper, Kenneth Ko, Al Morton, Dan Bugenhagen, Timothy Carey, Alissa Cooper, Kenneth Ko, Al Morton, Dan
Romascanu, Henning Schulzrinne, Andrea Soppera, Barbara Stark, and Romascanu, Henning Schulzrinne, Andrea Soppera, Barbara Stark, and
Jason Weil. Jason Weil.
skipping to change at page 51, line 16 skipping to change at page 51, line 16
Information Models and Data Models", RFC 3444, DOI 10 Information Models and Data Models", RFC 3444, DOI 10
.17487/RFC3444, January 2003, .17487/RFC3444, January 2003,
<http://www.rfc-editor.org/info/rfc3444>. <http://www.rfc-editor.org/info/rfc3444>.
[RFC7398] Bagnulo, M., Burbridge, T., Crawford, S., Eardley, P., and [RFC7398] Bagnulo, M., Burbridge, T., Crawford, S., Eardley, P., and
A. Morton, "A Reference Path and Measurement Points for A. Morton, "A Reference Path and Measurement Points for
Large-Scale Measurement of Broadband Performance", RFC Large-Scale Measurement of Broadband Performance", RFC
7398, DOI 10.17487/RFC7398, February 2015, 7398, DOI 10.17487/RFC7398, February 2015,
<http://www.rfc-editor.org/info/rfc7398>. <http://www.rfc-editor.org/info/rfc7398>.
[RFC7536] Linsner, M., Eardley, P., Burbridge, T., and F. Sorensen,
"Large-Scale Broadband Measurement Use Cases", RFC 7536,
DOI 10.17487/RFC7536, May 2015,
<http://www.rfc-editor.org/info/rfc7536>.
[RFC7594] Eardley, P., Morton, A., Bagnulo, M., Burbridge, T., [RFC7594] Eardley, P., Morton, A., Bagnulo, M., Burbridge, T.,
Aitken, P., and A. Akhter, "A Framework for Large-Scale Aitken, P., and A. Akhter, "A Framework for Large-Scale
Measurement of Broadband Performance (LMAP)", RFC 7594, Measurement of Broadband Performance (LMAP)", RFC 7594,
DOI 10.17487/RFC7594, September 2015, DOI 10.17487/RFC7594, September 2015,
<http://www.rfc-editor.org/info/rfc7594>. <http://www.rfc-editor.org/info/rfc7594>.
Appendix A. Change History Appendix A. Change History
Note to the RFC Editor: this section should be removed on publication Note to the RFC Editor: this section should be removed on publication
as an RFC. as an RFC.
A.1. Non-editorial changes since -16 A.1. Non-editorial changes since -17
o The information model is subdivided into aspects and not sections.
o Changes to address the GEN-ART review comments.
A.2. Non-editorial changes since -16
o Addressing Alissa Cooper's review comments. o Addressing Alissa Cooper's review comments.
A.2. Non-editorial changes since -15 A.3. Non-editorial changes since -15
o The reference to the framework is now informational. o The reference to the framework is now informational.
A.3. Non-editorial changes since -14 A.4. Non-editorial changes since -14
o Clarified that the cycle number is in UTC. o Clarified that the cycle number is in UTC.
A.4. Non-editorial changes since -13 A.5. Non-editorial changes since -13
o Removed the ma-config-device-id from the ma-config-obj. o Removed the ma-config-device-id from the ma-config-obj.
o Added ma-config-report-group-id and clarified how two flags ma- o Added ma-config-report-group-id and clarified how two flags ma-
config-report-agent-id and ma-config-report-group-id work. config-report-agent-id and ma-config-report-group-id work.
A.5. Non-editorial changes since -12 A.6. Non-editorial changes since -12
o Renamed the ma-metrics-registry-obj to ma-registry-obj since tasks o Renamed the ma-metrics-registry-obj to ma-registry-obj since tasks
may refer to different registries (not just a metrics registry). may refer to different registries (not just a metrics registry).
o Clarifications and bug fixes. o Clarifications and bug fixes.
A.6. Non-editorial changes since -11 A.7. Non-editorial changes since -11
o Clarifications and bug fixes. o Clarifications and bug fixes.
A.7. Non-editorial changes since -10 A.8. Non-editorial changes since -10
o Rewrote the text concerning the well-known "channel" option name. o Rewrote the text concerning the well-known "channel" option name.
o Added ma-report-result-event-time, ma-report-result-cycle-number, o Added ma-report-result-event-time, ma-report-result-cycle-number,
and ma-event-cycle-interval. and ma-event-cycle-interval.
o Added ma-capability-tags. o Added ma-capability-tags.
o Added a new section showing an example execution. o Added a new section showing an example execution.
o Several clarifications and bug fixes. o Several clarifications and bug fixes.
A.8. Non-editorial changes since -09 A.9. Non-editorial changes since -09
o Added ma-status-schedule-storage and ma-status-action-storage. o Added ma-status-schedule-storage and ma-status-action-storage.
o Removed suppress-by-default. o Removed suppress-by-default.
o Moved ma-report-result-metrics of the ma-report-result-obj to ma- o Moved ma-report-result-metrics of the ma-report-result-obj to ma-
report-table-metrics of the ma-report-table-obj so that the report-table-metrics of the ma-report-table-obj so that the
relationship between metrics and result tables is clear. relationship between metrics and result tables is clear.
o Added ma-report-conflict-obj. o Added ma-report-conflict-obj.
o Added ma-report-result-status to ma-report-result-obj. o Added ma-report-result-status to ma-report-result-obj.
o Several clarifications and bug fixes. o Several clarifications and bug fixes.
A.9. Non-editorial changes since -08 A.10. Non-editorial changes since -08
o Refactored the ma-report-task-obj into the ma-report-result-obj. o Refactored the ma-report-task-obj into the ma-report-result-obj.
o Introduced the ma-report-table-obj so that a result can contain o Introduced the ma-report-table-obj so that a result can contain
multiple tables. multiple tables.
o Report schedule, action, and task name as part of the ma-report- o Report schedule, action, and task name as part of the ma-report-
result-obj. result-obj.
o Report conflicts per ma-report-result-obj and not per ma-report- o Report conflicts per ma-report-result-obj and not per ma-report-
row-obj. row-obj.
o Report the start/end time as part of the ma-report-result-obj. o Report the start/end time as part of the ma-report-result-obj.
A.10. Non-editorial changes since -07 A.11. Non-editorial changes since -07
o Added ma-schedule-end and ma-schedule-duration. o Added ma-schedule-end and ma-schedule-duration.
o Changed the granularity of scheduler timings to seconds. o Changed the granularity of scheduler timings to seconds.
o Added ma-status-suppression-obj to report the status of o Added ma-status-suppression-obj to report the status of
suppressions as done in the YANG data model. suppressions as done in the YANG data model.
o Added counters to schedule and action status objects to match the o Added counters to schedule and action status objects to match the
counters in the YANG data model. counters in the YANG data model.
o Using tags to pass information such as a measurement cycle o Using tags to pass information such as a measurement cycle
identifier to the collector. identifier to the collector.
o Using suppression tags and glob-style matching to select schedules o Using suppression tags and glob-style matching to select schedules
and actions to be suppressed. and actions to be suppressed.
A.11. Non-editorial changes since -06 A.12. Non-editorial changes since -06
o The default execution mode is pipelined (LI12) o The default execution mode is pipelined (LI12)
o Added text to define which action consumes data in sequential, o Added text to define which action consumes data in sequential,
pipelines, and parallel execution mode (LI11) pipelines, and parallel execution mode (LI11)
o Added ma-config-measurement-point, ma-report-measurement-point, o Added ma-config-measurement-point, ma-report-measurement-point,
and ma-config-report-measurement-point to configure and report the and ma-config-report-measurement-point to configure and report the
measurement point (LI10) measurement point (LI10)
skipping to change at page 54, line 12 skipping to change at page 54, line 27
o Introduced ma-capability-obj and ma-capability-task-obj to expose o Introduced ma-capability-obj and ma-capability-task-obj to expose
the capabilities of a measurement agent (LI05) the capabilities of a measurement agent (LI05)
o Use 'ordered list' or 'unordered set' instead of list, collection, o Use 'ordered list' or 'unordered set' instead of list, collection,
etc. (LI02) etc. (LI02)
o Clarification that Actions are part of a Schedule (LI03) o Clarification that Actions are part of a Schedule (LI03)
o Deleted terms that are not strictly needed (LI04) o Deleted terms that are not strictly needed (LI04)
A.12. Non-editorial changes since -05 A.13. Non-editorial changes since -05
o A task can now reference multiply registry entries. o A task can now reference multiply registry entries.
o Consistent usage of the term Action and Task. o Consistent usage of the term Action and Task.
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).
 End of changes. 27 change blocks. 
65 lines changed or deleted 73 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/