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

"MORTON, ALFRED C (AL)" <acmorton@att.com> Wed, 16 November 2016 02:38 UTC

Return-Path: <acmorton@att.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 306C61294D8 for <lmap@ietfa.amsl.com>; Tue, 15 Nov 2016 18:38:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, 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 E2wqRNpS2G1H for <lmap@ietfa.amsl.com>; Tue, 15 Nov 2016 18:38:29 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 304711293FC for <lmap@ietf.org>; Tue, 15 Nov 2016 18:38:29 -0800 (PST)
Received: from pps.filterd (m0049295.ppops.net [127.0.0.1]) by m0049295.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id uAG2ZTTT029629 for <lmap@ietf.org>; Tue, 15 Nov 2016 21:38:29 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049295.ppops.net-00191d01. with ESMTP id 26rct5tqcy-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <lmap@ietf.org>; Tue, 15 Nov 2016 21:38:28 -0500
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id uAG2cRCI018851 for <lmap@ietf.org>; Tue, 15 Nov 2016 21:38:27 -0500
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id uAG2cM8O018806 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <lmap@ietf.org>; Tue, 15 Nov 2016 21:38:24 -0500
Received: from clpi183.sldc.sbc.com (clpi183.sldc.sbc.com [135.41.1.46]) by mlpi409.sfdc.sbc.com (RSA Interceptor) for <lmap@ietf.org>; Wed, 16 Nov 2016 02:38:11 GMT
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id uAG2cBms024502 for <lmap@ietf.org>; Tue, 15 Nov 2016 20:38:11 -0600
Received: from mail-azure.research.att.com (mail-azure.research.att.com [135.207.255.18]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id uAG2c4di024218 for <lmap@ietf.org>; Tue, 15 Nov 2016 20:38:06 -0600
Received: from exchange.research.att.com (njmtcas2.research.att.com [135.207.255.47]) by mail-azure.research.att.com (Postfix) with ESMTP id E0B59E07EB for <lmap@ietf.org>; Tue, 15 Nov 2016 21:38:03 -0500 (EST)
Received: from njmtexg5.research.att.com ([fe80::b09c:ff13:4487:78b6]) by njmtcas2.research.att.com ([fe80::d550:ec84:f872:cad9%15]) with mapi id 14.03.0319.002; Tue, 15 Nov 2016 21:38:03 -0500
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: "lmap@ietf.org" <lmap@ietf.org>
Thread-Topic: [lmap] I-D Action: draft-ietf-lmap-information-model-12.txt
Thread-Index: AQHSM8aw71LaQYSPa0uSCTrZGDc8F6Da8pzQ
Date: Wed, 16 Nov 2016 02:38:03 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF6469E5@njmtexg5.research.att.com>
References: <147795313794.23217.15358328180744934565.idtracker@ietfa.amsl.com>
In-Reply-To: <147795313794.23217.15358328180744934565.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.49.184]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-11-15_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609300000 definitions=main-1611160040
Archived-At: <https://mailarchive.ietf.org/arch/msg/lmap/Vv1UG7ZSaIcSjD927GouI0RIOBA>
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 02:38:31 -0000

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