< draft-ietf-lmap-information-model-08.txt   draft-ietf-lmap-information-model-09.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: September 16, 2016 M. Bagnulo Expires: September 22, 2016 M. Bagnulo
Universidad Carlos III de Madrid Universidad Carlos III de Madrid
J. Schoenwaelder J. Schoenwaelder
Jacobs University Bremen Jacobs University Bremen
March 15, 2016 March 21, 2016
Information Model for Large-Scale Measurement Platforms (LMAP) Information Model for Large-Scale Measurement Platforms (LMAP)
draft-ietf-lmap-information-model-08 draft-ietf-lmap-information-model-09
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 September 16, 2016. This Internet-Draft will expire on September 22, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Notation . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Notation . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. LMAP Information Model . . . . . . . . . . . . . . . . . . . 5 3. LMAP Information Model . . . . . . . . . . . . . . . . . . . 5
3.1. Pre-Configuration Information . . . . . . . . . . . . . . 8 3.1. Pre-Configuration Information . . . . . . . . . . . . . . 9
3.1.1. Definition of ma-preconfig-obj . . . . . . . . . . . 9 3.1.1. Definition of ma-preconfig-obj . . . . . . . . . . . 10
3.2. Configuration Information . . . . . . . . . . . . . . . . 10 3.2. Configuration Information . . . . . . . . . . . . . . . . 10
3.2.1. Definition of ma-config-obj . . . . . . . . . . . . . 12 3.2.1. Definition of ma-config-obj . . . . . . . . . . . . . 12
3.3. Instruction Information . . . . . . . . . . . . . . . . . 13 3.3. Instruction Information . . . . . . . . . . . . . . . . . 13
3.3.1. Definition of ma-instruction-obj . . . . . . . . . . 15 3.3.1. Definition of ma-instruction-obj . . . . . . . . . . 16
3.3.2. Definition of ma-suppression-obj . . . . . . . . . . 16 3.3.2. Definition of ma-suppression-obj . . . . . . . . . . 16
3.4. Logging Information . . . . . . . . . . . . . . . . . . . 17 3.4. Logging Information . . . . . . . . . . . . . . . . . . . 17
3.4.1. Definition of ma-log-obj . . . . . . . . . . . . . . 19 3.4.1. Definition of ma-log-obj . . . . . . . . . . . . . . 19
3.5. Capability and Status Information . . . . . . . . . . . . 19 3.5. Capability and Status Information . . . . . . . . . . . . 19
3.5.1. Definition of ma-capability-obj . . . . . . . . . . . 19 3.5.1. Definition of ma-capability-obj . . . . . . . . . . . 19
3.5.2. Definition of ma-capability-task-obj . . . . . . . . 20 3.5.2. Definition of ma-capability-task-obj . . . . . . . . 20
3.5.3. Definition of ma-status-obj . . . . . . . . . . . . . 20 3.5.3. Definition of ma-status-obj . . . . . . . . . . . . . 20
3.5.4. Definition of ma-status-schedule-obj . . . . . . . . 21 3.5.4. Definition of ma-status-schedule-obj . . . . . . . . 21
3.5.5. Definition of ma-status-action-obj . . . . . . . . . 22 3.5.5. Definition of ma-status-action-obj . . . . . . . . . 22
3.5.6. Definition of ma-status-suppression-obj . . . . . . . 24 3.5.6. Definition of ma-status-suppression-obj . . . . . . . 24
3.5.7. Definition of ma-interface-obj . . . . . . . . . . . 24 3.5.7. Definition of ma-interface-obj . . . . . . . . . . . 25
3.6. Reporting Information . . . . . . . . . . . . . . . . . . 25 3.6. Reporting Information . . . . . . . . . . . . . . . . . . 26
3.6.1. Definition of ma-report-obj . . . . . . . . . . . . . 27 3.6.1. Definition of ma-report-obj . . . . . . . . . . . . . 27
3.6.2. Definition of ma-report-task-obj . . . . . . . . . . 27 3.6.2. Definition of ma-report-result-obj . . . . . . . . . 28
3.6.3. Definition of ma-report-row-obj . . . . . . . . . . . 28 3.6.3. Definition of ma-report-table-obj . . . . . . . . . . 29
3.7. Common Objects: Schedules . . . . . . . . . . . . . . . . 29 3.6.4. Definition of ma-report-row-obj . . . . . . . . . . . 29
3.7.1. Definition of ma-schedule-obj . . . . . . . . . . . . 30 3.7. Common Objects: Schedules . . . . . . . . . . . . . . . . 30
3.7.1. Definition of ma-schedule-obj . . . . . . . . . . . . 31
3.7.2. Definition of ma-action-obj . . . . . . . . . . . . . 32 3.7.2. Definition of ma-action-obj . . . . . . . . . . . . . 32
3.8. Common Objects: Channels . . . . . . . . . . . . . . . . 33 3.8. Common Objects: Channels . . . . . . . . . . . . . . . . 33
3.8.1. Definition of ma-channel-obj . . . . . . . . . . . . 33 3.8.1. Definition of ma-channel-obj . . . . . . . . . . . . 34
3.9. Common Objects: Task Configurations . . . . . . . . . . . 34 3.9. Common Objects: Task Configurations . . . . . . . . . . . 35
3.9.1. Definition of ma-task-obj . . . . . . . . . . . . . . 35 3.9.1. Definition of ma-task-obj . . . . . . . . . . . . . . 36
3.9.2. Definition of ma-option-obj . . . . . . . . . . . . . 36 3.9.2. Definition of ma-option-obj . . . . . . . . . . . . . 37
3.10. Common Objects: Registry Information . . . . . . . . . . 37 3.10. Common Objects: Registry Information . . . . . . . . . . 37
3.10.1. Definition of ma-metric-registry-obj . . . . . . . . 37 3.10.1. Definition of ma-metric-registry-obj . . . . . . . . 38
3.11. Common Objects: Event Information . . . . . . . . . . . . 37 3.11. Common Objects: Event Information . . . . . . . . . . . . 38
3.11.1. Definition of ma-event-obj . . . . . . . . . . . . . 38 3.11.1. Definition of ma-event-obj . . . . . . . . . . . . . 39
3.11.2. Definition of ma-periodic-obj . . . . . . . . . . . 39 3.11.2. Definition of ma-periodic-obj . . . . . . . . . . . 40
3.11.3. Definition of ma-calendar-obj . . . . . . . . . . . 40 3.11.3. Definition of ma-calendar-obj . . . . . . . . . . . 41
3.11.4. Definition of ma-one-off-obj . . . . . . . . . . . . 42 3.11.4. Definition of ma-one-off-obj . . . . . . . . . . . . 42
3.11.5. Definition of ma-immediate-obj . . . . . . . . . . . 42 3.11.5. Definition of ma-immediate-obj . . . . . . . . . . . 43
3.11.6. Definition of ma-startup-obj . . . . . . . . . . . . 42 3.11.6. Definition of ma-startup-obj . . . . . . . . . . . . 43
3.11.7. Definition of ma-controller-lost-obj . . . . . . . . 42 3.11.7. Definition of ma-controller-lost-obj . . . . . . . . 43
3.11.8. Definition of ma-controller-connected-obj . . . . . 43 3.11.8. Definition of ma-controller-connected-obj . . . . . 43
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44
5. Security Considerations . . . . . . . . . . . . . . . . . . . 43 5. Security Considerations . . . . . . . . . . . . . . . . . . . 44
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 44 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 44
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 44 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 45
7.1. Normative References . . . . . . . . . . . . . . . . . . 44 7.1. Normative References . . . . . . . . . . . . . . . . . . 45
7.2. Informative References . . . . . . . . . . . . . . . . . 44 7.2. Informative References . . . . . . . . . . . . . . . . . 45
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 45 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 46
A.1. Remove suppress-by-default . . . . . . . . . . . . . . . 45 A.1. Remove suppress-by-default . . . . . . . . . . . . . . . 46
A.2. Overlapping schedules/actions are skipped . . . . . . . . 45 A.2. Overlapping schedules/actions are skipped . . . . . . . . 46
A.3. Storage usage reporting and control . . . . . . . . . . . 45 A.3. Storage usage reporting and control . . . . . . . . . . . 46
A.4. Configuration vs. instruction: ma-task-obj . . . . . . . 45 A.4. Configuration vs. instruction: ma-task-obj . . . . . . . 46
A.5. Streamline the reporting model . . . . . . . . . . . . . 46 A.5. Streamline the reporting model . . . . . . . . . . . . . 46
Appendix B. Non-editorial Changes since -07 . . . . . . . . . . 46 Appendix B. Non-editorial Changes since -08 . . . . . . . . . . 47
Appendix C. Non-editorial Changes since -06 . . . . . . . . . . 46 Appendix C. Non-editorial Changes since -07 . . . . . . . . . . 47
Appendix D. Non-editorial Changes since -05 . . . . . . . . . . 47 Appendix D. Non-editorial Changes since -06 . . . . . . . . . . 47
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 47 Appendix E. Non-editorial Changes since -05 . . . . . . . . . . 48
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 48
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. The main components of a large-scale
measurement platform are the Measurement Agents (hereafter MAs), the measurement platform are the Measurement Agents (hereafter MAs), the
Controller(s) and the Collector(s). 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
skipping to change at page 27, line 17 skipping to change at page 27, line 42
Where the Configuration and Instruction information represent Where the Configuration and Instruction information represent
information transmitted via the Control Protocol, the Report information transmitted via the Control Protocol, the Report
represents the information that is transmitted via the Report represents the information that is transmitted via the Report
Protocol. It is constructed at the time of sending a report and Protocol. It is constructed at the time of sending a report and
represents the inherent structure of the information that is sent to represents the inherent structure of the information that is sent to
the Collector. the Collector.
3.6.1. Definition of ma-report-obj 3.6.1. Definition of ma-report-obj
object { object {
datetime ma-report-date; datetime ma-report-date;
[uuid ma-report-agent-id;] [uuid ma-report-agent-id;]
[string ma-report-group-id;] [string ma-report-group-id;]
[string ma-report-measurement-point;] [string ma-report-measurement-point;]
[ma-report-task-obj ma-report-tasks<0..*>;] [ma-report-result-obj ma-report-results<0..*>;]
} ma-report-obj; } ma-report-obj;
The ma-report-obj provides the meta-data of a single report and The ma-report-obj provides the meta-data of a single report and
consists of the following elements: consists of the following elements:
ma-report-date: The date and time when the report was ma-report-date: The date and time when the report was
sent to a collector. sent to a collector.
ma-report-agent-id: An optional uuid uniquely identifying ma-report-agent-id: An optional uuid uniquely identifying
the measurement agent. the measurement agent.
ma-report-group-id: An optional identifier of the group of ma-report-group-id: An optional identifier of the group of
measurement agents this measurement measurement agents this measurement
agent belongs to. agent belongs to.
ma-report-measurement-point: An optional identifier for the ma-report-measurement-point: An optional identifier for the
measurement point indicating where the measurement point indicating where the
measurement agent is located on a path measurement agent is located on a path
(see [RFC7398] for further details). (see [RFC7398] for further details).
ma-report-tasks: An optional and possibly empty ma-report-results: An optional and possibly empty
unordered set of tasks result objects. unordered set of result objects.
3.6.2. Definition of ma-report-result-obj
3.6.2. Definition of ma-report-task-obj
object { object {
string ma-report-task-name; string ma-report-result-schedule-name;
[ma-metric-registry-obj ma-report-task-metrics<0..*>;] string ma-report-result-action-name;
[ma-option-obj ma-report-task-options<0..*>;] string ma-report-result-task-name;
[ma-option-obj ma-report-task-action-options<0..*>;] [ma-metric-registry-obj ma-report-result-metrics<0..*>;]
[string ma-report-task-tags<0..*>;] [ma-option-obj ma-report-result-options<0..*>;]
[string ma-report-task-column-labels<0..*>;] [string ma-report-result-tags<0..*>;]
[ma-report-row-obj ma-report-task-rows<0..*>;] datetime ma-report-result-start-time;
} ma-report-task-obj; [datetime ma-report-result-end-time;]
string ma-report-result-conflicts<0..*>;
[ma-report-table-obj ma-report-result-tables<0..*>;]
} ma-report-result-obj;
The ma-report-task-obj provides the meta-data of a result report of a The ma-report-result-obj provides the meta-data of a result report of
single task. It consists of the following elements: a single executed action. It consists of the following elements:
ma-report-task-name: A name uniquely identifying the task ma-report-result-schedule-name: The name of the schedule that
that produced the results being produced the result.
reported.
ma-report-task-metrics: An optional and possibly empty ma-report-result-action-name: The name of the action in the
schedule that produced the result.
ma-report-result-task-name: The name of the task that produced
the result.
ma-report-result-metrics: An optional and possibly empty
unordered set of registered metrics unordered set of registered metrics
and associated rulels that are and associated rulels that are
reported. reported.
ma-report-task-options: An optional ordered list of task ma-report-result-options: An optional ordered joined list of
options provided by the task object. options provided by the task object
and the action object.
ma-report-task-action-options: An optional ordered list of action ma-report-result-tags: An optional unordered set of tags.
options provided by the action This is the joined set of tags
object. defined for the task object and the
action object.
ma-report-task-tags: An optional unordered set of tags. ma-report-result-start-time: The date and time of the start of the
measurement task that produced the
reported result values.
ma-report-task-column-labels: An optional and possibly empty ma-report-result-end-time: An optional date and time indicating
when the measurement task finished.
ma-report-result-conflicts: A possibly empty set of names of
tasks that might have impacted the
measurement results being reported.
ma-report-result-tables: An optional and possibly empty
unordered set of result tables.
3.6.3. Definition of ma-report-table-obj
object {
[string] ma-report-table-column-labels<0..*>;]
[ma-report-row-obj ma-report-table-rows<0..*>;]
} ma-report-table-obj;
The ma-report-table-obj represents a result table and consists of the
following elements:
ma-report-table-column-labels: An optional and possibly empty
ordered list of column labels. ordered list of column labels.
ma-report-task-rows: An optional and possibly empty ma-report-table-rows: A possibly empty ordered list of
ordered list of result rows. result rows.
3.6.3. Definition of ma-report-row-obj 3.6.4. Definition of ma-report-row-obj
object { object {
datetime ma-report-row-start-time;
[datetime ma-report-row-end-time;]
string ma-report-row-conflicts<0..*>;
data ma-report-row-values<0..*>; data ma-report-row-values<0..*>;
} ma-report-row-obj; } ma-report-row-obj;
The ma-report-row-obj represents a result row and consists of the The ma-report-row-obj represents a result row and consists of the
following elements: following elements:
ma-report-row-start-time: The date and time of the start of the
measurement task that produced the reported
result values.
ma-report-row-end-time: An optional date and time indicating when
the measurement task that produced the
reported result values finished.
ma-report-row-conflicts: A possibly empty set of names of task that
might have impacted the measurement being
reported.
ma-report-row-values: A possibly empty ordered list of result ma-report-row-values: A possibly empty ordered list of result
values. When present, it contains an values. When present, it contains an
ordered list of values that align to the ordered list of values that align to the
set of column labels for the report. set of column labels for the report.
3.7. Common Objects: Schedules 3.7. Common Objects: Schedules
A Schedule specifies the execution of a single or repeated series of A Schedule specifies the execution of a single or repeated series of
Actions. An Action is a Task with additional specific parameters. Actions. An Action is a Task with additional specific parameters.
Each Schedule contains basically two elements: an ordered list of Each Schedule contains basically two elements: an ordered list of
skipping to change at page 44, line 50 skipping to change at page 45, line 37
7.2. Informative References 7.2. Informative References
[I-D.ietf-ippm-metric-registry] [I-D.ietf-ippm-metric-registry]
Bagnulo, M., Claise, B., Eardley, P., Morton, A., and A. Bagnulo, M., Claise, B., Eardley, P., Morton, A., and A.
Akhter, "Registry for Performance Metrics", draft-ietf- Akhter, "Registry for Performance Metrics", draft-ietf-
ippm-metric-registry-05 (work in progress), October 2015. ippm-metric-registry-05 (work in progress), October 2015.
[I-D.ietf-lmap-yang] [I-D.ietf-lmap-yang]
Schoenwaelder, J. and V. Bajpai, "A YANG Data Model for Schoenwaelder, J. and V. Bajpai, "A YANG Data Model for
LMAP Measurement Agents", draft-ietf-lmap-yang-01 (work in LMAP Measurement Agents", draft-ietf-lmap-yang-03 (work in
progress), July 2015. progress), March 2016.
[RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between [RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between
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,
skipping to change at page 46, line 13 skipping to change at page 47, line 5
should read the configured tasks and then only install schedules should read the configured tasks and then only install schedules
(with actions), suppressions, and events. That is, changing ma-task- (with actions), suppressions, and events. That is, changing ma-task-
obj is not part of an instruction but only part of the configuration. obj is not part of an instruction but only part of the configuration.
A.5. Streamline the reporting model A.5. Streamline the reporting model
The reporting model may need more attention; perhaps things can be The reporting model may need more attention; perhaps things can be
streamlined and also be made more efficient. Implementation streamlined and also be made more efficient. Implementation
experience will help to work this out. experience will help to work this out.
Appendix B. Non-editorial Changes since -07 Appendix B. Non-editorial Changes since -08
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
multiple tables.
o Report schedule, action, and task name as part of the ma-report-
result-obj.
o Report conflicts per ma-report-result-obj and not per ma-report-
row-obj.
o Report the start/end time as part of the ma-report-result-obj.
Appendix C. 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.
Appendix C. Non-editorial Changes since -06 Appendix D. 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 47, line 24 skipping to change at page 48, 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)
Appendix D. Non-editorial Changes since -05 Appendix E. 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. 34 change blocks. 
92 lines changed or deleted 127 lines changed or added

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