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

<philip.eardley@bt.com> Wed, 16 November 2016 09:07 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 9DAD112968F for <lmap@ietfa.amsl.com>; Wed, 16 Nov 2016 01:07:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.418
X-Spam-Level:
X-Spam-Status: No, score=-3.418 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 1TLwG2e7WIoq for <lmap@ietfa.amsl.com>; Wed, 16 Nov 2016 01:07:20 -0800 (PST)
Received: from smtpb1.bt.com (smtpb1.bt.com [62.7.242.141]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E68A5129689 for <lmap@ietf.org>; Wed, 16 Nov 2016 01:07:19 -0800 (PST)
Received: from E07HT05-UKBR.domain1.systemhost.net (193.113.197.167) by EVMED05-UKBR.bt.com (10.216.161.37) with Microsoft SMTP Server (TLS) id 14.3.248.2; Wed, 16 Nov 2016 09:07:13 +0000
Received: from rew09926dag03c.domain1.systemhost.net (10.55.202.26) by E07HT05-UKBR.domain1.systemhost.net (193.113.197.167) with Microsoft SMTP Server (TLS) id 8.3.342.0; Wed, 16 Nov 2016 09:07:17 +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 09:07:17 +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 09:07:16 +0000
From: philip.eardley@bt.com
To: acmorton@att.com, lmap@ietf.org
Thread-Topic: [lmap] I-D Action: draft-ietf-lmap-information-model-12.txt
Thread-Index: AQHSM8asad/zoPM9/E2KEj17dvlPlKDa/VqAgABoDCA=
Date: Wed, 16 Nov 2016 09:07:16 +0000
Message-ID: <76980d09da0a4bc2a0dcfd987be82e94@rew09926dag03b.domain1.systemhost.net>
References: <147795313794.23217.15358328180744934565.idtracker@ietfa.amsl.com> <4D7F4AD313D3FC43A053B309F97543CF6469E5@njmtexg5.research.att.com>
In-Reply-To: <4D7F4AD313D3FC43A053B309F97543CF6469E5@njmtexg5.research.att.com>
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.243]
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/a_gF9_uqi2QRB_umkbxLGeD9ARY>
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 09:07:23 -0000

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