IETF Logo Mail Archive

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

"Kovatsch Matthias" <kovatsch@inf.ethz.ch> Tue, 06 August 2013 13:13 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 2AAED21F9E36 for <core@ietfa.amsl.com>; Tue, 6 Aug 2013 06:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.74
X-Spam-Level:
X-Spam-Status: No, score=-4.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, 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 wNhRgbvQK8Ur for <core@ietfa.amsl.com>; Tue, 6 Aug 2013 06:13:37 -0700 (PDT)
Received: from edge10.ethz.ch (edge10.ethz.ch [82.130.75.186]) by ietfa.amsl.com (Postfix) with ESMTP id 1378421F9C4A for <core@ietf.org>; Tue, 6 Aug 2013 06:13:35 -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; Tue, 6 Aug 2013 15:13:22 +0200
Received: from MBX210.d.ethz.ch ([fe80::ed77:7d47:9467:69a9]) by CAS20.d.ethz.ch ([fe80::2cd8:4907:7776:c56d%10]) with mapi id 14.02.0298.004; Tue, 6 Aug 2013 15:13:23 +0200
From: Kovatsch Matthias <kovatsch@inf.ethz.ch>
To: "robert.cragie@gridmerge.com" <robert.cragie@gridmerge.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: AQHOkgNzWyLXgEb5yEyiT6XrPBPgmZmIHPTw
Date: Tue, 06 Aug 2013 13:13:22 +0000
Message-ID: <55877B3AFB359744BA0F2140E36F52B515036055@MBX210.d.ethz.ch>
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>
In-Reply-To: <51FFE462.7050903@gridmerge.com>
Accept-Language: en-US, de-CH
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [129.132.130.253]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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: Tue, 06 Aug 2013 13:13:43 -0000

> 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

v2.23.0 | Report a Bug | By Email