Re: [lmap] LMAP Framework issue #3 (take 2) Interactions between MA and Controller

["STARK, BARBARA H" <[e-mail]>]

> Defining a test is fine, however added information is required to ensure the
> test was executed in the same fashion so the test results are comparable.
> - So we'll need to go beyond the test attributes in order to do this... (beyond
> frame size, ...)
> 
> Typical test implementation attributes I've had to define in the past
> 
> Test engine / Environmental factors
> 	-- Test engine (which TCP stack), no cross traffic, hour of day, target
> type or class, ....
> 
> Test procedure factors
> 	-- Stability factor used (delay, or trending and how much), thresholds
> for pass fail, Data trimming (95% of frames met x), ...
> 
> If these are not added to the Abstracted test command set I think we'll miss
> the target.

Hi Mike,
In http://tools.ietf.org/html/draft-burbridge-lmap-information-model-00 (which I hope will be used as a basis for lmap's Information Model deliverable), there's currently a section on Reporting Information that includes an "MA Context" element. IMO, the information you describe belongs here. Since you seem to have an idea of what you'd like to see included in Reporting Information, perhaps you could provide a more specific and "normalized" list that notes where you think the particular element is a string, datetime, enumerated list (and provide enumerations), etc. 

Perhaps the authors of that draft could say whether they'd like that sort of input, and if there's some sort of format they'd like to get that input in.

Anyway, I don't think there needs to be discussion about whether or not what you ask for is in scope of lmap. I think it's just a matter of getting the specifics of what it is fleshed out in the Information Model. At the level of the framework, I think what the framework currently says is great (see below). But maybe you would like to propose an additional bullet to expound in a single sentence or so a bit more on the idea of "context".
Barbara

------------------ from http://tools.ietf.org/html/draft-eardley-lmap-framework-02 ----
4.1.  Information Model
... snip ...
   The Information Model is divided into two main parts, each of which
   may be broken down into sub-parts:
... snip ...
   o  information about the Report: Information transmitted from the MA
      to the Collector including measurement results and the context in
      which they were conducted.  This includes:

      *  the MAs identifier, or perhaps a Group-ID to anonymise results

      *  the actual Measurement Results, including the time they were
         measured

      *  the details of the Measurement Task (to avoid the Collector
         having to ask the Controller for this information later)