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

"MORTON, ALFRED C (AL)" <acmorton@att.com> Thu, 17 November 2016 01:21 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 D04E912986A for <lmap@ietfa.amsl.com>; Wed, 16 Nov 2016 17:21:26 -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 rAjHHtWW2lAs for <lmap@ietfa.amsl.com>; Wed, 16 Nov 2016 17:21:24 -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 F0F2E1297C4 for <lmap@ietf.org>; Wed, 16 Nov 2016 17:21:23 -0800 (PST)
Received: from pps.filterd (m0053301.ppops.net [127.0.0.1]) by mx0a-00191d01.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id uAGKtEgQ008342; Wed, 16 Nov 2016 15:56:13 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by mx0a-00191d01.pphosted.com with ESMTP id 26rx8qse4p-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 16 Nov 2016 15:56:12 -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 uAGKu9vH000845; Wed, 16 Nov 2016 15:56:11 -0500
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id uAGKttOO000424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 16 Nov 2016 15:56:02 -0500
Received: from clpi183.sldc.sbc.com (clpi183.sldc.sbc.com [135.41.1.46]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Wed, 16 Nov 2016 20:55:47 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 uAGKtlfs011783; Wed, 16 Nov 2016 14:55:47 -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 uAGKtaHb011190; Wed, 16 Nov 2016 14:55:37 -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 D89E9E070F; Wed, 16 Nov 2016 15:55:35 -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; Wed, 16 Nov 2016 15:55:35 -0500
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "philip.eardley@bt.com" <philip.eardley@bt.com>
Thread-Topic: [lmap] I-D Action: draft-ietf-lmap-information-model-12.txt
Thread-Index: AQHSM8aw71LaQYSPa0uSCTrZGDc8F6Da8pzQgADLTwCAAAnHAIAAZL+AgAAKogD///MyEA==
Date: Wed, 16 Nov 2016 20:55:35 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF656C54@njmtexg5.research.att.com>
References: <147795313794.23217.15358328180744934565.idtracker@ietfa.amsl.com> <4D7F4AD313D3FC43A053B309F97543CF6469E5@njmtexg5.research.att.com> <76980d09da0a4bc2a0dcfd987be82e94@rew09926dag03b.domain1.systemhost.net> <20161116094216.GB51980@elstar.local> <217244c70df845bd82d4fa159f53ad50@rew09926dag03b.domain1.systemhost.net> <20161116162054.GC52611@elstar.local>
In-Reply-To: <20161116162054.GC52611@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [31.133.151.243]
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-16_06:, , 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-1611160313
Archived-At: <https://mailarchive.ietf.org/arch/msg/lmap/lbY_tDwGpresCwtvL41-7unXCTk>
Cc: "lmap@ietf.org" <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: Thu, 17 Nov 2016 01:21:27 -0000

> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-
> university.de]
> Sent: Wednesday, November 16, 2016 11:21 AM
> To: philip.eardley@bt.com
> Cc: MORTON, ALFRED C (AL); lmap@ietf.org
> Subject: Re: [lmap] I-D Action: draft-ietf-lmap-information-model-12.txt
> 
> On Wed, Nov 16, 2016 at 03:42:51PM +0000, philip.eardley@bt.com 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.
> 
[ACM] 

Juergen,
You have described a Task registry on several occasions, but we have no
details in writing or examples in the Framework RFC because this registry
concept is new.

Now that the information model has been generalized to allow for a Task 
registry, I want to understand how you intend to use that registry
and how it interacts with the Metrics registry (whose role we have 
understood for years, but now potentially changes, I cannot tell how).

Phil and I have both asked for examples so that we can understand 
the implications of the changes you've executed. Examples have been
the stepping stones to reach greater clarity in much of our work in
LMAP over the last year, and I provided quite a few examples for the 
metrics registry and Cycle Number discussions.

Help us understand how you think LMAP will work now,
Al