Re: [core] WG interest in Sleepy Node topic

"Dijk, Esko" <esko.dijk@philips.com> Fri, 08 November 2013 15:37 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 2F9BD21E818D for <core@ietfa.amsl.com>; Fri, 8 Nov 2013 07:37:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.322
X-Spam-Level:
X-Spam-Status: No, score=-1.322 tagged_above=-999 required=5 tests=[AWL=-1.856, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 bCBgN5V3CrdZ for <core@ietfa.amsl.com>; Fri, 8 Nov 2013 07:37:11 -0800 (PST)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0188.outbound.messaging.microsoft.com [213.199.154.188]) by ietfa.amsl.com (Postfix) with ESMTP id B9CAB21E8189 for <core@ietf.org>; Fri, 8 Nov 2013 07:37:04 -0800 (PST)
Received: from mail93-db8-R.bigfish.com (10.174.8.232) by DB8EHSOBE034.bigfish.com (10.174.4.97) with Microsoft SMTP Server id 14.1.225.22; Fri, 8 Nov 2013 15:36:56 +0000
Received: from mail93-db8 (localhost [127.0.0.1]) by mail93-db8-R.bigfish.com (Postfix) with ESMTP id 91B03AE0359 for <core@ietf.org>; Fri, 8 Nov 2013 15:36:56 +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: -28
X-BigFish: VPS-28(zz217bI15d6Oc85fh9251I4015I14ffIdd85kzz1f42h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah8275dh18c673h1de097h186068hz2dh109h2a8h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1b2fh1bceh2222h224fh1fb3h1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h20f0h2216h1155h)
Received: from mail93-db8 (localhost.localdomain [127.0.0.1]) by mail93-db8 (MessageSwitch) id 138392501485708_3499; Fri, 8 Nov 2013 15:36:54 +0000 (UTC)
Received: from DB8EHSMHS018.bigfish.com (unknown [10.174.8.245]) by mail93-db8.bigfish.com (Postfix) with ESMTP id 084E1A0004B; Fri, 8 Nov 2013 15:36:54 +0000 (UTC)
Received: from mail.philips.com (157.55.7.222) by DB8EHSMHS018.bigfish.com (10.174.4.28) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 8 Nov 2013 15:36:52 +0000
Received: from 011-DB3MMR1-012.MGDPHG.emi.philips.com (10.128.28.96) by 011-DB3MMR1-006.MGDPHG.emi.philips.com (10.128.28.56) with Microsoft SMTP Server (TLS) id 14.3.146.2; Fri, 8 Nov 2013 15:36:52 +0000
Received: from 011-DB3MPN2-082.MGDPHG.emi.philips.com ([169.254.2.206]) by 011-DB3MMR1-012.MGDPHG.emi.philips.com ([10.128.28.96]) with mapi id 14.03.0146.002; Fri, 8 Nov 2013 15:36:46 +0000
From: "Dijk, Esko" <esko.dijk@philips.com>
To: "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>, Core <core@ietf.org>
Thread-Topic: WG interest in Sleepy Node topic
Thread-Index: Ac7cK1YqMzRJhdYORw+JQXBuUFLKkgAa8Nog
Date: Fri, 08 Nov 2013 15:36:45 +0000
Message-ID: <031DD135F9160444ABBE3B0C36CED6180CC27408@011-DB3MPN2-082.MGDPHG.emi.philips.com>
References: <D60519DB022FFA48974A25955FFEC08C0561B74B@SAM.InterDigital.com>
In-Reply-To: <D60519DB022FFA48974A25955FFEC08C0561B74B@SAM.InterDigital.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.106]
Content-Type: multipart/alternative; boundary="_000_031DD135F9160444ABBE3B0C36CED6180CC27408011DB3MPN2082MG_"
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] WG interest in Sleepy Node topic
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, 08 Nov 2013 15:37:17 -0000

> 1. Does the WG want to keep discussing Sleepy Nodes in CORE?
Yes, let's continue to use the mailing list and CoRE I-Ds for this.

> 2. Does the WG want to see some immediate development of the Mirror Server concept
First thing to do is check how well it satisfies the requirements, compared to other methods. For that, we need requirements. For the requirements, we need use cases! See http://tools.ietf.org/html/draft-dijk-core-sleepy-reqs-00#section-3 for an initial set of building control use cases.

I'm open to receive any other use cases; we could publish these on the mailing list and collect them from there.

Esko

From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf Of Rahman, Akbar
Sent: Friday, November 08, 2013 03:37
To: Core
Subject: [core] WG interest in Sleepy Node topic

Hi All,



Once again we ran out of time on the agenda to discuss the WG interest on the topic of Sleepy Nodes

http://www.ietf.org/id/draft-rahman-core-sleepy-nodes-do-we-need-00.txt


However, Carsten did suggest that we carry the discussion that we would have had in the meeting forward to the WG list.  The key questions that we need WG feedback on are:


1.       Does the WG want to keep discussing Sleepy Nodes in CORE?  The Sleepy Node support could be in:

a.       CoAP Protocol

b.      CORE Link Format

c.       CORE Resource Directory

d.      Etc.



2.       Sub-Question:

a.       Does the WG want to see some immediate development of the Mirror Server concept (which seems to have near unanimous support and is well correlated to Sleepy Node support)?


Any and all comments are appreciated!  Please write back even if you answered earlier Emails on this topic as we need to gauge WG interest.


Thanks,


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.