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

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

Well, I meant the full cycle, when to sleep, when to wake, and for each how long.

> 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