Re: [6lowapp] Proposed charter for 6LoWAPP BOF

"Don Sturek" <d.sturek@att.net> Fri, 30 October 2009 16:02 UTC

Return-Path: <d.sturek@att.net>
X-Original-To: 6lowapp@core3.amsl.com
Delivered-To: 6lowapp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C736728C0D7 for <6lowapp@core3.amsl.com>; Fri, 30 Oct 2009 09:02:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.058
X-Spam-Level:
X-Spam-Status: No, score=0.058 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, MSGID_MULTIPLE_AT=1.449, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b3R3T7ao9BTd for <6lowapp@core3.amsl.com>; Fri, 30 Oct 2009 09:02:10 -0700 (PDT)
Received: from n12b.bullet.mail.mud.yahoo.com (n12b.bullet.mail.mud.yahoo.com [209.191.125.179]) by core3.amsl.com (Postfix) with SMTP id DF8033A694C for <6lowapp@ietf.org>; Fri, 30 Oct 2009 09:02:09 -0700 (PDT)
Received: from [68.142.194.244] by n12.bullet.mail.mud.yahoo.com with NNFMP; 30 Oct 2009 16:02:25 -0000
Received: from [68.142.201.253] by t2.bullet.mud.yahoo.com with NNFMP; 30 Oct 2009 16:02:25 -0000
Received: from [127.0.0.1] by omp414.mail.mud.yahoo.com with NNFMP; 30 Oct 2009 16:02:25 -0000
X-Yahoo-Newman-Id: 24230.34946.bm@omp414.mail.mud.yahoo.com
Received: (qmail 98865 invoked from network); 30 Oct 2009 16:02:24 -0000
Received: from adsl-69-224-190-125.dsl.sndg02.pacbell.net (d.sturek@69.224.190.125 with login) by smtp101.sbc.mail.sp1.yahoo.com with SMTP; 30 Oct 2009 09:02:24 -0700 PDT
X-Yahoo-SMTP: fvjol_aswBAraSJvMLe2r1XTzhBhbFxY8q8c3jo-
X-YMail-OSG: dhoQFYwVM1nwDnv8VpH33Zfde.UXeWIMHoU5yO4gm_xCxyywZR_G8a_ngqfcRCsjn7fCD2cN7hMwbIghgQ9EvWc8k0hAZOj.9LdUNMI9ThY9giNZzn_NWYXx7or0NmLz3P1RgutDqDdV_KgX8ZYdZGpJFCxb888oBDPBqUURUEdBDInm3rs6YK92KiZT5oUxVgpfgAnc3EGNE2Kriwjdp9XYWv1TKRuHAcAY4nVhL8k6WgZR1BUyOE6TtWU-
X-Yahoo-Newman-Property: ymail-3
From: "Don Sturek" <d.sturek@att.net>
To: "'Jonathan Hui'" <jhui@archrock.com>
References: <B27B00F8-1A4F-4258-86FC-C02E78778E45@cisco.com> <184E130A-881A-4E1F-8408-FB03A7849A82@sensinode.com> <CE5B892A-3699-4CBF-8B6A-588F5A7DE99A@cisco.com> <EB735931-0D15-4017-94F1-3B10A0EC814D@sensinode.com> <843F0B9E-8C62-47A6-AFEC-4BE31D62CDB5@cisco.com> <2AA1E2A3-9EA9-4B94-85BA-834C66826A85@tzi.org> <C93E77B9-349F-451C-BAED-273555EEE5DE@cisco.com> <21B63CBB-3197-4985-A2FA-1214F159ADFC@archrock.com> <0C312AA6-92FD-4B55-9F6D-6A3989F9CC40@tzi.org> <008201ca5964$7aa1b4a0$6fe51de0$@sturek@att.net> <F6294845-9D2E-488F-B005-FF2345209F65@archrock.com> <014001ca5974$8cb63430$a6229c90$@sturek@att.net> <F8ACB652-2C64-4EC1-8DC3-B317929DA38E@archrock.com>
In-Reply-To: <F8ACB652-2C64-4EC1-8DC3-B317929DA38E@archrock.com>
Date: Fri, 30 Oct 2009 09:02:18 -0700
Message-ID: <017401ca597a$5c54e470$14fead50$@sturek@att.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcpZeIGsKQqcasnEQvyBseZAmE5F3gAAXdTA
Content-Language: en-us
Cc: 6lowapp@ietf.org
Subject: Re: [6lowapp] Proposed charter for 6LoWAPP BOF
X-BeenThere: 6lowapp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: d.sturek@att.net
List-Id: Application protocols for constrained nodes and networks <6lowapp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowapp>
List-Post: <mailto:6lowapp@ietf.org>
List-Help: <mailto:6lowapp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2009 16:02:10 -0000

Hi Jonathan,

Aggregators are great devices when defined by end customers to meet an
application need.  The trouble comes in when we introduce them for network
layer support in non-obvious places.

I think we should try to find solutions which avoid PEPs and other
aggregation devices in general.  If we find we have to have these devices,
we should work with those responsible for deployment to be sure this maps to
their solution space.

Don


-----Original Message-----
From: Jonathan Hui [mailto:jhui@archrock.com] 
Sent: Friday, October 30, 2009 8:49 AM
To: d.sturek@att.net
Cc: 'Carsten Bormann'; 6lowapp@ietf.org
Subject: Re: [6lowapp] Proposed charter for 6LoWAPP BOF


Hi Don,

On Oct 30, 2009, at 8:20 AM, Don Sturek wrote:

> Most utilities already have Data Aggregators in their network.   
> Those are
> typically used in the neighborhood area network where collections of  
> meters
> are interfaced to the utility back office.  One example of this is  
> Outage
> notification.    Having a few meters tell you there is an outage is  
> fine,
> having all of the meters in Los Angeles tell you the power went out  
> is not
> helpful.......

Right.  Then I would ask if you would find it useful/necessary for  
this WG to work on standardizing a service that can effectively  
aggregate LLN devices?

I'm really asking these questions because I don't think it's obvious  
what pieces are necessary.  Even less obvious if we don't have clear- 
cut application targets.

--
Jonathan Hui