Re: [lmap] on use cases and requirements

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Fri, 26 July 2013 03:17 UTC

Return-Path: <rachel.huang@huawei.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 8705F21F8456 for <lmap@ietfa.amsl.com>; Thu, 25 Jul 2013 20:17:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.348
X-Spam-Level:
X-Spam-Status: No, score=-6.348 tagged_above=-999 required=5 tests=[AWL=-0.249, BAYES_00=-2.599, GB_ABOUTYOU=0.5, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R4uhNtnILAJp for <lmap@ietfa.amsl.com>; Thu, 25 Jul 2013 20:17:54 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9932521F844E for <lmap@ietf.org>; Thu, 25 Jul 2013 20:17:52 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATU47378; Fri, 26 Jul 2013 03:17:49 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 26 Jul 2013 04:16:46 +0100
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 26 Jul 2013 04:17:46 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.43]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.01.0323.007; Fri, 26 Jul 2013 11:17:40 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: "philip.eardley@bt.com" <philip.eardley@bt.com>, "dromasca@avaya.com" <dromasca@avaya.com>, "lmap@ietf.org" <lmap@ietf.org>
Thread-Topic: on use cases and requirements
Thread-Index: Ac6JNA/7jjUgkfhDSx2RandUUF8HhwAAwTCwABqq9IA=
Date: Fri, 26 Jul 2013 03:17:40 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB458595EA@nkgeml501-mbs.china.huawei.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA12881146@AZ-FFEXMB04.global.avaya.com> <9510D26531EF184D9017DF24659BB87F35B80337A5@EMV65-UKRD.domain1.systemhost.net>
In-Reply-To: <9510D26531EF184D9017DF24659BB87F35B80337A5@EMV65-UKRD.domain1.systemhost.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.104]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [lmap] on use cases and requirements
X-BeenThere: lmap@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 26 Jul 2013 03:17:58 -0000

Hi Philip,

Yes, I think it could be regarded as one usage of ISP use case. 

It will be great to work with you and ken on this. I will attend this meeting. Let's meet in the LMAP breakfast.

Best regards,
Rachel

-----Original Message-----
From: lmap-bounces@ietf.org [mailto:lmap-bounces@ietf.org] On Behalf Of philip.eardley@bt.com
Sent: Thursday, July 25, 2013 9:17 PM
To: dromasca@avaya.com; lmap@ietf.org
Subject: Re: [lmap] on use cases and requirements

I had a look at the new drafts, couple of questions

Ken,
http://tools.ietf.org/html/draft-nagami-lmap-use-case-measurement-provider-00
you talk about a "measurement provider" - if I get it right, this is someone who provides information about different ISPs. this seems to me very similar to the regulator use case - but it's a public interest group, or a company providing the information instead of a regulator. It's probably worth pointing this out in http://tools.ietf.org/html/draft-linsner-lmap-use-cases - would this then cover your use case?

You also mention a smartphone, I think it's worth adding this explicitly to draft-linsner

You also have a lot of interesting details about your deployment. My feeling is that it would take a lot of work to summarise all the state-of-the-art, so we shouldn't try (perhaps we could add a few references in one of the docs)


Rachel,
http://tools.ietf.org/id/draft-huang-lmap-data-collection-use-case-00.txt
I take this as a slight expansion of the ISP use case described in http://tools.ietf.org/html/draft-linsner-lmap-use-cases 
Could we work with you on adding a little text about simulations to our draft? - ie the ISP could use measurements to feed its simulation tools (assuming it uses simulations as part of the way it works out where a fault is, or where to add capacity, etc). 
Will you be in Berlin? Marc, Ken and I are meeting in the lmap breakfast to discuss use cases. 


Dan,
Personally I'm happy to drop as much of Section 3 as people want (even all of it).
I agree we should think carefully in terms of what the output of lmap needs to do - what are the most important aspects of which use cases.
Reading between the lines, you think the use cases doc should only cover those aspects that we're going to (try to) make sure we solve during the initial lmap charter. And not be a general use case doc that would need future lmap capability.
Is that right? 
(I'm ok if the answer is 'yes')

Thanks
phil

> -----Original Message-----
> From: lmap-bounces@ietf.org [mailto:lmap-bounces@ietf.org] On Behalf Of
> Romascanu, Dan (Dan)
> Sent: 25 July 2013 13:40
> To: lmap@ietf.org
> Subject: [lmap] on use cases and requirements
> 
> If you have a look at the updated agenda at
> https://datatracker.ietf.org/meeting/87/agenda/lmap/ you will realized
> that Jason and me slightly updated the section dedicated to use cases
> and added ten minutes of discussion. Let me try to explain the
> motivation and what we would try to achieve. According to the charter
> in a couple of months the WG will need to submit the first WG Internet-
> Drafts on Use Cases and Framework. These two documents should provide
> clear enough requirements for the following phases where we need to
> proceed to the creation of the Information Model, and discuss about the
> selection or development of protocols for Control and Reporting and
> their associated data models. At this moment in time we have one draft-
> linsner-lmap-use-cases-03 as principal document on use cases, and two
> new contributions, which is good for this phase. What we need to start
> doing is to sort out of the use cases the subset that matches the
> current WG charter - and we may need to drop  or prioritize some of the
> aspects of the use cases for this purpose.
> 
> (To be more specific and take this just as an example, I am not sure
> that all the characteristics described in Sections 3.2, 3.3, 3.5 in
> draft-linsner-lmap-use-cases-03 are LMAP problems or problems that
> belong to the requirements of the first phase of LMAP.)
> 
> Regards,
> 
> Dan
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 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