[lmap] Feedback on draft-eardley-lmap-framework

[Benoit Claise <[e-mail]>]

Dear authors,

A couple of high level points (next to the ones Dan made)
One of the goal behind this email is to generate discussions, either on 
the list, or during the IETF meeting next week.

-

    It is possible that communications between two Collectors, two
    Controllers and a Controller and Collector may be useful in some use
    cases, perhaps to help a measurement system scale.  Work on such a
    protocol is out of scope of LMAP (?)

There are many aspects to this:
* Report Protocol load balancing, such as Reliable Server Pooling 
(http://datatracker.ietf.org/wg/rserpool/)
* Results deduplication, if the Report Protocol duplicates results to 
multiple collector
* etc...

We need to have simplifying assumptions to start with, otherwise it 
might prove difficult to solve all problems at once.

-  I like the facts that the framework clearly labels the constraints, 
and the items out of scope.

-

   Standardised methods are needed for each metric that is measured.  A
    registry for commonly-used metrics [registry] is also required, so
    that a test can be defined simply by its identifier in the registry.
    The methods and registry would hopefully also be referenced by other
    standards organisations.

    o  Such activities are in scope of the IPPM working group (possibly
       re-chartered) and not LMAP.

IPPM was jut rechartered

Regards, Benoit