< draft-ietf-lmap-information-model-12.txt   draft-ietf-lmap-information-model-13.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: May 4, 2017 M. Bagnulo Expires: May 21, 2017 M. Bagnulo
Universidad Carlos III de Madrid Universidad Carlos III de Madrid
J. Schoenwaelder J. Schoenwaelder
Jacobs University Bremen Jacobs University Bremen
October 31, 2016 November 17, 2016
Information Model for Large-Scale Measurement Platforms (LMAP) Information Model for Large-Scale Measurement Platforms (LMAP)
draft-ietf-lmap-information-model-12 draft-ietf-lmap-information-model-13
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 May 4, 2017. This Internet-Draft will expire on May 21, 2017.
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
skipping to change at page 3, line 23 skipping to change at page 3, line 23
3.11.3. Definition of ma-calendar-obj . . . . . . . . . . . 42 3.11.3. Definition of ma-calendar-obj . . . . . . . . . . . 42
3.11.4. Definition of ma-one-off-obj . . . . . . . . . . . . 44 3.11.4. Definition of ma-one-off-obj . . . . . . . . . . . . 44
3.11.5. Definition of ma-immediate-obj . . . . . . . . . . . 45 3.11.5. Definition of ma-immediate-obj . . . . . . . . . . . 45
3.11.6. Definition of ma-startup-obj . . . . . . . . . . . . 45 3.11.6. Definition of ma-startup-obj . . . . . . . . . . . . 45
3.11.7. Definition of ma-controller-lost-obj . . . . . . . . 45 3.11.7. Definition of ma-controller-lost-obj . . . . . . . . 45
3.11.8. Definition of ma-controller-connected-obj . . . . . 45 3.11.8. Definition of ma-controller-connected-obj . . . . . 45
4. Example Execution . . . . . . . . . . . . . . . . . . . . . . 46 4. Example Execution . . . . . . . . . . . . . . . . . . . . . . 46
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47
6. Security Considerations . . . . . . . . . . . . . . . . . . . 48 6. Security Considerations . . . . . . . . . . . . . . . . . . . 48
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 48 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 48
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 48 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 49
8.1. Normative References . . . . . . . . . . . . . . . . . . 49 8.1. Normative References . . . . . . . . . . . . . . . . . . 49
8.2. Informative References . . . . . . . . . . . . . . . . . 49 8.2. Informative References . . . . . . . . . . . . . . . . . 49
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 49 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 49
A.1. Configuration of the device-id . . . . . . . . . . . . . 50 A.1. Non-editorial changes since -13 . . . . . . . . . . . . . 50
A.2. Reporting of agent-id and group-id . . . . . . . . . . . 50 A.2. Non-editorial changes since -12 . . . . . . . . . . . . . 50
Appendix B. Change History . . . . . . . . . . . . . . . . . . . 50 A.3. Non-editorial changes since -11 . . . . . . . . . . . . . 50
B.1. Non-editorial changes since -12 . . . . . . . . . . . . . 50 A.4. Non-editorial changes since -10 . . . . . . . . . . . . . 50
B.2. Non-editorial changes since -11 . . . . . . . . . . . . . 50 A.5. Non-editorial changes since -09 . . . . . . . . . . . . . 50
B.3. Non-editorial changes since -10 . . . . . . . . . . . . . 50 A.6. Non-editorial changes since -08 . . . . . . . . . . . . . 51
B.4. Non-editorial changes since -09 . . . . . . . . . . . . . 51 A.7. Non-editorial changes since -07 . . . . . . . . . . . . . 51
B.5. Non-editorial changes since -08 . . . . . . . . . . . . . 51 A.8. Non-editorial changes since -06 . . . . . . . . . . . . . 51
B.6. Non-editorial changes since -07 . . . . . . . . . . . . . 51 A.9. Non-editorial changes since -05 . . . . . . . . . . . . . 52
B.7. Non-editorial changes since -06 . . . . . . . . . . . . . 52 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 52
B.8. Non-editorial changes since -05 . . . . . . . . . . . . . 52
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 53
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 10, line 28 skipping to change at page 10, line 28
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;]
credentials ma-preconfig-credentials; credentials ma-preconfig-credentials;
} ma-preconfig-obj; } ma-preconfig-obj;
The ma-preconfig-obj is essentially a subset of the ma-config-obj The ma-preconfig-obj describes information that needs to be available
described below. The ma-preconfig-obj consists of the following to the MA in order to bootstrap communication with a Controller. The
elements: ma-preconfig-obj consists of the following elements:
ma-preconfig-agent-id: An optional uuid uniquely identifying ma-preconfig-agent-id: An optional uuid uniquely identifying
the measurement agent. the measurement agent.
ma-preconfig-control-tasks: An unordered set of tasks objects. ma-preconfig-control-tasks: An unordered set of tasks objects.
ma-preconfig-control-channels: An unordered set of channel objects. ma-preconfig-control-channels: An unordered set of channel objects.
ma-preconfig-control-schedules: An unordered set of scheduling ma-preconfig-control-schedules: An unordered set of scheduling
objects. objects.
skipping to change at page 11, line 31 skipping to change at page 11, line 31
In addition the MA will be given further items of information that In addition the MA will be given further items of information that
relate specifically to the MA rather than the measurements it is to relate specifically to the MA rather than the measurements it is to
conduct or how to report results. The assignment of an ID to the MA conduct or how to report results. The assignment of an ID to the MA
is mandatory. If the MA Agent ID was not optionally provided during is mandatory. If the MA Agent ID was not optionally provided during
the pre-configuration then one must be provided by the Controller the pre-configuration then one must be provided by the Controller
during Configuration. Optionally a Group ID may also be given which during Configuration. Optionally a Group ID may also be given which
identifies a group of interest to which that MA belongs. For example identifies a group of interest to which that MA belongs. For example
the group could represent an ISP, broadband product, technology, the group could represent an ISP, broadband product, technology,
market classification, geographic region, or a combination of market classification, geographic region, or a combination of
multiple such characteristics. Where the Measurement Group ID is set multiple such characteristics. Additional flags control whether the
an additional flag (the Report MA ID flag) is required to control MA ID or the Group ID are included in Reports. The reporting of a
whether the Measurement Agent ID is also to be reported. The Group ID without the MA ID allows the MA to remain anonymous, which
reporting of a Group ID without the MA ID allows the MA to remain may be particularly useful to prevent tracking of mobile MA devices.
anonymous, which may be particularly useful to prevent tracking of
mobile MA devices.
Optionally an MA can also be configured to stop executing any Optionally an MA can also be configured to stop executing any
Instruction Schedule if the Controller is unreachable. This can be Instruction Schedule if the Controller is unreachable. This can be
used as a fail-safe to stop Measurement and other Tasks being used as a fail-safe to stop Measurement and other Tasks being
conducted when there is doubt that the Instruction Information is conducted when there is doubt that the Instruction Information is
still valid. This is simply represented as a time window in seconds still valid. This is simply represented as a time window in seconds
since the last communication with the Controller after which an Event since the last communication with the Controller after which an Event
is generated that can trigger the suspension of Instruction is generated that can trigger the suspension of Instruction
Schedules. The appropriate value of the time window will depend on Schedules. The appropriate value of the time window will depend on
the specified communication Schedule with the Controller and the the specified communication Schedule with the Controller and the
skipping to change at page 12, line 18 skipping to change at page 12, line 16
Configuration and Instruction information by examining the Capability Configuration and Instruction information by examining the Capability
and Status information for the MA. and Status information for the MA.
3.2.1. Definition of ma-config-obj 3.2.1. Definition of ma-config-obj
object { object {
uuid ma-config-agent-id; uuid ma-config-agent-id;
ma-task-obj ma-config-control-tasks<1..*>; ma-task-obj ma-config-control-tasks<1..*>;
ma-channel-obj ma-config-control-channels<1..*>; ma-channel-obj ma-config-control-channels<1..*>;
ma-schedule-obj ma-config-control-schedules<1..*>; ma-schedule-obj ma-config-control-schedules<1..*>;
[uri ma-config-device-id;]
credentials ma-config-credentials; credentials ma-config-credentials;
[string ma-config-group-id;] [string ma-config-group-id;]
[string ma-config-measurement-point;] [string ma-config-measurement-point;]
[boolean ma-config-report-agent-id;] [boolean ma-config-report-agent-id;]
[boolean ma-config-report-group-id;]
[boolean ma-config-report-measurement-point;] [boolean ma-config-report-measurement-point;]
[int ma-config-controller-timeout;] [int ma-config-controller-timeout;]
} ma-config-obj; } ma-config-obj;
The ma-config-obj consists of the following elements: The ma-config-obj consists of the following elements:
ma-config-agent-id: A uuid uniquely identifying the ma-config-agent-id: A uuid uniquely identifying the
measurement agent. measurement agent.
ma-config-control-tasks: An unordered set of task objects. ma-config-control-tasks: An unordered set of task objects.
ma-config-control-channels: An unordered set of channel ma-config-control-channels: An unordered set of channel
objects. objects.
ma-config-control-schedules: An unordered set of scheduling ma-config-control-schedules: An unordered set of scheduling
objects. objects.
ma-config-device-id: An optional identifier for the
device.
ma-config-credentials: The security credentials used by ma-config-credentials: The security credentials used by
the measurement agent. the measurement agent.
ma-config-group-id: An optional identifier of the ma-config-group-id: An optional identifier of the
group of measurement agents this group of measurement agents this
measurement agent belongs to. measurement agent belongs to.
ma-config-measurement-point: An optional identifier for the ma-config-measurement-point: An optional identifier for the
measurement point indicating measurement point indicating
where the measurement agent is where the measurement agent is
located on a path (see [RFC7398] located on a path (see [RFC7398]
for further details). for further details).
ma-config-report-agent-id: An optional flag indicating ma-config-report-agent-id: An optional flag indicating
whether the identifier (ma- whether the agent identifier (ma-
config-agent-id) should be config-agent-id) is included in
included in reports. The default reports. The default value is
value is false. true.
ma-config-report-group-id: An optional flag indicating
whether the group identifier (ma-
config-group-id) is included in
reports. The default value is
false.
ma-config-report-measurement-point: An optional flag indicating ma-config-report-measurement-point: An optional flag indicating
whether the measurement point whether the measurement point
(ma-config-measurement-point) (ma-config-measurement-point)
should be included in reports. should be included in reports.
The default value is false. The default value is false.
ma-config-controller-timeout: A timer is started after each ma-config-controller-timeout: A timer is started after each
successful contact with a successful contact with a
controller. When the timer controller. When the timer
skipping to change at page 48, line 35 skipping to change at page 48, line 35
anonymous and for information about location or other context that anonymous and for information about location or other context that
might be used to identify or track the MA to be omitted or blurred. might be used to identify or track the MA to be omitted or blurred.
The Information Model should support wherever relevant, all the The Information Model should support wherever relevant, all the
security and privacy requirements associated with the LMAP Framework. security and privacy requirements associated with the LMAP Framework.
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, Timothy (apologies to those unintentionally omitted): Vaibhav Bajpai, Michael
Carey, Al Morton, Dan Romascanu, Andrea Soppera, and Barbara Stark. Bugenhagen, Timothy Carey, Alissa Cooper, Kenneth Ko, Al Morton, Dan
(XXX: complete this list) Romascanu, Henning Schulzrinne, Andrea Soppera, Barbara Stark, and
Jason Weil.
Philip Eardley, Trevor Burbridge, Marcelo Bagnulo and Juergen Trevor Burbridge, Philip Eardley, Marcelo Bagnulo and Juergen
Schoenwaelder worked in part on the Leone research project, which Schoenwaelder worked in part on the Leone research project, which
received funding from the European Union Seventh Framework Programme received funding from the European Union Seventh Framework Programme
[FP7/2007-2013] under grant agreement number 317647. [FP7/2007-2013] under grant agreement number 317647.
Juergen Schoenwaelder was partly funded by Flamingo, a Network of Juergen Schoenwaelder was partly funded by Flamingo, a Network of
Excellence project (ICT-318488) supported by the European Commission Excellence project (ICT-318488) supported by the European Commission
under its Seventh Framework Programme. 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, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997, RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:
Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,
<http://www.rfc-editor.org/info/rfc3339>. <http://www.rfc-editor.org/info/rfc3339>.
skipping to change at page 49, line 44 skipping to change at page 49, line 47
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>.
Appendix A. Open Issues 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. Configuration of the device-id A.1. Non-editorial changes since -13
Is it the job of the LMAP information model to configure a device-id?
If not, remove ma-preconfig-device-id from ma-preconfig-obj and ma-
config-device-id from ma-config-obj.
A.2. Reporting of agent-id and group-id
The description of ma-config-report-agent-id is not consistent with
some other text where it is stated that setting ma-config-report-
agent-id to false will have no effect if the group-id is not set.
This behavior is somewhat surprising; it seems simpler to have two
controls, namely ma-config-report-agent-id and ma-config-report-
group-id, each independently controlling whether the agent-id or the
group-id is contained in reports.
Appendix B. Change History o Removed the ma-config-device-id from the ma-config-obj.
Note to the RFC Editor: this section should be removed on publication o Added ma-config-report-group-id and clarified how two flags ma-
as an RFC. config-report-agent-id and ma-config-report-group-id work.
B.1. Non-editorial changes since -12 A.2. 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.
B.2. Non-editorial changes since -11 A.3. Non-editorial changes since -11
o Clarifications and bug fixes. o Clarifications and bug fixes.
B.3. Non-editorial changes since -10 A.4. 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.
B.4. Non-editorial changes since -09 A.5. 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.
B.5. Non-editorial changes since -08 A.6. 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.
B.6. Non-editorial changes since -07 A.7. 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.
B.7. Non-editorial changes since -06 A.8. 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 52, line 43 skipping to change at page 52, 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)
B.8. Non-editorial changes since -05 A.9. 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. 
66 lines changed or deleted 53 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/