Re: [core] FW: New Version Notification for draft-rahman-core-sleepy-nodes-do-we-need-00.txt

 >         "Should we have a CORE deliverable for CoAP support of Sleepy Nodes?"
Yes!  (motivation: existing WG documents do not provide the complete solution yet that is required at CoAP level)

> of in-protocol mechanisms (a bunch of Options, basically)
I don't fully agree; it could be one or more options that are needed; it could be perhaps done without new options.
The thing that is needed at least, in my opinion, is functionality like [I-D.vial-core-mirror-server].  (If needed I can motivate this further on the list with use cases.)

> (as opposed to a fully fledged architecture to support Sleepy nodes, which other SDOs are in a better position to provide)
Agree. I see mirror server as an example of a useful/required component, but it is not a full architecture yet. But any CoRE defined 'building block' should fit in such architectures.

Esko

-----Original Message-----
From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf Of Thomas Fossati
Sent: Friday, October 11, 2013 08:49
To: Rahman, Akbar
Cc: core@ietf.org
Subject: Re: [core] FW: New Version Notification for draft-rahman-core-sleepy-nodes-do-we-need-00.txt

Hi Akbar, thank you very much for this.

I think you are providing a really good service to the working group in keeping the background discussion on this important topic alive.

Personally, I think that providing a set of in-protocol mechanisms (a bunch of Options, basically) to tackle well known and understood scenarios (as opposed to a fully fledged architecture to support Sleepy nodes, which other SDOs are in a better position to provide) is something that is perfectly in scope with CoAP goals and WG interest and energy  -- as you sensed it back in August.

And yes, I'd have given you my +1 when you polled the mailing list about this, if I weren't on holiday :-)

Cheers

On Fri, Oct 11, 2013 at 4:39 AM, Rahman, Akbar <Akbar.Rahman@interdigital.com> wrote:
> Hi Carsten (and WG),
>
>
> I wrote a short draft based on the following question from IETF-87 (Berlin):
>
>         "Should we have a CORE deliverable for CoAP support of Sleepy Nodes?"
>
>
> http://www.ietf.org/mail-archive/web/core/current/msg04750.html
>
>
>
> Any and all comments will be much appreciated.
>
>
>
> Akbar
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Thursday, October 10, 2013 11:34 PM
> To: Rahman, Akbar; Rahman, Akbar
> Subject: New Version Notification
> fordraft-rahman-core-sleepy-nodes-do-we-need-00.txt
>
>
> A new version of I-D, draft-rahman-core-sleepy-nodes-do-we-need-00.txt
> has been successfully submitted by Akbar Rahman and posted to the IETF repository.
>
> Filename:        draft-rahman-core-sleepy-nodes-do-we-need
> Revision:        00
> Title:           Sleepy Devices: Do we need to Support them in CORE?
> Creation date:   2013-10-11
> Group:           Individual Submission
> Number of pages: 6
> URL:             http://www.ietf.org/internet-drafts/draft-rahman-core-sleepy-nodes-do-we-need-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-rahman-core-sleepy-nodes-do-we-need
> Htmlized:        http://tools.ietf.org/html/draft-rahman-core-sleepy-nodes-do-we-need-00
>
>
> Abstract:
>    This document summarizes the discussion in the CORE WG related to the
>    question of whether support of sleepy devices is required for the
>    CoAP protocol, CORE Link Format, CORE Resource Directory, etc.  The
>    only goal of this document is to trigger discussions in the CORE WG
>    so that all relevant considerations for sleeping devices are taken
>    into account.
>
>
>
>
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
_______________________________________________
core mailing list
core@ietf.org
https://www.ietf.org/mailman/listinfo/core

________________________________
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.