[lmap] [information model] ma-task-object issues

[Holger Wiehen <[e-mail]>]

Hi. 

I noticed 2 issues with the ma-task-object (LMAP Information Model).


1) Missing protocol information (OWAMP, TWAMP,…) 

In order to measure the metric specified on a task, coordination will be necessary between the Measurement Agent and a Measurement Peer, in most cases.
Shouldn’t the task indicate the measurement protocol to use, besides the metric to be measured?  In my understanding, the metric coming from the Ippm-Metrics-Registry will be protocol agnostic.
Today we rely on some implicit default for the measurement protocol. Alternatively the task could inform which protocol is to be used for a given metric. This would apply to capabilities (“I support metric X measured with Owamp”) and instructions (“measure metric Y, using Owamp”).


2) Inconsistency with the Yang Data Model

The information model only specifies “ma-task-functions” (Ippm Metrics) for a task.
The data model specifies “functions” (Ippm Metrics) and alternatively a “program” (local executable) to perform a task.
Should the “program” attribute appear in the information model?



Holger Wiehen