IETF Logo Mail Archive

Re: [core] WG interest in Sleepy Node topic

Abhijan Bhattacharyya <abhijan.bhattacharyya@tcs.com> Fri, 08 November 2013 21:01 UTC

Return-Path: <prvs=017b77d3c=abhijan.bhattacharyya@tcs.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 61C4111E80E9 for <core@ietfa.amsl.com>; Fri, 8 Nov 2013 13:01:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.179
X-Spam-Level:
X-Spam-Status: No, score=-6.179 tagged_above=-999 required=5 tests=[AWL=0.419, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 tF3lDO8kOgK6 for <core@ietfa.amsl.com>; Fri, 8 Nov 2013 13:01:10 -0800 (PST)
Received: from inkolg01.tcs.com (inkolg01.tcs.com [121.241.215.10]) by ietfa.amsl.com (Postfix) with ESMTP id E5DEB11E80DC for <core@ietf.org>; Fri, 8 Nov 2013 13:00:51 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.93,662,1378837800"; d="scan'208";a="469471073"
Received: from INKOLSALDLPMTA1.india.tcs.com (unknown [127.0.0.1]) by INKOLSALDLPMTA1.india.tcs.com (Service) with ESMTP id B75D9DAC12; Sat, 9 Nov 2013 02:30:38 +0530 (IST)
Received: from InKolM02.tcs.com (unknown [172.18.18.104]) by INKOLSALDLPMTA1.india.tcs.com (Service) with ESMTP id 78283DAC02; Sat, 9 Nov 2013 02:30:38 +0530 (IST)
MIME-Version: 1.0
Importance: Normal
X-Priority: 3 (Normal)
In-Reply-To: <CAEW_hywQnHfu=ys7ee1drghRSYDLcM9rSP3naeACmpE=mWeFhw@mail.gmail.com>
References: <CAEW_hywQnHfu=ys7ee1drghRSYDLcM9rSP3naeACmpE=mWeFhw@mail.gmail.com>, <D60519DB022FFA48974A25955FFEC08C0561B74B@SAM.InterDigital.com>
From: Abhijan Bhattacharyya <abhijan.bhattacharyya@tcs.com>
To: Rahman Akbar <Akbar.Rahman@InterDigital.com>, "core@ietf.org WG" <core@ietf.org>
Message-ID: <OF7DBEC9A2.838811BA-ON65257C1D.007367F4-65257C1D.00736808@tcs.com>
Date: Sat, 09 Nov 2013 02:30:32 +0530
X-Mailer: Lotus Domino Web Server Release 9.0HF507 August 20, 2013
X-MIMETrack: Serialize by Notes Server on InKolM02/TCS(Release 9.0HF507 | August 20, 2013) at 11/09/2013 02:30:32, Serialize complete at 11/09/2013 02:30:33, Itemize by Notes Server on InKolM02/TCS(Release 9.0HF507 | August 20, 2013) at 11/09/2013 02:30:33, Serialize by Notes Server on InKolM02/TCS(Release 9.0HF507 | August 20, 2013) at 11/09/2013 02:30:34, Serialize complete at 11/09/2013 02:30:34, Serialize by Router on InKolM02/TCS(Release 9.0HF507 | August 20, 2013) at 11/09/2013 02:30:37, Serialize complete at 11/09/2013 02:30:37
Content-Type: multipart/alternative; boundary="=_alternative 007367F665257C1D_="
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 21:01:14 -0000

Hi Akbar,
Its a yes from my side in favour of supporting sleepy nodes in CoRE.
One of the many reasons why we have started advocating for CoAP to our customers, compared to any other competing technologies, is the assumption that support for sleepy nodes is very much there in CoAP's road map. If we deviate then probably CoAP will lose an edge as there are competing solutions which already incorporate support for sleepy-node-state-machine at the application layer.
Another point I would like to make is: The probable intention behind confining the sleep-management considerations within the Layer-2, etc.  is probably to make the application more agnostic about the lower-part of the stack. In an ideal world we would like to do that. But when we are in the constrained world of IoT/M2M (or whatever you call it) probably we cannot have that much liberty.   

The mirror server may not always be a practicable solution. We need other proposals.

Regards
Abhijan Bhattacharyya
Associate Consultant
Scientist, Innovation Lab, Kolkata, India
Tata Consultancy Services Limited
Mailto: abhijan.bhattacharyya@tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty.	IT Services
Business Solutions
Consulting
____________________________________________


From: Rahman, Akbar <Akbar.Rahman@interdigital.com>
Date: Fri, Nov 8, 2013 at 8:06 AM
Subject: [core] WG interest in Sleepy Node topic
To: Core <core@ietf.org>


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


_______________________________________________
core mailing list
core@ietf.org
https://www.ietf.org/mailman/listinfo/core


=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you

v2.23.0 | Report a Bug | By Email