[net2-wg] net2 review of collection TEPs

[Omprakash Gnawali]

Should we make the user of collection specify AM id's rather than this
being a hard-coded? Making this change would significantly change the
way applications use collection.

- om_p

On Thu, Apr 17, 2008 at 2:28 PM, Philip Levis <pal at cs.stanford.edu> wrote:
>
>
>  On Apr 17, 2008, at 1:27 PM, Romain Thouvenin wrote:
>
> > On Thu, Apr 17, 2008 at 2:43 AM, Omprakash Gnawali <gnawali at usc.edu>
> wrote:
> >
> > > We have gotten enough experience with collection TEP that we should
> > > start standardizing it. We will do it in two steps:
> > >
> > > Step 1 - The interface (TEP 119)
> > >
> > > Step 2 - The protocols (TEP 123 and 124)
> > >
> > > Could folks take a look at TEP 119 and either make changes or suggest
> > > changes by this Friday? I would like us to submit the TEP to a
> > > shepherd soon.
> > >
> > > If someone has an idea on who would be good shepherds for these TEPs,
> > > please send your suggestion as well. Someone who has some experience
> > > designing, using, collection would be preferable, but someone who has
> > > general experience with sensor network protocols and applications
> > > would work as well.
> > >
> > > Thanks.
> > >
> > > - om_p
> > >
> >
> > Hello,
> >
> > As this TEP includes interface description, I would have expected a
> > bit more details about the two given interfaces: RootControl and
> > UnicastNameFreeRouting.
> >
> > For RootControl, since set and unset returns error_t, what are the
> > different values that one can reasonably expect? Is there non-obvious
> > cases when the call would [not] be a success?
> > For UnicastNameFreeRouting, I don't see a description of its semantics.
> >
> > I would also like to point out a double "the" in third paragraph of
> section 2.
> >
> > My two cents.
> >
>
>  These are great comments. Often, when going up for review, TEPs differ a
> bit from their code because the implementation has evolved a lot. And
> sometimes it requires a clean read from a new person to realize this. :)
>
>  Phil
>
>  Phil
>