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

Shidan <shidan@gmail.com> Wed, 04 November 2009 17:20 UTC

Return-Path: <shidan@gmail.com>
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 0407C28C112 for <6lowapp@core3.amsl.com>; Wed, 4 Nov 2009 09:20:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.385
X-Spam-Level:
X-Spam-Status: No, score=-2.385 tagged_above=-999 required=5 tests=[AWL=0.213, BAYES_00=-2.599, HTML_MESSAGE=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 X27TBbn291p2 for <6lowapp@core3.amsl.com>; Wed, 4 Nov 2009 09:20:53 -0800 (PST)
Received: from mail-ew0-f207.google.com (mail-ew0-f207.google.com [209.85.219.207]) by core3.amsl.com (Postfix) with ESMTP id 546CF28C0FF for <6lowapp@ietf.org>; Wed, 4 Nov 2009 09:20:52 -0800 (PST)
Received: by ewy3 with SMTP id 3so3325794ewy.37 for <6lowapp@ietf.org>; Wed, 04 Nov 2009 09:21:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=vUriwYbfs9il+djGkTit+QLSRdzX1VK3XtUX5q2fEf8=; b=LsOQlwm/X1wkDR0IFO0A8Iez+DC0Yv30QRcZ1uO9whrjgmmAvnPBG5tPzlE51+YCOS UnCV1WZjhSxZX8cY9MfHZ0Y8ZF2WxhC8qMnXltgpYdbaez5fPGVN0Iur2rgZQj4I9LWR 9Ul2Zg66qD0nb5mvYh4/5dKt8+sjn/FhxIJJI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TqmiJQ8KpRu1KVKRWRaXG8br8zJ131GLCMxqmfsXFPYPWoAzn2NtrrnadN6+iFdYqL YuG4RYCqikWWhFdMG8MeDVANteGGYsDxoOhwOxk9U6io9ZcvStOmmVHwhCE6NKppUOmq Y0lHaiDqrRebevFPasENRdDmrYS4Y8yzR5/3c=
MIME-Version: 1.0
Received: by 10.216.90.77 with SMTP id d55mr600746wef.146.1257355270019; Wed, 04 Nov 2009 09:21:10 -0800 (PST)
In-Reply-To: <4AF1AD4C.5080908@gridmerge.com>
References: <OF164C5409.51429B82-ONC1257663.007E96BE-C1257663.008109C1@schneider-electric.com> <4AF17892.8040108@cisco.com> <0D212BD466921646B58854FB79092CEC9D15C2@XMB-AMS-106.cisco.com> <4AF1AD4C.5080908@gridmerge.com>
Date: Wed, 4 Nov 2009 12:21:09 -0500
Message-ID: <429b380e0911040921r4d139947r687a3c77a568169e@mail.gmail.com>
From: Shidan <shidan@gmail.com>
To: robert.cragie@gridmerge.com
Content-Type: multipart/alternative; boundary=0016e6d7ea6839e49f04778ed6cc
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
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: Wed, 04 Nov 2009 17:20:54 -0000

I couldn't agree more with your points which I highlighted below. We can't
look at this in a vacuum of just HANs but rather, it has to be a holistic
view.

In this case since time is of the essence, looking specifically at energy
management use cases is fine. I think Don went down this path in the thread
for message filtering and collectors and I think it would be good if we saw
more of how CoAp would relate to the rest of the networks and the
ideal qualities we want in it considering this holistic view, and then see
how much of that is possible.

---
Shidan

On Wed, Nov 4, 2009 at 11:35 AM, Robert Cragie
<robert.cragie@gridmerge.com>wrote;wrote:

>  Not considering specific use cases, I see two general requirements coming
> out here:
>
>    1. The requirement for a universal application protocol  which can work
>    across the wider internet all the way from head-end to edge devices
>    2. The requirement for an application protocol specific to low-power,
>    resource constrained nodes (CoAP)
>
> (1) pushes from the wider Internet to the edge devices.
> (2) pushes from the edge devices to the wider Internet.
>
> The utopian aim would be to find the intersection of these requirements, if
> it exists. Then the Internet of Things truly becomes feasible.
>
>