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

Rick Bullotta <rick.bullotta@thingworx.com> Tue, 06 August 2013 14:28 UTC

Return-Path: <rick.bullotta@thingworx.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 28EC721F99BE for <core@ietfa.amsl.com>; Tue, 6 Aug 2013 07:28:31 -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=[BAYES_00=-2.599, 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 Yyir0jhpuYPB for <core@ietfa.amsl.com>; Tue, 6 Aug 2013 07:28:26 -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 DF81E21F8EE6 for <core@ietf.org>; Tue, 6 Aug 2013 07:28:17 -0700 (PDT)
Received: from BLUPR06MB001.namprd06.prod.outlook.com (10.242.190.139) by BLUPR06MB004.namprd06.prod.outlook.com (10.242.190.155) with Microsoft SMTP Server (TLS) id 15.0.731.16; Tue, 6 Aug 2013 13:42:53 +0000
Received: from BLUPR06MB001.namprd06.prod.outlook.com ([169.254.1.182]) by BLUPR06MB001.namprd06.prod.outlook.com ([169.254.1.248]) with mapi id 15.00.0731.000; Tue, 6 Aug 2013 13:42:53 +0000
From: Rick Bullotta <rick.bullotta@thingworx.com>
To: Kovatsch Matthias <kovatsch@inf.ethz.ch>
Thread-Topic: [core] Do we need a CORE charter item for CoAP support of Sleepy Nodes?
Thread-Index: AQHOkgNxoK0oRKVMJEy3Rv63x/1ReJmIKWwAgAAGZAA=
Date: Tue, 06 Aug 2013 13:42:52 +0000
Message-ID: <7B0EAB9A-75D3-46B1-8372-FB93D9B49042@thingworx.com>
References: <D60519DB022FFA48974A25955FFEC08C0537E49C@SAM.InterDigital.com> <51FBC0D2.2030909@ericsson.com> <51FEB8FF.9080101@anche.no> <5c07f5eb4caba701bd1c5b99cebe14a4@xs4all.nl> <6E0184DF-5393-48F7-AE1C-C09B2415DFEC@sensinode.com> <51FFE462.7050903@gridmerge.com> <55877B3AFB359744BA0F2140E36F52B515036055@MBX210.d.ethz.ch>
In-Reply-To: <55877B3AFB359744BA0F2140E36F52B515036055@MBX210.d.ethz.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [76.117.68.133]
x-forefront-prvs: 0930AAFAD9
x-forefront-antispam-report: SFV:NSPM; SFS:(51704005)(377454003)(189002)(199002)(24454002)(80022001)(77096001)(66066001)(65816001)(56816003)(47736001)(50986001)(76786001)(76796001)(77982001)(63696002)(36756003)(59766001)(54356001)(74366001)(79102001)(19580395003)(81542001)(46102001)(33656001)(19580385001)(19580405001)(81342001)(83322001)(69226001)(47976001)(49866001)(4396001)(56776001)(76482001)(74876001)(54316002)(74706001)(80976001)(51856001)(16406001)(31966008)(53806001)(74662001)(47446002)(74502001)(83072001)(23603001); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR06MB004; H:BLUPR06MB001.namprd06.prod.outlook.com; CLIP:76.117.68.133; RD:InfoNoRecords; MX:1; A:1; LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-ID: <20F565E8AA934C46B88CCEE6D0F817B4@ThingWorxInc.onmicrosoft.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: thingworx.com
Cc: "core@ietf.org" <core@ietf.org>
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: Tue, 06 Aug 2013 14:28:31 -0000

Would it be more accurate for #2 to state that the application actively controls when to *wake*? Small but important semantic difference.  

On Aug 6, 2013, at 9:13 AM, "Kovatsch  Matthias" <kovatsch@inf.ethz.ch> wrote:

>> I agree too with what Zach and Peter say. Sleepy nodes have to be
>> considered vertically through the stack so it goes beyond the reach of what is
>> being done in CoRE.
> 
> For a CoAP endpoint there are basically two ways to enable sleep:
> 1) Sleeping is managed transparently through the network stack and the application does not need to care ("radio duty cycling")
> 2) The application actively controls when to sleep, usually for longer periods ("sleepy nodes")
> 
> For the latter case, the application layer requires infrastructure support along the lines of draft-vial-core-mirror-server or draft-fossati-core-publish/-monitor-option (basically advanced cache control).
> 
> Zach has a valid point, though, that the WG currently has enough to do. However, this advanced cache control should be kept in mind...
> 
> Ciao
> Matthias
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core