IETF Logo Mail Archive

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

"Dijk, Esko" <esko.dijk@philips.com> Tue, 27 August 2013 08:49 UTC

Return-Path: <esko.dijk@philips.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 0573821E80B1 for <core@ietfa.amsl.com>; Tue, 27 Aug 2013 01:49:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.033
X-Spam-Level:
X-Spam-Status: No, score=-1.033 tagged_above=-999 required=5 tests=[AWL=-1.566, BAYES_00=-2.599, UNRESOLVED_TEMPLATE=3.132]
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 0JLtQD9UdX1N for <core@ietfa.amsl.com>; Tue, 27 Aug 2013 01:49:51 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0188.outbound.messaging.microsoft.com [213.199.154.188]) by ietfa.amsl.com (Postfix) with ESMTP id 38FA311E8171 for <core@ietf.org>; Tue, 27 Aug 2013 01:49:40 -0700 (PDT)
Received: from mail140-db8-R.bigfish.com (10.174.8.242) by DB8EHSOBE036.bigfish.com (10.174.4.99) with Microsoft SMTP Server id 14.1.225.22; Tue, 27 Aug 2013 08:49:38 +0000
Received: from mail140-db8 (localhost [127.0.0.1]) by mail140-db8-R.bigfish.com (Postfix) with ESMTP id ED7B61C01C0; Tue, 27 Aug 2013 08:49:37 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.7.222; KIP:(null); UIP:(null); IPV:NLI; H:mail.philips.com; RD:none; EFVD:NLI
X-SpamScore: -6
X-BigFish: VPS-6(zz15d6O9251I217bIdd85kzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzzz2dh2a8h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1b2fh1fb3h1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h1155h)
Received: from mail140-db8 (localhost.localdomain [127.0.0.1]) by mail140-db8 (MessageSwitch) id 137759337633932_25748; Tue, 27 Aug 2013 08:49:36 +0000 (UTC)
Received: from DB8EHSMHS015.bigfish.com (unknown [10.174.8.243]) by mail140-db8.bigfish.com (Postfix) with ESMTP id 0173F180041; Tue, 27 Aug 2013 08:49:36 +0000 (UTC)
Received: from mail.philips.com (157.55.7.222) by DB8EHSMHS015.bigfish.com (10.174.4.25) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 27 Aug 2013 08:49:35 +0000
Received: from 011-DB3MMR1-012.MGDPHG.emi.philips.com (10.128.28.96) by 011-DB3MMR1-011.MGDPHG.emi.philips.com (10.128.28.50) with Microsoft SMTP Server (TLS) id 14.3.146.2; Tue, 27 Aug 2013 08:49:35 +0000
Received: from 011-DB3MPN2-083.MGDPHG.emi.philips.com ([169.254.3.104]) by 011-DB3MMR1-012.MGDPHG.emi.philips.com ([10.128.28.96]) with mapi id 14.03.0146.002; Tue, 27 Aug 2013 08:49:29 +0000
From: "Dijk, Esko" <esko.dijk@philips.com>
To: Zach Shelby <zach@sensinode.com>, "Rahman, Akbar (Akbar.Rahman@InterDigital.com)" <Akbar.Rahman@InterDigital.com>, "core@ietf.org" <core@ietf.org>
Thread-Topic: [core] Do we need a CORE charter item for CoAP support ofSleepy Nodes?
Thread-Index: AQHOkswvTqhaUYoSEEGsofLy7bcxiZmIpNOAgAj+V4A=
Date: Tue, 27 Aug 2013 08:49:28 +0000
Message-ID: <031DD135F9160444ABBE3B0C36CED618CFB869@011-DB3MPN2-083.MGDPHG.emi.philips.com>
References: <D60519DB022FFA48974A25955FFEC08C0537E49C@SAM.InterDigital.com><51FBC0D2.2030909@ericsson.com> <51FEB8FF.9080101@anche.no><5c07f5eb4caba701bd1c5b99cebe14a4@xs4all.nl> <6E0184DF-5393-48F7-AE1C-C09B2415DFEC@sensinode.com> <D60519DB022FFA48974A25955FFEC08C0537E7C3@SAM.InterDigital.com> <A7D35037-CE39-49CD-B2F4-92602F175D9D@sensinode.com>
In-Reply-To: <A7D35037-CE39-49CD-B2F4-92602F175D9D@sensinode.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [194.171.252.103]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: philips.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%0$Dn%INTERDIGITAL.COM$RO%1$TLS%0$FQDN%$TlsDn%
Subject: Re: [core] Do we need a CORE charter item for CoAP support ofSleepy 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: Tue, 27 Aug 2013 08:49:58 -0000

> Sure, but let's look at this when we have time in the WG. The carrot is the faster we get current work off our plate, the faster we get to new work items. So let's get to WG draft reviews and tickets....

Agree there's quite some open work items currently. However that should not stop us from picking up a new topic, if the consensus is that this new topic is more important, or more urgently required, than the ones on the plate right now!  (But it seems this has been decided now not in favor of the 'sleepy' topic.)

For the coming time (if time permits) I'll have a first look at 'sleepy' requirements and the proposed solutions, to see how these compare.

Esko

________________________________
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