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

Zach Shelby <zach@sensinode.com> Tue, 06 August 2013 20:40 UTC

Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <D60519DB022FFA48974A25955FFEC08C0537E7C3@SAM.InterDigital.com>
Date: Tue, 06 Aug 2013 23:40:39 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <A7D35037-CE39-49CD-B2F4-92602F175D9D@sensinode.com>
References: <D60519DB022FFA48974A25955FFEC08C0537E49C@SAM.InterDigital.com><51FBC0D2.2030909@ericsson.com> <51FEB8FF.9080101@anche.no><5c07f5eb4caba701bd1c5b99cebe14a4@xs4all.nl> <6E0184DF-5393-48F7-AE1C-C09B2415DFEC@sensinode.com> <D60519DB022FFA48974A25955FFEC08C0537E7C3@SAM.InterDigital.com>
To: "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>
Cc: core@ietf.org
Subject: Re: [core] Do we need a CORE charter item for CoAP support ofSleepy Nodes?
Precedence: list

On Aug 6, 2013, at 8:41 PM, "Rahman, Akbar" <Akbar.Rahman@InterDigital.com> wrote:

> 	"If we would like to document a setup to support such endpoints,
> then it should probably done by just documenting something done in a
> complete architecture 	for the sake of allowing re-use. We also have
> existing solutions like Mirror Server that can be used in some cases
> where that architecture is applicable…"

And in particular I meant we should document complete-architecture solutions used by other SDOs or in deployments as a way to re-use known mechanisms being used to solve real problems, rather than inventing neat solutions because we can. 

> I agree.  The missing link though is that need to identify a new WG
> deliverable for CoAP support of Sleepy Node for this (hence my initial
> Email). We have NOT yet adopted the Mirror Server (or any of the other
> proposals) for Sleepy Node support.  We need to do this or otherwise we
> will be delivering a set of CoAP standards to the market with an
> important functionality/guidance that is missing (i.e. Sleepy Node
> support).  I think we as a WG recognized this when we formulated the
> initial charter as we explicitly refer to support of "sleepy nodes" in
> the charter several times.

Sure, but let's look at this when we have time in the WG. The carrot is the faster we get current work off our plate, the faster we get to new work items. So let's get to WG draft reviews and tickets…. 

Zach

-- 
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://www.sensinode.com @SensinodeIoT
Mobile: +358 40 7796297
Twitter: @zach_shelby
LinkedIn: http://fi.linkedin.com/in/zachshelby
6LoWPAN Book: http://6lowpan.net

[core] Do we need a CORE charter item for CoAP su… Rahman, Akbar
[core] Do we need a CORE charter item for CoAP su… Rahman, Akbar
Re: [core] Do we need a CORE charter item for CoA… Salvatore Loreto
Re: [core] Do we need a CORE charter item for CoA… Pete St. Pierre
Re: [core] Do we need a CORE charter item for CoA… Keoh, Sye Loong
Re: [core] Do we need a CORE charter item for CoA… Kovatsch Matthias
Re: [core] Do we need a CORE charter item for CoA… Pierpaolo Giacomin
Re: [core] Do we need a CORE charter item for CoA… peter van der Stok
Re: [core] Do we need a CORE charter item for CoA… Mani, Mehdi
Re: [core] Do we need a CORE charter item for CoA… Zach Shelby
Re: [core] Do we need a CORE charter item for CoA… Robert Cragie
Re: [core] Do we need a CORE charter item for CoA… Kovatsch Matthias
Re: [core] Do we need a CORE charter item for CoA… Rick Bullotta
Re: [core] Do we need a CORE charter item for CoA… Kovatsch Matthias
Re: [core] Do we need a CORE charter item for CoA… Rahman, Akbar
Re: [core] Do we need a CORE charter item for CoA… Alessandro Bassi
Re: [core] Do we need a CORE charter item for CoA… Zach Shelby
Re: [core] Do we need a CORE charter item for CoA… Carsten Bormann
Re: [core] Do we need a CORE charter item for CoA… Dijk, Esko
Re: [core] Do we need a CORE charter item for CoA… Dijk, Esko
[core] Reminder for chair review of draft-ietf-co… Rahman, Akbar