Re: [coman] Merged terminology draft

peter van der Stok <stokcons@xs4all.nl> Fri, 09 November 2012 14:52 UTC

Return-Path: <stokcons@xs4all.nl>
X-Original-To: coman@ietfa.amsl.com
Delivered-To: coman@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3934521F8703 for <coman@ietfa.amsl.com>; Fri, 9 Nov 2012 06:52:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.24
X-Spam-Level:
X-Spam-Status: No, score=0.24 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RAXLvqADVkMQ for <coman@ietfa.amsl.com>; Fri, 9 Nov 2012 06:52:15 -0800 (PST)
Received: from smtp-vbr2.xs4all.nl (smtp-vbr2.xs4all.nl [194.109.24.22]) by ietfa.amsl.com (Postfix) with ESMTP id E850621F8718 for <coman@ietf.org>; Fri, 9 Nov 2012 06:52:14 -0800 (PST)
Received: from roundcube.xs4all.nl (roundcube6.xs4all.net [194.109.20.204]) by smtp-vbr2.xs4all.nl (8.13.8/8.13.8) with ESMTP id qA9EpZqM038798 for <coman@ietf.org>; Fri, 9 Nov 2012 15:51:35 +0100 (CET) (envelope-from stokcons@xs4all.nl)
Received: from dhcp-460a.meeting.ietf.org ([130.129.70.10]) by roundcube.xs4all.nl with HTTP (HTTP/1.1 POST); Fri, 09 Nov 2012 15:51:35 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Date: Fri, 09 Nov 2012 15:51:35 +0100
From: peter van der Stok <stokcons@xs4all.nl>
To: coman@ietf.org
Organization: vanderstok consultancy
Mail-Reply-To: <consultancy@vanderstok.org>
In-Reply-To: <6294AA6E-540C-4004-8FE3-DA6E0DC0C7A8@tzi.org>
References: <6294AA6E-540C-4004-8FE3-DA6E0DC0C7A8@tzi.org>
Message-ID: <23d81132ef80b8aeac64c9f14d776ddb@xs4all.nl>
X-Sender: stokcons@xs4all.nl (IcFJzekbUXphrZ+UaMDAOw0pIixc5G3e)
User-Agent: XS4ALL Webmail
X-Virus-Scanned: by XS4ALL Virus Scanner
Subject: Re: [coman] Merged terminology draft
X-BeenThere: coman@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: consultancy@vanderstok.org
List-Id: Management of Constrained Networks and Devices <coman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/coman>, <mailto:coman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/coman>
List-Post: <mailto:coman@ietf.org>
List-Help: <mailto:coman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/coman>, <mailto:coman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 14:52:16 -0000

Dear all,

Next to the classification on memory, I should like to add a 
classification on power availability. In small nodes the largest power 
consumer is the transmitter. So I propose to classify the nodes 
according to their power-supply expressed as its transmission capacity. 
I propose three types of devices:

P0: battery-less devices. They have a capacitor which is charged by 
harvesting power delivered by a small movement or light. The stored 
energy  is just sufficient to send 1 or at most 2 packets per 
communication. For example, think of a light switch where the 
transmission power is delivered by pushing the button.

P1: battery-constrained devices. They have a battery with a limited 
charge. The device can continue sending packets over years by executing 
a cycle of relatively long off periods and short on periods in which a 
few packets can be sent and received. For example, think of a 
battery-powered temperature sensor with a life-time of 7-10 years.

P2: battery-unconstrained devices. They may have a battery which is 
usually rechargeable. The device can send and receive packets at any 
moment during its operational life. For example, think of a thermostat 
connected to an external power supply.

Hope this is helpful.

Peter van der Stok


Carsten Bormann schreef op 2012-11-08 20:43:
> As discussed in LWIG and COMAN today, Mehmet and I have extracted our
> common, "essential" terminology out of the LWIG WG document and
> Mehmet's COMAN draft, and merged it into one document.
>
> The intention is to move this forward within LWIG independently, in 
> an
> expedited way, and reference it from the next version of
> draft-ietf-lwig-guidance as well as further COMAN documents.
>
> Since we got positive feedback in the LWIG meeting for this little
> piece of surgery, I'm now asking the LWIG chairs to ask the question
> on the mailing list for working group adoption of this draft.
>
> Htmlized:        
> http://tools.ietf.org/html/draft-bormann-lwig-terms-00
>
> Clearly, this isn't perfect yet, but further improving the document 
> is
> the point of the WG process.
> Of course, comments that could lead to improvement are highly 
> welcome.
>
> Grüße, Carsten
>
> _______________________________________________
> coman mailing list
> coman@ietf.org
> https://www.ietf.org/mailman/listinfo/coman