1. Information Model for LMAP draft-ietf-lmap-information-model-03 and proposed changes for 04 IETF Interim, 12 th February 2015 Trevor Burbridge, BT 1

2. Motivation Overall Purpose – Guide standardisation of one or more control and reporting protocols – Enable high-level interoperability between protocols – Clarify MA information and functionality Structure – Assist protocols in breaking information down into separate messages that can be delivered at different times over different protocols – Aid readability 2

3. Information Model Sections Pre-Configuration Configuration Instruction Logging Capability & Status Reporting Minimal set of information necessary for an MA to securely contact an initial Controller Information configured by the Controller pertaining to Controller communication or general MA settings such as MA and Group ID Configuration by the Controller of what Measurement Tasks to perform, when to perform them, and where/when to report the results Information transmitted back to the Controller with configuration or instruction errors and general failure notices Information available to be fetched by the Controller such as the Measurement Tasks supported by the MA or interface configuration Information sent to the Collector regarding the Measurement Task results including MA context and Task Configuration 3

4. Changes in 03 Numerous small corrections, clarifications and improvements – Thanks to all who reviewed! More significant changes ……… 4

5. Downstream Tasks Terminology: ‘Destination Task’ instead of ‘Downstream Task’ Corrected: Scheduled Tasks output to other Scheduled Tasks (and not just Task Configurations) Schedule Scheduled Task A Schedule Scheduled Task B Output to….

6. Task Configurations vs. Scheduled Tasks Now allows parameters to be set specifically for a Scheduled Task as well as within Task Configuration – Allows general Task Configuration to be specialised within a Schedule – Flexibility and reduced data transfer – No arbitrary split Union of parameters within Task Configuration and Scheduled Task (task deals with ordering and duplicates) – Clarify that scheduled task options are appended to task configuration options 6

7. Generalisation of Task Configuration and Report Information Channel becomes Task Configuration Option (for tasks that use one: i.e. reporting and control tasks) Task role is “just another” task parameter – As is Channel – Can leave them out of the Information Model as they are defined per Task Question raised about defining these commonly used objects – Incorrectly removed role from capabilities Cross-traffic is “just another” task reporting column – Leaves format to individual tasks (can select which counters etc.) – Do we want to standardise? 7

8. Reporting Reporting, Management and other Tasks also need a registry (private, local) Inclusion of Task Configuration and Schedule information is dependent on the Reporting Task and options – Task configuration headers become optional 8

9. Timing Removed ISO8601 compliance for datetimes (just leave RFC 3339) Removed calendar defaults but added wildcard ‘*’ – Otherwise could default to every second 9

10. Persistence Data persistence is device dependent (not protocol dependent) – Controller can check through ‘Last Instruction” status Re-instated separate Pre-Configuration Information – Specified that device will revert to pre-configuration on factory reset 10

11. Other Kept JSON example (for now) – Currently useful but maybe superseded by forthcoming protocol documents e.g. YANG model – Added YANG IM reference 11

12. Suggestions for 04 Minor corrections Spell checked! Keep JSON for 04 Add JSON IM reference Re-instate role in capabilities – Keep as option for task configurations Standardise well known options? – Channel, role, cross-traffic … Move to per-task status information – E.g. last-invocation, last-completion for report task rather than last-report – As suggested in YANG IM implementation Move to per-task condition codes (in addition to per MA) – As suggested in YANG IM implementation Change name-value pair object for task configurations to option object (with name and value) Specify that scheduled task options are appended to task configuration options Other suggestions during or immediately following this interim 12