Re: [core] Do we need a CORE charter item for CoAP support of Sleepy Nodes?

"Kovatsch Matthias" <kovatsch@inf.ethz.ch> Fri, 02 August 2013 20:23 UTC

Return-Path: <kovatsch@inf.ethz.ch>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54C6711E80E1 for <core@ietfa.amsl.com>; Fri, 2 Aug 2013 13:23:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 TXrVM1N9bunW for <core@ietfa.amsl.com>; Fri, 2 Aug 2013 13:23:31 -0700 (PDT)
Received: from edge10.ethz.ch (edge10.ethz.ch [82.130.75.186]) by ietfa.amsl.com (Postfix) with ESMTP id A46F121E8050 for <core@ietf.org>; Fri, 2 Aug 2013 13:23:28 -0700 (PDT)
Received: from CAS20.d.ethz.ch (172.31.51.110) by edge10.ethz.ch (82.130.75.186) with Microsoft SMTP Server (TLS) id 14.2.298.4; Fri, 2 Aug 2013 22:23:16 +0200
Received: from MBX110.d.ethz.ch ([fe80::9d9a:a7f2:c282:5f6a]) by CAS20.d.ethz.ch ([fe80::2cd8:4907:7776:c56d%10]) with mapi id 14.02.0298.004; Fri, 2 Aug 2013 22:23:19 +0200
From: Kovatsch Matthias <kovatsch@inf.ethz.ch>
To: "Keoh, Sye Loong" <sye.loong.keoh@philips.com>, "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>, "core@ietf.org" <core@ietf.org>
Thread-Topic: [core] Do we need a CORE charter item for CoAP support of Sleepy Nodes?
Thread-Index: Ac6Oyy3lzRKNmIjvRwGckETkXD5QwgABUTTAADiV5CcAAq7OQA==
Date: Fri, 02 Aug 2013 20:23:19 +0000
Message-ID: <55877B3AFB359744BA0F2140E36F52B515022624@MBX110.d.ethz.ch>
References: <D60519DB022FFA48974A25955FFEC08C0537E49C@SAM.InterDigital.com> <EAE29B174013F643B5245BA11953A1BE2596D543@011-DB3MPN1-032.MGDPHG.emi.philips.com>
In-Reply-To: <EAE29B174013F643B5245BA11953A1BE2596D543@011-DB3MPN1-032.MGDPHG.emi.philips.com>
Accept-Language: en-US, de-CH
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [141.16.127.19]
Content-Type: multipart/alternative; boundary="_000_55877B3AFB359744BA0F2140E36F52B515022624MBX110dethzch_"
MIME-Version: 1.0
Subject: Re: [core] Do we need a CORE charter item for CoAP support of Sleepy Nodes?
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/core>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 20:23:36 -0000

Dear list

I still think radio duty cycling (virtually always-on with a duty cycly << 1%) is a preferable way to do it because it can be implemented in an independent lower layer without the need for any infrastructure.

However, there are very valid scenarios for sleepy nodes (the application decides when to sleep and wake up). For these we need infrastructure at the application layer, which should be defined in a standard way. Thus, we should work in this!

Ciao
Matthias


From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf Of Keoh, Sye Loong
Sent: Freitag, 2. August 2013 21:03
To: Rahman, Akbar; core@ietf.org
Subject: Re: [core] Do we need a CORE charter item for CoAP support of Sleepy Nodes?

Dear all,

I think sleepy node is an important topic, and most of the sensors and actuators need to conserve energy. Therefore, I think we need to tackle this issue. Yes, would agree to have a CoRE charter item for sleepy nodes.

cheers
Sye Loong
________________________________
From: core-bounces@ietf.org<mailto:core-bounces@ietf.org> [core-bounces@ietf.org] on behalf of Rahman, Akbar [Akbar.Rahman@InterDigital.com]
Sent: Thursday, August 01, 2013 6:02 PM
To: core@ietf.org<mailto:core@ietf.org>
Subject: [core] Do we need a CORE charter item for CoAP support of Sleepy Nodes?
Hi,


Carsten asked me to send this message out to the WG list as we did not have a chance to discuss the Sleepy Node topic in this IETF due to a lack of time on the agenda.

------------------------------------------------------------------------------
We have several current I-Ds in CORE (and LWIG) that discusses the topic of Sleepy Nodes.  Among those are:


draft-dijk-core-sleepy-reqs-00<https://datatracker.ietf.org/doc/draft-dijk-core-sleepy-reqs/>

draft-dijk-core-sleepy-solutions-01<https://datatracker.ietf.org/doc/draft-dijk-core-sleepy-solutions/>

draft-hong-lwig-sleepynode-problem-statement-00<https://datatracker.ietf.org/doc/draft-hong-lwig-sleepynode-problem-statement/>

draft-rahman-core-sleepy-03<https://datatracker.ietf.org/doc/draft-rahman-core-sleepy/>


Hence the following question to the WG:


*         Should we have a CORE deliverable for CoAP support of Sleepy Nodes?


Please write back with your thoughts!



Best Regards,


Akbar

________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.