[Tinyos-devel] Fwd: Request for Comments: TEP 123 - Collection Tree Protocol

[Andreas Köpke]

I could imagine one application: if we want to make the duty cycle dependent 
on the hop count to the destination. 
But that might be a bit artificial.
Best, Andreas

Omprakash Gnawali wrote:
> One of the discussions we had was if we wanted a hop-count field in
> the frames. We decided not to include it because we could not a
> compelling reason to include it. If people have an opinion on this
> one, it would be good to hear. Without a good X in "I could not do X
> without hop count in the frames and I need to do X in my application",
> it does not make sense to include hop count.
>
> - om_p
>
> On Mon, Dec 8, 2008 at 11:40 AM, Jonathan Hui <jwhui at cs.berkeley.edu> wrote:
> > TinyOS Developers,
> >
> > I have been asked to shepherd TEP 123 (The Collection Tree Protocol).
> > As the title suggests, TEP 123 documents the Collection Tree Protocol
> > (CTP), which provides a best-effort anycast datagram communication
> > service to one or more root nodes.
> >
> > Getting feedback from TinyOS developers is an essential part of the
> > TEP process. If you have any comments or suggestions for improving TEP
> > 123, please email them to me (or the list) by Tuesday, December 23rd,
> > 2008. After the review period, I will work with the authors to ensure
> > that each of the comments are addressed before TEP 123 is finalized.
> >
> > The current draft of TEP 123 can be found at:
> > http://tinyos.cvs.sourceforge.net/viewvc/tinyos/tinyos-2.x/doc/txt/tep123
> >.txt?revision=1.13&view=markup
> >
> > --
> > Jonathan Hui
> > _______________________________________________
> > Tinyos-devel mailing list
> > Tinyos-devel at millennium.berkeley.edu
> > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel
>
> _______________________________________________
> Tinyos-devel mailing list
> Tinyos-devel at millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel