IETF Logo Mail Archive

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

"Mani, Mehdi" <Mehdi.Mani@itron.com> Mon, 05 August 2013 13:21 UTC

Return-Path: <Mehdi.Mani@itron.com>
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 91F4521F9A57 for <core@ietfa.amsl.com>; Mon, 5 Aug 2013 06:21:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 Vb3JHjigmUp8 for <core@ietfa.amsl.com>; Mon, 5 Aug 2013 06:20:50 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0241.outbound.protection.outlook.com [207.46.163.241]) by ietfa.amsl.com (Postfix) with ESMTP id C922121F9E9D for <core@ietf.org>; Mon, 5 Aug 2013 06:20:48 -0700 (PDT)
Received: from BL2PR04MB082.namprd04.prod.outlook.com (10.255.231.149) by BL2PR04MB081.namprd04.prod.outlook.com (10.255.231.146) with Microsoft SMTP Server (TLS) id 15.0.731.12; Mon, 5 Aug 2013 13:05:27 +0000
Received: from BL2PR04MB082.namprd04.prod.outlook.com ([169.254.1.21]) by BL2PR04MB082.namprd04.prod.outlook.com ([169.254.1.21]) with mapi id 15.00.0731.000; Mon, 5 Aug 2013 13:05:27 +0000
From: "Mani, Mehdi" <Mehdi.Mani@itron.com>
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: Ac6Oyy3lzRKNmIjvRwGckETkXD5QwgABUTTAADiV5CcAimg90A==
Date: Mon, 05 Aug 2013 13:05:26 +0000
Message-ID: <498402aa885f437ebb03cc1fe8b1f4c5@BL2PR04MB082.namprd04.prod.outlook.com>
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
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [85.115.60.180]
x-forefront-prvs: 0929F1BAED
x-forefront-antispam-report: SFV:NSPM; SFS:(189002)(199002)(377454003)(55904002)(374574003)(57704003)(85714005)(4396001)(66066001)(80022001)(83072001)(65816001)(81542001)(16236675002)(74366001)(81342001)(19580395003)(74876001)(76796001)(80976001)(19580405001)(74316001)(49866001)(69226001)(76576001)(83322001)(79102001)(15202345003)(74502001)(47446002)(74706001)(33646001)(77096001)(16406001)(46102001)(56816003)(51856001)(54316002)(63696002)(53806001)(19300405004)(31966008)(74662001)(18717965001)(56776001)(50986001)(19580385001)(47736001)(59766001)(77982001)(76482001)(54356001)(47976001)(76786001)(23603001)(567094001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BL2PR04MB081; H:BL2PR04MB082.namprd04.prod.outlook.com; CLIP:85.115.60.180; RD:InfoNoRecords; MX:1; A:1; LANG:en;
Content-Type: multipart/alternative; boundary="_000_498402aa885f437ebb03cc1fe8b1f4c5BL2PR04MB082namprd04pro_"
MIME-Version: 1.0
X-OriginatorOrg: itron.com
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: Mon, 05 Aug 2013 13:21:07 -0000

+1
-Mehdi

From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf Of Keoh, Sye Loong
Sent: vendredi 2 août 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.

v2.23.0 | Report a Bug | By Email