Re: [lmap] I-D Action: draft-ietf-lmap-information-model-12.txt

[Juergen Schoenwaelder <[e-mail]>]

On Wed, Nov 16, 2016 at 03:42:51PM +0000, [e-mail] wrote:
> The Section 4 example is about timing of events & schedules - pipelining /serialise etc - which is useful.
> 
> I meant something like: take some variant of the example in RFC7594 and explain how to use the information model
> <<   The Controller instructs one or more MAs and communicates the set of
>    Measurement Tasks an MA should perform and when.  For example, it may
>    instruct an MA at a home gateway: "Measure the 'UDP latency' with
>    www.example.org; repeat every hour at xx.05".  The Controller also
>    manages an MA by instructing it on how to report the Measurement
>    Results, for example: "Report results once a day in a batch at 4am".
> >>
> 
> Strictly speaking this is not needed, but I think it would be useful, as the information model is now quite abstract (eg measurement tasks and registries no longer immediately obvious - as they're just tasks & registires). If other people think this is pointless, then I'm ok. 
>

My preference would have been to make the document even more concise.
The reason is that maintaining consistency is a pain. And I believe we
actually have a reasonable balance between explanatory text and
concrete definitions. And the document does not exist in isolation.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <http://www.jacobs-university.de/>