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

<philip.eardley@bt.com> Wed, 16 November 2016 15:43 UTC

Return-Path: <philip.eardley@bt.com>
X-Original-To: lmap@ietfa.amsl.com
Delivered-To: lmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CDE61294A8 for <lmap@ietfa.amsl.com>; Wed, 16 Nov 2016 07:43:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.099
X-Spam-Level:
X-Spam-Status: No, score=-4.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3bdjOqCg3TEc for <lmap@ietfa.amsl.com>; Wed, 16 Nov 2016 07:43:16 -0800 (PST)
Received: from smtpb1.bt.com (smtpb1.bt.com [62.7.242.142]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07BBE129453 for <lmap@ietf.org>; Wed, 16 Nov 2016 07:43:15 -0800 (PST)
Received: from E07HT02-UKBR.domain1.systemhost.net (193.113.197.160) by EVMED06-UKBR.bt.com (10.216.161.38) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 16 Nov 2016 15:43:12 +0000
Received: from rew09926dag03c.domain1.systemhost.net (10.55.202.26) by E07HT02-UKBR.domain1.systemhost.net (193.113.197.160) with Microsoft SMTP Server (TLS) id 8.3.342.0; Wed, 16 Nov 2016 15:42:52 +0000
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by rew09926dag03c.domain1.systemhost.net (10.55.202.26) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 16 Nov 2016 15:42:51 +0000
Received: from rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e]) by rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e%12]) with mapi id 15.00.1210.000; Wed, 16 Nov 2016 15:42:51 +0000
From: philip.eardley@bt.com
To: j.schoenwaelder@jacobs-university.de
Thread-Topic: [lmap] I-D Action: draft-ietf-lmap-information-model-12.txt
Thread-Index: AQHSM8asad/zoPM9/E2KEj17dvlPlKDa/VqAgABoDCCAAA56AIAAX5Qg
Date: Wed, 16 Nov 2016 15:42:51 +0000
Message-ID: <217244c70df845bd82d4fa159f53ad50@rew09926dag03b.domain1.systemhost.net>
References: <147795313794.23217.15358328180744934565.idtracker@ietfa.amsl.com> <4D7F4AD313D3FC43A053B309F97543CF6469E5@njmtexg5.research.att.com> <76980d09da0a4bc2a0dcfd987be82e94@rew09926dag03b.domain1.systemhost.net> <20161116094216.GB51980@elstar.local>
In-Reply-To: <20161116094216.GB51980@elstar.local>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.202.242]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lmap/9CIFpkdOv6Yx_AvHx4sDAVJ5a8I>
Cc: acmorton@att.com, lmap@ietf.org
Subject: Re: [lmap] I-D Action: draft-ietf-lmap-information-model-12.txt
X-BeenThere: lmap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Large Scale Measurement of Access network Performance <lmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lmap>, <mailto:lmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lmap/>
List-Post: <mailto:lmap@ietf.org>
List-Help: <mailto:lmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lmap>, <mailto:lmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Nov 2016 15:43:19 -0000

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. 


-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de] 
Sent: 16 November 2016 09:42
To: Eardley,PL,Philip,TUB8 R <philip.eardley@bt.com>
Cc: acmorton@att.com; lmap@ietf.org
Subject: Re: [lmap] I-D Action: draft-ietf-lmap-information-model-12.txt

Phil,

I am not sure which example you find missing. There is an example for an execution in section 4. There is no concrete serialization example because the information model is abstract and does not define any serialization rules. A concrete example (in XML serialization) can be found in the YANG data model - and the grand plan was to have the JSON serialization of the same model in the RESTCONF document.

/js

On Wed, Nov 16, 2016 at 09:07:16AM +0000, philip.eardley@bt.com wrote:
> Sorry for having been quiet on this recently. Thanks for all the work on this Juergen. 
> 
> I think it would be good to have a section that provides an example - to act as some kind of link from the architecture doc to the info model. The info model is now more generic (eg no specific measurement tasks) - so I think it would be useful to show a simple example with measurement & reporting.  
> 
> Thanks,
> phil
> 
> -----Original Message-----
> From: lmap [mailto:lmap-bounces@ietf.org] On Behalf Of MORTON, ALFRED 
> C (AL)
> Sent: 16 November 2016 02:38
> To: lmap@ietf.org
> Subject: Re: [lmap] I-D Action: 
> draft-ietf-lmap-information-model-12.txt
> 
> Hi Juergen,
> 
> In the latest Info Model...
> > -----Original Message-----
> ...
> > 
> > There's also a htmlized version available at:
> > https://tools.ietf.org/html/draft-ietf-lmap-information-model-12
> > 
> [ACM]
> The metric registry has become generic:
> 
> 3.10.  Common Objects: Registry Information
> 
>    Tasks and actions can be associated with entries in a registry.  A
>    registry object refers to an entry in a registry (identified by a
>    URI) and it may define a set of roles.
> 
> 3.10.1.  Definition of ma-registry-obj
> 
>      object {
>          uri                 ma-registry-uri;
>         [string              ma-registry-role<0..*>;]
>      } ma-registry-obj;
> 
>    The ma-registry-obj refers to an entry of a registry and it defines
>    the associated role(s).  The ma-registry-obj consists of the
>    following elements:
> 
>    ma-registry-uri:          A URI identifying an entry in a registry.
> 
>    ma-registry-role:         An optional and possibly empty unordered
>                              set of roles for the identified registry
>                              entry.
> -=-=-=-=-=-=-=-=-
> 
> It's not clear to me how the generic object works with respect to the performance metric registry. It was clear when the metric aspect was prominent (ma-metric-registry-obj).
> This may be because the idea of an LMAP task registry has been mentioned, but I haven't seen any details about the LMAP task registry and maybe an example would help. 
> It would be good to see how the LMAP Task Registry and IANA Performance metrics registry are used together.
> 
> Since I'm mostly interested in using LMAP for control and reporting of registered performance metrics, the composition of these measurement tasks should be as straightforward as possible.
> 
> A follow-up question is how this will change the data model, which still appears to contain specific references to metrics.
> 
> regards,
> Al
> 
> 
> _______________________________________________
> lmap mailing list
> lmap@ietf.org
> https://www.ietf.org/mailman/listinfo/lmap
> 
> _______________________________________________
> lmap mailing list
> lmap@ietf.org
> https://www.ietf.org/mailman/listinfo/lmap

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>