Re: [lmap] Merged framework draft

"MORTON, ALFRED C (AL)" <acmorton@att.com> Mon, 23 September 2013 12:32 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 095FF21F99F8 for <lmap@ietfa.amsl.com>; Mon, 23 Sep 2013 05:32:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.555
X-Spam-Level:
X-Spam-Status: No, score=-105.555 tagged_above=-999 required=5 tests=[AWL=0.444, BAYES_00=-2.599, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 cLEXHqqReVyg for <lmap@ietfa.amsl.com>; Mon, 23 Sep 2013 05:32:47 -0700 (PDT)
Received: from mail-pink.research.att.com (mail-pink.research.att.com [192.20.225.111]) by ietfa.amsl.com (Postfix) with ESMTP id 7898E21F8EB5 for <lmap@ietf.org>; Mon, 23 Sep 2013 05:32:46 -0700 (PDT)
Received: from mail-green.research.att.com (unknown [135.207.178.10]) by mail-pink.research.att.com (Postfix) with ESMTP id A076E12075C; Mon, 23 Sep 2013 08:32:43 -0400 (EDT)
Received: from njfpsrvexg1.research.att.com (njfpsrvexg1.research.att.com [135.207.177.20]) by mail-green.research.att.com (Postfix) with ESMTP id E7F2DE004A; Mon, 23 Sep 2013 08:32:05 -0400 (EDT)
Received: from concierge.research.att.com (135.207.255.39) by njfpsrvexg1.research.att.com (135.207.177.20) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 23 Sep 2013 08:32:45 -0400
Received: from NJFPSRVEXG8.research.att.com ([fe80:0000:0000:0000:cdea:b3f6:62.250.24.65]) by concierge.research.att.com ([135.207.24.83]) with mapi; Mon, 23 Sep 2013 08:32:26 -0400
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: "trevor.burbridge@bt.com" <trevor.burbridge@bt.com>, "marcelo@it.uc3m.es" <marcelo@it.uc3m.es>, "lmap@ietf.org" <lmap@ietf.org>
Date: Mon, 23 Sep 2013 08:32:25 -0400
Thread-Topic: [lmap] Merged framework draft
Thread-Index: Ac64PlvJ85+HBdwnSZidzMfN/rJmZgADesjQAALeSBA=
Message-ID: <2845723087023D4CB5114223779FA9C8AAEE8AE0@njfpsrvexg8.research.att.com>
References: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9CFD7CE@EMV67-UKRD.domain1.systemhost.net> <9904FB1B0159DA42B0B887B7FA8119CA128E22FE@AZ-FFEXMB04.global.avaya.com> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9CFD7E0@EMV67-UKRD.domain1.systemhost.net> <52400816.7070900@it.uc3m.es> <ED51D9282D1D3942B9438CA8F3372EB72C2E55546B@EMV64-UKRD.domain1.systemhost.net>
In-Reply-To: <ED51D9282D1D3942B9438CA8F3372EB72C2E55546B@EMV64-UKRD.domain1.systemhost.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [lmap] Merged framework draft
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: Mon, 23 Sep 2013 12:32:55 -0000

I also think this memo is worthy of "initial wg I-D".

And, same as many WG participants I'm sure, 
there's a bit of text I'd like to tweak 
(especially lines I contributed).

Al

> -----Original Message-----
> From: lmap-bounces@ietf.org [mailto:lmap-bounces@ietf.org] On Behalf Of
> trevor.burbridge@bt.com
> Sent: Monday, September 23, 2013 7:04 AM
> To: marcelo@it.uc3m.es; lmap@ietf.org
> Subject: Re: [lmap] Merged framework draft
> 
> Also for myself. Fairly comprehensive and captures all of the major points
> that have been discussed/agreed so far.
> 
> Trevor.
> 
> >-----Original Message-----
> >From: lmap-bounces@ietf.org [mailto:lmap-bounces@ietf.org] On Behalf Of
> >marcelo bagnulo braun
> >Sent: 23 September 2013 10:21
> >To: lmap@ietf.org
> >Subject: Re: [lmap] Merged framework draft
> >
> >agree
> >
> >El 23/09/13 11:04, philip.eardley@bt.com escribió:
> >>
> >> Personally I think it is
> >>
> >> *From:*Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> >> *Sent:* 23 September 2013 09:56
> >> *To:* Eardley,PL,Philip,TUB8 R; lmap@ietf.org
> >> *Subject:* RE: Merged framework draft
> >>
> >> Hi,
> >>
> >> Thanks to Philip and all the authors for the good work.
> >>
> >> We need however to be a little more aggressive. The WG charter
> >> includes the following milestone.
> >>
> >> Sep 2013
> >>
> >>
> >>
> >> Initial WG I-D for the LMAP Framework including terminology
> >>
> >> According to the authors - is this I-D in good enough shape for
> >> becoming the initial WG I-D? If the authors say 'yes' the chairs can
> >> ask on the WG list about consensus on this issue.
> >>
> >> We have a similar milestone for the Use Cases document.
> >>
> >> Regards,
> >>
> >> Dan
> >>
> >> *From:*lmap-bounces@ietf.org <mailto:lmap-bounces@ietf.org>
> >> [mailto:lmap-bounces@ietf.org] *On Behalf Of *philip.eardley@bt.com
> >> <mailto:philip.eardley@bt.com>
> >> *Sent:* Monday, September 23, 2013 11:47 AM
> >> *To:* lmap@ietf.org <mailto:lmap@ietf.org>
> >> *Subject:* [lmap] Merged framework draft
> >>
> >> We have been working on a framework draft that merges the previous 2
> >> framework drafts & the terminology draft, as well as including various
> >> things that have been discussed on the list since.
> >>
> >> Our plan is to produce an update before the Vancouver deadline. We
> >> have a few things that we're planning to work on, but we wanted to get
> >> it out in order to get everyone else's comments.
> >>
> >> http://www.ietf.org/id/draft-folks-lmap-framework-00.txt
> >>
> >> Terminology:
> >>
> >> Information Model definition tweaked, new definition for Subscriber
> >> and Test Traffic.
> >>
> >> Protocol Model:
> >>
> >> Added a high-level protocol model
> >>
> >> Privacy considerations:
> >>
> >> A substantial new section. It may be better removing it and security
> >> considerations into a new draft about threats and how to alleviate
> them?
> >>
> >> Looking forward to the discussions!
> >>
> >> Phil, Al, Paul, Marcelo, Aamer, Trevor.
> >>
> >>
> >>
> >> _______________________________________________
> >> 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
> _______________________________________________
> lmap mailing list
> lmap@ietf.org
> https://www.ietf.org/mailman/listinfo/lmap